That makes sence, and I do understand all that. Normalizing dialpatterns etc. But I guess my question is how does this make it easier than using the traditional way w/o LRG? Seems to involve just as much, if not more, effort to account for all these other types of calls. <br>
<br><br><br><div class="gmail_quote">On Wed, Nov 18, 2009 at 12:04 PM, Ryan Ratliff <span dir="ltr"><<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="word-wrap: break-word;">It's not an LRG issue as much as your dialplan not taking this situation into account. You can use called party transformations to manipulate digits all kinds of ways. For example on your New York gateway you have a transformation pattern that says if the called party number is 10 digits but doesn't start with 212, prefix a 1 onto it.<div>
<br></div><div>You could also use toll bypass and let all calls to the Atlanta numbers route as 10 digit calls via your Atlanta gateway.</div><div><br><div>
<span style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><div>
-Ryan</div></span>
</div>
<br><div><div><div></div><div class="h5"><div>On Nov 18, 2009, at 11:18 AM, Nick Marus wrote:</div><br>When using local route groups (lrg) with call forwarding. CM7.13 seems to send the forwarded call out the originating device and likewise screws up local/longdistance dialing.<br>
<br>Example, user A in atlanta has phone forwarded to 10 digit local (9+10) number. call forward css utilizes local route groups. user B in newyork, calls user A, and the call attempts to dial out the ny gateway (9+10). It fails as the 10 digit number is not dialable from ny and would need to be 11.<br>
<br>Is there a way around this? without creating new cfwd-css for the phones, which would imo nullify any advantage of lrg.<br><br>Thanks, <br clear="all"><br>-- <br>Nick Marus<br><a href="mailto:nmarus@gmail.com" target="_blank">nmarus@gmail.com</a><br>
</div></div>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">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>
</div><br></div></div></blockquote></div><br><br clear="all"><br>-- <br>Nick Marus<br><a href="mailto:nmarus@gmail.com">nmarus@gmail.com</a><br>