vTS Conductor unable to create conference

[Austin Lutz]

Has anyone come across this error in vTS Conductor? I am using TCP from Conductor ---> vTS in the lab for testing. 

TelePresence Server's license capacity exceeded: An individual TelePresence Server's license resource is insufficient to create a conference

I have applied the following licenses to vTS and none to Conductor. (Running it in demo mode). Because of this error, it is not allowing conference creation. Any ideas?

Virtual Machine activation 
Encryption 
Third party interop
License keys TS screen licenses x 5 

[Patrick Sparkman]

You say you're using TCP from Conductor to vTS,  you need to be using TLS, which is why Encryption is required on the TPS.

Can you provide us a screenshot of your conference template you're trying to use for the conference?  What types of endpoints are you testing with?

[Austin Lutz]

Patrick,

I've changed it from TCP to TLS from conductor to vTS per your recommendation. 

My endpoints are (2) 9971s and (1) DX80. Attached is the conference template on conductor

[Jonathan Robb · Accepted solution]

Hi,

Try changing your max number of cascades to 0 and test that out, also max number of screens would generally be 3 or 1, unless using an actual 4 screen system.

Your template is set to reserve 10 ports per conference which looks like its going to overwhelm your available 5 screen Licenses

-Jonathan

[Patrick Sparkman]

Jonathan beat me to it, but as he mentioned you should reduce your number of cascades, keep in mind that for every cascade will consume 1 video port license, and If you're not planning on using multi-screen systems you should reduce the maximum number of screens to 1.

[Austin Lutz]

Thanks guys! I'm definitely making some head way with this. The conference now gets created after changing cascades to 0.

Now I'm getting this message, along with 3 way audio, but only 2 way video. 

conferencefactory.controller: Level="INFO" Event="A conference has been successfully created on the conference bridge and is ready to receive participants." Conference_display_name="001035010042-0x6943dbb335183cf4" Conference_name="001035010042-0x6943dbb335183cf4" Conference_template_name="Conference Template 1" Conference_unique_identifier="96a68f685dfb51a32f7cdcddc77c68e386fbac8c" Conference_bridge_address="172.16.54.140" Conference_bridge_conference_name="001035010042-0x6943dbb335183cf4" Conference_bridge_UUID="849f8d65-1f38-4c74-a191-1dbd87d9cff7" Process_time="0.0786948730238" Request_unique_identifier="f3d78e21-3f9b-11e5-9641-7b2aeec45806" Requester_(VCS/Unified_CM/client)_address="172.16.54.12" UTCTime="2015-08-10 20:11:14,893"

I inititated the AdHoc conference from the dx80, bringing in both 9971s one at a time. Any other ideas on this?

[Jonathan Robb]

Hi Austin,

Could you advise what is the full version of CUCM you are running just to rule out one possible issue with 9971 phones using video based MRG.

Also, if all three endpoints (DX and two 9971) show as in the conference on the TPS itself,  it could be a bandwidth issue where the 3rd endpoint drops back down to audio to get under a bandwidth limitation between locations.

-Jonathan

[Austin Lutz]

Jonathan,

10.5.2 SU2A is our current version. 

All 3 endpoints are located in the same location.