[cisco-voip] CUBE - Dial-peer multiple destination-pattern matching

[Walenta, Philip]

To add what has been said already - managing large scales of numbers in a router becomes very problematic.  The bigger your dial plan, the worse it gets.  It's far easier to let IME handle this automatically.

I've managed large scales before - and as Ryan said - it gets to looking like a toddlers playroom.  That cannot be understated.  The chance for errors in something like this grows almost exponentially.  You don't want to troubleshoot this many dial patterns if something isn't working.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Huff
Sent: Monday, October 26, 2015 7:12 AM
To: Ed Leatherman
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUBE - Dial-peer multiple destination-pattern matching

A couple of items to keep in mind;

1.) Can only be used on VOIP dial peers

2.) When you have multiple pattern matches, the match with the longest prefix is considered the matching criteria which does not necessarily have to be the most specific match.

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/dialpeer/configuration/15-mt/vd-15-mt-book/vd-mdp-dialpeer.pdf

Unless there is an underlying reason for MPS I would suggest a SME or just stand up an IC/SIP trunk between the clusters and kick on ILS. The justification for SME would be scalability and number of connected calls.

Where MPS has served me well is in a deployment with an insane amount of e164 numbers. It allowed me to exceed the "rule of 15" for voice translations on the router and also do some aggressive summarization without having to make CCM's numplan stack look like a toddler's playroom.

Sent from my iPad

On Oct 26, 2015, at 6:39 AM, Ed Leatherman <ealeatherman at gmail.com<mailto:ealeatherman at gmail.com>> wrote:
I don't have any experience with the file based patterns. If they have room for a few more VM's, putting SME in the middle and hang CUBE off of that might be another way to do it cleanly. Then ils could take care of those patterns.

On Mon, Oct 26, 2015 at 5:42 AM, Boon <ciscovoipuser at gmail.com<mailto:ciscovoipuser at gmail.com>> wrote:
I have a client who is planning on splitting their single CUCM cluster with CUBE and PSTN SIP into two separate clusters.

The challenge is that they want to share the CUBE solution and DID range between both clusters.

I can see an opportunity here to use the IOS dial-peer feature 'Multiple Destination Pattern' matching using a file hosted in the router flash.

Although the configuration looks pretty straight forward I wanted to find out if any of you guys had deployed this feature and whether there are any gotchas to be aware of? I'm aware of the minimum IOS version requirement. I'm wondering whether file maintenance can become an issue.

Also, has anyone used this with a CUBE HA solution?

Any help appreciated. Thanks

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip



--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151026/e60adfa2/attachment.html>