<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0"
 xmlns:blogChannel="http://backend.userland.com/blogChannelModule"
>

<channel>
<title>Topic &#x27;Re: Likelihood of (666) ever becoming a valid NANPA area code...&#x27; in forum &#x27;VOIP Tech Chat&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954277</link>
<description></description>
<language>en</language>
<pubDate>Fri, 25 Mar 2022 11:11:39 EDT</pubDate>
<lastBuildDate>Fri, 25 Mar 2022 11:11:39 EDT</lastBuildDate>

<item>
<title>Re: N9X</title>
<link>http://www.dslreports.com/forum/Re-N9X-29958622</link>
<description><![CDATA[cb14 posted : <div class="bquote"><said>said by <a href="/profile/1273917" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1273917');">N9MD</a>:</said><p>Although NANPA could certainly put these A/Cs to use over the next few years, the rate of consumption of new DIDs in the world region covered by the "1" country code will ultimately demand adding an extra digit somewhere.<br></p></div>Off course, we do not know how the political decisions will look like and based on that, how fast the US/Can population will grow, but based on current situation i do not see the need for that for very many years to come. Here in SE FL, the predictions of necessity to ad more area codes did not come through in spite of very steep population growth. Just about everyone around here has a cell phone, the growth of mobile subscribers comes here largely from tablet etc users and unlike us VOiP freaks, most people do not need a dozen DIDs. Hopefully also businesses will start to understand that fax is a 20th century technology and start dropping it, freeing additional numbers.<br>Also, one day area codes may become obsolete, freeing a large number of additional number combinations. So my belief is that we will be fine with 10 digits for years to come. :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-N9X-29958622</guid>
<pubDate>Sun, 29 Mar 2015 22:24:16 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29958250</link>
<description><![CDATA[toro posted : <div class="bquote"><said>said by <a href="/profile/1466531" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1466531');">NefCanuck</a>:</said><p>Why does the US/Canada share the area code system anyways?<br><br>If each country had their own full set of area codes wouldn't we be nowhere near capacity at this point?  Make the US country code 1 and Canada can be 2 and things are good to go right?<br></p></div>Hmm, Canada has currently only 38 area codes. I don't see how not having those it would make a big difference for USA.<br><small>--<br>Providers (through asterisk): voip.ms, freephoneline, anveo direct, smartcall.ro, ipcomms, callcentric. Hardware: Linksys SPA series, Grandstream HT series, Panasonic KX-TGP5x0, Vonage VDV2x, Moto VT2x42<br>&raquo;<A HREF="http://www.voipfan.net" >www.voipfan.net</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29958250</guid>
<pubDate>Sun, 29 Mar 2015 18:38:58 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29958248</link>
<description><![CDATA[doc posted : <div class="bquote"><said>said by <a href="/profile/1466531" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1466531');">NefCanuck</a>:</said><p>Make the US country code 1 and Canada can be 2 and things are good to go right?</p></div>That would shed maybe 10% of the numbers in use (based on Canada having a population of around 10% of the US), which would make no difference to the bigger picture.<br><br>Plus country code "2" is already used (as the first digit of several other country codes), however I'm sure the Canadians would be happy with one of the available free codes like +978.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29958248</guid>
<pubDate>Sun, 29 Mar 2015 18:37:48 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29958104</link>
<description><![CDATA[PX Eliezer1 posted : <div class="bquote"><said>said by <a href="/profile/1466531" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1466531');">NefCanuck</a>:</said><p>Why does the US/Canada share the area code system anyways?<br><br>If each country had their own full set of area codes wouldn't we be nowhere near capacity at this point?  Make the US country code 1 and Canada can be 2 and things are good to go right?<br></p></div>But we love you guys.<br><br>Seriously, if there are countries that should be separated from the "1" North American Dial Plan it should be:<br><br>Bermuda, Anguilla, Antigua & Barbuda, the Bahamas, Barbados, the British Virgin Islands, the Cayman Islands, Dominica, the Dominican Republic, Grenada, Jamaica, Montserrat, Sint Maarten, St. Kitts and Nevis, St. Lucia, St. Vincent and the Grenadines, Trinidad and Tobago, and Turks & Caicos.<br><br>See also:<br>&raquo;<A HREF="http://www.lincmad.com/caribbean.html" >www.lincmad.com/caribbean.html</A><br><br>By the way, country codes starting with "2" generally go with the continent of Africa, for example Egypt 20, South Africa 27, Nigeria 234, although there are exceptions such as Aruba (297).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29958104</guid>
<pubDate>Sun, 29 Mar 2015 17:02:02 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29957998</link>
<description><![CDATA[NefCanuck posted : Here's a thought I've had for several years now.<br><br>Why does the US/Canada share the area code system anyways?<br><br>If each country had their own full set of area codes wouldn't we be nowhere near capacity at this point?  Make the US country code 1 and Canada can be 2 and things are good to go right?<br><br>NefCanuck]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29957998</guid>
<pubDate>Sun, 29 Mar 2015 15:55:49 EDT</pubDate>
</item>
<item>
<title>Re: N9X</title>
<link>http://www.dslreports.com/forum/Re-N9X-29957860</link>
<description><![CDATA[Fisamo posted : The idea of keeping the second digit of 9 reserved was, as I understand it, for switching equipment.  Defining "M" as 0-8, any pattern of NMX-XXX-XXXX, the switching equipment would know to ignore anything after 10 digits.  If a pattern of N9X-XXX-XXXX were detected, the switching equipment would automatically know that the number was incomplete.  <br><br>All because, unlike cell phones, you don't press a "send" button when you dial a number - numbers are transmitted to the switching equipment (on an analog line) one digit at a time.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-N9X-29957860</guid>
<pubDate>Sun, 29 Mar 2015 14:23:58 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29957375</link>
<description><![CDATA[PX Eliezer1 posted : <div class="bquote"><said>said by <a href="/profile/1833185" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1833185');">mdseuss</a>:</said><p>I'm glad that someone had the good sense to assign exchange 978-666 to Salem MA....<br></p></div>Area code 321 originally was going to be assigned to Chicago, but Robert Osband in Florida led a successful campaign to get it assigned to Cape Canaveral and the Kennedy Space Center area (as in 3-2-1-Liftoff).<br><br>But Chicago later got 872 which spells USA, so that's good too.<br><br>-----<br><br>In a similar light, the fact of Interstate "76" starting at Philadelphia was quite deliberate.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29957375</guid>
<pubDate>Sun, 29 Mar 2015 10:15:37 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29957207</link>
<description><![CDATA[mdseuss posted : <br>I'm glad that someone had the good sense to assign exchange 978-666 to Salem MA ... while they were available on Google Voice, I grabbed one.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29957207</guid>
<pubDate>Sun, 29 Mar 2015 07:57:28 EDT</pubDate>
</item>
<item>
<title>Re: N9X</title>
<link>http://www.dslreports.com/forum/Re-N9X-29956094</link>
<description><![CDATA[doc posted : <div class="bquote"><said>said by <a href="/profile/1273917" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1273917');">N9MD</a>:</said><p>My point is that the idea of reserving N9X for future expansion was somewhat short-sighted and is now outdated as a means of keeping up with DID assignments ... since these additional 3-digit A/Cs would be consumed quickly over the next 10 years or so.</p></div>Unless they use it as a transitionary mechanism, rather than just a new area code.<br><br>ie, Area code 456 becomes area code 4956.  Both run in parallel for a time (which can happen as there's guaranteed to be no conflicts), then 456 is deprecated. Eventually other 4 digits area codes (without the second digit being 9) can be allocated.  That said, appending 0 or 1 to the end of the existing 3 digit codes could probably achieve much the same thing.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-N9X-29956094</guid>
<pubDate>Sat, 28 Mar 2015 14:58:03 EDT</pubDate>
</item>
<item>
<title>Re: N9X</title>
<link>http://www.dslreports.com/forum/Re-N9X-29956087</link>
<description><![CDATA[bw5745 posted : Adding a digit at the end is problematic. Every new number issued would match an existing number in the first 10 digits. It would make much more sense to change all NXX to N9XX. You know right away that you need to dial old 10 digit numbers with the new 9. After everyone is used to the new system, you can start releasing new N[1 to 8, or 0]XX area codes with no conflict.<br><br>I think this style of number expansion has been used in other countries.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-N9X-29956087</guid>
<pubDate>Sat, 28 Mar 2015 14:54:40 EDT</pubDate>
</item>
<item>
<title>N9X</title>
<link>http://www.dslreports.com/forum/N9X-29956031</link>
<description><![CDATA[N9MD posted : Yep! Simply maintaining three digit A/Cs won't help ... <br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<B>N</B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<B>9</B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <B>X</B><br>...&nbsp;allowed numbers &nbsp; &nbsp;&nbsp;2-9 &nbsp;&nbsp; 9 &nbsp;&nbsp;&nbsp;&nbsp;0-9 &nbsp;&nbsp;in the respective positions<br>... yielding multipier &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;8&nbsp;&nbsp;x&nbsp;&nbsp;1&nbsp;&nbsp;x&nbsp;&nbsp;10&nbsp;&nbsp;=&nbsp;&nbsp;80<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<U> - 1</U>&nbsp;&nbsp;&nbsp;for disallowed A/C999 <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;79&nbsp;&nbsp;&nbsp;&nbsp;available 3-digit area codes<br><br>My point is that the idea of reserving N9X for future expansion was somewhat short-sighted and is now outdated as a means of keeping up with DID assignments ... since these additional 3-digit A/Cs would be consumed quickly over the next 10 years or so. <br><br>Although NANPA could certainly put these A/Cs to use over the next few years, the rate of consumption of new DIDs in the world region covered by the "1" country code will ultimately demand adding an extra digit somewhere. And as you stated ... but not necessarily for your self-serving rationale ;) ... the more sensible approach appears to be that of adding a final "0" to existing numbers ... and to begin issuing new 12-digit DIDs (including the leading "1").<br><br>Incidentally, as soon as 12-digit numbering/dialing is announced, I'll be buying loads of NYSE/ASE/NASDAQ/OTC stocks in the paper production and commercial printing industries ... given the new stationery and envelopes and business cards and print advertising that will be needed.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/N9X-29956031</guid>
<pubDate>Sat, 28 Mar 2015 14:22:36 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955640</link>
<description><![CDATA[Arne Bolen posted : <div class="bquote"><said>said by <a href="/profile/1273917" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1273917');">N9MD</a>:</said><p>adding an 11th digit (NPA-NXX-XXXX<B>X</B>) to the end of a DID would not depend on the N9X.</p></div>Personally I would prefer a zero being added to the end of my DID, giving me a phone number ending with five zeros.  :D Changing my area code from 781 to 7981 would OTOH make my nice phone number less attractive.  :(<br><br>However, changing 800 possible 3-digit area codes must be so much easier compared to changing thousands of numbers on exchanges. My bet is on 4-digit area codes.<br><small>--<br><A HREF="https://www.myvoipnews.com">My VoIP News Daily</a> - myvoipnews@secure.mailbox.org - <A HREF="https://www.peerio.com/">Peerio</a>:myvoipnews - 781-691-0000 x6100</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955640</guid>
<pubDate>Sat, 28 Mar 2015 10:22:57 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955436</link>
<description><![CDATA[N9MD posted : <div class="bquote"><said>said by <a href="/profile/1652916" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1652916');">Arne Bolen</a>:</said><p>My guess is that the current three-digit area codes at some point may be changed to four-digit area codes.<br></p></div>... which would negate the need for N9X 'expansion' since X9N is still only 3 digits, and would allow only a relatively small number of new area codes while maintaining the current 11-digit format.  This would limit the number of new DIDs that could be added to the system.<br><br>A 4-digit area code --- or --- adding an 11th digit (NPA-NXX-XXXX<B>X</B>) to the end of a DID would not depend on the N9X. The latter would add close to 9 billion new DIDs (if my math is correct). It's too early in the morning here to calculate how many new DIDs would result from the former (4-digit AC). ;)<br><br>By the way, Arne, it just dawned on me (as dawn is approaching in Boca Raton ) why my 6am post got such a quick response from you ... it's your 'old world' location.  :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955436</guid>
<pubDate>Sat, 28 Mar 2015 06:33:55 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955422</link>
<description><![CDATA[Arne Bolen posted : <div class="bquote"><said>said by <a href="/profile/1273917" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1273917');">N9MD</a>:</said><p>I thought that 'expansion' implies NANPA eventually going to 12-digit DIDs ... simply adding a '0' to the end of every <U>existing</U> NANPA DID ... 1-201-555-1212 becomes 1-201-555-1212<B>0</B> ... with new 12-digit DIDs ending in '1', '2', etc. ... e.g., 1-201-555-1212<B>1</B>.</p></div>My guess is that the current three-digit area codes at some point may be changed to four-digit area codes.<br><small>--<br><A HREF="https://www.myvoipnews.com">My VoIP News Daily</a> - myvoipnews@secure.mailbox.org - <A HREF="https://www.peerio.com/">Peerio</a>:myvoipnews - 781-691-0000 x6100</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955422</guid>
<pubDate>Sat, 28 Mar 2015 05:48:43 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955413</link>
<description><![CDATA[N9MD posted : <div class="bquote"><said>said by <a href="/profile/1652916" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1652916');">Arne Bolen</a>:</said><p><div class="bquote"><said>said by <a href="/profile/1273917" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1273917');">N9MD</a>:</said><p>I find a total absence of any Code showing a middle digit '9' (X9X); e.g., 297, 591, 994, etc.</p></div><div class="bquote"><said>said by &raquo;<A HREF="http://www.nanpa.com/area_codes/index.html" >www.nanpa.com/area_codes &middot;&middot;&middot; dex.html</A> :</said><p>N9X<br>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.</p></div></p></div>That'll teach me to set my screen view 'zoom' to 150% so I can read the 'small print in <B>TOS</B>es. :)<br><br>I didn't see the bottom of the page you referenced ... even though my three referenced pages were accessed through your referenced page.<br><br>Meanwhile, how does this N9X 'expansion' info impact 'expansion'?<br><br>I thought that 'expansion' implies NANPA eventually going to 12-digit DIDs ... simply adding a '0' to the end of every <U>existing</U> NANPA DID ... 1-201-555-1212 becomes 1-201-555-1212<B>0</B> ... with new 12-digit DIDs ending in '1', '2', etc. ... e.g., 1-201-555-1212<B>1</B>.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955413</guid>
<pubDate>Sat, 28 Mar 2015 05:31:57 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955229</link>
<description><![CDATA[Fisamo posted : Considering that 666 has been used as a valid CO code in (at least one--grin) state for over 35 years, I'm sure it will be an area code eventually.  Newington, CT : 860-666-xxxx; was around in the days that 203 was the only area code in the state, long before any concern regarding exhaust of available phone numbers.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29955229</guid>
<pubDate>Sat, 28 Mar 2015 00:01:06 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954514</link>
<description><![CDATA[anon posted : <div class="bquote"><said>said by <a href="/profile/1892658" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1892658');">arpawocky</a>:</said><p>According to NANPA, 666 is not assigned but is assignable, as an ERC (Easily Recognizable Code). However, given the negative stigma associated with 666, I doubt it will ever be assigned, no matter how crowded the area-code space becomes.</p></div>It's only a matter of time.  NWO and all that 'stuff.  Add another layer to the tinfoil :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954514</guid>
<pubDate>Fri, 27 Mar 2015 17:50:18 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954454</link>
<description><![CDATA[Arne Bolen posted : <div class="bquote"><said>said by <a href="/profile/1273917" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1273917');">N9MD</a>:</said><p>I find a total absence of any Code showing a middle digit '9' (X9X); e.g., 297, 591, 994, etc.</p></div><div class="bquote"><said>said by &raquo;<A HREF="http://www.nanpa.com/area_codes/index.html" >www.nanpa.com/area_codes &middot;&middot;&middot; dex.html</A> :</said><p>N9X<br>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.</p></div><br><small>--<br><A HREF="https://www.myvoipnews.com">My VoIP News Daily</a> - myvoipnews@secure.mailbox.org - <A HREF="https://www.peerio.com/">Peerio</a>:myvoipnews - 781-691-0000 x6100</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954454</guid>
<pubDate>Fri, 27 Mar 2015 17:21:16 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954425</link>
<description><![CDATA[N9MD posted : Hmmm! Another Area Code curiosity. <br><br>In looking down the currently active AC list ... <br>&raquo;<A HREF="http://www.nanpa.com/enas/geoAreaCodeNumberReport.do" >www.nanpa.com/enas/geoAr &middot;&middot;&middot; eport.do</A><br><br>and those planned but not yet in service  ...<br>&raquo;<A HREF="http://www.nanpa.com/enas/plannedNpasNotInServiceReport.do" >www.nanpa.com/enas/plann &middot;&middot;&middot; eport.do</A><br><br>and non-geographic codes currently in service ...<br>&raquo;<A HREF="http://www.nanpa.com/enas/nonGeoNpaServiceReport.do" >www.nanpa.com/enas/nonGe &middot;&middot;&middot; eport.do</A><br><br>I find a total absence of any Code showing a middle digit '9' (X9X); e.g., 297, 591, 994, etc.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954425</guid>
<pubDate>Fri, 27 Mar 2015 17:10:55 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954333</link>
<description><![CDATA[phonesimon posted : Consider using 1-700 instead: &raquo;<A HREF="http://www.nanpa.com/faq/sitefaq.html" >www.nanpa.com/faq/sitefaq.html</A> item 55]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954333</guid>
<pubDate>Fri, 27 Mar 2015 16:31:55 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954326</link>
<description><![CDATA[arpawocky posted : Righ, but they could allocate it as an ERC at some point in time.. I guess I probably should have asked clearer.. ie, what is the likliehood of it being valid as an ERC.<br><br>777 could at some point be allocated as an ERC too, which would collide with CallCentric's use of 1-777. I'm considering a similar use case for 1-666 and am curious if ppl think the negative connotation of 666 will keep NANPA from ever allocating it period (as an area code, an ERC, or anything else they might think of later)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954326</guid>
<pubDate>Fri, 27 Mar 2015 16:27:27 EDT</pubDate>
</item>
<item>
<title>Re: Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954315</link>
<description><![CDATA[PX Eliezer1 posted : No, and they have denied Nevada their dearly desired 777 for the same reason.<br><br>cf:<br>&raquo;<A HREF="http://www.nanpa.com/area_codes/" >www.nanpa.com/area_codes/</A><br><br><div class="bquote"><p>Easily Recognizable Codes:	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.<br><br>N11: 	 These (particular) 8 ERCs, called service codes, are not used as area codes.<br></p></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954315</guid>
<pubDate>Fri, 27 Mar 2015 16:23:13 EDT</pubDate>
</item>
<item>
<title>Likelihood of (666) ever becoming a valid NANPA area code...</title>
<link>http://www.dslreports.com/forum/Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954277</link>
<description><![CDATA[arpawocky posted : According to NANPA, 666 is not assigned but is assignable, as an ERC (Easily Recognizable Code). However, given the negative stigma associated with 666, I doubt it will ever be assigned, no matter how crowded the area-code space becomes.<br><br>I'd like to hear others thoughts on this.<br><br>I'm asking with a very practical reason in mind.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Likelihood-of-666-ever-becoming-a-valid-NANPA-area-code-29954277</guid>
<pubDate>Fri, 27 Mar 2015 16:10:16 EDT</pubDate>
</item>
</channel>
</rss>
