I have minimal experience in CUBE, I need to configure SIP Trunk for a customer in couple of days so I need some help. Here is their setup, customer has MPLS router at their HQ to connect to all the remote branches, in the same MPLS router customer is adding the SIP from the same SP. I got the SIP information from the SP and need some clarifications from the experts what I need to do on the MPLS/CUBE router. Here are the information I got from SP
(All IP's are for eg. )
Customer IP : 184.108.40.206
SP SBC IP : 220.127.116.11 port 5060
RTP IP and Port range : 18.104.22.168 (port 8000 - 39998)
Firewall ports open 22.214.171.124/28
My question is
1. Do I need to configure the customer IP (126.96.36.199) as a loopback address and bind that interface to SIP traffic going to SP?
2. Do I need to configure another private IP as another loopback address and bind that to CUCM traffic?
3. What should be done to route this SP provided IP's to make the calls go through?
Please find the responses to your questions below...
1) this depends on what ip address your provider expects to see. Most providers allow sip traffic into their network only if they see an ip address they recognise.
2) not required . Just make sure that on the callmanger sip trunk page the ip address mentioned is the ip address of the cube that callmanger can reach . Same applies to the session target mentioned in the sip dialpeers on the cube.
3) i) configure an outbound sip dial -peer with the ip address of sip provider this will help in routing of oubound calls
ii) If your provider has asked for autentication then sure that in your sip user agent configuration you have the sip service provider's ip address listed and have the correct credentals.
Here is a configuration example that has all the configuration examples of what I have explained. It covers all the basics and configuration....
Thank you so much for your response. We got the SIP trunk working fine now, we ended up creating customer IP as a loopback and advertise on the BGP side and added some inbound prefix for SP IP's to come in and I also have to change the SIP trunk IP address on the CM as the customer IP to make the call go through in and out. Now I'm battling with t38 fax on the SIP trunk which I think we can fix it soon.
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...