Notifications

Cisco CUBE Single provider but two separate Signaling ip's for different DID/DDI  

  RSS

joeyitnerd2009
(@joeyitnerd2009)
New Member
Joined: 4 months ago
Posts: 2
27/11/2019 3:36 pm  

 H! I have a real world question that maybe you can perhaps guide me through.

I have a London +44 ######### site that has been in production for a few years with a cube configuration and Colt the ITSP (sip-server ip4:84.14.x.x).We’re now opening a Dublin Ireland site +353 ######### and we need voice  connectivity but our Ireland datacenter isn’t ready and since we’re using the same provider colt we can leverage our circuit in London.... leveraging the same cube public ip to the carrier, but they provided us a new signaling ip. Is it possible to use separate signaling ip’s for 212.36.x.x aka sip-server ip4:212.36.x.x on the cube? 


Quote
Pasha Teplitsky
(@pasha)
Member Admin
Joined: 4 years ago
Posts: 23
27/11/2019 4:40 pm  

It seems that the functionality that you are looking for is the Multi-Tenancy on CUBE and it's available starting from versions
Cisco IOS 15.6(2)T
Cisco IOS XE Denali 16.3.1

In a nutshell, you are basically replacing the sip-ua configuration with voice-class tenant config so it would look like something like that:

before CUBE multi-tenancy:

sip-ua
registrar 1 ipv4:1.1.1.1 expires 3600
credentials username abcde password 7 123123kjhkjh realm ucpros.net
authentication username abcde password 7 123123kjhkjh

voice service voip
bind control source-interface GigabitEthernet0/1

After CUBE multi-tenancy:

voice class tenant 1
registrar 1 ipv4:1.1.1.1 expires 3600
credentials username abcde password 7 123123kjh  realm ucpros.net
authentication username abcde password 7 123123kjhkjh
sip-server ipv4:1.1.1.1
bind control source-interface GigabitEthernet0/0

voice class tenant 2
registrar 1 ipv4:2.2.2.2 expires 3600
credentials username bbaasdadbb password 7 123jkh123kjh realm ucpros2.net
sip-server ipv4:1.1.1.2
bind control source-interface GigabitEthernet0/1

 

Does it make sense?


ReplyQuote
joeyitnerd2009
(@joeyitnerd2009)
New Member
Joined: 4 months ago
Posts: 2
29/11/2019 8:21 pm  

@pasha

Our ITSP doesn't require authentication (username and pw) since a straight handoff from our network to the itsp.  I like the mutlitenant config, but isn't that a use case for two separate ITSP? In this case it's the same provider just different locations (London and Dublin, so i was thinking something like multiple-registrar feature? I could be just way off 🙂

 

Current config:

sip-ua

registrar 1 ipv4:84.14.x.x

registrar 2 ipv4:212.36.x.x

 

 

 

 

 


ReplyQuote
Pasha Teplitsky
(@pasha)
Member Admin
Joined: 4 years ago
Posts: 23
03/12/2019 6:18 pm  

@joeyitnerd2009

I think that using the multi-tenancy feature will give you the flexibility of using a 'tenant' per dial-peer like so:

Device (config)# dial-peer voice 1 voip
Device (config-dial-peer)# voice-class sip tenant 1

It really doesn't have to be different ITSPs, just another way to separate and differentiate configs.

This post was modified 4 months ago by Pasha Teplitsky

ReplyQuote
Share: