How to increase the default bit rate/bandwidth for movi calls?

[startryst]

Hi, Expert

As the subject, not sure what's the default setup, but the movi calls to each other in LAN can achieve only 352*288, with configured bitirate 314kb/s in the statistics during the call

see below picture for detail:

[Haydn von Imhof]

Hi There

The default call rate can be set in the Device provisioning template for Movi/Jabber on TMS.

Also check the default call rate on your VCS, by default its set to 384Kbps.

VCS > VCS Configuration > Bandwidth > Configuration

Also check to see if you have any bandwidth limits set on any of your VCS zones.

[startryst]

Are you talking about the Max bandwidth In/ Out of in the template? There isn't any default setting on that.

Sent from Cisco Technical Support iPhone App

[Haydn von Imhof]

Yes sorry the Max bandwidth In/ Out of in the template.

If those values have been set then check the Default call bandwidth on the VCS control.

According to the Admin Guide “the Jabber Video client will be set to send the provisioned value.

With no provisioning, the default starting level is lower than the maximum that can be set by the user”

[startryst]

Haydn von Imhof wrote:
“the Jabber Video client will be set to send the provisioned value.
With no provisioning, the default starting level is lower than the maximum that can be set by the user”

What's that above wording means? If there isn't any Max Bandwidth In/Out setting in the configuration template in TMS, what's the bandwidth for the Movi users, are they will take the default call bandwith from

VCS > VCS Configuration > Bandwidth > Configuration?

[mahkrish]

Hi,

The bandwidth of Jabber for iPad has been limited to 384 kbps maximum since that's all the current hardware is capable of handling.  

BR,
Mahesh Adithiyha

[startryst]

Hi, Mahesh

So how to differentiate the bandwidth between Movi2Movi call and iPad2iPad or even Movi2iPad calls? so that as long as iPad in the situation, the bandwidth will be limited to 384kbps, but for Movi they might try an higher bandwidth at first, will slow down if the connection not enough? which I think it's more sense, what's the solution?

setting the configuration template of iPad in TMS to 384kbps?

[startryst]

Hi, Haydn

Yes, I found it's 384kbps under VCS > VCS Configuration > Bandwidth > Configuration, so I've update that settings to 1000 on both VCS Control and VCS Expressway, and I did an check for all other Zones and subzones, there isn't any limitation for the bandwidth setting. So I would like to try again based on this, before I make any update to the TMS configuration template, because there isn't any default settings on the template to limit such bitrate...

[mahkrish · Accepted solution]

Hi, I have tested this in our Lab earlier and the call flow is Jabber --> VCS-C --> C40 endpoint. Please refer to the snpshot of TMS Jabber template, VCS-C bandwidth settings and connected call rate details on C40.

As informed earlier, the bandwidth of Jabber for iPad has been limited to 384 kbps maximum since that's all the current iPad hardware is capable.

[startryst]

Hi, Mahesh

Yes, which means the Jabber will take the lower bandwidth setting between the TMS configuration template and the default bandwidth settings in VCS control and VCS Expressway....

[Martin Koch · Accepted solution]

In addition from what is already said.

Just that something is not there does not mean that it does not have an impact.

If you look in the jabbervideo admin guide, the default for Maximum Out Bandwidth is 384.

Please recheck the provisioning and jabber video admin guide that your deployment is ok.

I think in one guide was mentioned that the bandwidth setting was a minimum requirement.

Also keep in mind that there are other mechanisms (also mentioned in the admin guide)

like, storage of the bandwidth of the last calls, bandwidth probing, packet loss ... which can change the behavior.

Please set the value via the provisioning, check on the client what is set up under bandwidth

for the client, adjust if needed and test again.

[startryst]

Hi, Martin

You're right, the configuration template of TMS will decidce the Max bandwidth which Movi used to talk with others, I did some interesting test as below:

1. Set the Max Bandwidth In/Out to 1000, and default bandwidth of VCS-Control and VCS-Expressway to 1000, the movi talk with each other at 1Mbps

2. Set the Max Bandwidth In/Out to 2000, and default  bandwidth of VCS-Control and VCS-Expressway to 1000, the movi talk with  each other at 1Mbps

So it looks both parameter has effect that it determine by the lower one.

Then my final configuration as below, pls take a look and get back to me whether it's the most reasonable one:

1. Movi configuration template: Max In/Out bandwidth 1000, Clear Path On

2. iPad configuration template: Max Out bandwidth 384(no set for the In), Clear Path On

3. Default bandwidth on VCS-Control and VCS-Expressway set to 1000

[Martin Koch]

Do you have a local subzone including the internal ip addresses of the jabbervideo client machines?

Would be interesting to see how it behaves if you have set up unlimited bandwidth there.

Never saw the issue if the bandwidth is properly provisioined that the default rate would be used.

Remember if you change provisioning data you have to logout and login again with your jabbervideo client

to activate them.

Also check that you do not limit the per call bandwidth on the traversal zone.

Also make sure you have the xml device templates of the versions you use uploaded and

proper configs for them. Which VCS/TMS/Jabber video versions do you use? You use tmspe, right?

[startryst]

Hi, Martin

Let me answer your question one by one:

1. No local subzone

2. Yes, everytime I changed anything, I'll logout my Jabber video client, and that's right.

3. No limit on the per call bandwidth on traversal zone

4. Yes, the iPad and Movi xml device template are all downloaded from Cisco.com, and it's the latest one.

5. Jabber Video 4.5, VCS X7.2, TMSPE 13.2.1

[Martin Koch]

each version of movi/jabbervideo has its own xml template, and I would also recomend to have them present.

Check that both clients use the same version.

Do you have the same behavior if both clients are registered to the same VCS-C?

In the old Movi2 times having the local subzone ips defined was a requirement, at least I would test to set

these (just define the two local ips of the two machines running jabbervideo if you have answered the above

question with yes.)

I am not 100% sure, but I would say the default bandwidth should only be used if there is no

bandwidth info available. Is the sip part of the traversal zone active?

Maybe looking at the debug output on the vcs and jabber could come in handy.

I would say the 2mbit should work even with the default bandwidth set, but again, there are many

tweaks where bandwidth settings can be hidden and where behavior might change :-)