01-26-2016 01:27 AM - edited 03-18-2019 05:29 AM
Hi;
I am using Telepresence Server with TP conductor and Cisco VCS. I have 3 screen licenses and I am using the below mentioned parameters for calling which will use 1 and 1/2 license per call which means that only two participants can talk to each other in a conference as 1+1+1/2+1/2 = 3. The problem is that when the 2nd participant tries to join the meeting, it doesn't let him to do that. I checked the licenses on TP conductor and it says 79% of utilization.
Any help will be appreciated.
1080p30 |
Stereo |
720p30 |
1 and 1/2 |
Solved! Go to Solution.
01-27-2016 11:31 AM
How many TP servers do you have? If you have only 1 TP server, there's no need for you to set the maximum number of cascades configured on the Conductor conference templates. This would be your problem since it will affects the resources that are reserved on the primary TP server for connections to additional conference bridges but in your case you don't have.
Set the value to 0 in this case.
regards,
Acevirgil
01-26-2016 04:18 AM
What are the endpoints joining in the conference?
TP server firmware version?
Conductor firmware version?
VCS firmware version?
Could you also share the screenshot of conference template configuration on the Conductor that this conference is utilizing.
Under Conference configuration > Conference templates
regards,
Acevirgil
01-26-2016 09:25 PM
01-27-2016 11:31 AM
How many TP servers do you have? If you have only 1 TP server, there's no need for you to set the maximum number of cascades configured on the Conductor conference templates. This would be your problem since it will affects the resources that are reserved on the primary TP server for connections to additional conference bridges but in your case you don't have.
Set the value to 0 in this case.
regards,
Acevirgil
01-28-2016 02:57 AM
After setting value of cascading from 1 to 0 it worked. Yet there is another issue which is not regarding licensing.
Today I created a new search rule on vcs i.e test@ny.com and the same alias i created on tp conductor but when I am calling from any endpoint, the call is rejected.
As per the logs on vcs, it says that "Call Rejected" and "No detail found"
Regards,
01-28-2016 03:17 AM
Could you tell us what is your current dial plan for the conference aliases?
Could you also share a screenshot on how you configured your search rules on the VCS targeting Conductor as neighbor zone.
regards,
Acevirgil
01-28-2016 05:21 AM
01-28-2016 08:29 AM
Is the conference template and alias set to allow the conference to be created?
You can check your Conductor dial plan by going to Maintenance > Tools > Check dial plan. This will tell you what an incoming call into Conductor will do, what conference alias it matches if any, and what conference template it will use.
Also, it's recommended that any VCS search rule that is routes to Conductor, should be set to Stop on successful match.
02-01-2016 05:05 AM
It worked after putting the alias in parenthesis as the conference name was "\1"
01-26-2016 05:30 AM
Most issues like this are related to an incorrectly configured conference template, as Acevirgil mentions, please provide a screenshot of the conference template that you're using.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide