File uploaded by acaputo Employee on Jun 27, 2015
Version 1Show Document
  • View in full screen mode

This proof-of-concept document is quite popular, all over the world. I thought I'd re-post it here with a summary. Typically, a Video Management Software (VMS) takes control of an encoder and/or IP Camera when commissioning the device into the system. There are also encoders and/or IP cameras that will lose their individual intelligence when connected to a general VMS system, because the compatibility is minimal outside their own proprietary software. However, there are specific brands that allow bi-directional communications (proof-of-concept uses Axis and Verint, only because they were the two I had on hand in my lab at home), meaning that if someone logs into the web or telnet interface of the encoder and/or IP camera and makes changes, those changes are then automatically modified within the VMS, and visa-verse. There's a synchronization that occurs. In a dual VMS architecture, you need a smart enough VMS system that will communicate bi-directionally with the devices (the proof-of-concept uses Genetec Omnicast and OnSSI). This way, wherever configuration changes are made, both VMS system and/or devices will all synchronize, continuously using the same, single Multicast stream. Operationally, collaboration and compromise may be required because the stakeholder using one VMS may wish to archive video at a higher resolution, but the stakeholder with the other VMS may not have the storage capacity, thus reducing their archive retention period.


The real value of this collaboration is that it does not require any additional hardware, if the right networking equipment is available to configure a shared Multicast stream.