I had meet this problem already and here it is again with a new installation.
CME has public IP and ITSP SIP trunk. For this to work, SIP bind must not be configured, all works fine and there is two way voice with ITSP SIP trunk.
Problem is, customer also wants to use SIP client over IPsec VPN. For this to work, "sip bind all" must be configured with a LAN interface, otherwise router will source SIP packet with WAN address, making it fail.
What happens, is that once "sip bind all" is configured, RTP connections to ITSP will have the LAN as source, as if the NAT process is entirely skipped.for RTP packets That causes one way voice.
I had resolved this adding a VPN gateway router front end to CME, doing that all works fine.
Does anybody has an indea for have both SIP VPN clients, and SIP trunk work simultaneously with a same router ?
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...