The above debug line indicates that we are sending the RTP event on the outgoing leg. To verify, collect a packet capture off of the terminating device. It should show the RTP events. Only thing to watch out for is the non-standard payload type. Looks like whoever is sending the events is using 99. The default with Cisco devices is 101.
The above is assuming that we're looking at a CUBE set to do SIP on both call legs.
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...
[toc:faq]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 discusse...