<div dir="ltr">UCM 10 has changes in store to address this local route group limitation.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 15, 2013 at 11:35 AM, paul dial <span dir="ltr"><<a href="mailto:dialp@ucar.edu" target="_blank">dialp@ucar.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Yes, CER could be an issue. I think you would have the same issue
with redundancy in the RL - maybe break those patterns out
separately?<br>
<br>
FWIW, I'm also interested in your original question, "Has there
been any thought of a Local Route List feature in addition or
replacing the local route group option?" I don't understand why
Local Route Groups were chosen and not Local Route lists?<span class="HOEnZb"><font color="#888888"><br>
<br>
--paul</font></span><div><div class="h5"><br>
<br>
<br>
<br>
<div>On 11/15/2013 8:29 AM, Heim, Dennis
wrote:<br>
</div>
<blockquote type="cite">
<div>
<p class="MsoNormal"><span style="color:#1f497d">Thanks for the
reply. I think the only issue with that, is if CER is in
play from a failover/redundancy perspective.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt">Dennis
Heim | Solution Architect (Collaboration)</span></b><span style="color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt">World Wide
Technology, Inc. | <a href="tel:314-212-1814" value="+13142121814" target="_blank">314-212-1814</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:#00007f">PS
Engineering: </span></i></b><i><span style="color:#00007f"> Innovate & Ignite.</span></i><span style="font-size:13.5pt"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="color:#1f497d"><u></u> <u></u></span></b></p>
</div>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">mailto:cisco-voip-bounces@puck.nether.net</a>] <b>On
Behalf Of </b>paul dial<br>
<b>Sent:</b> Friday, November 15, 2013 10:14 AM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Local Route Route Group
Design<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Dennis,<br>
<br>
I ran into a similar situation and ended up moving the backup
from the RL to the RG. For example, our Local Route Group is
defined in the Device Pool (DP). So DP SFO would point to
RG_SFO. RG_SFO would contain the primary destination for SFO
and also a secondary location (in some cases we have more than
two members in the RG). Likewise DP NYC would point to RG_NYC
which would contain the primary destination for NYC and any
back up locations. <br>
<br>
I believe that will allow you to keep just a single RP for \+!
and your RL would look like RL_LocalCalls and just have the
Standard Local Route Group as a member and uses the RG that is
defined by the DP. Not sure if this is the best way of doing
it or what the exact implications are of moving the redundancy
from the RL to the RG.<br>
<br>
--paul<br>
<br>
<u></u><u></u></p>
<div>
<p class="MsoNormal">On 11/15/2013 5:45 AM, Heim, Dennis
wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Has there been any thought of a Local
Route List feature in addition or replacing the local route
group option?<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Here is my use case, if I am missing
something, please let me know…<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Dial Plan is E.164. We have translation
patterns that normalize the Called number. From there the
calls match at \+.! Route pattern the sends the call to the
gateway. The route list assigned to that route pattern
includes the following members: (1) Standard Local Route
Group (2) HQ-PSTN-RG. <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">The use case is this, what happens when
we have regional or different secondary destinations? If we
had some sites in the western US, that if their local
circuits were unavailable we wanted the calls to go through
a San Francisco regional site (SFO-PSTN-RG). At the same
time, we had some sites in the eastern US, that if their
local circuits were available we wanted the call to go
through a New York regional site (NYC-PSTN-RG). <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">As it is with local route group’s, we
would need to have multiple route pattern’s \+.! Placed in
different partitions, and assigned a different route list.
For our example we would have the following:<u></u><u></u></p>
<p><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>Route List 1 (SFO)<u></u><u></u></p>
<p style="margin-left:1.0in"><span style="font-family:"Courier New""><span>o<span style="font:7.0pt "Times New Roman""> </span></span></span>Standard
Local Route Group<u></u><u></u></p>
<p style="margin-left:1.0in"><span style="font-family:"Courier New""><span>o<span style="font:7.0pt "Times New Roman""> </span></span></span>SFO-PSTN-RG<u></u><u></u></p>
<p><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span>Route List 2 (NYC)<u></u><u></u></p>
<p style="margin-left:1.0in"><span style="font-family:"Courier New""><span>o<span style="font:7.0pt "Times New Roman""> </span></span></span>Standard
Local Route Group<u></u><u></u></p>
<p style="margin-left:1.0in"><span style="font-family:"Courier New""><span>o<span style="font:7.0pt "Times New Roman""> </span></span></span>NYC-PSTN-RG<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">In order to feed the local route group’s,
we would need separate PSTN translation patterns (<a href="mailto:9.@" target="_blank">9.@</a>), with
separate partitions and calling search spaces to feed the
different \+.! Route pattern. Is that how others are handing
this scenario? <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">If we had a local route list instead of
local route group, then that could be specified on the
device pool, and we could have one set of patterns and be
able to easily manage multiple failure path’s.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Thoughts?<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.5pt">Dennis
Heim | Solution Architect (Collaboration)</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.5pt">World Wide
Technology, Inc. | <a href="tel:314-212-1814" value="+13142121814" target="_blank">314-212-1814</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.5pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><i><span style="color:#00007f">PS
Engineering: </span></i></b><i><span style="color:#00007f"> Innovate & Ignite.</span></i><u></u><u></u></p>
<p class="MsoNormal"><b> </b><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span><br>
<br>
<br>
<u></u><u></u></span></p>
<pre>_______________________________________________<u></u><u></u></pre>
<pre>cisco-voip mailing list<u></u><u></u></pre>
<pre><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><u></u><u></u></pre>
<pre><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><u></u><u></u></pre>
</blockquote>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
</div>
</blockquote>
<br>
</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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>