Like this, multiple CUCM clusters are pointing the QSIG ICT towards GK.
With this scenario calls are not going through from a phone in CUCM towards phone in other side and as we know, this is because Annex M1 not yet implemented in H323 or in any other protocol, Due to this we are creating another topology as mentioned below.
Phone --- CUCM -- Non QSIG ICT GK --- GW ---- H323 PRI GW --- Phone
Due to this case the number of trunks to GK has become almost doubled, 1 for QSIG and another for Non QSIG. we don't want to over load the GK as well
Just wondering is there any possibility for GK.
1) To route only QSIG calls between clusters and not to Gateways
2) And by removing the QSIG feature send the call to GW so there is no need of additional Non QSIG trunk to GK from the CUCM clusters.
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...