Release Notes for Cisco Video Surveillance Manager, Release 7.12

Smart Licensing

A license must be purchased and installed for each Media Server and non-Cisco camera added to your deployment. You can choose from 2 licensing methods:

• Traditional Licensing—Licenses are installed on the Operations Manager and maintained locally.
• Cisco Smart Software Licensing—Licenses are managed from a central location (Cisco Smart Software Manager) or on-premises (Cisco Smart Software Manager satellite). Smart Software Licensing allows you to manage licenses for Cisco products in your organization. Smart Licenses are automatically added to your account when ordering. Learn more.

See the Cisco Video Surveillance Operations Manager User Guide for more information and instructions.

Network Attached Storage Support for LTS servers

LTS servers support NAS (Network Attached Storage) in Cisco VSM Release VSM 7.12 and higher.

Usage notes

NAS performance is dependent on the NAS specification.

Procedure

To mount a NAS on an LTS server:

Step 1 On the LTS server, run the setup_media_storage script in /usr/BWhttpd/bin.

Step 2 Select 2, when prompted, to mount the NAS partition (Figure 1).

Step 3 Enter the NAS server location.

• NAS_server:storage_point
• For example: vsm712-netapp-ns:/vsm/lts-storage1

Figure 1 Option to Mount a NAS Partition

Camera Discovery: Manual and Scheduled

IP cameras that have been installed on the network can be discovered and added to Cisco VSM. You can manually trigger discovery, or schedule automatic discovery.

Camera discovery can be performed for a variety of cameras, including cameras that support Bonjour, Onvif cameras, and other cameras.

Auto-configuration can also used to automatically enter basic settings and add the device to Cisco VSM.

See the Cisco Video Surveillance Operations Manager User Guide for more information.

Figure 2 Camera Discovery and AutoConfig Flow

Tip You can also move a discovered camera to the Blacklist to prevent it from being added to Cisco VSM or from being discovered in future discovery actions (Figure 2). Blacklisted Cameras will not get discovered again until removed from the blacklist.

Cameras Pending Approval List

Cameras discovered on the network are added to the Cameras Pending Approval list (Figure 2), allowing you to review the discovered cameras, add additional configuration settings if necessary, and manually approve the camera addition to Cisco VSM.

Auto-Configuration

If Auto-configuration is enabled for a camera model, then the basic configuration and template is automatically applied to the camera, and the camera is added directly to the enabled state (Figure 2). Auto-configuration settings are accessed in System Settings > Auto Provisioning Settings.

Supported Cameras

Camera discovery is supported on Cisco, Axis, Bosch, Panasonic, IQinVision, Sony, Vivotek and Onvif cameras.

Camera Discovery Process

Camera discovery can be manually triggered or automatically performed according to a schedule.

You can also (optionally) enable the auto-configuration defaults for the camera model to automatically complete the basic camera properties and enable the camera in Cisco VSM.

Procedure

See the Cisco Video Surveillance Operations Manager User Guide for more information about the following topics procedures.

Procedure

Bookmarks Automatically Deleted with Video

Bookmarks are automatically deleted if the video no longer exists. For example:

• Camera Bookmark—If recording is present, then bookmark will be groomed off based on the maximum retention period of the primary MS or Failover or Redundant or LTS server, plus 1 day.
• Location Bookmark—If a bookmark is applied at a location, the same rule applies based on the longest maximum retention period of the camera’s primary Media Server or Failover / Redundant / LTS server, plus 1 day. Any camera that meets this condition is disassociated from the bookmark. If no camera is associated with the bookmark, then that bookmark is deleted.
• Bookmark with Single Camera Recording Off— If a camera is in “Live only” mode, the bookmark will be groomed off at the end of 1 day. (This is based on the maximum retention period of the primary Media Server or LTS server, plus 1 day. Since the maximum retention period of the primary Media Server or LTS server is 0, grooming occurs at the end of 1 day.)

Real-time Camera Status in Maps

The cameras’ state is dynamically updated on maps without needing to reload the maps page (Figure 3).

Figure 3 Dynamic Map States

Hover your mouse over a camera to see any new health, security or motion alerts (Figure 4).

Figure 4 View Camera Alerts in Maps

Media Storage Combined into a Single Logical Volume

You can now use the setup_media_storage script to configure a Logical Volume (LVM) that combines multiple partitions into a single logical partition. This allows media to be automatically stored across partitions.

The setup_media_storage script formats the current partition and creates a logical volume. To avoid recording loss, this script must be run when configuring the server and before any cameras are added.

New storage can also be added to an existing LVM using the setup_media_storage script. If new storage is not added to an LVM, it will be added to Cisco VSM as a separate partition.

Prerequisites

At least one partition must be configured as LVM. You can then extend that partition by adding more drives to system.

Background

Previously, media partitions were managed separately, such as media1, media2 etc. Media Servers were unable to store recordings from a camera across partitions, so a camera’s video might be groomed from the partition used for that device even if additional capacity was available in another partition. If a partition ran out of storage space, additional storage had to be added as a new media partition.

Improved Video File Storage

By default, all SMD video files are created in 5 minute intervals. Starting in Cisco VSM, however, a new SMB video file is created as soon as an event start/stop is triggered.

This means that event based SMD files can be less than 5 minutes (based on the event duration). This saves disk space, since a 1 minute recording only results in a 1 minute file.

If an event lasts more than 5 minutes, multiple SMDs are created of 5 minutes each. Only the first and last SMD will be less than 5 minutes based on the event start and stop times.

SASD Option to Filter By Active Alerts

In Cisco SASD, the Alert workspace now includes the Active filter which will display only the alerts causing the current problem.

Enhanced Storage Retention Dashboard Status

The Storage Retention Status in the Storage Retention Dashboard now displays a new OK status icon for additional information, such as when a camera’s recordings are using less storage than estimated.

For example, Cisco VSM estimates the required storage based on the camera bitrate. If Cisco VSM estimates a camera’s recording storage size to be 4GB, but the actual recording storage used is only 2.5GB, the new OK status icon is displayed. Click this to view additional information in the Retention Status field.

Procedure

Step 1 Log in to the Cisco VSM Operations Manager.

Step 2 Click Monitor Video.

Step 3 Click Storage Retention Dashboard.

Step 4 Select a Media Server and select a camera.

Retention Status—Warnings are displayed if the deviation goes above or below the specified percentage. For example:

—Storage retention is OK.

—Additional information is available. For example, less space is used than originally estimated.

—Estimated storage based on streaming is higher than expected.

Next to Reason, click for more information.

See the Cisco Video Surveillance Operations Manager User Guide for more information.

HA Failover Timeout Configurable Up To 5 Minutes

HA failover from a Media Server to the Failover Server can be configured up to 5 minutes by modifying a text file.

This prevents the HA failover from occurring if the network is going up and down or is unreliable.

See the Cisco Video Surveillance Operations Manager User Guide for more information.

Encrypted Tamper Proof Video Files (CVB format)

CVA clips can be saved as.CVB files that fail to play if they are tampered with.

CVB files are encrypted with a security key. If the file is tampered with, the key cannot be decrypted and playback will fail.

Procedure

Step 1 Select a video pane from the viewing application (such as Cisco SASD or Operations Manager).

Tip To create a multi-pane clip in the CVA format, press Shift-Click to select multiple concurrent panes, or Ctrl-Click to select individual panes. Individual panes cannot be saved in sync mode.

Step 2 In the green seek bar, Ctrl-Click and drag the mouse cursor to create a bookmark span. The bookmark span is shown in orange (Figure 5).

Step 3 Right-click the bookmark and select an option to create a CVA clip (Figure 5).

Figure 5 Creating a Video Clip

.

Step 4 (Optional) Revise the start and end date and time (Figure 6). Enter a time between 30 seconds and 24 hours (the range cannot include more than one codec and the start time must be before the end time). Use the Set Duration field to enter a specific length of time for the clip. The duration begins at the beginning bookmark time.

Figure 6 CVA Clip Settings

d. (Optional) Select Enable tamper proof and enter a password (Figure 6).

e. Click OK.

f. Select a location on a local disk and click Save.

g. Wait for the clip to be generated and downloaded. Video streaming is paused during CVA/CVB clip generation.

h. Play the clip using a video player such as the Cisco Review Player.

CVA/CVB Clip Passwords Can Be Reset

To reset a forgotten password for a CVB clip, users must belong to a User Group with Reset Clip Password permission.

• The clip’s last modified timestamp is updated when the password is recovered.
• You can only reset the password using the same server where the clip was created. For example, if the clip was created using Operations Manager 'A', you cannot reset the password from Operations Manager 'B' or SASD Federator.

Procedure

Step 1 Right-click the video pane and choose Reset Clip Password.

Step 2 Select the select CVB clip from your local drive.

Step 3 Enter and re-enter the new password.

Step 4 Click OK when the confirmation message appears.

Step 5 Play the CVA/CVB clip.

Alert Notifications Can Be Sent to WebEx Teams

Health and security alerts can now be sent to WebEx Teams (formerly Spark). This is in addition to email addresses.

Notifications may also include a snapshot of the camera on which the event occurred.

Procedure

Step 1 Log in to the Cisco VSM Operations Manager.

Step 2 Enter an Authtoken in Cisco VSM to enable communication with WebEx Teams:

The Authtoken is a public key provided by your WebEx Teams administrator that allows messages to be securely sent from VSM to WebEx Teams.

a. Go to System Settings > Settings.

b. In the General tab, enter the Authtoken string in the WebEx Teams User Authtoken field.

c. Click Save.

Step 3 Enter one or more WebEx Teams Rooms that will receive notifications.

a. Select Operations > Notification Policies.

b. Click Add.

c. Select Health or Security.

d. For Security, select By Location or By Camera.

e. Select Send notification on WebEx Teams.

f. Enter the WebEx Team names, separated by a comma. If the name does not exist it will be created.

g. Enter the notification settings for the event type. See the Cisco Video Surveillance Operations Manager User Guide for more information

h. Click Add.

i. Create additional entries for additional locations, cameras, and recipients, if necessary.

Revoke Longer Duration RTSP URLs

Cisco VSM now provides a way to view details about long duration RTSP URLs, and if necessary, revoke them to disable streaming.

Procedure

Step 1 Click Cameras.

Step 2 Select a location and camera.

Step 3 Click General > Camera Covert & Whitelisted RTSP URL Details (Figure 7).

The URLs are listed on the right.

Step 4 To revoke a URL, select the entry and click Revoke URL.

Figure 7 Whitelisted RTSP URL Details

Trigger Events and Actions Using External Sensors

3rd party sensors can now be integrated into Cisco VSM to send events that trigger VSM actions, such as recording video from a specific camera. External sensors are a type of device in Cisco VSM, and are managed like cameras.

For example, a door sensors is added to Cisco VSM. When the door is opened, a Cisco VSM event is generated that causes a camera pointed at that door to record video for 5 minutes.

Sensor types, sensor states and other details are defined by the 3rd party product, in cooperation with Cisco Systems. The following examples show sensor integration for the Identiv Connected Physical Access Manager (ICPAM).

To integrate sensors, do the following:

• Add Sensor Types
• Add Sensor Templates
• Add or Import Sensors

Add Sensor Types

For example, add a door sensor type with states “Door Open” and “Door Closed”. These states can be used to trigger Cisco VSM events and actions.

Step 1 Go to System Settings > Settings.

Step 2 Click the Sensor System Settings tab.

Step 3 Click Add.

Step 4 Enter the following settings:

• Sensor Type Name—Enter a meaningful name, such as “DoorSensor”.
• Sensor States—Click Add and enter the possible device states used to trigger an event. For example “Door Open, Door Closed”. Separate each state with a comma.
• Change Icon—Click Change Icon to display a custom icon for sensors added to location maps. You can upload new icon images, or select an existing icon image.
• Tags—(Optional) Enter a keyword that assist in a Find.
• Description—(Optional) Enter a meaningful description, such as “Exterior doors that record video when opened”.

Step 5 Click Save. The sensor type is shown in the list to the right and can be modified or deleted.

Add Sensor Templates

Templates define the triggers and actions for the sensor types and can be applied to multiple sensors. For example, create a template that will record video whenever a door is opened.

Procedure

Step 1 Go to Sensors > Sensor Templates.

Step 2 Click Add.

Step 3 In the General tab, enter the following properties:

• Template Name—A meaningful name, such as “Door Sensor”.
• Sensor Type—Click to select a type.
• Description—(Optional) Enter a meaningful description, such as “Exterior doors that record video when opened”.
• Associated Location—Click to select the location.

Step 4 Click the Sensor Events tab to define the triggers and actions for the sensor type.

a. Click Add to create a new Trigger / Action entry.

b. Under Pattern:

– Select a Trigger (such as Sensor Trigger).

– Select a Sensor Event Type (such as Door Open or Door Closed).

c. Under Resulting Action, select the actions that will occur if an event occurs.

– One-Time Action: The action that will be triggered, such as Aim Camera or Record for some time.

– Select the additional settings for the selected action.

d. Click Create.

Add or Import Sensors

To integrate sensors, add the devices to Cisco VSM and associate them with camera and sensor template. You can add a single sensor or add multiple devices by importing sensors from a CSV file.

Add a Single Sensor

Procedure

Step 1 Add the sensor.

a. Go to Sensors > Sensors.

b. Select a location.

c. Click Add.

d. Enter the sensor settings as described in Table 2 .

e. Click Associate Camera(s) with Sensor, select one or more cameras and click OK. Use the filters to narrow the results, or click Search to display all cameras.

f. Click Add.

Step 2 Define the triggers and actions for the sensor.

a. Select the General > Sensor Events tab.

b. Click Set Template to change the template selection.

– Select Custom to create event triggers that apply only to the current sensor.

– De-select Custom to select an existing template.

c. Click Save.

If Custom is selected:

a. Click Add to create a new Trigger / Action entry.

b. Under Pattern:

– Select a Trigger (such as Sensor Trigger).

– Select a Sensor Event Type (such as Door Open or Door Closed).

c. Under Resulting Action, select the actions that will occur if an event occurs.

– One-Time Action: The action that will be triggered, such as Aim Camera or Record for some time.

– Select the additional settings for the selected action.

d. Click Save.

Sensor Settings

Import Sensors From a File

Procedure

Step 1 Go to Devices > Sensors.

Step 2 Click Add > Import Sensors From a File.

Step 3 Import Step 1 - Click the Download Sample button for instructions to create an import file in plain text CSV format that contains the sensor device settings.

• Create a file that can be opened and saved using Excel or OpenOffice Calc.
• Enter the sensor settings as described in Table 2 .

Step 4 Import Step 2 - File Upload :
Click Choose to select the CSV file from a local or network disk. Click Upload.

Step 5 Import Step 3 - Processing :
Wait for the import process to complete.

Step 6 Import Step 5 - Results :

• If a success message appears, continue to Step 8.
• If an error message appears, continue to Step 7

Step 7 If an error message appears, complete the following troubleshooting steps:

• Click Download Annotated CSV, save the error file and open it in Excel or OpenOffice Calc.
• Correct the annotated errors in the //Error rows.
• Save the revised file in the.CSV format.
• Return to Step 2 and re-import the corrected CSV file.

Step 8 Click Close.

Revised Upgrade Process for Operations Manager HA Servers

Security enhancements in Cisco VSM Release 7.12 require a revised upgrade process for Operations Manager HA Servers.

Procedure

To upgrade the system software on a Operations Manager server in HA mode, do the following -

Step 1 Log into the Operations Manager using the virtual IP address.

Step 2 Click the pencil icon in the title bar to place the server in maintenance mode .

Note The icon is grey when maintenance mode is on, meaning most user configuration will be rejected (only system tasks and logging are allowed).

Step 3 Go to VSOM High Availability tab and click Delete to delete the HA configuration.

Step 4 Upgrade the Master Log in to the Peer Operations Manager server:

a. Log in to the Master Operations Manager using it’s direct IP address.

b. Upload the upgrade.zip file.

c. Upgrade the Master Operations Manager server.

Step 5 Upgrade the Peer Operations Manager server, upload the.zip file and upgrade the Peer server.

Step 6 Upgrade the Split Brain Media Servers.

Step 7 After the Master, Peer and Split Brain Media Servers are upgraded, re-establish HA.

Cisco Connected Safety and Security UCS Platform Series Servers

Cisco VSM Release 7.12 is pre-installed on new installations of the Cisco Connected Safety and Security UCS Platform Series when ordered with the Cisco VSM software installed.

Supported Servers

• KIN-UCSM5-1RU-K9 / KIN-UCSM5-2RU-K9

Related Documentation

• Cisco CSS UCS Server User Guide — supported features, physical installation and setup instructions
• Release Notes for the Cisco CSS UCS Servers

Notes

• After the server appliance is installed, see the Cisco Video Surveillance Manager: Install and Upgrade Guide to perform the initial Cisco VSM setup.
• For additional server hardware documentation, see the Cisco UCS C-Series Server Documentation (Roadmap).

Upgrading from Previous Cisco VSM Releases

For complete instructions, see the Cisco Video Surveillance Manager: Install and Upgrade Guide.

Upgrade methods

The following table describes the upgrade methods based on how old your server’s current release is.

Platform Notes

• Release 7.0 was pre-installed on the Cisco Multiservices Platform (Cisco MSP) servers, including the CPS-MSP-1RU-K9 and CPS-MSP-2RU-K9.
• Release 7.2 to Release 7.7 was pre-installed on the CPS-UCS-1RU-K9 and CPS-UCS-2RU-K9 Cisco CSS UCS series servers.

– The CIVS platform is not supported and cannot be upgraded to VSM 7.7 or later.

• Release 7.7 to 7.11.1 is also pre-installed on the Cisco CSS UCS series servers:

– CPS-UCSM4-1RU-K9 / Cisco CPS UCSM4 2RU

• Release 7.11.1 and higher is also pre-installed on the Cisco CSS UCS series servers:

– KIN-UCSM5-1RU-K9 / KIN-UCSM5-2RU-K9

Note Virtual Machine (VM) installations can also be upgraded using the Cisco VSM Management Console. Upgrades are supported from release 7.8 or higher on the RHEL6 operating system. See Cisco Video Surveillance Virtual Machine Deployment and Recovery Guide for UCS Platforms for more information.

Recovery/Factory Image

You can also create a bootable USB flash drive that can be used to recover an installation or perform a a factory installation of Cisco VSM Release 7.12 on a supported physical server that shipped with Cisco VSM Release 7.12 pre-installed. This includes CPS-UCSM5-1RU-K9 and CPS-UCSM5-2RU-K9.

For more information, see Cisco Video Surveillance Manager: Install and Upgrade Guide

Supported Devices: Cisco

Table 5 through Table 11 provide information about Cisco devices supported in this release:

• Cisco 2400/2500, 2600, 2800, and 2900 Series Basic functionality such as streaming and recording is supported. Any features that require a firmware upgrade are not supported.
• Cisco 3000 Series
• Cisco 4000 Series and 5000 Series Basic functionality such as streaming and recording is supported. Any features that require a firmware upgrade are not supported.
• Cisco 6000 Series
• Cisco 7000 Series
• Cisco 8000 Series
• Cisco CIVS-SENC-4P and CIVS-SENC-8P

Additional Notes on Cisco Devices

• Cisco 4500 and 4500E support video analytics.
• Redundancy is supported for all Cisco devices some exceptions for the 2400, 2500, 2900 and 5000 series. The 2400, 2500, 2900 and 5000 series do not support sending events to the redundant server such motion detection and contact closure events.
• Cisco 5000 series does not support motion detection at video bit-rates above 4,000 (4 Mbps). The “H” video preset in Templates has been chosen to not exceed this, so motion detection will work.
• The Cisco 5000 and 2900 camera series do not allow changes to the authentication settings (username/password) or networking settings (DHCP/Static, DNS, etc.) through Cisco VSM. These values can only be changed using the camera web interfaces.
• Focus, Auto Focus and Zoom support are not available for Cisco 6000P, 3421V, 3520, 3530, 3535, and 3050 camera models.
• When Cisco VSM manages a Cisco 6930, 2830, or 2835 camera, it automatically enables the HTTP protocol on the camera and uses this protocol to send PTZ commands to the camera. Other configuration commands continue to use the HTTPS protocol.
• The Cisco 2830, 2835, 3000 series, 6000 series and 7030 cameras now support MJPEG primary streams.
• Cisco 3421V and 6050 cameras do not support Contact Closure, Cisco 7030 camera supports 3 input ports. All other Cisco 3000, 6000, 8000 series cameras support 1 input port.
• In PTZ Tour Configuration, the configured transition time configured includes the time that it takes the camera to move from the one preset position to the next preset position in addition to the time that the camera is expected to stay in the preset position. If the transition time is configured to a value that is less than the time that it takes the camera to move from one preset position to the next, the camera moves between the first and second presets positions only, instead of touring between all preset positions that are configured in the tour.
• The minimum firmware version required to support camera applications is 2.5.0-10.
• The minimum firmware version required to support connected edge storage is 2.0.

Supported Devices: Arecont

Table 12 provides information about Arecont devices that this Cisco VSM release supports.

Additional Notes on Arecont Devices

• AV20185, AV20365, AV12186, AV8365 and AV8185 are 4-channel IP cameras. In order to support multiple video channels from a single device, Cisco VSM 7 models these devices as “Encoders”.
• Arecont devices have not yet been qualified to support redundancy in Cisco VSM 7.
• Secondary streams are not supported in H, M, L template settings for Arecont Devices. However secondary stream can be configured using Custom templates.
• Arecont cameras divide the Maximum FPS the camera supports by the number of streams. This could result in lower FPS when both primary and secondary streams are configured for these cameras.
• Arecont AV10XX5, AV5115, AV2115 support VBR and multicast streaming.
• There is a restriction with motion detection for Arecont multi-sensor cameras. False motion events are generated if both half and full resolution size images are requested simultaneously using Cisco VSM or Arecont Camera Web Interface or a third party Media Player.

Supported Devices: Axis

Table 13 , Table 14 , and Table 15 provide information about Axis devices supported in this release.

Table 15 provides information about additional Axis devices that this Cisco VSM release supports.

Additional Notes on Axis Devices

• Axis P3301 IP camera and Q7401, Q7404, and Q7406 encoders have been qualified to support redundancy in Cisco VSM 7.0.1.
• Axis 233D supports contact closure configuration and events.
• Support for 0.1fps MJPEG stream for all supported Axis models.

The following table documents the various Field-Of-Views supported for the Axis M3007 panoramic cameras and support for PTZ and Motion Detection for these Field-Of-Views.

The Axis M3007 camera allows the user to configure various mounting options directly in the camera web interface that affects the possible values for Field-Of-Views that can be configured on the camera. The table below provides this mapping:

Supported Devices: IQinVision

Table 18 provides information about IQinVision devices that this Cisco VSM release supports.

Additional Notes on IQinVision Devices

• IQinVision devices have not yet been qualified to support redundancy in Cisco VSM 7.
• Support configuring NTP on the IQinVision cameras to synchronize with their Cisco VSM Media Server.
• Added support for Firmware upgrade for all supported models.
• Added support for Camera Discovery for H.264 models.

Supported Devices: Mobotix

Table 19 provides information about Mobotix devices that this Cisco VSM release supports.

Additional Notes on Mobotix Devices

• Moboitx M10 and D10 IP cameras running with M10 series firmware work with the x10 Model.
• Mobotix devices are not qualified to support redundancy in Cisco VSM 7.

Supported Devices: Panasonic

Table 20 provides information about Panasonic devices that this Cisco VSM release supports.

Additional Notes on Panasonic Devices

• Panasonic devices have not yet been qualified to support redundancy in Cisco VSM 7.
• Only same field of views can be configured on primary and secondary streams on Panasonic cameras SW458/SF438.
• The following table documents the various Field-Of-Views supported for the Panasonic SF 458 and SF 438 panoramic cameras and support for PTZ and Motion Detection for these Field-Of-Views.

Supported Devices: Pelco

Table 22 provides information about Pelco devices that this release supports.

Additional Notes on Pelco Devices

• Pelco devices have not yet been qualified to support Redundancy in Cisco VSM 7.
• Audio volume controls are not supported for NET540XT
• For Pelco NET540xT PTZ to work, the analog camera should be chosen as Pelco Analog Camera (pelco_sarix) in Operations Manager and not as Pelco D.
• The user needs to directly configure the Serial protocol on the Pelco NET540XT encoder outside of Cisco VSM.
• The Pelco Spectra IV TXB-N (H.264 capable model) run Pelco Sarix firmware and can be supported in Cisco VSM as a Pelco Sarix Generic IP camera (additional details in the Generic IP camera section).

Supported Devices: Sony

Table 23 provides information about Sony devices that this release supports.

Additional Notes on Sony Devices

• Sony devices have not yet been qualified to support redundancy in Cisco VSM 7.
• These Sony devices do not support motion detection with the H.264 media type.
• The Sony SNC-RX5x0 cameras stop streaming video when the Object Detection window is opened in the camera’s web interface.
• For Sony HM662 Panoramic camera, only the 360 degree view is supported. De-warped views are not supported.

Supported Devices: Vivotek

Table 24 provides information about Vivotek devices that this release supports.

Supported Devices: Generic IP Cameras

Cisco VSM Release 7.12 provides the following device drivers to support IP cameras from various vendors. The functionality they support will depend on the particular device that they are used with. They are intended to provide a quick and easy way to support devices for which there isn’t yet a specific driver available for Cisco VSM. Since these drivers may not be tested with a specific device, some issues may be encountered. When using these drivers with a device, failover and redundancy are not supported.

Note The vendor specific generic driver should always be used before a non-vendor specific driver such as ONVIF.

Known Limitations

• Supports only IP Cameras, no support for Encoders
• No contact closure support
• Multicast streaming is supported only for the primary stream
• Multicast port must be an even number within the range 16000:19999
• Audio Multicast issues are observed on most of the ONVIF cameras. Hence do not enable audio when multicast is enabled for video.
• Capture Mode on the camera cannot be changed using ONVIF APIs. So, it is assumed that the camera is in the desired capture mode before adding it to VSOM using ONVIF

Device Specific Limitations

• This ONVIF driver has been tested with a limited number of camera models from Axis, Sony, Panasonic, Bosch, Pelco, Samsung, J2000IP, Hikvision and Cohu. We have found that these cameras have some variations in how they have implemented the ONVIF specification. Hence there may be compatibility issues when using this ONVIF driver with a particular device that is ONVIF compliant.
• Some of the known caveats are listed below:

AXIS

• ONVIF user account—Some Axis cameras require a special ONVIF user account, which can be created on the camera's web interface before adding an AXIS ONVIF camera to the VSOM. This page is at Setup --> System Options --> Security --> ONVIF --> Add
• Camera and VSMS (Media Server) Time Synchronization—ONVIF camera and VSMS server to which ONVIF camera is being added should have their time synchronized ideally using NTP.

HIKVISION

• Codec Change through VSOM—Hikvision camera requires a reboot after the codec is changed from VSOM.
• The Minimum Firmware Version of Hikvision cameras supported is V5.3.0, to be added as ONVIF camera in Cisco VSM.

SAMSUNG

• Megapixel Mode setting on the camera SND-7080
• To support the resolutions (1600*1200) and (2048*1536), change the Megapixel Mode to 3-Megapixel in the following page on the camera browser: Settings -> Audio & Video -> video profile -> Megapixel mode

COHU

• Enable Authentication on the camera before adding it to VSOM In the camera browser, go to Camera Setup -> Configuration -> User Settings. Select User and enable “Require Password” field.
• Media Transport Type— Only UDP is supported. Streaming fails if TCP is selected.
• Unsupported Resolutions —Streaming fails for the resolutions 176*144, 176*120, 160*120
• Codec Change through VSOM— Switching from H264 to JPEG or vice-versa requires a camera reboot. And camera needs to be deleted and added in VSOM after camera is up.
• Support for Audio— Camera does not support ONVIF Audio

BOSCH

• Frame rate— Only Framerate 30 is supported
• Dual Streaming— Secondary configuration overwrites the primary configuration. So, dual streaming is not supported on Bosch cameras using ONVIF.

PANASONIC

• Capture Mode Setting— If the camera is added in VSOM using Multicast, changing the capture mode on the camera browser manually causes the streaming to fail. After this, only the unicast streaming works
• User Authentication— User Authentication should be enabled in the camera browser as follows - Setup -> User mng -> User auth. Choose ON for User auth.

SONY

• Media Transport Type— Only UDP is supported. Streaming fails if TCP is selected
• Support for Audio— Camera does not support ONVIF Audio
• Set Configuration Issues — Camera returns success even if one or more of the parameters are not valid for that camera/video stream. ONVIF profile gets updated with values but Camera still uses the previous correct value. Recommend to configure only the values as allowed in the camera browser.
• Support for Password change on the camera— Camera does not support password change for the administrator users using ONVIF API.

Supported Devices: Analog Cameras

This Cisco VSM release provides support for the following analog cameras.

Notes on Cyberdome devices

• The Cyberdome I and Cyberdome II devices also have On Screen Display Menu support.

Device Models Validated in Cisco VSM as Generic IP Cameras

The camera models listed in Table 27 have been tested with VSM Release 7.12 as generic IP cameras.