Endpoints: Tandberg 95 MXP & 6000 MXP
Codian 4510 MCU: Software ver. 4.4
Tandberg GK: N6.3
Tandberg BC: Q6.3
When I create a conference in TMS and want an endpoint to dial out of our system to an MCU at another site (neighbored), the our local MCU is added automatically to the conference for some reason. For example, if I create a conference with Room 123 and an external "Dial Out" number 2222222, TMS adds our system's MCU and forces it to dial out to both Room 123 and 2222222, which is totally unecessary. This should simply be, as far as the endpoint is concerned, a direct dial to 2222222. Why is the MCU being automaticallly added? This will use up MCU licenses in a hurry when it isn't necessary at all.
I've gone through TMS>Administrative Tools>Configuration>General Settings, Network Settings, and Conference Settings and can't figure out why the MCU is being added. If we manually dial out, there's no issue. My goal is to automate all of the dialing, though.
Any pointers? I've put some of the settings from TMS>Admin Tools>Configuration>Conference Settings below.
Solved! Go to Solution.
Thanks for the suggestion!
I dropped the bandwidth down to 768kbps, removed the MCU from the list of participants, and then clicked on "connection settings" to verify things were as they should be. The MCU popped into the list again.
Did you try that for a conference that already had been saved? If so, TMS won't remove the MCU from the route, as TMS has no way of knowing if it was added explicitly by the user or not.
Did you try the same for a brand new conference, i.e.:
I figured it out! I need to lower the conference bandwidth. I had tried simply changing this already, but figured out the process to change conferences that are already scheduled:
Thank you so much for pointing me in the right direction!
Curious. For the scheduling options that are checked for the system you are telling to dial, are the options it supports checked? Go to the system in navigator, Settings>View Settings all the way at the bottom? Is the method at which you telling it to call, checked there?
That doesn't work either
I've tried setting it to "Only if needed" and "Always, except point-to-point"
Doesn't change anything.
When you schedule the conference, what is the protocol selected for the dial-out participant? Are you sure that your endpoint that will dial-out is proper registered using this protocol? Do you see it as "registered" when checking the endpoint into the "System >> Navigator"?
Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
Paulo, the problem was posted as solved about an hour before your post
The problem was bandwidth, not with protocol or registration.
I'm glad a more obvious solution is being investigated. Honestly, a pop-up warning "An MCU will be added because of bandwidth limitations. To avoid this, lower the conference bandwidth" (or somethiing to that effect) would be very helpful.
I noticed that 13.2.2 (the software version that I'm running) is not included in the list of releases affected by this. Should it be added? Or is 13.2.2 assumed to be affected because 13.1 is listed?