We recently implemented a Telepresence Conductor in our Tandberg Video network for creating AdHoc conferences. We configured 2 MCU's under a MCU pool and Created a MCU service.
We created a conference template with 5 ports reserved for Cascade.
We dial in a number and a adhoc conference gets created in the Bridge. When the participant count reaches 14 on first blade, the bridge creates a cascade link to second MCU for the 15th participant to join on Second MCU.
So now we try to create a new adhoc conference by dialing a new number. But unable to create new conference, the VCS search history states that Conductor Policy rejected the call.
Even though we had enough free ports on the second MCU, why were we not able to start the second conference. Please suggest.
One thing I would be sure of is that when counting ports it is important to take the MCUs port capacity from conductor rather than the MCUs. This is because Conductor and the MCUs picture of port usage differs because conductor reserves ports for different functions.
That said the issue may lie with the configuration on the Conductor, are you sure the service preference linked to from the template used to create the second ad-hoc call includes both of the MCUs?
There may be some more clues as to why this occurs in the event log on the Conductor. Conductor should write down here why the conference request was rejected.
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: email@example.com 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 ...