Montgomery Technology, Inc. Operator Manual. MTI HinleyViewer Surveillance Viewing Application. Rev. 1.0

Transcription

1 Montgomery Technology, Inc. Operator Manual MTI HinleyViewer Surveillance Viewing Application 16

2 Table of Contents Chapter 01: Overview... 4 System Architecture... 4 Optimal Hardware Requirements... 4 Category... 5 Products... 5 Details... 5 Chapter 02: Installing the MTI HinleyViewer application... 7 Prerequisites... 7 Installation... 7 Chapter 03: Initial Configuration... 9 Chapter 04: User Management Editing User Information Chapter 05: Media System Management Media Systems Explained Managing Media Systems Editing a Media System Chapter 06: Discovering Devices Step #1 Provide an IP Range Step #2 Select a System Type Step #3 Discovering the Devices Chapter 07: Media Map Management Managing Media Maps Editing a Control Point Chapter 08: Managing Viewers Editing a Media Viewer Chapter 09: Helper Tools The Media Map Builder Tool Installing the Media Map Builder Tool

3 Using the Media Map Builder Tool The Pelco Discovery Tool Installing the Pelco Discovery Tool Using the Pelco Discovery Tool The DigitalSentry (DS) Map Builder Tool Installing the DSMapBuilder Tool Using the DSMapBuilder Tool Chapter 10: Viewing Device Streams Viewing Options and Behavior Chapter 11: Special Features Remote Viewing through Firefox Mobile Access Chapter 12: Verified Manufacturers and Brand Nuances

4 Chapter 01: Overview With the full adoption of IP-based video surveillance systems, new standards have been developed which allow for significant integration between these surveillance systems and control systems. MTI has recognized the value of these new standards and has developed the MTI HinleyViewer application to take full advantage of them. HinleyViewer implements the ONVIF Profile S standard and the RTSP standard to integrate with video surveillance systems which implement these standards. In brief, ONVIF Profile S provides an Application Programming Interface (API) which allows client applications to discover, configure, and control compliant devices. This means that any client implementing this standard can detect these devices on a network, locate and access the video and audio streams provided by the device, and also control the pan, tilt and zoom of the device (if available). The application also implements RTSP for pulling video streams. This protocol can be used to access IP-based surveillance systems, even those that do not implement the ONVIF standard. System Architecture HinleyViewer is a browser-based web application with a web service API interface for integration. The application is designed around the Microsoft.Net Framework version and Internet Information Services 7+. The application can utilize a wide range of databases, including Microsoft SQL Server, Microsoft Access, or Sqlite. The preferred database for the application is Sqlite due to its portability. All examples given within this manual will be based on the assumption that the Sqlite database is used. The HinleyViewer application utilizes the VLC media player plugin for displaying video and audio from camera streams. This player is an open-source project that is available at The application also utilizes the FFMpeg media streamer for converting video streams for cross-domain viewing. FFMpeg is also an open-source project and is available at Optimal Hardware Requirements MTI provides its hardware and software with an understanding that certain hardware requirements have been met. MTI does not provide a list of minimum hardware requirements because we do not wish to communicate that there is a minimum amount of cost and work that must be provided. We, therefore, provide a list of optimal hardware requirements which are the specifications of the hardware that we provide for computers, networking, and wiring when the project calls for us to do so. Any compromises that fall below these requirements will cause MTI to be unable to warranty the performance and reliability of the system and will make the support of the system very difficult. The hardware provided for a project may certainly exceed these requirements, but it should never go below these requirements. 4

5 Category Products Details Networking Network Switches Network Wiring Network cabling should be CAT6 and should be certified to EIA/TIA 568A standards. Where fiber optics is used, either multi-mode or singlemode may be used, depending on distance and manufacturer recommendations. Fiber optics should be certified to EIA/TIA method B standards. The MTI system is certified to operate using HP ProCurve switches. Although other Managed switches may be used, this brand have been verified to work with the MTI system and to provide the performance requirements for the system. Unmanaged switches may be used on the edge of the network, but these switches should provide at least 32 KB of memory per port. User Interface Computers Computer hardware should meet the following optimal requirements o CPU: Intel i5 2.8 GHz o 667 MHz Memory Speed o 4 GB SDRAM o 80 GB Hard-Drive o 10/100 Network Interface Card o A Microsoft Windowsbased operating system running Microsoft.Net Framework (Windows 7, 8, and later are all supported). MTI supplies HP computers for all projects. These computers are preconfigured to meet 5

6 system requirements. Note that the displaying of digital video, especially highresolution video, requires considerable resources from the graphics card of the computer. MTI highly recommends the use of a graphics card with at least 2 GB of dedicated memory. Web Application Server Server Hardware should meet the following optimal requirements: o CPU: Intel Xeon Quad- Core at 2.8 GHz o 8 GB of RAM o RAID-5 or 6 HDD configuration o A Microsoft Windows Server operating system running Microsoft.Net Framework or later. 6

7 Chapter 02: Installing the MTI HinleyViewer application The HinleyViewer application can be configured to run on a centralized server or on a local computer. For both, the setup is pretty much the same, although the prerequisites may vary slightly. The following instructions detail the prerequisites needed prior to installation and the steps to take in installing the application. Prerequisites Internet Information Services 7.0 or higher (install by going to Programs > Windows Features) Microsoft.Net or higher (download from Internet Explorer 11 or higher (perform Microsoft Updates until the application is installed). VLC Player or higher ( Installation 1. Download the latest version of HinleyViewer by going to logging into the MTI Customer Portal at Once there, go to Software and browse to the Servers folder. Download the HinleyViewer.zip file. 2. Extract the HinleyViewer.zip file to the C:\inetpub\wwwroot directory on the destination computer. The result of this extraction should be folder at C:\inetpub\wwwroot\HinleyViewer. Under this folder should be a bin folder and other application folders and files. 3. Open Internet Information Services Manager and browse to Application Pools. a. Select the.net 4.5 application pool. Be sure to select the Integrated app pool. Right click on this app pool and select the Advanced Settings option. b. Under the Advanced Settings dialog, ensure that Enable 32-bit Applications is set to True. 7

8 4. Apply these changes, then expand the Sites > Default Web Site tree item. a. Right-click on the HinleyViewer folder under the default site and select the Convert to Application menu item. In the Add Application dialog, click the Select button next to the Application Pool field and select the app pool that you modified in step 3b. 5. You should now be able to access HinleyViewer by going to from Internet Explorer. 6. On any workstation that will be using HinleyViewer, you should also install the VLC Media Player. This can be downloaded from the Config menu on HinleyViewer once it has been configured, or you can download it from 8

9 Chapter 03: Initial Configuration The HinleyViewer application is very flexible, primarily because it can be configured to run on many different database types and under many different hardware and software arrangements. To make it that flexible, the application must be configured to use a database, and it must be provided with the database s login information and location. When you first access HinleyViewer, the application will automatically direct you to the Hinley Configuration page. This page requires a certain set of information to properly configure the application. The Database Type field provides a number of options as to the type of database you may want to use for Hinley. The preferred and recommended database type is the Sqlite database. This is a very portable database that also provides a great deal of performance. Depending on the type of database you select, other fields may appear and be required. o If you select the SQL Server or ODBC database types, fields for Database Server, DB User and DB Password will also appear. For SQL Server, these values will be 9

10 the SQL Server instance name for the server you wish to use, as well as the DB username and password for accessing the database. The File Path field provides the file system path at which the database should be created. For a Sqlite database, we highly recommend that you create this at c:\mti. Note, this folder must exist before setting the configuration. The Database Name field specifies the name of the database (without extensions). If a Sqlite database is created under the C:\mti, the file will be located at c:\mti\hinley.sqlite. Currently, the Software License field does not provide any functionality and is not used. Click the Save button to commit the changes. Once you have saved the configuration, you can click on the MTI Hinley title at the top left of the menu bar to browse back to the home page. Once on the home page, you can click on the Enter button to the right hand side of the menu bar. For the first log in to the system, the application will create a new system administrator user based on the username and password you provide at this point. We recommend that this initial system administrator be system/system, but any username and password can be used. 10

11 Chapter 04: User Management The HinleyViewer application allows an administrator manage user access. Users can be created to access either the configuration options or viewing options, or both. To manage users, go to the Config > Users menu option after logging in as an administrative user. 11

12 This menu option will take you to the Hinley Users page, which provides a list of all current users on the system. From this list, you can edit any existing user by clicking on the record for the user. Or, you can create a new user by clicking on the Create button at the top of the table. Editing User Information Whether you are creating a new user or editing an existing one, the Edit Hinley User page allows you to set all of the values related to a user. 12

13 The Full Name field specifies the name of the user, as he or she is known to others. The field specifies the address for the user. The Username field specifies the account name for this user that will be used to log into the system. The Password field specifies the password that will be used to log into the system. The Configuration permission checkbox designates that this user can have full access to all of the pages under the Config menu. The Viewing permission checkbox designates that this user can have full access to the Viewing menu. The Save button commits this information to the database. If this is a new user, this button creates a new record and saves the data. If this is an existing record, the action commits the new data to the existing record. Note that each user record is identifies by the Username field. Because of this, the Username field cannot be changed once it has been created. If you wish to change a username, you must first delete the user record and create a new one under the new username. 13

14 The Cancel button discards all changes and returns to the Hinley User list page. The Delete button permanently removes the user record from the database. 14

15 Chapter 05: Media System Management Media Systems Explained In the MTI Hinley system, a Media System is a unique brand or model of surveillance system which can be discovered and controlled using the ONVIF Profile S standard. MTI periodically adds new systems as default systems to new versions of the platform, but the absence of a media system does not mean that you cannot access it through HinleyViewer. Additionally, if you have the right settings, you can create a Media System definition and add it to your HinleyViewer setup to discover this type of system. Media Systems are defined by a portable XML file within the Hinley application. This means that you can create a new Media System definition, copy the resultant XML file to your file system and use it on any project from there on out. Managing Media Systems To access the media system list, go to Config > Systems. When you select this menu option, the Media Systems page will appear and will display a list of available Media Systems. 15

16 The Media Systems page presents a table of the currently saved media systems. These default systems supplied by MTI are located under the HinleyViewer\res\systems folder under the Internet Information Services root directory. The Path field in this table will display the file system folder at which the XML definition file is stored. To edit a specific Media System file, you can click on the row in the table for this system. Or, to add a new Media System, click the Create button at the top-left of the page. Editing an existing or new system will be explained in the next section. The Upload button at the top-left of the page allows you to add an existing Media System XML file to this instance of the application. To upload an XML file, click the Upload button. When you do, a dialog box will appear asking you to select the XML file. Click the Browse button and locate the file. Then click the Upload button to submit the file. 16

17 Editing a Media System Whether you are creating a new media system or editing an existing one, the Edit Media System page is used to provide the information needed for this. The System Name field designates the name that you want to use to identify the system. We recommend that this name be unique and include the manufacturer and model names. The Manager Address is not always used and may not be relevant to the system. For some systems, there is a central system manager that hosts information about the system. The IP address of this system manager is expected here. The Manager Protocol designates the HTTP protocol to be used when accessing the ONVIF services on the manager or on any device within this system. The options for this field are HTTP, which is unsecured but the most common protocol type, and HTTPS, which is secured using Secure Socket Layer protocol. This setting is dependent on the protocol used by the end device. As mentioned before, this is almost always going to be HTTP. 17

18 The Manager Port field designates the port at which the ONVIF service is available on each device. This is almost always going to be 80, unless the device is using HTTPS, in which case it will usually be 443. The Username field designates the username to be used to access the ONVIF service. On some systems, such as Pelco, this user is the same as the ones created within the Pelco system itself. On other systems, such as Axis, a separate, ONVIF-specific user must be created through the camera s web interface. The Password field designates the password to be used to access the ONVIF service. The Discovery Type field designates the method used by HinleyViewer to discover devices based on this Media System. The options for this field are as follows: o Manual A Manual discovery type means that Hinley will attempt to discover devices on your network manually, by polling each IP address within a range to check for the availability of the ONVIF services. o WS A WS discovery type means that Hinley will use the Web Service discovery standard to poll for ONVIF compliant devices. o UPNP A UPNP discovery type means that Hinley will use the Universal Plug and Play protocol to poll for devices and then check responsive devices for the ONVIF service. The Authentication Type field designates the type of authentication method Hinley will use when communicating with the ONVIF service on a device. The options are as follows: o WS A WS authentication type means that Hinley will use Web Service authentication ( nonced authentication) to access the service. o HTTP A HTTP authentication type means that Hinley will use both web service authentication and HTTP digest authentication to access the service. The Model Name field designates a specific model name that this system represents. This value does not have to be provided. If it is provided, Hinley will only discover devices that match this model name. The Manufacturer field designates a specific manufacturer name that this system represents. This value does not have to be provided. If it is provided, Hinley will only discover devices that match this manufacturer name. The URN/WS Types list designates the Universal Resource Numbers or Web Service Contract Types to filter devices by. If you are using the UPNP discovery type, then these values represent the URN types that you are looking for. Note, these values can be any part of the URN string. Typically, they are as simple as a name like Camera or Encoder. If you are using the WS discovery type, then these values represent the Web Service Contract Types to filter by. Again, this can be any part of the contract type name. With WS discovery, it is almost always the case that the contract type name is NetworkVideoTransmitter. What follows is a description of the fields and actions under this section: 18

19 o o To add a new WS or URN type, enter the name into the New URN Type field. Then click the Add button. If the value is not already in the Current URN List, the value will be added to the list and will appear there. To remove a value from the list, locate the value in the Current URN List field and select it. Then click the Remove button. The Profile Filters list designates the ONVIF Profile-S profiles that you wish to filter by when discovering a device. In ONVIF, a profile is a media configuration on the device that specifies the media compression method and resolution for the video. Profiles are identified by their tokens, which are unique names that are given to each profile. These profile tokens are model and manufacturer specific. You will need to understand the device and how it designates its ONVIF profiles to be able to filter profiles. To learn more about how these profiles are identified, you can start by creating a media system with no filters and then discovering the devices using that media system. Hinley will add all of the profiles on each device and you can then learn how the manufacturer identifies its profiles. To find out more about the Discovery process, see the chapter on this subject. What follows is a description of the fields and actions under this section: o To add a new profile filter, enter the token name for the profile into the New Profile Filter field and then click the Add button. If the profile token is not already in the Current Filter List field, it will be added. o To remove a profile filter from the list of current filters, locate the token in the Current Filter List field and select it. Once selected, click the Remove button to remove it from the list. The Save button commits the changes that you have made to the XML file. If you are editing an existing media system, the information you have changed will be committed to the existing XML file. If you are creating a new media system, the information will be used to create a new XML file. The Cancel button will discard all of your changes and return to the Media Systems page. The Delete button will remove the Media System and its corresponding XML file from the system. 19

20 Chapter 06: Discovering Devices The HinleyViewer application provides a feature known as Discovery, which you can use to discover devices on your network and add them to the HinleyViewer application for viewing. The discovery function will use the method you have designated in a media system (manual, WS, or UPNP) to search the network to discover devices. There are a couple of things worth noting about this function before we get into the specifics of how to use it: Note that this function depends on the viability and connectivity of your network. The devices that you are attempting to discover either need to be on the same IP subnet as the server that is hosting HinleyViewer or the device subnet must be routable from the server s subnet. Both the UPNP and WS discovery methods use UDP broadcast or multicast packets to discover devices. This means that you must have multicast and/or broadcast routing enabled on your network to discover devices using these methods. To discover devices using the discovery function, go to the Config > Discovery menu option. This will take you to the Discovery Wizard page. This page will provide you with a three-step wizard which will discover the devices on your network and add them to your Media Map (see chapter 07 for more information on Media Maps). 20

21 Step #1 Provide an IP Range The first step will ask you to provide an IP range for which to discover devices. This range is valid for media systems that use the UPNP or Manual discovery methods. For media systems that use the WS discovery method, this range does not matter. Note that you can change this range to be specific to the IP address range at which your devices are located. Once you have set the range for your devices, click the right arrow button at the bottom of the wizard to proceed to the next step. 21

22 Step #2 Select a System Type In the second step, you will need to do two things. First, you will need to select the type of system that you are discovering from the Media Systems drop-down box. This drop-down box contains all of the media systems that are known to the application. For more information on this, see chapter 05. Second, you will need to designate whether you want the discovered devices to be added to your existing Media Map or added to a brand new media map. For more information about media maps, see chapter 07. To add these devices to your existing media map, ensure that the Add To Current Media Map check box is checked. If you want to clear out the current media map and add these devices to a new map, then ensure that this checkbox is unchecked. Warning: if you leave this checkbox unchecked, any existing devices that have been added to your media map will be automatically removed. 22

23 Once you have set these two values, click the right arrow button at the bottom right of the wizard to progress to the next step. Step #3 Discovering the Devices In the third and final step, you can use the information you have already provided in the wizard to discover devices on your network. To begin the discovery process, click the Discover button. Once you do this, a progress bar will appear denoting that the discovery is in process. Once this progress bar goes away, the process has completed. Discovered devices will appear in the table below the Discover button. If no devices were discovered, check your connectivity to ensure that you can see these devices from the server (use the ping command to try it) and then click the Discover button again. Please note that the WS and UPNP protocols may take several attempts to completely discover all devices, so you may want to try two or three times. 23

24 Once you have discovered the devices, you can click the check button at the bottom right of the wizard to finish and go to the Media Map list. Or, you can use the back-arrow button to go back to previous steps and change values to discover more devices or different systems. 24

25 Chapter 07: Media Map Management In the MTI HinleyViewer application, a Media Map is a list of all of the media devices available to the application for viewing. This list allows Hinley to access the devices quickly without having to discover the available devices on the network every time. In the application, a Media Map contains Media Control Points. These Media Control Points are references to the individual ONVIF profiles on a device. So, it is possible for a single device, such as a video encoder or a panoramic camera, to have multiple media control points for the same device. A control point also designates the media streams available to the application, and the control functionality (pan-tilt-zoom) available. Managing Media Maps To manage the Hinley media map, click on the Config > Media Map menu option. When you do this, you will be directed to the Media Map page. 25

26 This page displays the current control points within the existing media map. Note that there is only one Media Map that is maintained for the application. All device control points are added to this media map. A media map is portable, though, from one HinleyViewer instance to another through the use of an XML file that the application creates, which represents the map. To edit an existing control point within the map, locate the control point in the table and click on the record. This will take you to the Edit Control Point page, which will be explained later. Additionally, if you click the Create button to add a new control point, you will be taken to this same page to edit the new control point. The Upload button allows you to upload an existing Media Map XML file. When you click this button, a dialog box will appear which will allow you to browse and select the XML file you wish to upload. Once you have selected the file, click the Upload button to submit the file. PLEASE NOTE that the application assumes that the uploaded file is the new media map to use and will remove all control points from the existing media map and add the control points from the XML file. The Download button allows you to download the existing media map to an XML file which you can save or use on another instance of HinleyViewer. When you click on this button, your browser will ask you what you want to do with the file. Choose to save the file to a known location that you can access. The Discover button will take you to the Discovery Wizard, which is explained in Chapter 06. The Update Profiles button will initiate a process which will go out and pole each existing control point in the media map to acquire its media stream URL and its control information. This action is useful when the initial media map does not contain the media stream URL or control information. This can often be the case if the integrator does not know of the profile specifics when he first generates the media map file. The Clear Map button will remove all of the existing control points from this media map. This action is useful if you wish to start over with your media map numbering. 26

27 Editing a Control Point To edit a control point within the media map, click on the record for that control point. Or, if you wish to add a new control point, click on the Create button. Both actions will take you to the Edit Media Control Point page. What follows is a description of each field and action on this page: The Identifier field is a unique integer value which represents this control point within the application. This value is also very important for interfacing with other applications, such as MTI s ProVision application. If you are editing an existing control point, you cannot change this value. If 27

28 you wish to reuse an identifier, you must delete the existing control point that is using this value and add it back as a new control point. When creating a new control point, you can designate any identifier you want it to have, as long as that identifier is not already used in the media map. The Device Address field designates the IP address of the device on which this control point resides. The Device Name is a user-friendly name which identifies this control point. This name can be anything you want it to be. This value will be presented to users who access the viewing module. The Profile Token field designates the ONVIF profile token for this control point. The Stream URL field designates the RTSP stream URL used to access the media for this control point. The Play Audio Stream? checkbox designates whether media pulled from this control point should include audio or not. If checked, the viewing module will modify the media URL so that the audio will be included in the presentation. The Username field designates the ONVIF username to use when accessing this control point. See Chapter 05 for an explanation of this functionality. The Password field designates the ONVIF password to use when accessing this control point. The Authentication Type dropdown designates the method used for authentication on the device. See Chapter 05 for an explanation of this functionality. The Load Profile button allows you to communicate with the device and acquire the profile information from it. When using this button, all you have to provide are values for the Device Address, Username, and Password, but you can also provide the Profile Token value. When you provide these values and then click this button, the application will pull the Media Stream URL, Pan Tilt Settings and Zoom Settings from the device. The Pan Tilt Settings and Zoom Settings sections provide fields that you can edit, but we advise against this. These fields should really only be populated by using the discovery process or by using the Load Profile button. These field values are device and manufacturer specific. The Save button commits the changes to the database. The Cancel button discards your changes and returns to the Media Map page. The Delete button removes the control point from the media map. 28

29 Chapter 08: Managing Viewers HinleyViewer allows you, as an administrator, to control the workstations that can view control points, the ways in which they can view them, and the control points that they can view. This is done by adding Viewers to the application. When you add a Viewer, this tells the application that access to the Viewing module is allowed from a workstation with the designated IP address, regardless of whether the user is logged in or not. Media Viewers can be managed by going to the Config > Viewers menu option. When you click on this menu option you will be taken to the Media Viewers page. To edit a viewer, you can click the record for the viewer to go to the Edit Media Viewer page. Or, to add a new viewer, click the Create button at the top of the table. 29

30 Editing a Media Viewer To edit an existing viewer, click on the record for that viewer in the table provided on the Media Viewers page. To create a new viewer, click on the Create button. With either action you will 30

31 be taken to the Edit Media Viewer page. This page provides the fields needed to define a Media Viewer in the system. What follows is an explanation of each field and action on this page: The Viewer Name field defines a user-friendly name for this viewer. The Viewer Address field defines the IP address from which requests for this viewer will come. NOTE: if you are planning to use the Viewing module without a login from the same computer on which you have HinleyViewer installed, you will need to add a Viewer with the IP address of This is the local IP address for the computer. Otherwise, if you are adding a computer that will be accessing the application from a different IP address, simply enter the IPv4 address for that computer. The Default View drop-down sets the default view mode for the viewer. This defines the number of views the user will see when he or she first starts the application on the Viewing module. The Allowed Views section allows you to add views which a user can access when in the Viewing module. To add a new view to the list, select the view from the New View dropdown. Or, if you wish to add all of the available views, select the All option. Then, click the Add button to add the view to the Current Allowed Views list. To remove a view from the list, select the view in the Current Allowed Views list and then click the Remove button. The Allowed Control Points section allows you to add control points which are available to this viewer. To add a group of control points, select the control points from the New Allowed Points list. Note that you can select multiple control points from this list by holding down the Ctrl key on the keyboard as you select. Or, if you wish to select a large group or all of the control points, select the top control point and then hold down the Shift key and select the last control point. Once you have selected all of the control points you wish to add, click the Add button to add then to the Current Allowed Points list. To remove a control point from the list, select that control point in the Current Allowed Points list and then click the Remove button. The Default Control Points section allows you to designate a set of control points as the default points that will load first when the viewer accesses the Viewing module. To add a control point as a default point, select the control point from the New Default Point dropdown and then click the Add button to add it to the Current Default Points list. To remove a control point from the list, select the point from the Current Default Points list and then click the Remove button. The Save button commits the changes that you have made to the database. The Cancel button discards the changes you have made and returns to the Media Viewers page. The Delete button permanently removes this record from the database. 31

32 Chapter 09: Helper Tools The HinleyViewer application ships with a number of useful tools which will help you to build a media map more quickly. These tools can also provide a way to build the media map for a system before the system is actually available for discovery. In this chapter we will explain each tool and how it can be used. All of the tools can be accessed by going to Config > Tools. Within this drop-down menu is listed all of the available tools. Since MTI uses Pelco video surveillance systems as our primary system for proofs of concept, most of the tools provided revolve around the Pelco systems. However, it is our intention to add other vendor-specific tools as the need arises. Any new tools will be added to this menu as they become available. The Media Map Builder Tool The Media Map Builder Tool is a generic tool that can be used to build a media map file for use with HinleyViewer. This tool is not dependent on any specific brand of surveillance system, and it can be used at any point in the project development to build a list of control points for the system. Installing the Media Map Builder Tool The Media Map Builder Tool comes with the installation for HinleyViewer. When you click on the link at Config > Tools > Media Map Builder, the web browser will ask you if you want to save a MediaMapBuilder.zip file. Choose to save this file to a known location. Then, browse to the file location and right-click on the file and choose Extract To from the context menu. Extract the file 32

33 contents to a folder on the local drive. After extracting the files, browse to this new location and double click on the MediaMapBuilder.exe file to run this tool. Using the Media Map Builder Tool The Media Map Builder is a single-form application which provides you with three actions and a table. To create a new media map file, click on the New button at the top of the form. This will clear the table below and make the file ready for your input. To open an existing media map file, click on the Open button at the top of the form. This action will present an Open File Dialog box which you can use to browse for an existing media map XML file. Once you have selected the media map file you wish to use, click the Open button the dialog and the contents of the file will be presented in the table. To save a media map to a file, click on the Save button at the top of the form. This action will present a Save File dialog box will allow you to save the media map as an XML file on the system. Once you have clicked the New button to create a new media map or clicked Open to edit an existing one, you can then begin adding control points. To do this, click on the first open record in the table. The fields provided are the basic values needed to create a media map. These fields are as follows: 33

34 ID This field corresponds to the Identifier field in HinleyViewer. This must be a unique integer value. Please note that this tool does not automatically increment your IDs, so you will need to keep up with the last ID value and ensure that all IDs are unique. Device Name A user-friendly name for the device. This value is what will be presented to users who utilize the Viewing module. IP Address The IP address of the device. Username The ONVIF username that should be used to access the device. Password The password for the ONVIF username. Authentication The Authentication Type to use when accessing the ONVIF services. The options are explained in Chapter 05. RTSP URL This value represents the RTSP stream URL for this control point. Note that this value is not necessarily needed at the point that the media map is created using this tool. The user can create a media map without this value and then use the Update Profiles action (see Chapter 07) once you export it to HinleyViewer. Once you have created the media map using the tool, save the file by clicking the Save button and choosing a file location. Now that you have saved the file, you can go to the HinleyViewer application, log in as an administrator, and go to Config > Media Map. In the Media Map page, select the Upload action and then browse and select the file that you have saved. Once the file is uploaded you should see your control points in the media map within HinleyViewer. Note that you will also need to click the Update Profiles button to discover the profile for each device if you have not provided an RTSP URL for each control point. Additionally, if you are using a device that has multiple inputs, such as an encoder, you may need to edit the control point and provide the Profile Token before running this action. The Pelco Discovery Tool The Pelco Discovery Tool can be used to discover configurations from a Pelco Endura system. The discovery tool will access an Endura System Manager and pull the current configuration from it. Installing the Pelco Discovery Tool To install PelcoDiscover, click on the Config > Tools > Pelco Discovery Tool to download a zip file containing the binaries. Once the ZIP file has downloaded, extract the file to a known location, like C:\PelcoDiscover. After extracting the files, browse to the extracted location and double-click on the PelcoDiscover.exe file to launch the application. 34

35 Using the Pelco Discovery Tool When you run PelcoDiscover, you see settings across the top that are required before the discovery can take place. The User and Password fields are the Pelco user credentials that you ll need to provide to access the System Manager. The System Manager Address field is the IP address of the System Manager from which you will need to pull the configuration. Once you have entered these values, click the Connect button to begin the discovery process. This process can take several seconds, so allow plenty of time (around 10 seconds) for it to complete. Once it has completed the table will populate with all of the devices that were discovered. Once you have discovered the devices, you can then save the resulting media map to an XML file that can be used in Hinley s media map (see chapter 07). To save the file, click on the Save XML button. This action will open a Save File dialog box which will allow you to save the file to a known location. You can then upload the file to HinleyViewer s Media Map to add the devices to your system. The DigitalSentry (DS) Map Builder Tool The DSMapBuilder Tool provides a convenient way of loading the configuration from a DigitalSentry system into a media map file for use within the HinleyViewer application. This tool can access the device.xml files that are made available when a DigitalSentry device has the Pelco API interface configured and running. Note that you will need to first install the Pelco Frame Server service 35

36 and Pelco API Service on the DigitalSentry DSSRV and also run and configure the Pelco API Config application before this tool will work. Installing the DSMapBuilder Tool To install the DSMapBuilder tool, click on the menu option at Config > Tools > DigitalSentry Map Builder within the HinleyViewer application. This will download a DSMapBuilder.zip file. Once you have downloaded this file, extract it to a known location such as C:\DSMapBuilder. When the extraction has completed, browse to the extracted folder and double click on the dsmapbuilder.exe file to launch the application. Using the DSMapBuilder Tool When the application runs, you will see three setting options and two actions. The first setting is the DS Device Addresses list. This is a text field that allows you to enter the IP address for each DigitalSentry DSSRV on the system. The Username and Password fields allow you to enter a Pelco user that can access all of the devices you have provided IP addresses for. Once you have provided the IP addresses and the user credentials, press the Load button to start the process of pulling the configuration from each device. When the process has finished, the Data table will be populated with all of the device information found on each of the devices. 36

37 Now that you have all of the device information, click the Save button to save this data as a media map XML file. When you click the Save button you can use the Save File dialog box to pick a file location to which the XML file will be saved. Once you have saved the media map XML file, you can go back to HinleyViewer and upload the media map file to the Media Map within the application (see chapter 07 for more information). 37

38 Chapter 10: Viewing Device Streams Now that you have the HinleyViewer fully configured, you can begin using the Viewing module from the computer on which Hinley is configured or from any other computer on the same network. noting: Before you begin viewing the video streams through HinleyViewer, there are a few things worth Viewing requires the installation of the VLC media player. HinleyViewer ships with a stand-alone installation of VLC which can be accessed by going to the Config > Tools > VLC Player, or you can download the latest version by going to Viewing capabilities and performance is greatly dependent on the quality of graphics card that the computer has. The Viewing only works with the following browsers: Internet Explorer version 10 and greater or Firefox. Viewing Options and Behavior To begin viewing video streams, select the Viewing menu. This menu will provide you with a list of available views. If you have logged in as a user which can access the Viewing module, then you will see all four possible views (Spot, 2-View, 4-View, and 6-View). If you are not logged in but are accessing the application from a computer that is configured as a Media Viewer (see chapter 08), then you will be presented with the number of views that have been configured for this viewer. Once you select the type of view you wish to access, the application will load this view and begin presenting the video for each stream associated with it. 38

39 The Viewing page presents a grid with each available video stream presented as a tile within that grid. If you select a Spot view, then you will see a single video stream. This video stream will take up the full page. If you select a 2-View, then you will see a single row of two video streams. These two video streams will share the full page size. If you select a 4-View, you will see two rows of two video streams each, with these four streams sharing the full page size. Finally, if you select a 6-View, you will see two rows of three video streams each, with these six streams sharing the full page size. One important thing to note is that the video will be displayed in the most relevant aspect ratio for the view mode you have selected, but the amount of the viewing window that the video takes up is primarily dependent on the resolution and aspect ratio at which the device is transmitting. For example, if you are viewing an analog camera that is transmitting at a 4:3 ratio in a Spot view on a computer monitor that is displaying at a high resolution on a 16:9 ratio, then there will be black borders around this video to make up for the difference between the camera s resolution and ratio and the monitor s resolution and ratio. Below each viewing tile is a drop-down box that allows the user to select the control point that he or she wishes to access for that tile. When the user selects a new control point from the drop-down box, the video stream for that tile changes to the stream for the selected control point. 39

40 If the tile is presenting a control point which supports PTZ control, six additional actions will be provided to the user to the right of the drop down box for that tile. They are as follows: The first action from the left is the action to zoom the PTZ device in. Depending on the responsiveness of the device, the action may take a few seconds to respond to your clicks. With this and any other action below, you can either click on the icon to send the command or you can click and hold to continue the command for a certain length of time. The second action is the action to zoom the PTZ device out. The third action is to pan the device to the left. The fourth action is to tilt the device up. The fifth action is to tilt the device down. The final action is to pan the device right. 40

41 Chapter 11: Special Features The HinleyViewer application provides a few special features that are important to know for expansion of the system and use in broader applications. Remote Viewing through Firefox The HinleyViewer application has a special feature that detects the browser being used and provides a special stream depending on the browser. In this case, if Internet Explorer is being used, then the application provides the streams through an embedded VLC media player. This method of access is useful for local computers which are directly tied to the same network as the application. It is preferred for this scenario because performance is much better. But, if you access the application through Firefox, HinleyViewer presents the video through a native HTTP stream. With this feature, HinleyViewer transcodes the video from its original stream into a routable, web-ready media stream. The benefit of this action means that the video can actually be viewed from anywhere, through any router or firewall, which greatly enhances remote viewing. However, with this feature, there are a few words of warning. First of all, because Hinley must transcode the streams, this action effectively doubles the demand on the hosting computer to do this. If you anticipate taking advantage of this feature, we recommend that you install HinleyViewer on a computer with considerable processor and memory resources (such as a quad core Intel Xeon processor with at least 8 GB or RAM). Secondly, because of the transcoding, there may be a slight delay in the video. This is greatly dependent on the strength of the computer on which HinleyViewer is running. Mobile Access One of the great added advantages that is available because of the previous feature mentioned is that viewing can be made available to any Android device through the use of Firefox on this device. A user who has an Android device with Firefox installed can use Firefox to access HinleyViewer remotely. When he or she does, the video streams are presented in the same way as mentioned above. 41

42 Chapter 12: Verified Manufacturers and Brand Nuances One very important thing to know when using HinleyViewer is that not all manufacturers fully or equally implement the ONVIF standard. MTI has verified the capabilities of our application and the manufacturer s behavior for popular brands, but there are nuances with each manufacturer that are important to know. It is our intention to maintain the following list as a knowledge base about these nuances. The following table provides a list of all device manufacturers and models that have been verified to work with Hinley and any nuances for each. Manufacturer System Details Pelco Endura Cameras, such as the Sarix line, and Encoders such as the NET55xx have been verified to work with Hinley. Authentication: HTTP Discovery Method: UPnP or Manual Nuances: MTI has discovered issues interfacing with the Sarix Pro line of cameras. While these cameras do provide an RTSP stream at rtsp/ip/stream1, they apparently have no available ONVIF interface. Pelco has told MTI that the cameras should be returned to them for repair due to a flaw in the operating system. Pelco DigitalSentry/DSSRV DSSRV does not directly implement the ONVIF Profile-S standard, but using the DSMapBuilder tool, you can acquire the standard RTSP stream for each camera on the DSSRV. Authentication: None Discovery Method: None 42 Nuances: MTI has discovered that Pelco Optera cameras which

43 are tied to a DSSRV cannot be viewed through the DSSRV s provided RTSP stream as it will attempt to use the immersive stream, which cannot be displayed except through Pelco s software. For these cameras, we recommend adding the camera directly to the Media Map and accessing its individual profiles (see below) Pelco Optera Pelco Optera is fully ONVIF Profile-S compliant and can be used with the application. Authentication: HTTP Discovery: UPnP or Manual Nuances: The mosaic/immersive view does not display correctly within Hinley. These cameras provide individual profiles for each angle of the camera. For example, a 360 camera will have a front, back, left, right, and down profile. All of these profiles are named front_video and so on. Axis All Axis is fully ONVIF Profile-S compliant and can be used with the application. Authentication: WS Discovery: WS Nuances: Axis cameras require the configuration of a separate ONVIF user. Additionally, unless the time of the camera matches within 5 seconds of the computer that is accessing it, you must turn off Replay Attack Protection feature by going to Advanced > Plain Config and 43

44 selecting the WebService group within the Axis web interface. 44

45 Chapter 13: Configuring ProVision to Use Hinley The latest version of ProVision 4 provides direct integration with the HinleyViewer application. This integration can be added to ProVision through the Configuration form. To configure ProVision, go to Alarm Log > Service > View Configuration. In the top-right section of the System Configuration form, select the CCTV tab. The following fields and values define the use of Hinley for camera call-ups within ProVision: Com Port Leave this field blank. Forms This value dictates how many individual forms will be opened for viewing. ProVision can be configured to open one or two separate instances of Hinley. V1, V2, Menu - This value dictates the initial number of views for each of the forms selected, plus some other options. The first value in the four numbers is the number of views desired for the first form. The second value is the number of views desired for the second form. The third number specifies whether the top menu within Hinley should be presented. If this value is 0, then no menu will be presented. If it is 1, then the menu will be presented. The fourth value 45