Telepresence Conductor

[RAMEEZ RAHIM]

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.

[dknightg]

Hi Rahim,

This does sound like some odd behaviour.

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.