<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>A couple of items to keep in mind; </div>
<div><br>
</div>
<div>1.) Can only be used on VOIP dial peers</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div><a href="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">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</a></div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
<div>Sent from my iPad</div>
</div>
<div><br>
On Oct 26, 2015, at 6:39 AM, Ed Leatherman <<a href="mailto:ealeatherman@gmail.com">ealeatherman@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">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.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Oct 26, 2015 at 5:42 AM, Boon <span dir="ltr"><<a href="mailto:ciscovoipuser@gmail.com" target="_blank">ciscovoipuser@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>I have a client who is planning on splitting their single CUCM cluster with CUBE and PSTN SIP into two separate clusters. <br>
</div>
<div>
<div><br>
</div>
<div>The challenge is that they want to share the CUBE solution and DID range between both clusters.</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Also, has anyone used this with a CUBE HA solution?</div>
<div><br>
</div>
<div>Any help appreciated. Thanks</div>
</div>
</div>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">Ed Leatherman<br>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</div>
</blockquote>
</body>
</html>