05-14-2013 05:21 PM - edited 03-18-2019 01:06 AM
I'm having issues getting TMS to schedule a 6Mbps call to a Telepresence Server.
When I create a booking on the TP server using TMS, I can select any bandwidth (2560Kbps, 4096Kbps, 6144Kbps etc). Whichever bandwidth I set the conference to, that's the call rate that TP server dials out with, EXCEPT 6144kbps. Whenever I set it to 6144Kbps, the call rate goes back to 1920Kbps.
If I dial out from the TP server itself, everything connects at 6Mbps OK (same with dialling back in).
Looking at the call history on VCS, the TP server only requests 1920Kbps when dialling out from a TMS scheduled meeting that's set to 6144Kbps.
All bandwidth restrictions have been removed from VCS, the endpoints support 6mbps (as evidenced by the Ad-Hoc dialling working OK in each direction). It seems like TMS is setting the conference bandwidth to 1920Kbps (or failing to set a conference bandwidth at all) despite being set to 6144Kbps.
VCS: 7.2
TP Server: 3.0(2.24)
TMS: 13.2
Any help appreciated
Solved! Go to Solution.
05-15-2013 01:13 AM
06-20-2013 11:52 PM
Hi,
All internal issue tracking systems say that it was fixed in 14.2.0. Are you saying that you still see the issue in 14.2.2?
-Kjetil
Sent from Cisco Technical Support iPhone App
05-15-2013 01:13 AM
05-15-2013 01:55 PM
Thanks Kjetil, this gives me good motivation to upgrade quicker
06-20-2013 03:30 PM
I've been anxiously awaiting the next releaser of TMS, but after reading the release notes for 14.2.2, this bug is still open. Any ideas when this will be fixed? We have 3 x Telepresence server clusters that just seem like they are being wasted when we can't schedule them at their full capacity.
06-20-2013 11:52 PM
Hi,
All internal issue tracking systems say that it was fixed in 14.2.0. Are you saying that you still see the issue in 14.2.2?
-Kjetil
Sent from Cisco Technical Support iPhone App
06-21-2013 12:49 AM
I read the release notes:
And it was still under "Open Issues". I then searched the bug ID and it does indeed say it was fixed in 14.2, I guess it just wasn't removed from the open issues list?
For the record, I haven't upgraded the affected TMS yet - the last few versions that have been released, I've always seen it in the "open issues" so I was waiting until it was fixed - looks like I should have read the resolved issues also!
Thanks!
06-21-2013 01:24 AM
Hah, it is actually mentioned both as a resolved issue and an open issue! I guess we just forgot to remove it from the list of open issues.
I'll look into getting it removed from the list of open issues.
Regards,
Kjetil
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide