The solution to this was two fold. First, the connection between TS and Conductor has to be port 5061 TLS. This does not mean you need to upload certs or anything, you just have to select TLS and 5061 on both TS and Conductor. After we made that change (still using port 60 TCP with our CUCM trunk) the CTS system could call and not get fast busy...but it would not connect. I got on with TAC and they went into enterprise service parameters, changed the SIP Max incoming message size to 11000 (was at 5000). Apparently the TS uses a larger SIP message size and it needs this setting expanded in CUCM. After that calls worked! Here is a more detailed message about what TAC helped with. Good job TAC on this one.
Calls scheduled through TMS for conductor are not connecting.
Telepresence Server Event Log:
Tearing down call from "4000" - destroy at far end request; remote teardown.
Resolution Summary:
Configure communication between the Telepresence Server and Conductor to use TLS over 5061
Telepresence Server:
- Enabled 5061/TLS in Network Services
- SIP Settings configured to TLS
Conductor:
Conference Bridge Configuration to 5061
CUCM:
In the CUCM Service Parameters>Advanced
SIP Max Incoming Message Size configured is configured for 5000 and needs to be at least 11000.
Cisco Unified Communications Manager with Cisco VCS (SIP Trunk) Deployment Guide Cisco VCS X8.5 Unified CM 8.6.x, 9.x, 10.x.
Pg. 32 Checking Unified CM message size limit http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-5/Cisco-VCS-SIP-Trunk-to-Unified-CM-Deployment-Guide-CUCM-8-9-10-and-X8-5.pdf
