TMS scheduled conference no auto connect via Conductor and TelePresenceServer

[dschmitz87]

Hi,

at the moment I am setting up a new video infrastructure. All components have the lateste software.

- SX-Endpoints are registered to CUCM

- CUCM has SIP trunk to conductor

- Ad.Hoc and Rendezvous conferences are working

- TS is managed by Conductor

- SX-Endpoints, Conductor and TS have been added to TMS

Now the problem. I am setting up a new conference in TMS and automatically the conductor will be added. Now I start the conference and the conductor tries to call the endpoints and the call fails. I thought conductor uses the trunk for rendezvous in order to dial out to cucm. Inbound CSS on the CUCM site has been configured. Do I need anything special on the conductor or TS?

If you need logs or something else just let me know.

Regards

Daniel

[Patrick Sparkman]

I don't know anything about CUCM, but in the Conductor logs, do you see it trying to tell the TelePresence Server to dial out to the endpoints?

[dschmitz87]

Hi Patrick,

on the Telepresence Server I see

2037 00:15:33.006 APP Info call 150: tearing down call to "1234@192.168.100.10" - destroy at far end request; timeout

2036 00:15:33.006 CMGR Info call 150: disconnecting, "1234@192.168.100.10" - timeout

2035 00:15:33.006 SIP Error call 150: Ending call due to INVITE transaction timeout

2030 00:15:00.927 APP Info call 150: new outgoing SIP call to "f997a3cd-e1d4-4abd-9649-a21d52a363e7@192.168.1.1:5073" from conference "5551000"

And on conductor I see:

conferencefactory.controller: Level="INFO" Event="The SIP address of an out-dialed participant will be overridden on the target conference bridge if the bridge supports the 'toOverride' parameter." Auto-dial_participant_address="f997a3cd-e1d4-4abd-9649-a21d52a363e7@192.168.1.1:5073" toOverride_sip_address="1234@192.168.100.10" UTCTime="2015-03-19 23:15:01,532" 

[Mike Assel]

Daniel, I'm having the exact same issue.  I followed the deployment guide to the the T.  Everything works except for out-dialing.  In my case I'm not using TMS scheduling yet (I will be soon), but I have an auto-dial participant configured.  I see the same error in my conductor logs.

Mike

[dschmitz87]

I found the solution. I had configured the SIP settings on TelePresence Server to use TCP instead of TLS. As soon as I changed the protocol, the calls worked fine.

[mguguvcevski]

Thanks Daniel for this hint. 

I also had everything configured with TCP, as soon as I changed Outbound transport to TLS under Configuration, SIP settings, calls to Auto-dialed participants started working. 

Thank you.

[Mike Assel]

And my resolution also turned out to be the same.  I had to get a TAC engineer involved to show me that I had missed that setting.  Oh well. :)