Created by: Raymond Ng on 18-12-2013 06:33:55 AM At the moment we are testing a Conductor and it's api capabilities with multi screen endpoints. When adding a participant to a meeting it is possible to define the factoryNumScreen attribute.
As we are using a Telepresence Server behind the Conductor and multiscreen endpoints we set the factoryNumScreen to 3. When dialling out to any endpoint. The conductor template has the setting "Optimize resources". When the "Optimize resources" is enabled resources should be freed under certain situations. These situations are:
If an endpoint only supports a lower quality than defined in the conference template for one of the following settings:
Participant quality
Guest quality
Chairperson quality
If an endpoint that uses the TelePresence Conductor's external policy server interface to dial into a rendezvous conference supports fewer screens than defined in the template under Maximum screens.
If an endpoint that is escalated into an ad hoc conference supports fewer screens than defined in the template underMaximum screens.
It is not clear to me what a "rendezvous conference" is and what "escalated into an ad hoc conference" means. When adding a single screen participant to a Telepresence server room behind a conductor with a template that has "Optimize resources" enabled and passing factoryNumScreen is 3 we hoped that 2 of the screenlicenses would have been "released".
After testing this it seems that no screenlicenses are released.
Our test environment looks like this: 1x Conductor XC 2.2.1 1x TelePresence Server 8710 (8 screen licenses) 1x TelePresence Mcu 4210 1x VCS Control X7.2.2
And a few endpoints - EX90 - EX60 - E20 - T150 MXP - Jabber for telepresence
We created a "Conference Template" and a "Conference Alias" on the Conductor with the following settings: ConferenceType: Meeting Call Polict mode: Off Limit nr participants: unchecked Limit conf duration: unchecked participant quality: Full HD Allow multiscreens: Yes Maximum screens: 3 Optimize Resolution: Yes
We diall single screen participants with the factoryNumScreen on 3 .The first 2 participants joined the conferenceroom without any problems. When dialing the third one the Conductor returns the message "Could not grow conference". Even afer waiting a couple of minutes the Conductor return the "Could not grow conference" when dialling the third participant.
The reason we don't pass the correct factoryNumScreen is because we just don't always know the amount of screens behind a videoaddress.
What are we doing wrong or is this expected behavior?
Subject: RE: Conductor and Optimize resources Replied by: Raymond Ng on 20-12-2013 02:07:58 AM I have received a response from the Conductor Team:
Today inbound calls are optimised, however, out dial participants are not optimised. This means that if you're using the 'magic' factoryNumScreens parameter set to 3 then 3 screens worth of capacity is reserved for the duration of the connection.
It's something we have on the backlog to resolve, but it won't be in the next release of software
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
