SIP Trunk with Internet Provider

[dtran]

Hi all, hope everyone is well !!

I am looking into migrating my internet service to a new provider and this new provider also offers voice services over the internet via SIP trunk.

Could someone tell me what information I need from the service provider or what information I need to provide to the service provider to configure the trunk ?

Do I need any special licenses on the router for SIP ? I am using FXO ports on the router today and I am running CUCM 10.5

Thanks all in advance !!!

Danny

[Mohammed al Baqari · Accepted solution]

Hi Danny,

To start with you need to CUBE license depending on the number of concurrent calls. You can still configure CUBE functions on IOS if you have UC license without CUBE license but you need CUBE license for compliance and HA features.

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-cube-licensing.html

Now, it should be the other way around, i.e. your provider should provide you with the information to be configured on your CUBE (IOS Router). This information usually includes codec, early-offer/delayed offer, source IP, dtmf-relay. Some providers require authentication and registration which you can validate with yours.

[Chris Deren · Accepted solution]

Besides CUBE and licenses you need to consider security when connecting to internet based SIP provider as you need to decide if you are going to do NAT between your CUBE and their SBC across your firewall or assign public ip address on your CUBE and allow direct access to internet in which case I would recommend a firewall or ACLs behind the CUBE on your network to limit port access in case your CUBE is hacked.  NAT seems like a simply solution, however NAT does not play well with SIP traffic leading to one way audio do to embedded media IP address embedded without the SDP content of the SIP messages. Some vendor claim they can look into the SDP headers, but I stay away from NAT when dealing with SIP as much as I can.  If this seems like more than you can handle, I suggest your engage reputable Cisco partner as it may be easy to create the connection with poor security causing all kinds of issues down the line.