Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Per number call routing

Hi all,

We see quite a lot of customer chosing to have both a PSTN (fixed number) SIP trunk and a mobile phone number SIP Trunk. Both from different providers. The mobile phone number SIP trunk is often a closed user group with a specificly pre negotiated pricing.

From the CUCM it would be quite simple to route fixed numbers to provider A and mobile phone numbers to provider B. But when there is also a contract negotiated with provider A for a certain call volume a specific call routing requirement becomes in place.

What needs to be done is to make sure a certain number of (non-continues) mobile phone numbers needs to be routed to provider B and all the other mobile phone numbers to provider A. There is no way in finding a way to summarize or find any routing logic in the phone numbers. They need to be routed individually.

What is the best way to implement this and of course maintain the solution.  The list of phone numbers will be altered (monthly I guess) and should be able to be reloaded quite easily.

I have not found a way to do this within CUCM other then creating a huge list of translation patterns, prefixess, etc. Maybe the solution must be found within Cisco UBE of maybe even an other (vendor's) application.

Looking forward and kind regards

Sijbren Beukenkamp

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Per number call routing

Whatever solution you apply on-prem is going to come with a lot of editing. I assume you are going to define an operational procedure and a role for an internal resource to manage the data. If you are using h323 or SIP gateways/CUBEs then you may want to consider leveraging a feature that Cisco added to the ISRs (and ASRs) called "Multiple Destination Pattern Support on Voice Dial-Peer". 

Here is a reference for the ASR that provides a decent overview. I have used this on ISRs, too.

http://www.cisco.com/en/US/docs/ios-xml/ios/voice/cube_fund/configuration/xe-3s/asr1000/vd-mdp-dialpeer.html

The basic idea is that you can configure a dial-peer to reference a pre-defined list of patterns to match the destination-pattern. This list can be defined locally on the router or it can be read from an off box web server. The latter method lends itself to some automation for your ops personnel that may make life easier.

Of course, no matter how you cut this the volume of edits and the number of patterns you have to manage could get out of hand quickly. So, make sure that once you have a handle on the tools available to you that you work through the full lifecycle of your process before you commit on the final solution.

HTH

-Bill
(b) http://ucguerrilla.com
(t) @ucguerrilla

Please remember to rate helpful responses and identify helpful or correct answers.

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

4 REPLIES

Re: Per number call routing

Just create an access code for each provider and any number can be route to different vendors

Sent from Cisco Technical Support iPhone App

Voice CCIE #37771
New Member

Re: Per number call routing

Hi,

That is not going to work. Within the Netherlands the mobile phone number is formated +316XXXXXXXXX. As numbers can be moved between operators there is no way the differentiate a phone number and allocated it to a specific provider/vendor.

/Sijbren

New Member

Re: Per number call routing

Hi William,

This is probably what I am look for. We are using SIP on a Cisco UBE device.

Thanks!

Is there a way to schedule the load/import of the text file when using URL?

Totally agree that the operations part is a key influencer whether or not to utilise the solution. As most of the UBE devices are onpremises I am thinking or creating a script which queries an LDAP server (Microsoft AD i.e.) and generate the text file. The only thing which needs to be looked at is loading the file on the UBE.

Is there a maximum number of e164 numbers which can be loaded?

/Sijbren

Re: Per number call routing

Whatever solution you apply on-prem is going to come with a lot of editing. I assume you are going to define an operational procedure and a role for an internal resource to manage the data. If you are using h323 or SIP gateways/CUBEs then you may want to consider leveraging a feature that Cisco added to the ISRs (and ASRs) called "Multiple Destination Pattern Support on Voice Dial-Peer". 

Here is a reference for the ASR that provides a decent overview. I have used this on ISRs, too.

http://www.cisco.com/en/US/docs/ios-xml/ios/voice/cube_fund/configuration/xe-3s/asr1000/vd-mdp-dialpeer.html

The basic idea is that you can configure a dial-peer to reference a pre-defined list of patterns to match the destination-pattern. This list can be defined locally on the router or it can be read from an off box web server. The latter method lends itself to some automation for your ops personnel that may make life easier.

Of course, no matter how you cut this the volume of edits and the number of patterns you have to manage could get out of hand quickly. So, make sure that once you have a handle on the tools available to you that you work through the full lifecycle of your process before you commit on the final solution.

HTH

-Bill
(b) http://ucguerrilla.com
(t) @ucguerrilla

Please remember to rate helpful responses and identify helpful or correct answers.

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

117
Views
0
Helpful
4
Replies
CreatePlease to create content