We have a Cisco 2811 at a remote site that is connected to our hub via a VPN. We are interested in terminating a service provider SIP trunk onto this 2811 using CUBE so phones at the remote site can use the SIP trunk on the 2811 as their gateway. The problem that I'm having relates inbound calls. Calls come in from the SIP trunk and appear to be terminated correctly. The problem is that when the call setup is attempted with CUCM, the source address in the SIP header is the public IP address on the 2811. It needs to be the internal IP address (assigned to loopback0). I see that I can change the SIP binding address and also re-write the source address in the SIP header, but the problem is that this applies to all traffic. If I bind SIP to the loopback0 (with the private IP), then incoming SIP calls from the service provider break. If i re-write our public IP address in the SIP header, then again everything breaks.
How can the SIP headers between the serviced provider and our 2811 use a public IP as the source address and the SIP headers between our 2811 and CUCM use an internal address?
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...