<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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]--></head><body lang=EN-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I’ve been going over the design and advantages of implementing a fully globalized (+E.164) dialplan within a Cisco UC environment. The concept and configuration methods are clear to me and I like to sum up the concept as I understand it by saying: “Globalize the called number as close to the source as possible and localize at the destination.”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Implementing a simple \+! Route Pattern pointing to the SLRG and using Called Party Transformation Masks to localize(manipulate) on the PSTN gateway(s) has obvious benefits when thinking about AAR/CFUR and TEHO. However this gets complicated by the fact that in my area (Alberta, Canada) the Area Codes overlap long distance calling boundaries (ie: my local area code is 403, however not all 403 numbers are local and require to be prefixed with a 1).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This would force configuration of an unmanageable amount of called number translations to ensure local calls and long distance calls are formatted properly to the PSTN. For example: <a href="http://www.localcallingguide.com/lca_exch.php?exch=000480">http://www.localcallingguide.com/lca_exch.php?exch=000480</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Has anyone come up with solutions to this issue for true a true TEHO dial plan in this type of scenario? My next steps are to have discussions with the providers in the area (Telus, Bell) to see if their side can be set up to deal with this. Ie: Accept all 10 digit numbers in the 403 area code and complete the call even if it is a long distance rate.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Any comments are welcome.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Ryan <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>