<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:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" 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 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
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:blue;
text-decoration:underline;}
p.standardparagraph, li.standardparagraph, div.standardparagraph
{mso-style-name:standardparagraph;
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
line-height:12.0pt;
font-size:10.0pt;
font-family:"Arial","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:navy;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.subcontent, li.subcontent, div.subcontent
{mso-style-name:subcontent;
margin-top:0in;
margin-right:7.5pt;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
line-height:12.0pt;
font-size:8.5pt;
font-family:"Verdana","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</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=blue>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I believe that all repeating area codes (222,333,444,555, etc.)
are reserved for future use as “easily recognizable”. The language
from nanpa.com site is <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 style='margin-right:7.5pt;line-height:12.0pt'><span
style='font-size:8.5pt;font-family:"Verdana","sans-serif";color:black'>More
about area codes...<o:p></o:p></span></p>
<p class=MsoNormal style='margin-right:7.5pt;line-height:12.0pt'><span
style='font-size:8.5pt;font-family:"Verdana","sans-serif";color:black'>The
format of an area code is NXX, where N is any digit 2 through 9 and X is any
digit 0 through 9. Initially, the middle digit of an area code had to be
"0" or "1". When this restriction was removed in 1995,
additional area code combinations became available. There are 800 possible
combinations associated with the NXX format. Some of these combinations,
however, are not available or have been reserved for special purposes<o:p></o:p></span></p>
<p class=MsoNormal style='margin-right:7.5pt;line-height:12.0pt'><span
style='font-size:8.5pt;font-family:"Verdana","sans-serif";color:black'>Among
them are the following: <o:p></o:p></span></p>
<table class=MsoNormalTable border=1 cellspacing=0 cellpadding=0 width="100%"
style='width:100.0%;margin-left:3.75pt;border:solid #555555 1.0pt'>
<tr>
<td width="20%" valign=top style='width:20.0%;border:none;border-right:solid #555555 1.0pt;
background:#EEEEEE;padding:7.5pt 3.75pt 7.5pt 3.75pt'>
<p class=MsoNormal style='mso-margin-top-alt:3.75pt;margin-right:0in;
margin-bottom:3.75pt;margin-left:0in'><span style='font-size:8.5pt;
font-family:"Verdana","sans-serif";color:black'>Easily Recognizable Codes<o:p></o:p></span></p>
</td>
<td width="80%" valign=top style='width:80.0%;border:none;background:#EEEEEE;
padding:7.5pt 3.75pt 7.5pt 3.75pt'>
<p class=MsoNormal style='mso-margin-top-alt:3.75pt;margin-right:0in;
margin-bottom:3.75pt;margin-left:0in'><span style='font-size:8.5pt;
font-family:"Verdana","sans-serif";color:black'>When the second and third
digits of an area code are the same, that code is called an easily
recognizable code (ERC). ERCs designate special services; e.g., 888 for
toll-free service.<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="20%" valign=top style='width:20.0%;border:none;border-right:solid #555555 1.0pt;
padding:7.5pt 3.75pt 7.5pt 3.75pt'>
<p class=MsoNormal style='mso-margin-top-alt:3.75pt;margin-right:0in;
margin-bottom:3.75pt;margin-left:0in'><span style='font-size:8.5pt;
font-family:"Verdana","sans-serif";color:black'>N11<o:p></o:p></span></p>
</td>
<td width="80%" valign=top style='width:80.0%;border:none;padding:7.5pt 3.75pt 7.5pt 3.75pt'>
<p class=MsoNormal style='mso-margin-top-alt:3.75pt;margin-right:0in;
margin-bottom:3.75pt;margin-left:0in'><span style='font-size:8.5pt;
font-family:"Verdana","sans-serif";color:black'>These 8 ERCs, called service
codes, are not used as area codes.<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="20%" valign=top style='width:20.0%;border:none;border-right:solid #555555 1.0pt;
background:#EEEEEE;padding:7.5pt 3.75pt 7.5pt 3.75pt'>
<p class=MsoNormal style='mso-margin-top-alt:3.75pt;margin-right:0in;
margin-bottom:3.75pt;margin-left:0in'><span style='font-size:8.5pt;
font-family:"Verdana","sans-serif";color:black'>N9X<o:p></o:p></span></p>
</td>
<td width="80%" valign=top style='width:80.0%;border:none;background:#EEEEEE;
padding:7.5pt 3.75pt 7.5pt 3.75pt'>
<p class=MsoNormal style='mso-margin-top-alt:3.75pt;margin-right:0in;
margin-bottom:3.75pt;margin-left:0in'><span style='font-size:8.5pt;
font-family:"Verdana","sans-serif";color:black'>The 80 codes in this format, called
expansion codes, have been reserved for use during the period when the
current 10-digit NANP number format undergoes expansion.<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="20%" valign=top style='width:20.0%;border:none;border-right:solid #555555 1.0pt;
padding:7.5pt 3.75pt 7.5pt 3.75pt'>
<p class=MsoNormal style='mso-margin-top-alt:3.75pt;margin-right:0in;
margin-bottom:3.75pt;margin-left:0in'><span style='font-size:8.5pt;
font-family:"Verdana","sans-serif";color:black'>37X and 96X<o:p></o:p></span></p>
</td>
<td width="80%" valign=top style='width:80.0%;border:none;padding:7.5pt 3.75pt 7.5pt 3.75pt'>
<p class=MsoNormal style='mso-margin-top-alt:3.75pt;margin-right:0in;
margin-bottom:3.75pt;margin-left:0in'><span style='font-size:8.5pt;
font-family:"Verdana","sans-serif";color:black'>Two blocks of 10 codes each
have been set aside by the INC for unanticipated purposes where it may be important
to have a full range of 10 contiguous codes available.<o:p></o:p></span></p>
</td>
</tr>
</table>
<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'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>At one place I worked, we ran a 10-digit NANP dialplan. We
used the format 700-1xx-yyyy for the non-did numbers. Area Code 700 is
reserved for IXC services (typically pay-per-call) and we had blokced it
outbound for toll-fraud purposes. We put a 1 as the first digit of the
office-code to insure that we didn’t accidentally overlap a legitmate
number, JUST IN CASE. Not the most pretty solution, since there is a real
purpose for it. But, we never had any issues with it once in use.<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'>Chris Beck<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>IT Lead - Voice Technologies<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>USG Corporation<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>312-436-4541 (office)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>312-730-5524 (Mobile)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>312-672-7714 (FAX)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>cbeck@usg.com<o:p></o:p></span></p>
</div>
<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>Ryan O'Connell<br>
<b>Sent:</b> Monday, July 14, 2008 12:10 PM<br>
<b>To:</b> Justin Steinberg<br>
<b>Cc:</b> cisco-voip@puck-nether.net; Matt Slaga (US)<br>
<b>Subject:</b> Re: [cisco-voip] E.164 dialing<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Yes agreed and understood, in fact the plan is based on UC version
7. So back to my questions though, with E.164 NANP and E.164 with UK does
anyone know if there are private numbers reserved? As far as I can see any Area
code that repeats itself has not been assigned to any NANP number as of yet
except for 888. They have been set aside as ERC (Easily Recognizable Codes)
numbers. This being said it doesn’t clearly define if these numbers will
ever be introduced as NANP numbers. So based on this using 444 XXX XXXX in NANP
we should be safe. As for the UK it seems as though they set aside a block for
“Corporate Numbering” 05x xxxx xxxx.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Thoughts?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Ryan<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<div>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<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"'> Justin Steinberg
[mailto:jsteinberg@gmail.com] <br>
<b>Sent:</b> Monday, July 14, 2008 7:45 AM<br>
<b>To:</b> Ryan O'Connell<br>
<b>Cc:</b> Matt Slaga (US); cisco-voip@puck-nether.net<br>
<b>Subject:</b> Re: [cisco-voip] E.164 dialing</span><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>I agree with Matt. so
many changes in UC7, I would hold off making any significant dialplan changes
until that release.<o:p></o:p></p>
<div>
<p class=MsoNormal>On Mon, Jul 14, 2008 at 9:39 AM, Ryan O'Connell <<a
href="mailto:Roconnell@unislumin.com">Roconnell@unislumin.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>That's what I'm saying is that I shouldn't need the
"+" if the number is a fully qualified E.164 number.<br>
<br>
Thoughts?<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
<br>
-----Original Message-----<br>
From: Matt Slaga (US) [mailto:<a href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com</a>]<br>
Sent: Monday, July 14, 2008 6:33 AM<br>
To: Ryan O'Connell; <a href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a><br>
Subject: RE: [cisco-voip] E.164 dialing<br>
<br>
Unfortunately, you are going to have to wait for UCM 7.0 to have full<br>
E164 support. Currently UCM throws up when it gets a '+'.<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Ryan O'Connell<br>
Sent: Friday, July 11, 2008 3:54 PM<br>
To: <a href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a><br>
Subject: [cisco-voip] E.164 dialing<br>
<br>
<br>
<br>
Hello,<br>
<br>
I am working on a Dialplan that is based on E.164 numbers. Essentially<br>
all internal DN's will be the fully qualified E.164 number without the<br>
"+" so for NANP that will be 11 digits and in Europe it will consist
of<br>
country-code followed by local exchange. Using partitions and CSS's to<br>
maintain interal 4 digit dialing intra-site and full E.164 inter-site.<br>
For DID's the above plan is pretty straight forward but for non-DID's I<br>
can't seem to find any ranges within the NANP that are designated as<br>
private addresses. So if I want to assign 100 DN's to be voicemail ports<br>
or lobby phones or whatever I was wondering what I should make these<br>
numbers so that it doesn't overlap with any PSTN numbers.<br>
<br>
If anyone can share thoughts or their experiences in this area that<br>
would be helpful thanks<br>
<br>
<br>
Ryno<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>
Disclaimer:<br>
<br>
This e-mail communication and any attachments may contain<br>
confidential and privileged information and is for use by the<br>
designated addressee(s) named above only. If you are not the<br>
intended addressee, you are hereby notified that you have received<br>
this communication in error and that any use or reproduction of<br>
this email or its contents is strictly prohibited and may be<br>
unlawful. If you have received this communication in error, please<br>
notify us immediately by replying to this message and deleting it<br>
from your computer. Thank you.<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><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
<table><tr><td bgcolor=#ffffff><font color=#000000>Confidentiality Notice: This email is intended for the sole use of the intended recipient(s) and may contain confidential, proprietary or privileged information. If you are not the intended recipient, you are notified that any use, review, dissemination, copying or action taken based on this message or its attachments, if any, is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy or delete all copies of the original message and any attachments. Thank you.<br>
</font></td></tr></table>