SYSTIMAX Solutions. CCTV Over IP. Design and Implementation Document CommScope/ AXIS Validated Design. December

Transcription

1 SYSTIMAX Solutions CCTV Over IP Design and Implementation Document CommScope/ AXIS Validated Design December

2 Contents Chapter 1 Executive Summary 2 Chapter 2 AXIS Solution Architecture Overview CCTV System CCTV Applications 7 Chapter 3 Physical Layer Design Ethernet/IP Network 8 Chapter 4 Integration with ipatch Disclaimer of Liability Introduction Pre-requisites ipatch ftp Server Setup Camera Setup Assign IP address for the camera Enable telnet Enable anonymous viewer login Camera event notification setup ipatch Event Notification Setup Verifying the integration Troubleshooting 30 Annex A

3 This design and implementation document represents a collaborative development effort between CommScope and AXIS Communications. It is in addition to design and installation guidelines from CommScope SYSTIMAX documents and AXIS Communications documents. CommScope 1100 CommScope Place SE Hickory, North Carolina AXIS Communications Emdalavägen 14 SE Lund Sweden CommScope/AXIS Validated Design The CommScope/AXIS Validated Design consists of systems and solutions designed, tested, and documented to facilitate faster, more reliable, and more predictable customer deployments. THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE. USERS ARE SOLELY RESPONSIBLE FOR THEIR APPLICATION OF THE DESIGNS. THE DESIGNS DO NOT CONSTITUTE THE TECHNICAL OR OTHER PROFESSIONAL ADVICE OF COMMSCOPE AND AXIS, THEIR SUPPLIERS OR PARTNERS. USERS SHOULD CONSULT THEIR OWN TECHNICAL ADVISORS BEFORE IMPLEMENTING THE DESIGNS. RESULTS MAY VARY DEPENDING ON FACTORS NOT TESTED BY COMMSCOPE AND AXIS. 1

4 Chapter 1 - Executive Summary This Design and Implementation Document (DID) represents a collaborative effort between CommScope and AXIS Communications in support of the CommScope-AXIS relationship. The intent of this document is to provide guidance to the respective sales and technical organizations of each party in the relationship for the design and implementation of an AXIS IP/Network camera system running over CommScope Intelligent Building Infrastructure Solutions (IBIS). This document can also be provided to the business and channel partners of both parties. CommScope IBIS is a modular, flexible cabling infrastructure system that supports voice, data, video and building automation systems (BAS) by providing a robust and cost effective connectivity for all of a building s BAS and communication systems. IBIS utilizes twisted pair and/or fiber optic cabling to provide connectivity in an open architecture environment. In addition, combining CommScope IBIS with CommScope ipatch Intelligent Infrastructure Solution provides the user with control of the physical infrastructure. CommScope IBIS and ipatch can support traditional analog CCTV systems or the newer IP/ Network camera system over Ethernet networks using various CommScope Solutions. These solutions support cabling for the installation of AXIS IP network camera technology. The purpose of this document is to help customers identify and implement these solutions. There are several standards that describe how BAS can be designed and implemented over structured cabling systems. The standards that supplement this DID are: 1. ANSI/TIA-862 Building Automation Cabling Standard. This standard specifies a generic cabling system for BAS used in commercial buildings that will support a multi-vendor environment. The purpose of this standard is to enable the planning and installation of a structured cabling system for BAS applications used in new or renovated commercial premises. It establishes performance, topology and technical criteria for various cabling system configurations for connecting BAS equipment and devices. It also provides information that may be used for the design of commercial BAS products. 2. ISO/IEC IS Generic Cabling for Homes. This standard specifies a generic cabling system for applications used in homes and multi-dwelling units. It includes support for CCCB (commands, controls and communications in buildings) applications which encompass lighting controls, building controls, security and fire alarms. 3. CENELEC EN Generic Cabling Systems Part 4: Homes. This standard specifies a generic cabling system for applications used in homes and multi-dwelling units. It is very similar to ISO/IEC IS

5 Chapter 2 - AXIS Solution Architecture 2.1 Overview Every building has to meet several basic requirements such as security, fire-life-safety, ventilation, lighting, health and comfort. Security comes from the need to protect property, content and personnel. Examples of security requirements are identification of vehicles entering and exiting a car park, controlling access to sensitive or secured areas, and precautions against terrorist bomb threats, robberies and burglaries. Security has become a global hot issue in the aftermath of September 11 terrorist attacks. The functions implemented by security systems include the following: Surveillance Detection Alarms Access control Elevator control Master clock control Communication and information management Several of these functions are usually integrated with those of other systems. For example, in case of a fire, all doors must be unlocked. Surveillance and access control are two of the main applications for security, with CCTV (closed circuit TV) as the main function for surveillance. 3

6 2.2 CCTV System Video surveillance systems have existed for some 25 years, starting out as 100% analog systems and gradually migrating to digital. As the name implies, CCTV is a system in which the circuit is closed and all the elements are connected directly. Its name was derived to differentiate the technology from broadcast television which was meant to be an entertainment medium and where any receiver that is correctly tuned can pick up the signal from the airwaves. CCTV can be divided into two main categories: analog and digital systems. An analog CCTV system using a video cassette recorder (VCR) represents a fully analog system consisting of analog cameras with coax output, connected to the VCR for recording. The VCR uses the same type of cassettes as a home VCR. The video is not compressed, and if recording at full frame rate, one tape lasts a maximum of 8 hours. In larger systems, a switcher/multiplexer can be connected in between the camera and the VCR. The switcher/ multiplexer makes it possible to record several cameras to one VCR, but at the cost of a lower frame rate. To monitor the video, an analog monitor is used. See Figure 1. An analog CCTV system using a digital video recorder (DVR) is an analog system with digital recording. In a DVR, the videotape is replaced with hard drives for the video recording, which requires the video to be digitized and compressed in order to store as many day s worth of video as possible. In some systems, the DVR can be connected to a LAN. In a hybrid CCTV system (see Figure 2), the analog cameras are connected to an IP network using video encoders (sometimes referred to as video servers). A video encoder digitizes and compresses the video. The video encoder then connects to an IP network and transports the video via a network Ethernet switch to a PC with video management software, a NAS (Network Attached Storage) device or a SAN (Storage Area Network) where it is stored on hard disks. A hybrid system offers the following advantages: Use of IP network and PC server hardware for video recording and management The system is scalable in steps of one camera at a time Off-site recording is possible Investment protection since existing analog cameras can still be used The system can easily be expanded by incorporating network cameras or upgraded to a true IP system 4

7 A digital CCTV system uses IP or Network cameras to connect to a LAN. These IP cameras are plug and play devices as far as the network is concerned and are easy to integrate into corporate LANs or WANs. See Figure 3. An IP/Network camera takes the video, compresses it and sends it over the LAN to a PC with video management software, and stores the video on a NAS device or a SAN. An IP camera is always streaming video across the network, and therefore, is always using bandwidth. Hence a separate or segmented LAN is recommended to avoid bottleneck issues on the main corporate network. However, some IP cameras now incorporate both storage and DVR functions and this helps to limit some of the bandwidth impact. The connection to the LAN is via 10/100/1000 Mb/s Ethernet. In addition, many of these IP cameras are IEEE 802.3af compliant, i.e. they are Power-over-Ethernet (PoE) enabled. By connecting them to PoE switches, additional saving can be obtained by eliminating the need for mains electrical sockets and mains cabling. A digital CCTV system using IP cameras offers the following additional advantages: High resolution cameras (megapixel) Consistent image quality Power-over-Ethernet and wireless functionality Pan/tilt/zoom, audio, digital inputs and outputs over IP along with video Full flexibility and scalability Figure 1: Traditional analog CCTV system Analog Cameras Coax cables Video multiplexer/switcher Coax cables Video recorder Monitor 5

8 Figure 2: Hybrid CCTV system Administrator PC Video Encoders Analog cameras Ethernet Switch Coax cables Outlet NAS/SAN Patch Panel Cable Cord Coax cables Coax cables Figure 3: Digital CCTV system Administrator PC PoE enabled Ethernet Switch Outlet IP Cameras NAS/SAN Patch Panel Cable Cord AXIS is the global market leader in network video. AXIS specializes in professional network video solutions for security surveillance and remote monitoring. The range of products includes network cameras, video encoders/servers, video decoders, video management software, and a full range of accessories.

9 2.3 CCTV Applications The most widely known use of CCTV is in security systems. Security guards use CCTV to watch over doors or other points of entry to a building or to observe areas that are vulnerable to break-in or vandalism. The true scope for CCTV applications is almost unlimited. Some other examples are listed below: Traffic monitoring Crime, crowd and vandalism control Production process control Aerial photography The main vertical markets are: Education: Security and remote monitoring of school playground areas, hallways and classrooms Transportation: Remote monitoring of railway stations and tracks, parking lots and garages, highways and airports Financial (Banking): Traditional security applications in high street banks, branch offices and ATM locations Government: For surveillance purposes, to provide safe and secure public environments Retail: For security and remote monitoring purposes to make store management easier and more efficient Industrial: Monitoring manufacturing processes, logistic systems, warehouses and stock control systems Audio can easily be integrated into network video as the network can carry any type of data, which reduces the need for extra cabling - as opposed to analog systems where an audio cable must be installed from endpoint to endpoint. A network camera captures audio at the camera, integrating it into the video stream, and then sending it back for monitoring and/or recording over the network. This makes it possible to use audio from remote locations. For instance, monitoring personnel at a company s headquarters can interact with surveillance scenes at remote branch offices. They can inform possible perpetrators that they are under surveillance and listen in on situations using the audio as an additional confirmation method. Audio can also be used in network cameras or video servers as an independent detection method, which triggers video recordings and alarms when audio levels above a certain threshold are detected. When using Axis network cameras, there are several audio modes to choose from: Simplex mode: Audio is sent by the operator to the camera or Audio is sent to the operator by the camera Half Duplex mode: Audio is sent to and from the operator; only one party at a time can send Full Duplex mode: Audio is sent to and from the operator simultaneously A unique feature of network video products, is their integrated digital inputs and outputs that are manageable over the network. These I/Os can be used in conjunction with alarm sensors such as door relay/contact, passive infrared detector (PIR), glass break detector, siren, and alarm/intrusion system. These days, lots of video is being recorded but not properly analyzed due to lack of time. This has led to the development of Intelligent Video (IV) applications. New IV systems are now being developed for taking video data of number plates and digitizing the plate for cross checking with a database. People counting and trip wire are other examples of IV applications. Intelligent Video is about turning raw video data into actionable information. Provision of intelligence through surveillance will therefore support potential quality decision-making in time critical situations. 7

10 Chapter 3 - Physical Layer Design 3.1 Ethernet/IP Network Ethernet/IP network devices are capable of transmitting at 10 Mb/s, 100 Mb/s, 1000 Mb/s and Mb/s rates. This section focuses on Ethernet/IP connectivity guidelines using CommScope twisted pair and fiber solutions. Table 1 provides the distances supported by CommScope twisted pair solutions for various Ethernet/IP LANs. Table 1: Maximum supported channel distances using CommScope PowerSUM, GigaSPEED XL and GigaSPEED X10D solutions. Ethernet/IP LANs Maximum Distance in meters PowerSUM GigaSPEED XL GigaSPEED X10D 100BASE-TX 100 1, 96 2, , 115 2, , 115 2, BASE-T 100 1, 96 2, , 115 2, , 115 2, GBASE-T Not Supported Limited Support , 96 2, 92 3 Notes: 1 For 20 C 2 For 30 C 3 For 40 C 4 Mitigation procedures according to ISO/IEC TR and TIA TSB-155 may be required to ensure support Table 2 provides the distances supported by CommScope fiber solutions for various Ethernet/IP LANs. Table 2 provides the distances supported by CommScope fiber solutions for various Ethernet/IP LANs. Ethernet/IP LANs 850nm 1300nm Maximum Distance in meters a, b OptiSPEED MM LazrSPEED 150 LazrSPEED 300 LazrSPEED 550 TeraSPEED N/A N/A 1310nm 1300nm N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Notes: a Assumes the use of two LC connectors and zero splices. b Excludes connectors at the device end-points. 8

11 Figure 4 shows a typical network design and Table 3 provides the various solution components for the design. Figure 4: Typical Network Design for a Digital CCTV system Administrator PC PoE enabled Ethernet Switch OutleT t AXIS IP Cameras NAS/SAN Patch Panel Cable Cord Table 3: CommScope PowerSUM, GigaSPEED XL and GigaSPEED X10D solution components. Patch Panel Cable PowerSUM GigaSPEED XL GigaSPEED X10D 1100PSCAT5E PM2150PSE 1061 Nonplenum (U/UTP) 2061 Plenum (U/UTP) 3061 LSZH (U/UTP) 1100GS3 (U/UTP) PM-GS3 (U/UTP) VisiPatch (U/UTP) ipatch 1100GS3 (U/UTP) ipatch M4200i (U/UTP & F/UTP) 1071 Nonplenum (U/UTP) 2071 Plenum (U/UTP) 3071 LSZH (U/UTP) 1100GS5 (U/UTP) PM-GS5 (U/UTP) M2000/M3000 (U/UTP) VisiPatch 360 (U/UTP) M3200 (F/UTP) ipatch 1100GS5 (U/UTP) ipatch M4200i (U/UTP & F/UTP) 1091 Nonplenum (U/UTP) 2091 Plenum (U/UTP) 3091 LSZH (U/UTP) 1291 Nonplenum (F/UTP) 2291 Plenum (F/UTP) 3291 LSZH (F/UTP) Outlet MPS100E (U/UTP) MGS400 (U/UTP) MGS600 (U/UTP) MFP520 (F/UTP) Cords DP8S (U/UTP) GS8E Nonplenum (U/UTP) GS8E-SND Nonplenum (U/UTP) GS8E-SPD Plenum (U/UTP) GS8H LSZH (U/UTP) GS8E-SLD LSZH (U/UTP) GS10E Nonplenum (U/UTP) GS10E-P Plenum (U/UTP) GS10E-L LSZH (U/UTP) G10FP Nonplenum (F/UTP) G10FP-L LSZH (F/UTP) 9

12 Chapter 4 - Integration with ipatch This chapter describes an example of a procedure for integrating an AXIS-IP Camera with ipatch System Manager. 4.1 Disclaimer of Liability The content of the ipatch System Manager Integration Examples are furnished for informational use only for the convenience of users and customers of CommScope ipatch products. It should not be construed as a binding commitment by CommScope Inc. of North Carolina or any of its affiliates (collectively, CommScope ). Your use of the CommScope ipatch products and your relationship with CommScope in connection therewith is set out in your respective end user licence agreement, BusinessPartner Agreement and/or in the Terms and Conditions for the use of the InSite web portal with CommScope. THE IPATCH SYSTEM MANAGER INTEGRATION EXAMPLES DO NOT FORM PART OF SUCH AGREEMENT AND CREATE NO LEGALLY BINDING OBLIGATIONS OR LIABILITY ON THE PART OF COMMSCOPE. Whilst every care has been taken by CommScope in the preparation of the ipatch System Manager Integration Examples, CommScope does not guarantee the accuracy or veracity of any information or opinion, or the appropriateness, suitability or applicability of any practice or procedure contained herein. CommScope accordingly assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content in the ipatch System Manager Integration Examples and all use by you of the ipatch System Manager Integration Examples and/or the content in the ipatch System Manager Integration Examples, including the integration samples, sample scripts and software settings contained herein, is at your own risk. Your use of any third party products ( non-commscope products ) which are referenced in the ipatchsystem Manager Integration Examples is at your own risk. CommScope provides the information in the ipatch System Manager Integration Examples relating to non-commscope products merely as a convenience for customers and users of CommScope products who also use the relevant non-commscope products and CommScope is not liable for any damages or injury arising from the use of such non-commscope products. Any information contained herein relating to non-commscope products should be confirmed with the relevant manufacturer or supplier of the respective non-commscope product. The fact that CommScope makes reference to any particular non-commscope product in the ipatch System Manager Integration Examples does not mean that CommScope endorses, authorises or sponsors that product, nor does it mean that CommScope is affiliated with the relevant manufacturer or supplier of the non-commscope product, nor does it mean that CommScope is warranting that the non-commscope product will work in combination with CommScope products. Information in the ipatch System Manager Integration Examples concerning non-commscope products has been obtained from the relevant suppliers and/or manufacturers of those products and/or their published announcements and/or other publicly available sources. CommScope has not tested any non-commscope products and cannot confirm the accuracy or reliability of their performance and/or any other claims related to those products. Questions about the capabilities of non-commscope products referenced in the ipatch System Manager Integration Examples should be addressed directly to the relevant manufacturers and/or suppliers of those products. 10

13 Your use of any third party websites ( non-commscope websites ) which are referenced or linked in the ipatch System Manager Integration Examples is at your own risk. CommScope provides these links merely as a convenience and is not liable for any damages or injury arising from use of such websites. The fact that CommScope provides a reference or link to a non- CommScope website does not mean that CommScope endorses, authorises or sponsors that website, nor does it mean that CommScope is affiliated with the website, its owners or sponsors. The materials at such non-commscope websites are not part of the materials for the ipatch System Manager Integration Examples and the use of such materials and any products downloaded at such websites is at your own risk. The information provided in the ipatch System Manager Integration Examples is provided without warranty of any kind, including, without limitation, any warranties as to the interoperability or compatibility of the CommScope products with any non-commscope products referenced herein. CommScope makes no representations or warranties whatsoever in the ipatch System Manager Integration Examples regarding CommScope or non-commscope products and no warranty is provided for either the functionality or problem resolution of any product or combination of products. CommScope does not provide service or support in respect of the non-commscope products referenced herein. For support issues regarding non-commscope products, please contact the manufacturer/supplier of the non-commscope product directly. CommScope does not provide problem resolution services or ongoing support in respect of the ipatch System Manager Integration Examples. Where the ipatch System Manager Integration Examples provide information regarding use of any CommScope products in combination with any non-commscope software products, you areresponsible for ensuring that you have all necessary permissions, licences and/or consents relating to the use of non- CommScope and CommScope software products. This information in the ipatch System Manager Integration examples is of an illustrative nature only, and any reference to settings and codes may need to be amended and/or adapted as appropriate to meet your specific requirements. All trademarks and trade names relating to the CommScope products referred to in the ipatch System Manager Integration Examples are trademarks or registered trademarks of CommScope Inc. of North Carolina or its affiliates. Other trademarks and trade names may be used in this document to refer to non-commscope products or entities claiming the marks and names of non-commscope products. CommScope disclaims any proprietary interest in trademarks and trade names other than its own. 11

14 4.2 Introduction This type of application is typically found in data centers and large communication rooms. An AXIS IP camera is located in front of a rack directed at the ipatch Intelligent patch panels in the cabinet. The camera is set to continuously record. The camera uses a circular (first-in-firstout) buffer for storing images, so as the image buffer fills, the oldest images will be overwritten by the newest images. When an unscheduled (i.e. unauthorized) connection is removed from an ipatch intelligent patch panel, then an alert is generated by the Event Notification function in ipatch System Manager. A user-defined alert can be created in Event Notification to execute an external program ( snapshot.exe ) when the event occurs. The external program sends a trigger to the camera. The trigger received by the camera switches the camera from pre-event mode to post-event mode. When the camera mode is switched, the camera prepares a sequence of.jpg images from before and after the event. The combined images show the person before, during and after making the unscheduled disconnection. The camera then makes an ftp connection to ipatch System Manager, and sends the images to a directory on the ipatch System Manager server. See Annex A for snapshot.pl perl source code file. This file needs to be compiled into executable snapshot.exe file. 12

15 4.3 Pre-requisites An ftp daemon must be running on the ipatch System Manager server. The camera uses ftp protocol to transfer image files from camera to System Manager Server. In order for the files to be received, there must be an ftp server daemon running on the ipatch System Manager server. In this example, a freeware program (filezilla) is used to provide the ftp server function running on the ipatch System Manager server. This can be downloaded from the web. Note: it must be an ftp server (not client) 4.4 ipatch ftp Server Setup The IP camera uses ftp protocol to transfer the image files to the ipatch System Manager server. The ftp daemon must be running on the System Manager Server. In this example, a freeware program called FileZilla is used. It can be downloaded from the following website: Note: the FileZilla server is required. 13

16 When the ftp server is installed, an ftp userid must be created (userid = camera, password = camera). This is the userid which the camera uses to logon to the ipatch System Manager and transfer the files The user must have a home directory on the ipatch System Manager Server, and also must have permission to store files at this directory. A home directory must also be created for this user. The home directory is: C:\Program Files\SYSTIMAX Solutions\iPatch System Manager\Web Server\English\ AXISsnapshots Note: This directory must be manually created first, and then assigned as the home directory for the camera user First create the AXISsnapshots directory. Then create the uploads directory. 14

17 Then start the ftp server. A userid must be created in the ftp server. This is the userid which the camera uses in order to login to the ftp server, and transfer the files. In the example below, the user is camera. The password is camera The user s home directory is C:\Program Files\SYSTIMAX Solutions\iPatch System Manager\Web Server\English\ AXISsnapshots Note: the user must have correct permissions for this directory. In this example all permissions (read/write/delete/append) are granted to the user. 15

18 4.5 Camera Setup Assign IP address for the camera The camera should be assigned an IP address in the same LAN as the ipatch System Manager Server. To assign an IP address to the camera, use the provided program (IPutility) For this integration it is assumed that the root password is set as below. User: root Password: public Enable telnet To enable telnet, Open a browser, with the IP address for the camera e.g. Then click on Setup 16

19 Then click on System Options Then click on Advanced Then click on Scripting and Open Script Editor 17

20 Then click on.. (dot dot this changes to the root / directory) Then click on etc 18

21 Then click on inittab This opens a text editor (with the file /etc/inittab). To enable the telnet server, locate the following line: #tnet:35.once:/usr/sbin/telnetd If there s a # mark at the beginning of this line (as above), then remove it. The line should look like this: tnet:35.once:/usr/sbin/telnetd Click on Save File. Note: The camera must be restarted for this change to take effect. 19

22 4.5.3 Enable anonymous viewer login Click Setup User Settings Enable anonymous viewer login (no user name or password required) Enable this feature (select the tick-box) And click Save Camera event notification setup The AXIS camera has an Event Notification feature which can automatically transfer a sequence of images to an ftp server (ie the ipatch System Manager server). The transfer of images is triggered by an external program (called: snapshot.exe) which runs on the System Manager server. When the snapshot.exe program is executed on the System Manager server, it makes a tcp/ip connection on port 80 to the camera. It then sends a trigger to the camera s Event Notification function. As soon as the trigger is received by the camera s Event Notification function, the images are transferred using ftp protocol to the ipatch System Manager server. 1. Define a new ftp server on the camera Open a browser, and connect to camera (in this example the camera has IP address ) 20

23 Click Setup Click Event Config Click Event Servers Click Add FTP 21

24 Enter the following details: Name: ipatchsmserver Network Address: IP address of ipatch System Manager server Upload path: uploads Port number: 21 User Name: camera Password: camera Then click the Test button You should see confirmation from the camera that the ftp connection is working. Look in the uploads directory on the ipatch System Manager server and verify that a file called test has been created. C:\Program Files\SYSTIMAX Solutions\iPatch System Manager\Web Server\English\ AXISsnapshots\uploads 22

25 The Event Server (called ipatchsmserver ) should look like this Click Event Types Click Add triggered Enter the following information: 1) Name: ipatchevent 2) Priority: Normal 3) Respond to Trigger: Always 4) Triggered by... Manual trigger 5) When Triggered... Upload images 6) Select upload type: tp 7) Include pre-trigger buffer: 8 seconds 8) Image frequency (frames per second): 3 9) Upload for: 8 seconds 10) Add date/time suffix (select this) Click OK 23

26 The created Event Type should look like this 24

27 4.6 ipatch Event Notification Setup Define Event Profile Add a new Notification Profile Select event to monitor (in this case, Unscheduled Connection Removed) 25

28 Select location Select Execute Program Enter: C:\Niall\perlprogs\axis\snapshot.exe Note: 1) Use the Browse button to select the executable program snapshot.exe 2) Specify the IP address of the camera (in this example the IP address of the camera is: ) 26

29 Stop Event Notification process. Change the registry setting. The default is msec (i.e. 20 seconds). This can be reduced to 1000 msec (i.e. 1 second) Start the Event Notification process 27

30 4.7 Verifying the integration Make an unscheduled disconnection. There should be a popup window from ipatch System Manager to notify that an unscheduled disconnection has been detected. 28

31 Browse to the uploads directory on the System Manager server: C:\Program Files\SYSTIMAX Solutions\iPatch System Manager\Web Server\English\ AXISsnapshots\uploads The images should be transferred to this directory. Note: There is a time delay from the time of the unscheduled disconnection until the images are transferred (typically around 10 seconds, but this will depend on the system configuration). A number of pre-event and post-images are uploaded. The images are in.jpg format, and can be viewed with Windows Picture and Fax Viewer as below. 29

32 4.8 Troubleshooting 1. Verify that the unscheduled disconnection event occurred 2. Check that the popup appears when the event occurs 3. Check that the Unscheduled Connection Removed event appears in System Manager 4. Check that the ftp server is running on ipatch System Manager machine (note: the FileZilla icon in the taskbar changes from red to green when files are being transferred from camera to ipatch System Manager) 30

33 5. Check that ftp login and connection are working on the ipatch System Manager server Open a DOS-window, and use ftp login: camera password: camera ftp> dir (you should see the uploads directory, this is the home directory for the userid: camera) 6. Check that ipatch Event Notification profile is executing the external program ( snapshot.exe ) Browse to the uploads directory on the System Manager server: C:\Program Files\SYSTIMAX Solutions\iPatch System Manager\Web Server\English\ AXISsnapshots\uploads 31

34 Two files should be automatically created every time the event occurs. ipatchunscheduleddisconnectevent snapshot.log The first file (ipatchunscheduleddisconnectevent) is a timestamp file. It is created automatically as soon as the unscheduled disconnect event occurs. The second file (snapshot.log) is a log file. The log file contains information about the event, and error messages if any errors occurred. 32

35 Annex A Script file: snapshot.pl if ((!$ARGV[0]) or (!$ARGV[1])) { print \n\nusage: snapshot [camera ip-address] [system manager ip-address]\n\n ; exit (-1); } $cameraip = $ARGV[0]; $ipatchip = $ARGV[1]; print /usr/html/local/scripts/camerasnap $ARGV[1] ; use Net::Telnet (); $t = new Net::Telnet(Timeout => 30); $t->open($cameraip); $t->login( root, public = $t->cmd( /usr/html/local/scripts/camerasnap $ARGV[1] ); 33

36 Visit our Web site or contact your local CommScope representative for more information CommScope, Inc. All rights reserved. All trademarks identified by or are registered trademarks or trademarks, respectively, of CommScope, Inc. This document is for planning purposes only and is not intended to modify or supplement any specifications or warranties relating to CommScope products or services. MI /11