<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body 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?<br>
    <br>
    --paul<br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 11/15/2013 8:29 AM, Heim, Dennis
      wrote:<br>
    </div>
    <blockquote
      cite="mid:0CC57FCAB07CEB4595526952471493D360D0906B35@PRODCMS1.wwt.local"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:black;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:"Consolas","serif";
        color:black;}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:992491594;
        mso-list-type:hybrid;
        mso-list-template-ids:1872126230 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Courier New";}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Courier New";}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Symbol;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Courier New";}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:Wingdings;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <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.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <p class="MsoNormal"><b><span style="font-size:10.5pt">Dennis
                Heim | Solution Architect (Collaboration)</span></b><span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="font-size:10.5pt">World Wide
              Technology, Inc. | 314-212-1814<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="font-size:10.5pt"><o:p> </o:p></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"><o:p></o:p></span></p>
          <p class="MsoNormal"><b><span style="color:#1F497D"><o:p> </o:p></span></b></p>
        </div>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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 class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">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 class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
                <b>Subject:</b> Re: [cisco-voip] Local Route Route Group
                Design<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></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>
          <o:p></o:p></p>
        <div>
          <p class="MsoNormal">On 11/15/2013 5:45 AM, Heim, Dennis
            wrote:<o:p></o:p></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?<o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></p>
          <p class="MsoNormal">Here is my use case, if I am missing
            something, please let me know…<o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></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. <o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></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).  <o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></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:<o:p></o:p></p>
          <p class="MsoListParagraph"
            style="text-indent:-.25in;mso-list:l0 level1 lfo2"><!--[if !supportLists]--><span
              style="font-family:Symbol"><span style="mso-list:Ignore">·<span
                  style="font:7.0pt "Times New Roman"">        
                </span></span></span><!--[endif]-->Route List 1 (SFO)<o:p></o:p></p>
          <p class="MsoListParagraph"
            style="margin-left:1.0in;text-indent:-.25in;mso-list:l0
            level2 lfo2"><!--[if !supportLists]--><span
              style="font-family:"Courier New""><span
                style="mso-list:Ignore">o<span style="font:7.0pt
                  "Times New Roman"">   </span></span></span><!--[endif]-->Standard
            Local Route Group<o:p></o:p></p>
          <p class="MsoListParagraph"
            style="margin-left:1.0in;text-indent:-.25in;mso-list:l0
            level2 lfo2"><!--[if !supportLists]--><span
              style="font-family:"Courier New""><span
                style="mso-list:Ignore">o<span style="font:7.0pt
                  "Times New Roman"">   </span></span></span><!--[endif]-->SFO-PSTN-RG<o:p></o:p></p>
          <p class="MsoListParagraph"
            style="text-indent:-.25in;mso-list:l0 level1 lfo2"><!--[if !supportLists]--><span
              style="font-family:Symbol"><span style="mso-list:Ignore">·<span
                  style="font:7.0pt "Times New Roman"">        
                </span></span></span><!--[endif]-->Route List 2 (NYC)<o:p></o:p></p>
          <p class="MsoListParagraph"
            style="margin-left:1.0in;text-indent:-.25in;mso-list:l0
            level2 lfo2"><!--[if !supportLists]--><span
              style="font-family:"Courier New""><span
                style="mso-list:Ignore">o<span style="font:7.0pt
                  "Times New Roman"">   </span></span></span><!--[endif]-->Standard
            Local Route Group<o:p></o:p></p>
          <p class="MsoListParagraph"
            style="margin-left:1.0in;text-indent:-.25in;mso-list:l0
            level2 lfo2"><!--[if !supportLists]--><span
              style="font-family:"Courier New""><span
                style="mso-list:Ignore">o<span style="font:7.0pt
                  "Times New Roman"">   </span></span></span><!--[endif]-->NYC-PSTN-RG<o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></p>
          <p class="MsoNormal">In order to feed the local route group’s,
            we would need  separate PSTN translation patterns (<a
              moz-do-not-send="true" href="mailto:9.@">9.@</a>), with
            separate partitions and calling search spaces to feed  the
            different \+.! Route pattern. Is that how others are handing
            this scenario? <o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></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.<o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></p>
          <p class="MsoNormal">Thoughts?<o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></p>
          <p class="MsoNormal"><b><span style="font-size:10.5pt">Dennis
                Heim | Solution Architect (Collaboration)</span></b><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-size:10.5pt">World Wide
              Technology, Inc. | 314-212-1814</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="font-size:10.5pt"> </span><o:p></o:p></p>
          <p class="MsoNormal"><b><i><span style="color:#00007F">PS
                  Engineering: </span></i></b><i><span
                style="color:#00007F"> Innovate & Ignite.</span></i><o:p></o:p></p>
          <p class="MsoNormal"><b> </b><o:p></o:p></p>
          <p class="MsoNormal"> <o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:"Times New
              Roman","serif""><br>
              <br>
              <br>
              <o:p></o:p></span></p>
          <pre>_______________________________________________<o:p></o:p></pre>
          <pre>cisco-voip mailing list<o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre>
        </blockquote>
        <p class="MsoNormal"><span
            style="font-size:12.0pt;font-family:"Times New
            Roman","serif""><o:p> </o:p></span></p>
      </div>
    </blockquote>
    <br>
  </body>
</html>