Support for Diversion Header in Cisco Emergency Responder
I'm troubleshooting an issue where it appears as though CER is sending an invalid Diversion Header to the AT&T SIP Trunking service. Having reviewed the trace I see the following:
The Request line (from the trace) looks fine--we can clearly see that the customer is attempting to call 911. But it looks as though whatever CER is doing to the Diversion header (populating it with 911 or 9911) is not an acceptable format for AT&T.
TAC advised the customer to configure a command under the sip-profiles in CUBE to either strip or ignore Diversion Header. The customer reported success with this approach. TAC also advised the customer that the CER was properly configured—thus it appears that the CER’s default behavior is to populate the Diversion Header with a format that the AT&T can’t support.
Is there a configuration within CER which will populate the Diversion Header with a 10 digit TN such as how it appears in the PAI?
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...