Jabber Video - Signaled Vs. Configured Bitrate

[Glen Lamison]

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.

[ahmashar]

Hi,

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.

The more details, the faster you get answers

regards, Ahmad

[Glen Lamison]

Hello,

Here are the software versions:

TMS: 13.2.2

TMSPE: 1.0

VCSC: X7.2.1

VCSE: X7.2.1

Jabber Video: 4.4.3, 4.5.7, & 4.6.3 (all Windows)

Thanks,

Glen

[ahmashar]

Hi Glen,

can you also check and post your provisioning settings on TMS for jabber clients?

I would be interested to see Max in/out Bandwidth restriction set there.

regards, Ahmad

[Glen Lamison]

Hi Ahmad,

The max in/out bandwidth is set for 384 for inside and 768 for public for all configuration templates:

Thanks,

Glen