Inside our network our Jabber Video clients are limited to 384 kbps. When in a call, Jabber client stats show the “Max allowed bitrate” and the “Configured bitrate” at 384. However, the “Signaled bitrate” is 2048 kbps. The 2048 is what is configured for the “Default call bandwidth” on our VCS.
The issue I’m having is when the Jabber client is in a Local Subzone with a bandwidth limit, the signaled bitrate of 2048 is counting against the limit instead of the 384. Is this normal behavior or do I have something configured incorrectly.
please mention what version of software you use with type (windows, MAC), etc. so we can check whether this is a software bug in your deployed version or is something to do with your setup and configuration.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...