TMS is unable to set the bandwidth on TX systems on a call by call basis, and thus always assumes worst case bandwidth usage when calculating whether a bridge has enough bandwidth available. I *think* TMS assumes 4000kbps per codec for video, 4000kbps for collaboration features, and a little bit (64kbps?) for audio. If my memory serves me right, 49792kbps on the TelePresence Server should then be enough to host three TX9000s as TMS sees it, but I might be overlooking something (as it's been a while since I last had to troubleshoot TX bandwidth calculation issues).
I'll ask some of my colleagues tomorrow and try to get some accurate numbers for you. I'll look into getting TMS's assumptions about TX and CTS bandwidth usage into the official TMS documentation as well.
I was slightly mistaken last night, TMS actually reads the "Quality (per Display)" value defined for the system on the CUCM when calculating bandwidth usage.
You use "Highest detail, best motion". TMS then assumes 4000 kbps per codec, 64kbps per microphone, 500 kbps for the "Auto Collaborate" feature, and 3500 kpbs for the "Auto Collaborate Upgrade" feature. (I'll have to admit that I don't know what the last two features actually are, I'm just looking at TMS's numbers here).
A TX9000 has three codecs and three microphones. TMS then calculates that each TX9000 needs
(4000kbps x 3) + 3500kbps + 500kbps + (64kbps x 3) = 16162 kbps of bandwidth. But as 3 x 16162 kbps is less than the TelePresence Server's bandwidth of 49792 kbps, you should still be good.
I think you have to open a TAC case on this one and if possible provide a database copy; we can then do debugging from there.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...