Sip calls from CME sent to Provider with wrong header...
I have an issue with a CME 7.0 on a 2821 platform. This customer is currently using E1 PRI to dial outside but he would like to try Sip call from local provider. So I did the configuration of the SIP Trunk. My gateway is registered and incoming calls to ephone ( sccp ) are working.
However I noticed a strange behaviour with outgoing call.
Here is what happen:
Cisco 7941 SCCP phone with extension "91" (registered to CME) place a call over the SIP trunk.
If I make a debug ccsip message, I can see the first packet sent (which is INVITE) has a completely wrong header (I believe):
So IOS will not be able to match the transaction and perhaps will trash these (debug ccsip all wil confoirm.) It is as if no response was received to our Invite and that's why we see so many Invite (re)transmission.
Also note that the VIA header in 1xx responses are also invalid:
You should check with the SIP provider on above but first check if ITSP can get to GW IP 10.10.10.254 or is it being NATed? What other devices are there between the GW and ITSP ? See if they can pull a trace on their end and compare with this to see how the headers look/what IP addrs. show up in there.
Re: Sip calls from CME sent to Provider with wrong header...
Thanks for your analysis.
We have a Cisco ASA between the 2821 and the SIP Provider. I'm not sure this device is responsible of the wrong Sip packet since incoming calls are working fine, but we'll have a look. We have a conf call tomorrow with the Provider in order to compare the packets on the two sides.
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...