I have a CUCM 4.2 and a 4.3 cluster. Each cluster has a remote site or two hanging off of it. Since the different clusters are the result of an acqusition, there is overlap in the dialplans. using an ICT we are appending additional digits to the front of the Calling Number but in order to get it to work properly we had to add the digits on the ICT. Thus we can only add digits for one site, and not the others. Although this works now, it is not scalable.
What I would like to do is SIP trunks between the 4.x Clusters. First trunk on port 5060, second on 5061 etc. I could then use manipulate the digits by send traffic from a specific site down a specific trunk. The question is, will this work?
Collapsing the clusters into one and upgrading is in the works, but is still a ways out.
Purchasing additional hardware is not an option at this time.
Additional acquisitions are possible which is why this is becoming an issue.
I don't follow. Regardless of protocol, you can establish multiple ICT trunks between one cluster andother clusters. Meaning, Cluster_A could have an ICT for Cluster_B and a separate one for Cluster_C, etc. etc. I don't think I follow the need for having multiple ICTs between two clusters. Can you clarify why you believe that would be necessary? Maybe provide some examples of what you are trying to overcome?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...