07-27-2014 12:29 PM - edited 03-18-2019 03:13 AM
07-27-2014 02:28 PM
URI dialing was not added until CUCM 9.x. Every build before that only supports numeric dialing. If the call is egresses out of the cluster CUCM will suffix the numeric number with the CUCM node's IP address or the Cluster Top Level Domain if specified under System Enterprise Parameters.
07-27-2014 02:48 PM
Hi jonathan,
Thank for reply.
Actually we have SX 20 configured into CUCM 8.6.
CUCM 8.6 is connected with Virtual TP Conductor & TP Conductor is connected with virtual TP Server.
We have setup meet-me video conference. We have setup Route Pattern in CUCM for meet-me number, which is configured for SIP Trunk, which is pointing to conductor. When we dial meet-me number from SX20 its keep dialing only , not answering. .. we dial from web interface of sx20 it shows 6499@22.130.10.5 dialing.
in this situation do i need to split the dialed number 6499@22.130.10.5 from cucm ? how SX 20 will forward call to conductor & in which format conductor should accept calls 6499@22.130.10.5 or 6499 ?
Regards,
07-29-2014 04:28 PM
When you placed the call, did you enter '6499' or '6499@22.130.10.5' into the SX20? It should be the former, CUCM should have a route pattern and SIP trunk (not a SIP Route, just a normal Route Pattern). Also, make sure you have followed the steps outlined in the deployment guide for Conductor with CUCM.
07-30-2014 01:58 AM
Hello Jonathan,
Thank for replying.
Problem has been resolved. Issue was in my trunk configuration between Condcutor & CUCM only.
My conductor was configured for TCP protocol & my CUCM was configured as TLS (sip trunk security profile).
I configured both on same protocol & it worked.
Regards,
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: