I've configured a SIP trunk for an IXC and am recieving an error from the carrier that there is an error in my configuration. The SIP trunk itself is pretty straightforward except for a source port set to 5061 (5060 is already taken by another device.) Since I'm getting an error from the IXC side, I assume that connectivity itself isn't an issue. Can someone suggest something I should look for?
After a packet sniff I found out what the issue was. The IXC I am using does not support CallManager so you will likely not be able to get configuration support from them (they are very Asterisk-friendly.) All you have to do is configure the Caller ID DN field in the Outbound Calls section of the SIP trunk with les.net's Peer Name field. That's pretty much it. When the trunk tries to build a connection to the IXC for the outbound call, it uses and authorization format of peername@publicipaddress for authentication. When you log into your IXC peer you can configure the Outbound Caller ID there.
Oh, and when you set up your DTMF mode, choose "auto" from the drop-down box.
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...