<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:x="urn:schemas-microsoft-com:office:excel" 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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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-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;}
--></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-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Since not everything supports the + yet (actually maybe 8.6 finally fixed the hold outs) you will find yourself translating back/forth into and out of E.164.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I like E.164 without the plus based on Cisco Advanced Services rollouts, see third option in the SRND “Variable Length Dial Plan with Flat Addressing”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Interested in see what carrier says about your routing Intralata calls as LD without requiring the user to dial 1, I’m seeing a similar issue in Houston with long distance Intralata calls being 11 digits vs 10 digits in a E.164 setup.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";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"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Roger Wiklund<br><b>Sent:</b> Thursday, February 02, 2012 6:23 PM<br><b>To:</b> Ryan Schwab<br><b>Cc:</b> cisco-voip@puck.nether.net<br><b>Subject:</b> Re: [cisco-voip] E.164 Globalized Dialplan - Localizing on the egress<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><br><br>On Thu, Feb 2, 2012 at 10:55 PM, Ryan Schwab <<a href="mailto:schwaby81@shaw.ca">schwaby81@shaw.ca</a>> wrote: <br>> I’ve been going over the design and advantages of implementing a fully<br>> globalized (+E.164) dialplan within a Cisco UC environment. The concept and<br>> configuration methods are clear to me and I like to sum up the concept as I<br>> understand it by saying: “Globalize the called number as close to the source<br>> as possible and localize at the destination.”<br>><br>><br>><br>> Implementing a simple \+! Route Pattern pointing to the SLRG and using<br>> Called Party Transformation Masks to localize(manipulate) on the PSTN<br>> gateway(s) has obvious benefits when thinking about AAR/CFUR and TEHO.<br>> However this gets complicated by the fact that in my area (Alberta, Canada)<br>> the Area Codes overlap long distance calling boundaries (ie: my local area<br>> code is 403, however not all 403 numbers are local and require to be<br>> prefixed with a 1).<br>><br>><br>><br>> This would force configuration of an unmanageable amount of called number<br>> translations to ensure local calls and long distance calls are formatted<br>> properly to the PSTN. For example:<br>> <a href="http://www.localcallingguide.com/lca_exch.php?exch=000480" target="_blank">http://www.localcallingguide.com/lca_exch.php?exch=000480</a> <br>><br>><br>><br>> Has anyone come up with solutions to this issue for true a true TEHO dial<br>> plan in this type of scenario? My next steps are to have discussions with<br>> the providers in the area (Telus, Bell) to see if their side can be set up<br>> to deal with this. Ie: Accept all 10 digit numbers in the 403 area code and<br>> complete the call even if it is a long distance rate.<br>><br>><br>><br>> Any comments are welcome.<br>><br>Hi,<br><br>I'm in the same boat as you. While E.164 globalization is the way to<br>go I have come a cross two major problems:<br><br>SIP trunks: getting more and more common but the way most ITSPs<br>authenticate calls, it's just impossible to normalize calling/called<br>numbers with just one SIP-trunk. You need multiple trunks to be able<br>to have site specific outbound transformation patterns. I have solved<br>this with multiple SIP-trunks to the same CUBE, using SIP security<br>profiles with incrementing SIP ports.<br><br>Countries with open dial plans: This is a real pain. Perhaps if you<br>are in US or in France or whatever with closed dial plans where you<br>always have to dial area codes this is easy peasy. But I'm in Sweden<br>and we have an open dial-plan so you can call subscribers without area<br>code if you are in the same area.<br><br>So for me using SRLG + globalization I still have to create site<br>specific translation rules to match local numbers and prepend area<br>code and +country code.<br><br>Basic example in City called Uppsala:<br><br>900.! -> predot, prefix +46 - International calls<br>9[^0].! -> predot, prefix +4618 -> Uppsala city subscriber numbers<br>90[^0].! -> predot, prefix +46 -> other area codes<br><br>So I have to create the same stuff for another city (Stockholm) but<br>replace the subscriber numbers with +468 (area code is 08).<br><br>In the end I can use SLRG to at least save some route pattern config.<br>Also E164 globalization with all the benefits. But still stuck with<br>site specific junk.<br><br>/Roger<br><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><br><span style='color:white'>itevomcid</span> <o:p></o:p></p></div></body></html>