To be honest, I'd not use RTMT for this. I'd stick to port mirroring and wireshark. Wireshark is real-time. RTMT imposses a large (relative) delay in getting at the traces. Plus, the RTMT logs will have bucket loads more stuff in there, so trying to tease out the bits you want is much harder.
I'd only investigate the RTMT SIP logs if you thought CUCM was mis-handling the SIP packets based on your configuration.
I would agree but unfortunately I have access to the CUCM cluster only. No access to switch infrastructure and no access to the Lync hardware. At this stage just knowing the SIP trunk was up would be a bonus.
Be sure to set the level of trace to detailed or debug and not just error. When you get the sdi traces from RTMT open one file in notepad++. There is an option to search files in the whole folder. Search the files for the called #. I search dd="xxxx", where xxxx is the called number. There will be a unique call id # assiociated with the call. Then you can search the file by that call id # and you will see the invite,trying, ok, and so on. You will also be able to check if the mesages are sent udp/tcp and what port they are on, default being 5060.
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...