×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

CUBE for multiple SIP trunking

Answered Question

Hi Experts

can i a  use common CUBE infra for multiple customer SIP trunking requirements. For eg i want to deploy only a single CUBE router on my side with different loopbacks which in turn connect to different customer CUBE devices

Correct Answer by Manish Gogna about 3 years 2 months ago

Yes, as  explained in one of the posts that i mentioned

You will then need to use your sip bind commands at the dial-peer level. E.g

interface loopback1----------------------------------------Interface pointing to SIP provider 1
ip address 10.10.10.1 255.255.255.0

 

interface loopback2-----------------------------------------Interface pointing to SIP provider 2
ip address 20.20.20.1 255.255.255.0

 

dial-peer voice 10 voip
description “Primary path to SIP SP-1”
destination-pattern 91[2-9]..[2-9]......
session protocol sipv2
session target ipv4:10.10.10.2
voice-class sip options-keepalive
voice-class sip bind control source-interface loopback1
voice-class sip bind media source-interface loopback1

 

dial-peer voice 20 voip
description “Secondary path to SIP SP-2”
destination-pattern 91[2-9]..[2-9]......
session protocol sipv2
session target ipv4:20.20.20.2
preference 2
voice-class sip options-keepalive
voice-class sip bind control source-interface loopback2
voice-class sip bind media source-interface loopback2

If your DDIs are provisioned differently on these providers, you will need to use sip profiles to authenticate before you will be allowed to place outbound calls through them.

HTH

Manish

 

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Manish Gogna Wed, 06/04/2014 - 23:36
User Badges:
  • Cisco Employee,

Yes, as  explained in one of the posts that i mentioned

You will then need to use your sip bind commands at the dial-peer level. E.g

interface loopback1----------------------------------------Interface pointing to SIP provider 1
ip address 10.10.10.1 255.255.255.0

 

interface loopback2-----------------------------------------Interface pointing to SIP provider 2
ip address 20.20.20.1 255.255.255.0

 

dial-peer voice 10 voip
description “Primary path to SIP SP-1”
destination-pattern 91[2-9]..[2-9]......
session protocol sipv2
session target ipv4:10.10.10.2
voice-class sip options-keepalive
voice-class sip bind control source-interface loopback1
voice-class sip bind media source-interface loopback1

 

dial-peer voice 20 voip
description “Secondary path to SIP SP-2”
destination-pattern 91[2-9]..[2-9]......
session protocol sipv2
session target ipv4:20.20.20.2
preference 2
voice-class sip options-keepalive
voice-class sip bind control source-interface loopback2
voice-class sip bind media source-interface loopback2

If your DDIs are provisioned differently on these providers, you will need to use sip profiles to authenticate before you will be allowed to place outbound calls through them.

HTH

Manish

 

Actions

This Discussion

Related Content