Thanks Teresa. I will try that next. Sometimes I can see in CUCM where the H323 is sending the signaling from one interface, but it expects it from another, which then tells me the customer did not bind the h323 to loopback interface, etc. (or something like that)
The source IP for that will be in hex. Ex: '0A0A0A01' is 10.10.10.1 in the H225 setup message as the 'SourceAddress' or something to that effect.
I would suggest doing a google for 'Triplecombo' or 'translatorx' for CUCM traces. It really makes them more digestable and is what a great percentage of TAC uses to analyze the traces - a couple of tools by Cisco employees.
You'll want to make sure the right check boxes are on - namely H323/H225, All Gateway, etc.
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...