Solved: CUBE for multiple SIP trunking

ambi · ‎06-04-2014

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

Manish Gogna · ‎06-04-2014

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

View solution in original post

Manish Gogna · ‎06-04-2014

Hi,

Multiple SIP trunks terminating on same CUBE is possible. Please check the following posts for details

https://supportforums.cisco.com/discussion/11734001/cisco-cube-multi-sip-trunks

https://supportforums.cisco.com/discussion/10556546/multiple-sip-trunks-single-cube

HTH

Manish

ambi · ‎06-04-2014

Manish

i do not have multiple SIP trunks . Here is a sample topology of what i plan to do

Will this work

Manish Gogna · ‎06-04-2014

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

Bekzod Fakhriddinov · ‎03-28-2018

Manish, that config is for outbound dial-peer, BUT how will look inbound dial-peer from 2 ISP at this case?