Cisco IP Gateway Encoder (CIVS-SGxx) doesnt work with VSMS for H.264
I have fourteen Cisco IP Gateway Encoder (CIVS-SGxx) Cards mounted in convergence Chassis. They work fine with our VSOM/VSMS using MPEG-4, however when I change it to H.264 in both the VSOM, and on the encoder (via the Stream Manager Configuration Tool) it doesnt ever start the proxy.
In the ims.log I see:
2009-10-14 10:33:01.669 [ proxy(31819).p_acam12_2 BE_PROXY=1 ] Incorrect video from encoder (expecting H.264, received MPEG4). Restarting.
Re: Cisco IP Gateway Encoder (CIVS-SGxx) doesnt work with VSMS f
For IP Video Surveillance, the media, whether it be TCP-based as is the case with Motion JPEG camera feeds, UDP/RTP-based for MPEG-4 and H.264 or TCP-based web delivery, the recommendation is to mark this traffic as DSCP decimal value 40 or CS5. The control plane traffic for video surveillance, such as RTSP, is recommended to be set at CS3 or decimal value 24. As a best practice, IP cameras are recommended to be configured for NTP, SNMP and Syslog, and these applications are suggested to be marked DSCP with decimal value 16 or CS2.
There is a very limited amount of network traffic in a video surveillance deployment for control plane and network management applications compared to media streams. Because of this, some network managers may find it both practical and expedient to mark media as CS5 and all other traffic from cameras, clients and servers as either CS3 or CS2.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...