Hello! We are trying to setup a SIP trunk on CME 4.2. Having done this a bunch of times before, we went about doing it the usual way. (no registration) Unfortunately, this particular carrier insists on using a non standard SIP Port. So instead of 5060, they are using 5070. I tried specifying a session target of ipv4:xxx.xxx.xxx.xxx:5070 on my dial-peers but that didn't work.
Debug CCSIP All shows nothing on inbound calls. If I do a debug ip udp, I can see the inbound traffic on port 5070, but CME does NOT recognize this as SIP traffic.
IP PBXs can access the PSTN using these types of trunks, but need a media gateway that converts the IP voice traffic to traditional PSTN, which sometimes can result in successive translation from IP domain to TDM domain. These successive translations increase the maintenance costs of the gateways, increases latency, and reduces voice quality.In order to avoid these problems, the IP PBXs use protocols for session initiation and management, the most prominent of which is Session Initiation Protocol (SIP).
Refer the following url for more information on configuring SIP Trunking on CME:
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...