Cisco CUBE Configuration

This guide will help you get your Cisco CUBE connected to SIP.US It was tested on a CUBE device with the external interface configured to use a private IP of This particular configuration is specific to the CUBE, should not be used on CME, and negates the need for any special callerID configuration. As long as you have a callerID on the extension, it should be used and pass to SIP.US using the configuration options below.

1. Configuring a sip profile

The item below takes the external IP of the CUBE in the FROM header of the SIP INVITE packet and translates it into a domain name which is resolvable by SIP.US. Failure to do this will result in the inability to make outbound calls.

     voice class sip-profiles 1
     request INVITE sip-header From modify "@172\.16\.1\.1\>;" ">;"


2. Creating the dial peer 

The dial peer configuration below assumes that the CUBE will receive 11 digits that are within the scope of the North American Numbering Plan. If you will only receive 10 digits at the CUBE level, you will need to prepend a 1 before sending it to SIP.US. SIP.US requires country code + number for all calls. In the U.S. and Canada this country code is "1." Please be sure to substitute the correct values for items between the carrots below (you will not need the carrots).

     dial-peer voice 1 voip
     description **Outgoing Calls to SIP.US SIP Trunk**
     destination-pattern 1[2-9]..[2-9]......T
     session protocol sipv2
     session target 
     voice-class sip dtmf-relay force rtp-nte
     voice-class sip profiles 1
     dtmf-relay rtp-nte
     codec g711ulaw
     no vad
     authentication username <yourtrunknumber> password 7 <yourtrunkpassword> realm


3. Creating a registration to SIP.US

The sip-ua statements below ensure that you will receive inbound calls from SIP.US and that when you make an outbound call, proxy authentication challenges are handled correctly. It also keeps the connection to SIP.US alive by sending a registration message about every 60 seconds. This is enough to overcome most firewall UDP timeout settings. Note however, that if you own a very aggressive firewall (Sonicwall is the most well known example to this author) it's UDP timeout may only be 30 seconds. You will want to increase that timeout, as the minimum registration interval accepted by SIP.US is 60 seconds. Again, please substitute correct values between the carrots and remember that the carrots are not necessary.

     credentials username <yourtrunknumber> password 7 yourtrunkpassword realm
     authentication username <yourtrunknumber> password 7 <yourtrunkpassword> realm
     retry invite 2
     retry register 10
     timers connect 100
     registrar 1 expires 360 refresh-ratio 20 auth-realm


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk