How does a person or business get listed in 411?  What company answers when
someone dials 411?  Can a virtual number get a listing on the dial in 411,
or can it only be listed online, like in whitepages.com or yellowpages.com?



Believe it or not, I have a rather urgent need to know ASAP.  A client needs
to get his company listed right away.



Vicki Siedow

Siedow & Associates Investigations
2629 Foothill Blvd. # 262

La Crescenta, CA 91214
(Los Angeles County)
877-To-Vicki
818-242-0130
Vicki@... <mailto:Siedow@...>
http://VickiPI.com

http://flipmysteries.tv

http://flipjustice.org

http://PrepaidLegal.com/hub/vsiedow
CA Licensed PI #22852
CITRMS: Certified Identity Theft Risk Management Specialist
http://FLIPmysteries.tv

http://FLIPjustice.org





[Non-text portions of this message have been removed]

I have some questions re the year of changes in LEC-ownership for the
communities in the Las Vegas NV Metro area...

Las Vegas "itself" (which includes the locality of "North Las Vegas)
and probably some of the exchange areas to the south and west (such as
Mount Charleston, Blue Diamond, Jean, Searchlight), had been served by
the Southern Nevada Telephone Company for decades, well into probably
the mid-1960s. Central Telephone Company (Centel) bought out the
Southern Nevada Telephone Company sometime in the mid or late 1960s,
but does anyone know the exact year that this took place?

BTW, the Southern Nevada Telephone Company in its earlier years had
been associated with the electric power and light company for Las Vegas.
I don't know if the power company also provided gas, water, sewer, etc.
though.

Just to the southeast of Las Vegas is the (incorporated) community of
Henderson NV. During WW-2, Henderson was a major industrial and
manufacturing plant area for the "war effort", and also had housing for
the workers at the plants. Right after "the war", many of the plants
shut down or had reduced output. Some workers were laid off, others quit
and moved elsewhere, but there were those who remained in the area. By
the early 1950s, Henderson was incorporated as its own city. I don't
know who the original telco company was, but by the 1960s-era, the
Continental Telephone Company (Contel) became the local telco for
Henderson NV. By the mid-to-late 1970s, Centel in Las Vegas took over
the Henderson operations from Contel. Does anyone know what the name of
the original telco provider was for the Henderson exchange? What year
during the 1960s did Contel actually take over? And what year during
the 1970s did Centel take over from Contel?

Boulder City NV, just to the southeast of Henderson, was originally the
US-Federal-Government-owned housing for construction workers hired in
the building of Boulder/Hoover Dam during the 1930s. The US Federal
Government was the original owner of the telco exchange in Boulder City.
By the late 1970s, Centel was the telco for Boulder City. Does anyone
know the years of any ownership changes, as well as any other details
regarding Boulder City's telco?

Local calling was eventually expanded for _ALL_ Centel/Sprint telephone
exchanges in the Las Vegas NV area -- there is _NO_ toll between any
Centel/Sprint/Embarq/CenturyLink exchanges in this region.

There was also some ratecenter consolidation in the early 2000s:
Blue Diamond, Henderson, Boulder City are all now part of the Las Vegas
NV exchange/ratecenter. These three are now simply "localities" of Las
Vegas NV. Mount Charleston, Jean, Nelson, Searchlight, and even "far
away" Laughlin NV are all still individual ratecenters, but all have
full EAS/Local w/r/t to each other as well as what is now a larger
consolidated Las Vegas NV ratecenter.

It is still a toll call to call other parts not all that distant, such
as Moapa Valley Telco, Lincoln Valley Telco, Rio Virgin Telco (which is
a different LATA and also serves parts of nearby Utah and Arizona),
some other adjacent states' LATAs which extend into Clark County, which
have Frontier/Citizens Telco, and also some at&t/Nevada*Bell exchanges
in Clark County and the southern part of nearby Nye County to the west.

Centel was bought by United in the early 1990s, right about the time
that United finished its phased purchase of GTE's one-time ownership of
Sprint (IXC) which GTE had bought from Southern Pacific Railways in the
late 1970s or early 1980s, and which GTE and United went into a 50/50
joint-venture in 1986... GTE's Sprint competitive IXC and United's
competitive IXC US-Telecom merged operations to become "US-Sprint",
owned 50/50 by both GTE and United. But within a year or two, GTE
announced that they would begin pulling out of the joint-venture,
selling off their half of Sprint over to United in phases. By the early
1990s, United now owned 100% of Sprint, and also bought Centel LEC, and
changed the name of the parent company/LEC United and the LEC Centel to
the name of the (competitive) IXC, Sprint.

In 2005, Sprint bought Nextel Wireless, and announced that they would
retain the original Sprint IXC and Sprint's wireless operations, and
consolidate Nextel's wireless into Sprint's. But that Sprint "LTD"
(Local Telephone Division), legacy United and Centel LECs would be
spun-off to a brand new entity to eventually be named "Embarq". The new
Embarq name and separate ownership/operations took effect during 2006,
but Embarq retained corporate HQ in Kansas City KS, which also has been
the HQ of (post-GTE) Sprint.

And then in October 2008, CenturyTel, another group owner of rural
independent telcos, and HQ's in Monroe LA (although not the ILEC for
Monroe LA which is at&t/BellSouth/So.Cntrl.Bell) announces that it
would buy out Embarq (legacy Sprint's United and Centel LECs). This
was completed by Summer 2009 (last year). The name of the new merged
entity is named CenturyLink.

And in late April 2010, CenturyLink announced that it will buy Qwest
(legacy RBOC US-West, which is the pre-divestiture BOCs Mountain Bell,
Northwestern Bell, and Pacific Northwest Bell). If this is approved by
all regulatory agencies and other required bodies, then CenturyLink
will be the ILEC for _TWO_ different Las Vegas-es:
Las Vegas NV, and also (Qwest/US-West/Mountain Bell) Las Vegas NM.

I wonder if the name will change again?
Maybe to CenturyQwest or even CenturyBell? :-)
(Afterall, Qwest/US-West is an RBOC, legacy "Bell")

But if anyone knows any further details on the history of some of
the ILECs for the Las Vegas NV metro area, and the year of ownership
changes in the 1960s/70s-era, etc....

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

I happened to stumble upon CNAC's listing of available CO codes for NPA
249, which is the new overlay code for 705 in Central/Northeastern
Ontario.  It is available at http://www.cnac.ca/data/ac249.htm.  I
noticed that there are numerous CO codes that are protected from
assignment in the EAS of various rate centres, and these CO codes all
correspond to the existing 705 CO codes in those rate centres.  Most of
these seem to be remote communities, but one of them is Parry Sound
which is far from remote and a fairly well-known cottage destination.
Penetanguishene is also not too far from Barrie.

Is the CRTC allowing 7-digit dialing to continue in these communities or
excluding them from the 249 overlay?  That seems to be the only logical
reason why there is so much CO code protection in 249.  I'm wondering if
someone more familiar might be able to shed some light on this?

Many thanks,
Nick

On Thu, 5/13/10, Nick Dubanow <nick at skycomp.ca> wrote:

> I happened to stumble upon CNAC's listing of available CO codes for
> NPA 249, which is the new overlay code for 705 in Central/Northeastern
> Ontario.

(The 705/249 overlay is effective in early 2011, though)

> It is available at http://www.cnac.ca/data/ac249.htm.  I noticed that
> there are numerous CO codes that are protected from assignment in the
> EAS of various rate centres, and these CO codes all correspond to the
> existing 705 CO codes in those rate centres.  Most of these seem to be
> remote communities, but one of them is Parry Sound which is far from
> remote and a fairly well-known cottage destination. Penetanguishene is
> also not too far from Barrie.
>
> Is the CRTC allowing 7-digit dialing to continue in these communities
> or excluding them from the 249 overlay?  That seems to be the only
> logical reason why there is so much CO code protection in 249.  I'm
> wondering if someone more familiar might be able to shed some light on
> this?


I'm just as mystified as you!
(regarding any continued c.o. code protection)

ALL of 705 (and 249) is to have mandatory ten-digit dialing, there are to
be no exceptions on calling from 705/249 to other (adjacent) area codes
even if the call is "local". Also, calls _TO_ 705/(249) are all going to
be ten-digits, there really are no exceptions there neither.

And for that matter, all local calling to/from 705/(249) and adjacent
area codes is to/from other adjacent area codes that already are
ten-digit dialing mandatory within themselves, even though one of them
doesn't yet have any formal overlay until 17-May-2010, and another
doesn't yet have any formal overlay until June 2013.

705/(249) borders:

- 0N 807
but there are _NO_ local calling "corridors" between 705/249 and 807.

- MI 906
though there is still a rather wide body of water between the ON and MI
towns both named "Sault St. Marie", and there is _NO_ local calling
between 705/(249) and 906.

- ON 519/226
(already overlay/ten-digit dialing)

- ON 905/289/(365)
(already overlay/ten-digit dialing)

- ON 613/(343)
(already ten-digit dialing;
first "POTS" overlay 343-NXX code takes effect on Monday 17-May-2010)

- PQ 819/(873)
(already ten-digit dialing;
the 873 overlay to 819 takes effect in 2013)

Also, there is _NO_ local calling between 705/(249) and the islands in
Hudson Bay and James Bay, etc. which are technically in the jurisdiction
of Nunavut Territory, and thus are in NPA 867.

The only thing I can think of, is that any continued/legacy "protection"
of c.o.codes in 705, which really should be obsolete even by NOW, and
that these c.o.codes are also being inadvertently "copied over" as well
to 249. As the US/Canada moves more and more to consistent mandatory
ten-digit dialing, the need to "protect" _ANY_ c.o. codes to allow
continued 7-digit local dialing across NPA boundaries where such local
calling exists, becomes OBSOLETE, since any/all inter-NPA local calling
routes also becomes mandatory 10-digits anyhow.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

On Thursday NIGHT, the WV-PSC approved of VeriZon's sale of legacy BOC
Bell Atlantic (Chesapeake & Potomoc Telephone) to Frontier.

"Details at Eleven!"

(I'll try to have a more detailed followup post later on)

This is the last of all of the 9 such states which were required to
approve of any sale of VZ to Frontier for their own states, in the
14 states of the overall transaction. All of the other states involve
legacy GTE and Contel of VeriZon, while West Virginia is legacy BOC
(C&P Tel) of VeriZon.

Today, Thursday 13-May-2010, is the anniversary of VeriZon and Frontier
announcing the intended sale, back on Wednesday 13-May-2009.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA, pre-Katrina

Earlier, I wrote:

> On Thursday NIGHT, the WV-PSC approved of VeriZon's sale of legacy BOC
> Bell Atlantic (Chesapeake & Potomac Telephone) to Frontier.
>
> "Details at Eleven!"
>
> (I'll try to have a more detailed followup post later on)
>
> This is the last of all of the 9 such states which were required to
> approve of any sale of VZ to Frontier for their own states, in the
> 14 states of the overall transaction. All of the other states involve
> legacy GTE and Contel of VeriZon, while West Virginia is legacy BOC
> (C&P Tel) of VeriZon.
>
> Today, Thursday 13-May-2010, is the anniversary of VeriZon and Frontier
> announcing the intended sale, back on Wednesday 13-May-2009.


There are numerous news/media/press/etc. reports on this, especially from
radio/TV/newspaper/etc. websites, which can all be found from doing
Google "News" searches.

The West Virginia Public Service Commission's "Order", dated Thursday
13-May-2010, can be downloaded as a pdf file (over 6-megs), from the
webpage for this VZ/Frontier filing with the WV-PSC on this matter:
http://www.psc.state.wv.us/scripts/WebDocket/tblCaseActivitiesList.cfm?CaseID=36\
696

The FCC still needs to approve the entire deal, the sale of VeriZon's
legacy GTE (and Contel) exchange areas in most of the states where they
still have retained such legacy GTE (and Contel), as well as the sale of
VZ' legacy BOC Bell-Atlantic/C&P-Tel-of-WV, all to Frontier. The FCC's
webpage with downloadable documents for this matter is:
http://www.fcc.gov/transaction/frontier-verizon.html

Additionally, the ratecenter of Crows-Hematite VA, a very small rural and
rather isolated settlement with a low population, gets its dial-tone from
the VZ/BA/C&P-WV ratecenter/c.o.switch of White Sulphur Springs WV, which
is to be sold to Frontier. ALL are associated with the Charleston WV LATA.
While Crows-Hematite VA is close the VZ/BA/C&P-VA Roanoke VA LATA, and
has inter-LATA EAS with nTelos'/Clifton-Forge-Wayne's ILEC's ratecenters
of Clifton Forge VA, Covington VA, and Potts Creek VA, there are _NO_
other nearby VeriZon/Bell-Atlantic/C&P-VA exchanges/switches nearby to
"rewire" the Crows-Hematite VA customers over to -- and it could also
require a LATA-change as well, if it were to happen. (nTelos/CF-W ILEC
also serves Waynesboro VA, but that too is a bit of a distance away from
Clifton Forge/Covington/Potts Creek VA). ALL of the Roanoke VA LATA
ratecenters surrounding Crows-Hematite for something like 40-50 miles
(within VA) are all "independent", _NOT_ VZ/BA/C&P-VA!

Frontier has applied to the Virginia State Corporation Commission to be
an ILEC within the state of Virginia (they have no other presence as an
ILEC in Virginia), specifically to be the new ILEC for Crows-Hematite VA,
taken over from VeriZon (C&P-Va). The VA-SCC has a docket on file, and
documents can be downloaded from:
http://docket.scc.virginia.gov/vaprod/DOCUMENTS.ASP?MATTER_NO=127929
The VA-SCC still has to approve of this sale.

VeriZon is in the process of re-aligning certain central-office dial-tone
provision in a handful of communities along the MD/VA state-line, in the
western part of WV's eastern panhandle/ western part of MD's western
panhandle. This (both the small part of eastern WV, and western MD) is
all a part of the Haggerstown MD LATA. Some Maryland ratecenters/customers
of VZ/BA/C&P-MD have been getting their dial-tone from VZ/BA/C&P-WV
c.o.switches in West Virginia for decades. Vice-versa, some West Virginia
ratecenters/customers of VZ/BA/C&P-WV have been getting their dial-tone
from VZ/BA/C&P-MD c.o.switches in Maryland for decades. VeriZon (C&P) is
re-aligning these customers/ratecenters so that they will soon receive
their dial-tone from nearby VZ (C&P) c.o.switches in their own state.
EXISTING legacy local/EAS (intra-LATA) calling (both intra-state and
inter-state) that has existed for decades WILL CONTINUE, only now if it
is inter-state, it will also be inter-company (between VeriZon/C&P-MD and
Frontier in West Virginia).

VeriZon is retaining legacy GTE (and Contel) in Pennsylvania and Virginia
which are both Bell-Atlantic BOC states of VeriZon -- Bell-of-PA and
C&P-of-Va.

North Carolina is one of the states where VeriZon is selling off old GTE
(including Contel), over to Frontier. However, the somewhat isolated
ratecenter of Knotts Island NC (once-Contel-later-GTE) is being retained
by VeriZon. Knotts Island NC is either a barrier island or a peninsula
that extends south from the eastern coast of Virginia. There is a remote
switch at Knotts Island (it does not get its dial-tone from Virginia,
though), but the only access by land to Knotts Island NC is through
Virginia. There is a ferry boat connecting Knotts Island NC with the
mainland of eastern NC though, and the mainland part of NC in the area
is Carolina-Tel-and-Tel/United/Sprint/Embarq-now-part-of-CenturyLink and
the United/CenturyLink "Rocky Mount NC" LATA. Knotts Island NC is rather
a part of the VZ/BA/C&P Norfolk VA LATA, and maintains a community of
interest with southeastern Virginia, which has traditionally been both
BOC C&P-VA and Contel, all now part of VeriZon. Note that there is also
some inter-LATA intra-state EAS/local between Knotts Island NC and the
CenturyLink (old United/Carolina-Tel) on the northeastern NC mainland.

VeriZon is retaining the legacy GTE (and Contel) that it has still
retained in California, although they are selling a handful of exchanges
that border Oregon (old GTE/West Coast, which is more associated with
GTE and its predecessors for OR/WA/ID), and also border Nevada (old
Contel, not too far from Reno/etc), and also border Arizona (old Contel),
over to Frontier, which also has a presence in Oregon, Nevada, and
Arizona. Back in the 1990s, Frontier's predecessor, Citizens Tel, bought
some old GTE and Contel in California that GTE chose not to retain.

VeriZon is retaining the legacy GTE/Contel in Texas that they did NOT
sell to Valor back in 2000 shortly after BA/NYNEX bought GTE/Contel to
become Frontier. (Valor was a brand new ILEC created circa 2000 or so,
mostly to buy legacy GTE/Contel in Oklahoma, New Mexico, and SOME
exchanges in Texas including both the TX and AR sides of Texarkana;
other GTE/Contel areas in Arkansas were sold by VZ to CenturyTel. In
2006, Valor merged with the landline side that Alltel spun-off when
Alltel was to be wireless-only, to form the new Windstream; Alltel
Wireless is mostly now being merged into VeriZon-Wireless).

And VeriZon is retaining legacy GTE in Florida, all in the Tampa Bay/etc.
metro area, which is all its own LATA, and has been General Telephone for
over 50 years now.

I might have mentioned in previous postings that Florida had old GTE (the
Tampa Bay/etc. area) but that it never had any old Contel. It turns out
that is not true... in the old 904 area code of 1965 thru 1997, the
Florida panhandle and north-eastern Florida, Contel had five separate
small contiguous patches of service area. By the early 1980s or so, most
of it was sold to Centel (later merged into United to become Sprint then
spun-off-to-become-Embarq, now purchased by CenturyTel to become a part
of CenturyLink), and one exchange in the far western part of the
panhandle was sold to what has since become part of Frontier.

Contel was once present in 42 different states, all at the same time!
One of these states was Alaska (along with GTE, PTI) as well. The only
states where Contel never had any service were Mississippi, Hawaii (which
of course was 100% GTE-HTC), Massachusetts/ Rhode Island/ Connecticut,
and Maryland/ Delaware, and of course nothing in the (NOT a state) of DC
which like MA, RI, CT, MD, DE, is 99% or even 100% a BOC state. And
Contel was never present in Ohio, although there was (and still is) a
Continental Telephone Company in Ohio, however, this is _NOT_ the same
"Contel". The Continental OHIO Telephone Company is a local home-grown
telco in the TOWN named "Continental OH"! And Contel once had a presence
in parts of Canada and the Caribbean as well!

GTE's one-time operations outside of the mainland US included parts of
Canada (MOST of British Columbia, much of eastern Quebec), Hawaii,
Alaska, the Caribbean (Puerto Rico, Dominican Republic, and even a small
interest in Venezuela's CANTV), and in addition to Hawaiian Tel, General
also owned Micronesian Telecom in the Mariana Islands (Saipan/etc) but
_NOT_ to be confused with the Federated States of Micronesia... and until
1967 also PLDT Philippine Long Distance Telephone (ILEC and LD), when
friends of the Marcos family took over GT&E's interests in PLDT.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA, pre-Katrina

> The only thing I can think of

I have a feeling I know why.  Party lines.

There is probably some sort of technical limitation that prevents the
same CO code from being assigned to a single EAS, regardless of the NPA.
All of the protected codes in 249 correspond with areas that would have
party lines - Indian reserves, remote communities and cottage
destinations.  Not only that, but if you look at the code availability
in NPA 343 (http://www.cnac.ca/data/ac343.htm) there are also a number -
though not nearly as many - protected CO codes, and these also
correspond with cottage communities that would likely have party line
service.

Having said that, I personally think it is a good idea to avoid
assigning the same CO code in two different NPAs to the same single rate
centre, and that it should also be avoided in the same EAS as much as
possible.  I will never forget getting a phone call on my cell phone
from a woman thinking I was her husband and demanding that I pick up
items from the grocery store on the way home.  After much confusion, we
figured out the problem.  My cell phone was 905-321, his was 289-321 and
we both had the same last four digits.  Both of those CO codes serve the
Niagara Region and are local to each other.  The woman, without
thinking, dialled 905 by default rather than 289 and got me.

At 20:51 2010/05/13, Nick Dubanow wrote:
>I happened to stumble upon CNAC's listing of available CO codes for NPA
>249, which is the new overlay code for 705 in Central/Northeastern
>Ontario.  It is available at http://www.cnac.ca/data/ac249.htm.  I
>noticed that there are numerous CO codes that are protected from
>assignment in the EAS of various rate centres, and these CO codes all
>correspond to the existing 705 CO codes in those rate centres.  Most of
>these seem to be remote communities, but one of them is Parry Sound
>which is far from remote and a fairly well-known cottage destination.
>Penetanguishene is also not too far from Barrie.

There is no technical reason to block the code from use, as there
will only be 10 digit dialing available to everyone. The blockage of
current EAS NXX's in overlapping NPA's is for user clarity only and
generally applied to every local EAS area in all area codes and has
been since overlapping area codes have applied in Canada. There
currently is a standing methodology letter outlining the process in
Canada for overlapping NPA's NXX assignments. I believe it is also
applied in the US in the same manner.

For instance in your Parry Sound example of 203, the customer
confusion calling a person with the same local 7 digit number that
could be your next door neighbour or yourself for that matter, would
be something the telephone industry likes to avoid at all costs.
People can be quite insistent/indignant/abusive about why someone
else has been assigned their number even if it is in a different
community EAS area and different NPA now, think what it would be like
if it was right in the same town on a different companies system or
for that matter the same company.
You wouldn't even want to dream of being on the receiving end of that
call. People literally believe that they own "their number" as long
as they are paying for it. A false belief, but after an hour on the
phone, you tend to give up the explanation process on the NPA
differences and let them write the CRTC to complain.

Dennis

I'm curious about how many distinct local calling areas there are in the US, and
I'm not sure how I would figure this out.

Suggestions?

Thank you!

Chris Silker
Onvoy Voice Services

Subject:
FCC Has Now Approved VeriZon Sale of Most GTE/Contel to Frontier

At the moment as I type this, in the 5-pm hour Eastern, Friday 21-May-2010,
there isn't anything yet at the Federal Communications Commission's (FCC)
website, but a Google News search on "VeriZon Frontier Sale" will
result in well over a hundred results of radio/TV/newspaper/etc.
websites which now put up news items regarding the FCC's approval of
this VeriZon/Frontier transfer.

This would be mostly legacy GTE-including-Contel in several (but not all
of the) states where VeriZon has continued to so far retain such old
GTE-including-Contel, as well as legacy BOC Chesapeake-and-Potomac Tel
(of RBOC Bell Atlantic) including the Crows-Hematite VA ratecenter
(which gets its dialtone from C&P-WV' White Sulphur Springs VA remote
switch).

On Monday 17-May-2010, the Virginia SCC (State Corporations Commission)
gave its final approval for Frontier to take over the Crows-Hematite VA
ratecenter from VeriZon (BA/C&P).

The actual URL for the document is way too long to post, but the general
reference page at the VA-SCC website regarding the transfer from VeriZon
to Frontier regarding Crows-Hematite VA is:

http://docket.scc.virginia.gov/vaprod/DOCUMENTS.ASP?MATTER_NO=127929

which lists the documents in reverse-chronological-order, the 17-May-2010
approval being the top-most document linked to (a pdf file).

And the nine states (of the 14 total in this VeriZon sale to Frontier)
which were required to approve of this sale, had all approved, the
West Virginia PSC approving it last Thursday (13-May-2010).

Five states (of the 14 total) do not have it written in their legislative
statutes or regulatory procedures, for their state regulatory agencies
to approve of such a sale/transfer of telco ownership --

North Carolina Utilities Commission
Michigan Public Service Commission
Indiana Utility Regulatory Commission
Public Service Commission of Wisconsin
Idaho Public Utilities Commission

All that was required for these five states was for the FCC and other
federal regulatory agencies to approve of the sale, as well as any
necessary approval by shareholders of VeriZon and Frontier.

The nine states where approval was required and the date of approval are:

Wednesday 28-October-2009:  Public Utilities Commission of Nevada
Wednesday 28-October-2009:  Public Service Commission of South Carolina
Thursday  29-October-2009:  California Public Utilities Commission
Thursday  11-February-2010: Public Utilities Commission of Ohio
Thursday  18-February-2010: Arizona Corporation Commission
Friday    26-February-2010: Oregon Public Utilities Commission
Friday    16-April-2010:    Washington (state) Utilities & Transportation
Commission
Wednesday 21-April-2010:    Illinois Commerce Commission
Thursday  13-May-2010:      West Virginia Public Service Commission

VeriZon and Frontier jointly announced their decision to have this sale
of telco areas, just over a year ago, on Wednesday 13-May-2009, pending
regulatory/etc. approval. Over the next several weeks/months during the
late-Spring and throughout the Summer of 2009, they also jointly filed
the necessary requests to the required regulatory agencies.

On Tuesday 01-September-2009, the Federal Trade Commission (FTC) granted
approval (involving the Hart-Scott-Rodino Antitrust Improvements Act of
1976, regarding certain conditions of the IRS)

On Tuesday 27-October-2009, Frontier's shareholders approved (approval
by VeriZon shareholders was apparently NOT required, probably since it
didn't involve a purchase, but rather a sale?).

The sale of legacy GTE (and Contel) in California involves only about a
dozen or so exchange areas near the CA state border with Oregon, Nevada,
Arizona, all three states' old GTE and Contel being sold by VeriZon to
Frontier as part of this sale -- old GTE "West Coast Telephone Company"
on the Pacific coast at the Oregon state line, a couple of old Contel
exchanges near Lake Tahoe bordering Nevada, and a handful of old Contel
exchanges in San Bernardino/Riverside/imperial counties which border
Arizona. The vast bulk of (retained so far) GTE and Contel within the
bulk of California are still to be retained by VeriZon. (GTE did sell
off some old GTE and/or Contel in California to Citizens Tel, which is
now Frontier, back in 1995, however).

Also being retained by VeriZon is old GTE and Contel so far retained in
Texas (some old GTE and Contel was sold to the new Valor Telecom back
in 2000, Valor merged with Alltel's spun-off landline in 2006 to become
Windstream).

And the GTE in the Tampa FL metro area is also being retained by
VeriZon. (Old Contel in the Florida panhandle and northeast Florida was
sold to Centel way back in 1985, Centel becoming part of Sprint/United
in the early 1990s, legacy Centel & United spun-off to Embarq in 2006,
and bought by CenturyTel in 2008/09 to become CenturyLink; one Contel
exchange near the FL/GA state-line was sold to Alltel probably in the
mid-1980s, and that exchange was fully consolidated into a nearby
Alltel ratecenter; another Contel exchange in northwest Florida was sold
back in the early 1970s to Southland Tel (AL) which was bought by
Rochester (NY) Tel circa 1991, Rochester Tel renamed itself Frontier in
the mid-1990s and was merged with Citizens circa 2000).

Also being retained by VeriZon is GTE (and Contel) in Pennsylvania and
Virginia. VeriZon is PA is also legacy BOC Bell Atlantic's Bell of
Pennsylvania; VeriZon in VA is also legacy BOC BA/C&P-Va.

While North Carolina (GTE and Contel) is being sold to Frontier, the
Knotts Island NC ratecenter (once-GTE, once-Contel) is being retained
by VeriZon. Knotts Island NC is part of the Norfolk VA LATA, and has
much more of a community of interest with Virginia than with North
Carolina. It is its own (remote) switch -- i.e., it doesn't actually get
"dialtone" from a VA-based c.o.switch, although it is part of the
Norfolk VA LATA, and its "host" switch is in Virginia.

There are a handful of central offices/ratecenters in the Haggerstown MD
LATA, along the West Virginia/Maryland state-line, where VA customers/
ratecenters get dialtone from MD-side c.o.switches, and vice-versa where
MD customers/ratecenters get dialtone from VA-side c.o.switches. VeriZon
does have plans to re-wire these customers so that they will get
dialtone from their own states' side c.o.switches, so that there can be
a "clean break" of the presently VZ/BA/C&P-WV side ratecenters (soon to
be Frontier), from the presently-and-still-retained VZ/BA/C&P-MD side
ratecenters. Local/EAS will be retained where it already exists, only
that it will become inter-LEC (between VZ and Frontier) inter-state
(between MD and VA), instead of intra-VA inter-state.

Previous postings of mine on this subject give more details, including
links to various VeriZon and Frontier regulatory and network/technical
documents at their respective websites.

It is expected that the network/technical/etc. and legal/regulatory/
business/financial/etc. issues (especially with NeuStar-NANPA, NECA,
Telcordia-TRA, etc) will be fully completed for an "official transfer"
from VeriZon to Frontier to be "officially effective" on Wednesday
30-June-2010 / Thursday 01-July-2010.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

I have a small typo at the end of a paragraph near the end of the post
regarding the FCC's approval today (Friday 21-May-2010) of VeriZon's
sale of large areas of landline operations over to Frontier...

[ ... ]

> There are a handful of central offices/ratecenters in the Haggerstown MD
> LATA, along the West Virginia/Maryland state-line, where VA customers/
> ratecenters get dialtone from MD-side c.o.switches, and vice-versa
> where MD customers/ratecenters get dialtone from VA-side c.o.switches.
> VeriZon does have plans to re-wire these customers so that they will
> get dialtone from their own states' side c.o.switches, so that there
> can be a "clean break" of the presently VZ/BA/C&P-WV side ratecenters
> (soon to be Frontier), from the presently-and-still-retained VZ/BA/C&P-MD side
> ratecenters. Local/EAS will be retained where it already exists, only
> that it will become inter-LEC (between VZ and Frontier) inter-state
> (between MD and VA), instead of intra-VA inter-state.

That last line should be:

" ... instead of intra-VZ inter-state."

or: " ... instead of intra-VeriZon inter-state."

(NOT " ... intra-VA inter-state.")


Also, VeriZon is retaining all other RBOC Bell Atlantic: NJ, PA, DE, MD,
DC, VA; and old NYNEX: MA, RI, CT (Byram and Greenwich only, since the
rest of the state is at&t/SBC/SNET-including-Woodbury) ... although
legacy Bell Atlantic in West Virginia (and Crows-Hematite VA) are being
sold to Frontier; and old NYNEX (NET&T) in ME, NH, VT was sold to
FairPoint in 2007/08.

mjc

It was pointed out that there were some other potential typos in that
paragraph regarding the WV/MD border situation. The typo was not one
that would be picked up by any spell-check, and it was more of a factual
error. I mis-typed VA where it should have been WV. And in one case,
I meant to type 'VZ' (for VeriZon) but mis-typed it as VA.

Here is how that particular paragraph SHOULD read:

------------------------------------------------------------------------
There are a handful of central offices/ratecenters in the Hagerstown MD
LATA #240, along the West Virginia/Maryland state-line, where WV customers/
ratecenters get dialtone from MD-side c.o.switches, and vice-versa where
MD customers/ratecenters get dialtone from WV-side c.o.switches. VeriZon
does have plans to re-wire these customers so that they will get
dialtone from their own states' side c.o.switches, so that there can be
a "clean break" of the presently VZ/BA/C&P-WV side ratecenters (soon to
be Frontier), from the presently-and-still-retained VZ/BA/C&P-MD side
ratecenters. Local/EAS will be retained where it already exists, only
that it will become inter-LEC (between VeriZon and Frontier) inter-state
(between MD and WV), instead of intra-VeriZon inter-state.
------------------------------------------------------------------------

The Hagerstown (one 'G') MD LATA #240 spills over into West Virginia in
two distinct areas --

one in extreme eastern WV in the eastern panhandle, where there is both
legacy GTE and/or Contel which was sold to Citizens (now Frontier) by
GTE in the early 1990s shortly after having taken over Contel alongside
legacy BOC VZ/BA/C&P-WV which is now being sold to Frontier. These
WV-side customers do get dial-tone from c.o.switches in West Virginia.

and also in the western part of the WV eastern panhandle / western part
of MD's western panhandle, and it is THIS region where some MD and WV
central offices provide dial-tone to customers in their own states as
well as in each others' states, and this is where VeriZon is planning to
re-wire customers so that they will be provided dial-tone from central
offices in their own states due to the VeriZon sale of legacy BOC BA/C&P-WV
to Frontier.


ALSO, earlier I wrote:

> Also, VeriZon is retaining all other RBOC Bell Atlantic: NJ, PA, DE, MD,
> DC, VA; and old NYNEX: MA, RI, CT (Byram and Greenwich only, since the
> rest of the state is at&t/SBC/SNET-including-Woodbury) ...

WOOPS... re NYNEX, I left out NY (state)! It was not intentional...
but I wonder if it could be an "omen"! :-)

Remember that in early 2004, when VeriZon announced that it was going to
shop for a buyer for legacy GTE-Hawaiian Telephone Company (which did
get sold to the Carlyle Group and was renamed Hawaiian Telcom), VeriZon
also announced that they were shopping for a buyer to takeover all of
legacy BA/NYNEX/NY-Tel ...

with the exception of the New York City Metro LATA #132, which includes
212/646/718/347/917/soon-also-929 NY City, Long Island's 516 (Nassau
County) and 631 (Suffolk County except for Fishers Island NY 631-788),
914 (Westchester County) and most of 845 (Putnam County, Rockland County,
and a small part of Orange County; but the rest of 845 is in the
Poughkeepsie LATA #133), as well as extreme southwest CT (Byram CT and
Greenwich CT ratecenters), the NY City Metro LATA #132 would still be
retained by VeriZon/BA/NYNEX/NY-Tel.

So far, nothing has ever come from this early-2004 VeriZon announcement
of a proposed sale of most of legacy New York Telephone, but you never
know if this could still be in the works. The most obvious "buyer" would
be Frontier, since they have Rochester NY which is one of the predecessors
to Frontier, and Frontier's legacy Rochester-Tel is an entire (non-BOC)
LATA in New York State.

I doubt that FairPoint, which is more-or-less next door in upper New
England, as well as in a few small parts of New York State as well, is
in any financial position to buy out (virtually all of) New York Tel!

Windstream (old Alltel, old Mid-Continent Tel) also has had a footprint
in New York State for decades...

It doesn't appear that CenturyLink has any "footprint" in New York State
neither from old CenturyTel, nor from (Sprint/Embarq) legacy United and
Centel. Also, CenturyLink is going to have its hands full for the time
being with taking over Qwest/US-West (legacy Mountain Bell, Northwestern
Bell, Pacific Northwest Bell) ....

> although legacy Bell Atlantic in C&P West Virginia (and Crows-Hematite VA)
> are being sold to Frontier; and old NYNEX (NET&T) in ME, NH, VT was
> sold to FairPoint in 2007/08.

Mark J. Cuccia
markjcuccia at yahoo dot com

In my original posting earlier this Friday afternoon,
"FCC Has Now Approved VeriZon Sale of Most GTE/Contel to Frontier",
I wrote:

> At the moment as I type this, in the 5-pm hour Eastern, Friday 21-May-2010,
> there isn't anything yet at the Federal Communications Commission's (FCC)
> website, but a Google News search on "VeriZon Frontier Sale" will
> result in well over a hundred results of radio/TV/newspaper/etc.
> websites which now put up news items regarding the FCC's approval of
> this VeriZon/Frontier transfer.

And at the present time, there still isn't yet anything in the way of
links/documents  at the FCC webpage dedicated to the VeriZon/Frontier
transaction, http://www.fcc.gov/transaction/frontier-verizon.html

HOWEVER, at the FCC's _MAIN_ webpage

http://www.fcc.gov

there are links to several documents re VeriZon/Frontier, all available
in Adobe-Acrobat .pdf and most also available in MS-Word .doc:

-----------------------------------------------------------------------
5/21/10
FCC Approves Frontier-Verizon Transaction to Significantly Expand
Broadband in Rural America.

News Release:
http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-298338A1.doc
http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-298338A1.pdf

Order:
http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-87A1.pdf

Genachowski Statement:
http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-87A2.doc
http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-87A2.pdf

Copps & Clyburn Joint Statement:
http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-87A3.doc
http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-87A3.pdf
-----------------------------------------------------------------------

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

By our latest data there appear to be at least 19,000 local calling areas based
upon a unique origin point in the US, including Alaska, Hawaii, Puerto Rico and
the US Virgin Islands. This does not include the possibility that a single
origin point can have more than one defined local calling area.

Ed Sullivan
CCMI

--- In local-calling-guide@yahoogroups.com, "egret17" <chris.silker@...> wrote:
>
> I'm curious about how many distinct local calling areas there are in the US,
and I'm not sure how I would figure this out.
>
> Suggestions?
>
> Thank you!
>
> Chris Silker
> Onvoy Voice Services
>

Ray,

Are you aware that the Local Calling Guide website has either been completely
down or intermittently down for the last few days?

Thanks!

No, I have not noticed any interruption from here. I just did an update over
the weekend, and all of the mirror sites were accessible.

On Tue, Jun 15, 2010 at 5:43 AM, diamond_egroups <diamond45@...> wrote:

> Ray,
>
> Are you aware that the Local Calling Guide website has either been
> completely down or intermittently down for the last few days?
>
> Thanks!
>
>


[Non-text portions of this message have been removed]

SUBJECT:  45 Years Ago-- Succasunna NJ 1ESS, also 305/904 FL NPA Split

2010 is the 45th anniversary of the first #1ESS being cut into full
PSTN service in Succasunna NJ, and is also the 45th anniversary of the
305/904 area code split for northern and north-central Florida. Also,
2010 follows the exact same "days-of-the-week" mapping that 1965 did!

At 12:01am EDT (right after Midnight) on Sunday 30-May-1965, the new
Succasunna NJ #1ESS, the very first one in the Public Switched Telephone
Network, was cut-into service, SUCCNJSUCG0. The 45th anniversary of
this very first #1ESS was JUST OVER two weeks ago!

Succasunna was also the very first time when the general public could
now have such new (optional extra-cost) "Custom Calling" services as
Call Waiting, 3-Way Calling, Call Forwarding, Speed-Calling. The first
two services could be activated with a switch-hook flash, while the use
and/or activation of Call Forwarding and Speed-Calling might have
required special codes, some of which could use the '*' (star) and '#'
(pound) DTMF buttons. Of course, the "star" (*) could be replaced by
rotary dial customers and 10-button touchtone customers (and even used
by 12-button touchtone customers as well) with '11'. The "pound" (#)
would "trail" a one or two digit code, to indicate to the central office
that the customer was finished dialing the number, or maybe that "part"
of the number, and to "cut-through" to the desired number, or to the
next stage of setting up a feature. Rotary customers, 10-button
touchtone customers, and even 12-button touchtone customers could simply
WAIT the three-to-five seconds of post-dial-delay for the central office
to "time-out" and cut through to either the desired number or to the
next stage of the feature set-up. "Trailing 'pounds'" (#) could also be
used on 011+/01+ IDDD calls which had variable length numbers, and also
on 0- (minus) calls direct to an Operator as '0#' since the central
office would be doing a post-dial-delay wait (until time-out) if the
customer simply dialed '0', since the call "could" be a 0+ ten-digit (or
seven-digit HNPA) Operator/Special billing call, or a 011+/01+ IDDD
call, or in post-divestiture years, a '00' call to the IXC/LD operator,
while '0' by itself is now the "local" operator.

In 1974, the only 201-NNX c.o.code on SUCCNJSUCG0 was 201-584. The next
201-NNX code, 201-927, was added to SUCCNJSUCG0 at some point AFTER
October 1975 and BEFORE February 1978.

201-584 was most likely the code for the cutover on 30-May-1965 since
a (partial) list of circa 1960 2L-5N EXchange NAmes in New Jersey posted
to Townson's Telecom Digest/Archives in September 1996 shows "JUstice 4"
(584) as being Succasunna NJ.

But did the SUCCNJSUCG0 1ESS replace a SXS office (or even #5XB) back on
Sunday 30-May-1965? Succasunna NJ is much further west/inside northern
New Jersey well away from the Panel/#1XB (and later #5XB) "revertive
pulsing" region of northeastern New Jersey along the Hudson River across
from New York City. When Englewood NJ first had originating customer DDD
access to just over a dozen major metro areas as of November 1951,
although it wasn't actually "known" as DDD yet, the list of 2L-5N areas
in northeastern New Jersey that Englewood already had direct dial
(message unit and toll) access to did NOT include Succasunna NJ. Of
course, I don't even know if Succasunna NJ was yet a "dial" office in
1951...

Some further details on later developments re Succasunna follow below.

Also in 1965, 45 years ago this year, the northern, north-central, and
northeastern areas of Florida which were still part of the 305 area code
were split off into the new 904 area code. 305 was retained (at that
time) by central Florida and the east coast of Florida from the Cape
Canaveral/Kennedy area southward, all the way to "The Keys". This split
took effect as a FLASH CUT, at 2:01am EDT on Sunday 11-July-1965. There
was _NO_ formal/official permissive dialing period. Such permissive dial
periods with area code changes/splits didn't even happen until the
714/619 split which was permissive on November 1982 (mandatory in
February 1983). Even the Virginia 703/804 split of Sunday 24-June-1973
was also a FLASH CUT with _NO_ formal/official permissive dial period!
(DESPITE what others' webpages attempt to indicate, which also
frequently have the WRONG implementation dates as well!).

Of course, even though there was no "formal/official" permissive dial
period, which in later decades could last anywhere from one month to a
year-and-a-half, it is POSSIBLE that both 904 and temporary continued
use of 305 "might" inadvertently work for several hours after the
official cut-date/time of 2:01am EDT Sunday 11-July-1965, since AT&T-LL,
Southern Bell, etc. had to first open up all valid/new 904-NNX codes in
the network, and then after that was completed (and tested), all old
"matching" 305-NNX codes which previously referenced locations now
officially in 904, had to be "removed" or "turned off" with vacant or
intercept type recordings if someone still dialed the old 305 NPA for
placing calls to this now-904 part of Florida, those same 305-NNX codes
to ultimately be re-assigned to locations in that part of Florida which
retained the 305 NPA code (at that time). Such an "inadvertent"
permissive dial period "could" have taken effect, for who knows...
3-hours? 6-hours? 8-hours? 12-hours? following 2:01am Eastern that
Sunday morning, 11-July-1965. I was only four years old at the time,
and while I was fascinated by the telephone even at that age, I wouldn't
have been doing any test-dialing to find out back then!!!!

With the July 1965 Florida 305/904 area code split, the state now had
three area codes, the third area code being 813 for the west (Gulf)
coast of southern Florida, all GTE (now VeriZon, still being retained
by VeriZon) for the Tampa Bay area, and CenturyLink/Embarq/Sprint/United
for the Fort Meyers area. 813 was carved out of 305 back in the early
1950s, although it wouldn't be until the early 1960s when calls could
be DIALED by customers elsewhere in the US/Canada to this 813 southwest
"independent" region of Florida. The _OLD_ name for VZ/GTE Tampa was
Peninsular Telephone Company which General Telephone purchased circa
1968, and the _OLD_ name for the CenturyLink-once-United Fort Meyers
area was Inter-County Telephone Company which United purchased probably
in the mid-1960s.

In Spring 1988, Florida's fourth area code, the 407 area code split from
305, for the Orlando and NASA regions (Orange County, Seminole County,
Osceola County, Brevard County, part of Volusia County, and a very small
part of Lake County) and also for points _north_ of Broward County --
i.e., Palm Beach County, Martin County, St.Lucie County, Indian River
County. 305 (at the time) was retained by Broward County, Dade County
(Miami/etc), and the "Keys" part of Monroe County.

Starting in 1995 and continuing through 2002, all four area codes in
Florida (as of 1988) have had several splits and/or overlays, the 904
area code included -- 352 for north-central Florida (Gainesville) in
1995, 850 for the panhandle (Tallahassee to Pensacola) in 1997, and 386
for both the Daytona area and points to the west of the Jacksonville
area/north of the Gainesville area in 2001. The 904 area code was
retained by the Jacksonville area itself in northeast Florida.

Some later developments regarding Succasunna NJ:

The second 201-NNX office code, 201-927, was added to the original
201-584 (JUstice 4-) at SUCCNJSUCG0 at some point AFTER October 1975,
but BEFORE February 1978.

SUCCNJSUCG0 (still a 1ESS, never upgraded to a 1AESS by NJ-Bell/Bell
Atlantic, WECO/Labs) was replaced by a new 5ESS, SUCCNJSUDS5, on
Saturday  28-September-1991. It still had the same two c.o.codes,
201-584 and 201-927.

201-252 was added to SUCCNJSUDS5 on Saturday 30-January-1993.

Succasunna NJ fell on the 973 side of the 201/973 area code split of
1997. Permissive dialing of the new 973 area code began on Sunday
01-June-1997. Mandatory use of the new 973 area code, meaning that the
use of the 201 area code for Succasunna and other parts of north-central
and north-western (and even some northeastern NJ was no longer allowed)
took effect on Saturday 06-December-1997 -- i.e., 201-252, 201-584, and
201-927, were replaced respectively by 973-252, 973-584, 973-927.

A new 973-NNX code, the fourth, 973-598, was added to SUCCNJSUDS5 on
Wednesday 30-September-1998.

In December 2001, the 973 area code was overlaid with the new 862 area
code. At the same time, 201 was overlaid with 551, and 732 (which split
from 908 back in 1997) was overlaid with 858. (908 had split from 201
back in 1990/91).

There are several other 973-NXX codes associated with the Succasunna NJ
ratecenter, as well as some new 862-NXX codes, and even some (default)
VeriZon-Wireless 201-NXX office codes which might probably have been
legacy Bell-Atlantic/(NYNEX) Mobile office codes pre-dating the 201/973
area code split of 1997 which were "grandfathered" in the 201 NPA
instead of changing to 973-NXX codes back then, also all associated with
the Succasunna NJ ratecenter.

But the VeriZon/Bell-Atlantic/NJ-Bell SUCCNJSUDS5 5ESS, which replaced
the 30-May-1965 SUCCNJSUCG0 1ESS (THE VERY FIRST) in 1991, has only
four "default" c.o.codes associated with it, all four also being
associated with the Succasunna NJ ratecenter, originally part of the
201 area code, but splitting/changing to the new 973 area code during
1997:

973-252 (since 30-January-1993, initially as 201-252)
973-584 (the ORIGINAL code as 201 "JUstice 4", predates the 1965 1ESS)
973-598 (since 30-September-1998)
973-927 (since the mid-1970s, initially as 201-927, originally on the 1ESS)

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

at&t/BellSouth Retiring Two More 1AESS C.O.Switches

at&t-ILEC is replacing two more 1AESS central office switches during
1st-Q/2011. Both are in legacy BellSouth states, one in Southern Bell
in West Palm Beach FL, the other in Southern Bell in Birmingham AL.

The two network disclosure documents can be found at the at&t website
of such documents, http://www.att.com/gen/public-affairs?pid=3137
click on the link to the southeast (BellSouth) states to scroll down.

http://www.att.com/public_affairs/regulatory_documents/ATT20100622L.1_Web.doc
dated Tuesday 22-June-2010, announces the retirement and replacement of
the currently existing Alcatel-Lucent BRHMALEW95E 1AESS, "Eastwood" in
Birmingham AL, scheduled for Friday night 11-February-2011. The 205-NXX
c.o.codes that are "default" served by this switch for at&t/BellSouth
are 205-951,956,957. All are associated with the Birmingham AL ratecenter.
The SS7 Point Code for the current 1AESS is 252-134-004. A Genband-Nortel
(Genband is the successor to most of Nortel's c.o.switch division)
MG9000-ABI-Remote (digital packet remote) BRHMALEWRPA will replace the
existing 1AESS, to be hosted by the Nortel DMS-100/200 tandem BRHMALMTDS0/0GT.
This tandem is indicated in the at&t ILEC network/technical disclosure
document as a DMS-500, but other sources show this switch as a DMS-200.
The tandem does NOT presently serve any local subscriber loops for dial-tone,
its CLLI right now is only BRMHALMT0GT, so it will need to be expanded
as such -- the DMS-100 function added along with the end-office CLLI
extension -DS0, so that it can "host" the new Genband-Nortel digital
packet remote that is replacing the retiring 1AESS. The SS7 Point Code
for the tandem/host is 252-134-023, which will also be the same
SS7 Point Code for the new digital packet remote switch.

http://www.att.com/public_affairs/regulatory_documents/ATT20100618L.1_Web.doc
dated Friday 18-June-2010, announces the retirement and replacement of
the currently existing Alcatel-Lucent WPBHFLRB84E 1AESS, "Riviera Beach"
in West Palm Beach FL, scheduled for Friday 18-March-2011. The 561-NXX
c.o.codes that are "default" served by this switch for at&t/BellSouth
are 561-494,840,841,842,844,845,848,863,881,882. All are associated with
the West Palm Beach FL ratecenter. It seems that during the old 2L-5N
EXchange NAme days, those 84x codes which did exist back then were known
as "VIctor (x)". Also note that the 561 area code for this part of
Florida had split from the 407 area code back in 1996, and even the
407 area code (which still includes the Orlando area) had split from
the original 305 area code back in 1988. The SS7 Point Code for the
current 1AESS is 252-046-033. A Genband-Nortel MG9000-ABI-Remote
(digital packet remote) WPBHFLRBRP0 will replace the existing 1AESS,
to be hosted by the Nortel DMS-100/200 tandem WPBHFLGRDS2/02T, "Gardens"
in West Palm Beach. This tandem does NOT presently serve any local
subscriber loops for dial-tone, its CLLI right now is only WPBHFLGR02T,
so it will need to be expanded as such -- the DMS-100 function added
along with the end-office CLLI extension -DS2, so that it can "host"
the new Genband-Nortel digital packet remote that is replacing the
retiring 1AESS. The SS7 Point Code for the tandem/host is 252-046-029,
which will also be the same SS7 Point Code for the new digital packet
remote switch.

Some of the 1AESS switches that at&t/Ameritech/Michigan-Bell is retiring
later this year (and early next year), and which the very last 1AESS in
the New Orleans area (Aurora, NWORLAAR---) when retired earlier this
year (January 2010) by at&t/BellSouth/South-Central-Bell, are being
replaced with those Genband-Nortel MG9000-ABI digital remote packet
switches. I don't know what the 'MG' stands for, but 'ABI' stands for
"Access Bridging Interface".

Assuming that there are no further announcements of retirements of 1AESS
switches (being replaced with digital or digital-packet switches) for
this year (2010) or early next year (2011), after the retirement and
replacement of the four at&t/MI-Bell and two at&t/BellSouth 1AESS
offices is completed, there will be around 55 remaining 1AESS offices
still within the US, as follows:

VeriZon/Bell-Atlantic/C&P will still have their three 1As remaining,
one each in: Baltimore MD, Richmond VA, Norfolk VA;

at&t/SBC/Ameritech/MI-Bell will still have their three remaining 1As,
one each in: Pontiac MI suburb of Detroit, Lansing MI, Grand Rapids MI;

at&t/SBC/Ameritech/IL-Bell will still have their two remaining 1As,
both in the Chicago IL area: Chicago "AUStin", Oak Park IL;

at&t/BellSouth/Southern-Bell will still have 18 remaining 1As, eight in
the Atlanta GA Metro and four more scattered about central/southern GA
(one each in Savannah GA, Waycross GA, Augusta GA, Warner-Robbins GA),
as well as six in Florida -- two in the Jacksonville FL Metro area and
four more still in the Miami/Ft.Lauderdale FL Metro area;

at&t/BellSouth/South-Central-Bell will still have eight 1As remaining,
one in Nashville TN, three more in the Birmingham/Bessemer AL metro
area, two in Shreveport LA, and the two c.o.switches here in Lafayette LA;

at&t/SBC/Southwestern-Bell will still have 21 remaining 1As, seven in
the St.Louis MO metro area, three in the Dallas TX metro area, four in
the Ft.Worth TX metro area, four in the Houston TX metro area, and three
more scattered about Texas (one each in Beaumont TX, Odessa TX, El Paso TX).

Further details on these 55 remaining 1AESS offices (CLLIs, default BOC
NPA-NXX office codes, switch-name, etc) as well as details on the four
1As in the Detroit MI area which are being retired and replaced with
digital/packet switches later this year or early next year (2011), can
be found in my posts on this topic from earlier this year.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

Back in April 2010, I had posted that the 2010-1Q NANPA Newsletter made
mention that toll-free 866 was approaching "exhaust" (estimated around
2011/12 time-frame), and that the North American telco industry would
request that the FCC approve opening up the "next" toll-free special
area code, 855, for assignment of actual numbers to actual customers.

Today, Tuesday 06-July-2010, NeuStar-NANPA issued Planning Letter #407,
regarding the opening up of toll-free special area code 855, this PL-407
can be downloaded from http://www.nanpa.com/pdf/PL_407.pdf which mentions
that on (Friday) 25-June-2010, the Wireline Competition division of the
FCC has authorized the opening up of 855 at "12pm" Eastern 01-October-2010.
I assume that this means "12 Noon" (Eastern) on Friday 01-October-2010
and not 12:01am (right after midnight) starting on that Friday...

NeuStar-NANPA does not "directly" assign ten-digit 8YY-nxx-xxxx line-numbers
to requesting customers or carriers. That is handled by a couple of
North American telephone industry consortium bodies, one of them being
DSMI (Database Services Management Inc), the other being "SMS Toll-Free".

At one time, Lockheed-Martin was involved with one of these two consortiums,
known as the "800 NASC" (Numbering Assignment Service Center). This was
several years before LM took over basic/overall/general NANPA functions
from Bellcore in the 1997/98 timeframe. I don't know if LM still has
anything to do with any "800 NASC" or "SMS Toll-Free" body anymore, but
I think that DSMI and/or "SMS Toll-Free" is still "somehow" associated
with Telcordia (formerly Bellcore).

The specific recent (1st half 2010) procedural history regarding 855
with the FCC and various industry bodies is outlined in this Planning
Letter.

One thing that is not specifically mentioned, though, is that originally,
both 866 and 855 were to have been introduced for toll-free numbering
assignments "nearly" simultaneously, both in Spring 2000, a (few) weeks
to a month apart from each other, 866 first followed by 855. I don't
remember the exact planned implementation dates/interval though.
However, the FCC postponed those dates. I seem to remember that the
ultimate implementation of 866 for actual line-number assignments was
in Fall 2000 (November?), and that 855 was "postponed until further
notice". The note in PL-407 mentions that 866 was actually implemented
in July 2000 (Summer). It was ten years ago, and I don't have immediate
access to my notes from back then.

There is no mention in today's Planning Letter about testing for the
new toll-free 855 special area code... I do remember that the 250 office
code within all toll-free area codes is reserved for "testing purposes"
on the -0000 through -1499 line-number block. (I assume that 8yy-250-1500
through -9999 is available for assignment to regular customers though).

Specific four-digit line-numbers or specific "blocks" of line-numbers
within the -0000 through -1499 range are to be "duplicate assigned" to
the same service providers regardless of the actual toll-free SAC, i.e.,
it is the same assignment on 800, 888, 877, 866, now 855, and future
844, 833, 822, etc. However, with mergers, name-changes, etc. and just
the overall change in the telco industry over the past ten years, I
don't know "exactly how" the ATIS-INC/NRRIC/OBF/etc. bodies which
maintained the 8yy-250-0000 thru -1499 test-number assignments still
hold today (2010). i.e., since VeriZon/NYNEX/NET&T no longer operates
in ME/NH/VT, does FairPoint have any (new) 855-250-xxxx or range of
-xxxx's for testing, separate and distinct from the legacy 8yy-250-xxxx(s)
for VZ/NET&T? Same for Frontier in legacy BOC areas in West Virginia,
now that this is no longer part of VZ/Bell-Atlantic which has its own
legacy 855-250-xxxx(s), etc. Remember that "for the most part" the
incumbent LEC maintains (copies of) databases for translations to
determine "which" IXC (or even LEC/CLEC) to hand-off a dialed 8yy-nxx-xxxx
call over to, the actual service provider(s) that route the dialed
toll-free number being determined by the paying/called customer who
has "purchased" that toll-free 8yy number/service.

Ten years ago, 855 was originally to have been implemented almost
simultaneously with 866, even though 855 has been postponed for ten years.
The local, LATA, and interexchange carrier networks (landline and
wireless, etc), were all to have been "readied" for proper database-dipping,
translation, and routing of 866-nxx-xxxx _AND_ 855-nxx-xxxx numbers as
of Spring 2000. Thus, if nothing has changed, and all new switches
implemented in the network since then have 855 opened up as "valid"
along the same lines as 866, 877, 888, 800 are for routing/etc., then
there "should" be no problem with opening up assignment of 855-nxx-xxxx
numbers and their proper routing throughout the network regardless of
which carrier/telco/etc. a call originates on, placed to an 855-nxx-xxxx
number.... Well, considering how the telco industry is these days,
I guess "we'll see"! (I do remember numerous routing problems with the
introduction of 877 back in Spring 1998, mainly with origination from
BellSouth Mobility)

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

July 11th in History: 1948 Media PA #5XB, 1965 FL 305/904 NPA Split

I had mentioned in previous postings about how this year, 2010, is the
45th Anniversary of the very first #1ESS switch being cut-in to full
public PSTN/NANP service (as opposed to "experimental only", i.e., the
Morris IL ECO of 1960-62) at Succasunna NJ on Sunday 30-May-1965, and I
had also mentioned that the Florida 305/904 Area Code Split took effect
as a FLASH-CUT also that year, on Sunday 11-July-1965 at 2:01am EDT.

And I had also mentioned the fact that calendar year 2010 is identical
to calendar year 1965 as far as how the dates fall on particular
days-of-the-week. This year, 2010, follows 1965, in that 30-May and
11-July are both Sundays, in both years.

ALSO, 2010 is the 62nd Anniversary of the very first #5XB switch being
cut-in to full public PSTN/NANP service (as opposed to experimental
"only"), also on Sunday 11-July-1948. Note that both the 305/904 Florida
NPA Split and the first #5XB being cut-in at Media PA both happened on
July 11th in their respective years, and both were on a Sunday, so even
1948 has the same day-of-week "mapping" as does 1965 and 2010.

Regarding the first #1ESS in Succasunna NJ, I had mentioned in my
earlier posting that I was unsure if it replaced a SXS office or a
#5XB office. I tend to think that it replaced an earlier Step-by-Step
(SXS) office. I did some digging up of info from google searches, and
there was a reference that AT&T/WECO/Labs worked with NJ Bell for the
cut-in of this very first #1ESS to be installed in a town that had
been served by a (roughly) 4000-line SXS switch. And since the first
#5XB office in Media PA was only installed 17 years ago, I doubt that
anything less than 17 years old (i.e., a #5XB) would have been in
service at Succasunna NJ, only to be pulled from service to be replaced
with the very first #1ESS.

As for the #5XB in Media PA, a suburb of Philadelphia PA, it is likely
that it replaced a previously existing common-battery manual central
office. The suburbs of Philadelphia had mostly been manual -- Panel had
NOT yet extended into those suburbs. The first #1XB office was only
ten years old, first being installed in Brooklyn NY in 1938. It seems
unlikely that AT&T/Western/Labs and Bell of Pennsylvania would have
pulled a #1XB that was only ten years old to replace it with the first
#5XB office...

Englewood/Teaneck NJ was able to dial their calls to Media PA as part
of the Philadelphia PA Metro area (215) with the first public use of
(limited) DDD (Direct Distance Dialing) effective November 1951, even
though it would be another 2-3 years before AT&T/Bell would actually
begin referring to customer "nationwide" long distance dialing as "DDD".
The 1951 customer instruction booklet only lists the TOWN name of Media
under Philadelphia and vicinity. It does NOT indicate the particular
NNX code -- or rather 2L EXchange NAme (plus 3rd-digit) for Media PA,
which would probably have been "LOwell 6-" (see below).

The "ratecenter" name for Media PA is officially known as "Philadelphia
Suburban Zone #12". The c.o.switch eventually had MEDIPAMEMG0 for its
CLLI code, the -MG(x) extension for "Marker Group", which was the code
extension used for Crossbar offices providing "local" end-office
services or functions.

It appears that the #5XB was still in service at Media PA as late as
1985. By 1990/91, Media PA was being served by a #5ESS (digital),
MEDIPAMEDS0. It does NOT seem that Media PA had any interim period of
being served by a #1ESS or #1AESS (non-digital), but was cutover from
#5XB directly to a digital ESS, the #5ESS, sometime after 1985 and
before 1991, but I don't have the exact date/year of that cutover.

The original 2L-5N "name" would most likely have been "LOwell 6-".
There was a new 215-565 added before 1974 (I do not have the year),
but it seems that 215-565 was added AFTER 7D ANC (All Number Calling)
format started to replace the 2L-5N "name" format. New office codes
would not have been "officially" referred to by 2L-5N, although since
both 565 and 566/LO.6 are both 56x codes in the same switch, one "could"
unofficially refer to 565 as "LOwell 5-". Later 215-NNX codes were added
later on, and the town of Media PA also fell on the new/split side of
the 215/610 area code split of 1994. VeriZon/BA/B-Pa also has a new
484-NXX code added since 484 had overlaid 610 back in 1999. The
ratecenter of Media PA/Philadelphia Suburban Zone #12 also has other
610-NXX and 484-NXX codes "default" assigned to wireless and CLECs as
well.

I don't know when the last #5XB (or any other manufacturer's crossbar)
in the NANP/DDD network was replaced with (digital) ESS, but it would
have been by the late 1990s-era. The last "known" US/Canada SXS office
was in Nantes PQ Canada, replaced with a DMS-10 in 2002. The last Panel
offices were being pulled from service in the late 1970s or maybe even
as late as 1982, I don't remember the "exact" date (year) when the last
"known" Panel office was removed from the PSTN/NANP/DDD network. But
there are still roughly 60 remaining #1AESS offices in the PSTN/NANP/DDD
network as I had mentioned in postings earlier this year.

VZ/BA/C&P has three of them, one each in:
Baltimore MD, Richmond VA, Norfolk VA.

at&t ILEC has the rest of them -- a handful in Michigan Bell (four of
them to be replaced with digital sometime this year or next year), two
in Illinois Bell in Chicago Metro, and several in Southern/South Central
Bell and Southwestern Bell, concentrated in certain specific metro
areas.

Other than the four known replacements this year or next year in
Michigan, I have no idea when at&t or VZ intends on replacing the other
remaining 1As. There will still be a few in Michigan even after the
four currently known replacements.

But as mentioned in my previous posting, Succasunna NJ #1ESS (which
appears to have never been upgraded to a #1AESS) was replaced with a
#5ESS in September 1991.

ANYHOW, Sunday 11-July-2010 is the 45th Anniversary of the Florida
305/904 Area Code split in 1965, and it will also be the 62nd Anniversary
of the very first public network use of #5XB cut-in at Media PA in 1948.
11-July-1948, 1965, and even 2010 also ALL0 happen to be on a SUNDAY as
well.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

The Pennsylvania-PUC has unanimously approved (5-0) an OVERLAY for the
570 area code region in north-central and north-eastern Pennsylvania.
The PA-PUC had actually approved the overlay last week, on Thursday
15-July-2010. There is a Press Release at the PA-PUC's website:

http://www.puc.state.pa.us/General/press_releases/Press_Releases.aspx?ShowPR=256\
3

and there are media reports at various local area radio/TV/newspaper
websites.

The PA-PUC's press release indicates that the new overlay area code will
be needed by 3-Q/2011, and hopes that the telco industry will have the
overlay implemented by 01-March-2011. At present, 7-digit dialing is
still possible for local intra-570 calls, so there will have to be what
is probably going to be an expedited transition to mandatory ten-digit
intra-570 local dialing.

It is also possible that further or stricter number/NXX-code conservation
measures could postpone the implementation of the new area code overlay.
This will be determined by the telco industry and regulatory, probably
when the next "NRUF" Survey is released by NeuStar-NANPA in late
October or early November 2010.

The new area code digits are NOT indicated at this current PA-PUC press
release of Thursday 15-July-2010, but my *GUESS* is that 272 will be the
new overlay area code.

570 split from 717 (retained by eastern south-central Pennsylvania) back
in 1998/99.

There are already overlays in Pennsylvania. Southeastern PA (Philadelphia
Metro) is the 215/267/(future-445) "core" part, and 610/484/(future-835)
is the "outer ring" (suburbs) part, 610 first split from 215 in 1994/95.
The initial 215/267 and 610/484 overlays took place in 1999.

Southwestern PA including Pittsburgh Metro was originally intended to
be overlaid, the original 412 area code overlaid with 724 back in 1997,
but that was canceled, a split implemented instead in 1998. Pittsburgh
PA Metro kept 412, the other areas of southwestern PA split to 724 in
1998. ALL of the 412 and 724 area was "officially overlaid" in Summer 2001,
but only ten-digit mandatory dialing was implemented so far. Even to this
day, there are still not any 878-NXX c.o.codes from the 878 overlay NPA.
However, 724 is almost out of available NXX c.o.codes, so it is likely
that there will finally be some 878-NXX codes assigned/activated by
late this year (2010) or early next year (2011).

The other two area codes in Pennsylvania (both dating back to the official
"origins" of the NANP/Area Code Format of October 1947), have also had
area code "relief" planning by the telco industry and regulatory. 814
for northwestern PA and western south-central PA, and also 717 which is
still retained by eastern south-central PA following the 717/570 split
of 1998/99 -- both have relief petitions pending before the PA-PUC,
overlays area requested in both cases by the telcos. No indication of
when the PA-PUC will make any kind of announcements as to split vs.
overlay (overlays are likely), and obviously not the codes themselves,
but my *GUESS* is for:
582 as the relief code for 814,
and 223 to overlay 717.

VeriZon/Bell-Atlantic/Bell-of-Pennsylvania is the dominant ILEC (BOC)
for Pennsylvania, but VZ/GTE-and-Contel is also dominant throughout most
of Pennsylvania. The legacy GTE including Contel in PA has been retained
by VZ and has been "integrated" into the day-to-day operations of
legacy BOC BA/B-PA, just as it has been in BA/C&P-Virginia. I doubt that
VeriZon will sell-off legacy GTE/Contel in PA or VA, unless they also
sell-off all of their legacy landline operations (BOC as well) in either
state. But I tend to think that PA and VA are rather profitable when
compared to West Virginia.

Other ILECs in PA which also operate in other states include:

- Windstream (from Alltel and also the local "Denver & Ephrata Tel")
- CenturyLink (from Embarq/Sprint/United)
- Frontier (from Citizens and others; but apparently NOT from any GTE
nor Contel within Pennsylvania which seems to all still be VeriZon)
- TDS Telecom
- Armstrong (which is also an ILEC in parts of NY, WV, MD)

and of course, there are other small locally owned independent rural
ILECs as well throughout the state.

I expect that NeuStar-NANPA and/or the PA-PUC will announce the actual
code digits for the overlay to 570, within another several weeks, and as
mentioned above, my *GUESS* is that 272 will be the overlay. Also, I
tend to think that the PA-PUC will be making their split vs. overlay
decisions and subsequent announcements on 814 and 717 later this year,
in Fall 2010.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

On Tuesday 20 July 2010, the CRTC announced that Toronto ON will likely
need an additional area code to its already existing 416/647 overlay,
by or during 2015.

http://crtc.gc.ca/eng/com100/2010/r100720.htm
for the CRTC press release

and

http://crtc.gc.ca/eng/archive/2010/2010-490.htm (HTML)
http://crtc.gc.ca/eng/archive/2010/2010-490.pdf (Adobe-Acrobat)
for the Telecom Notice of Consultation CRTC 2010-490

It doesn't actually specify that the new area code "must" be an
additional overlay, but that the telco industry in Ontario (through
the Canadian Numbering Administration) is to come up with one (or more)
area code relief options submitted to the CRTC.

However, considering that the last area code split in Canada was the
Alberta 403/780 split of early 1999, that every new area code introduced
in Canada in 2001, 2006, 2008, 2010, and planned so far for 2011-forward
is going to be an overlay, especially since 416/647 is already in an
overlay, and that adjacent 905/289 for the Toronto ON suburbs/"outer
ring" is to be overlaid with 365 in March 2013, it is very likely that
the existing 416/647 area code region for Toronto ON "itself" is going
to be further overlaid, NOT split. The "likely" new area code could be
437, but this is not yet a "given".

A few days ago, SAIC-CNA (Canadian Numbering Administrator) set up the
beginnings of a page at its website for documents and announcements
regarding additional relief (early 20-teens) for the 416/647 region,
http://www.cnac.ca/npa_codes/relief/416-647/relief_416-647.htm

Right now, it is only a "skeleton" page, with no additional documents
nor announcements (other than some June 2010 "NRUF-related" documents
regarding 416/647), it does not yet even have the CRTC's announcements
of Tuesday 20-July-2010. But those CRTC documents and other documents
going forward regarding 416/647/ (future 437 ??), will be posted here.

The existing 905/289/forthcoming-365 area code region for the Toronto ON
suburbs (outer ring) split from the 416/647 Toronto ON "City" area code
as the 416/905 area code split, back in 1993/94. This was the first
completely "brand new" geographic/POTS area code introduced in Canada
since 1962 when there was the 705/807 split in western Ontario, and when
709 was introduced for Newfoundland/Labrador splitting from having to
share from New Brunswick's 506 (although the use of 506 to identify or
"reach" any exchanges in Newfoundland/Labrador (NL) would have only been
used by Operators prior to 1962 since customer DDD "to" NL didn't start
until 1962 when 709 was "split" from sharing from NB's 506).

There were further splits in Canada in the later 1990s, but starting in
2001, every new area code in Canada was an overlay. In 2001, Toronto's
416 was overlaid with 647, and the Toronto Metro suburbs and "outer
ring" 905 was overlaid with 289. Other southern/southeastern Ontario
area codes which border 905/etc, or are at least close by to 416/etc,
have since been overlaid: 519 overlaid with 226 in 2006, 613 overlaid
with 343 this year 2010, and 705 to be overlaid with 249 next year 2011.
And then the 905/289 Toronto ON Metro's "outer ring" is to be overlaid
with 365 in March 2013.

And now it is announced by the CRTC that the 416/647 area code overlay
pair for Toronto ON "itself", will need further area code relief by 2015,
and although not specified as a "given" by the CRTC, it is very likely
that this will be a further overlay, and it is also quite likely that
437 could be the additional new area code.

More details to come as they are known.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

Today, Wednesday 28-July-2010, the Canadian Radio-Television and
Telecommunications Commission (CRTC) approved the future overlay of
Manitoba's 204 Area Code with the new 431 Area Code.

The Canadian telcos, through the SAIC-CNA (Canadian Numbering
Administration) has been preparing for relief for Manitoba's 204,
with an overlay as the primary relief method, for about a year now.

The CRTC's press release, dated today, announcing their decision for
this forthcoming area code relief, Telecom Decision CRTC 2010-526,
can be found at: http://www.crtc.gc.ca/eng/com100/2010/r100728.htm

The actual CRTC decision (2010-526) can be found at:
http://www.crtc.gc.ca/eng/archive/2010/2010-526.htm (HTML)
http://www.crtc.gc.ca/eng/archive/2010/2010-526.pdf (Adobe-Acrobat)

Implementation dates for the 204/431 Overlay are as follows...
Note that not all of these dates are referenced in the CRTC documents;
Note that these dates might not necessarily be the same as tentative
dates I had mentioned in previous postings for Manitoba's 204/431 NPA
Relief Planning.


Transition from 7-Digit to 10-Digit Local Intra-204 Dialing
-----------------------------------------------------------

Thursday  01-December-2011
Start date of a week-long "phase-in" for (official) permissive 10-digit
dialing alongside existing 7-digit dialing where not already in effect
(some c.o.switches already allow 10-d permissive)

Sunday    29-July-2012
Start date of a week-long "phase-in" for a REMINDER recording on local
calls still dialed as just 7-digits -- the 7-digit dialed local calls
will still be completed following the recording.

Saturday  20-October-2012
Start date of a week-long "phase-in" for MANDATORY dialing of 10-digit
local calls (no more 7-digit dialing allowed) -- such 7-digit dialed
local calls will NOT complete, but will instead only connect to this
mandatory 10-digit recorded announcement.


New 431-NXX C.O.Codes Request/Activation Dates
----------------------------------------------

Thursday  03-May-2012
earliest date for requesting assignment by the CNA of new 431-NXXes

Saturday  03-November-2012
(earliest) activation date for such new (pre-assigned) 431-NXXes


431-N10 Codes/Dates for -TEST/BILL Numbers
------------------------------------------

Monday    30-April-2012
Start of Test-Numbers

Monday    03-December-2012
Disconnect Test-Numbers (start of month-long disconnect period)

The TEST/BILL numbers could have distinct verbage for BILL vs. TEST,
and are also likely to be bi-lingual, English-then-French.

Also, the "10-digit reminder" and "10-digit mandatory" recordings for
local calls still dialed as just seven-digits following the respective
dates, are likely to be bi-lingual, English-then-French.

There is a rather sizeable French-speaking population in Winnipeg and
elsewhere throughout Manitoba.

The numbers ending -8378 (TEST) are _NOT_ "supposed" to return billing
supervision, while the numbers ending -2455 (BILL) _are_ "intended" to
return billing supervision.

At this time, it is expected that the MTS (the ILEC side of MTS-Allstream)
will have 431-610-8378/2455.

- Bell-Canada's "Bell-West" is a CLEC in Winnipeg MB;

- Telus Integrated Communications is a CLEC service in Winnipeg MB;

- Allstream (the CLEC and competitive IXC side of MTS-Allstream) has
had a presence in Winnipeg MB, long before MTS' 2004/05 purchase of
Allstream (legacy AT&T-Canada-LD, legacy Unitel, legacy CNCP);

- but at this time, Rogers does NOT have any service in Manitoba
(neither Rogers-CallNet legacy Sprint-Canada/CallNet, nor Rogers Cable);

- however Shaw (Cable-TV, CLEC) provides service in Manitoba.

At this time, I don't know how many other -TEST/BILL numbers will be
provided by the various CLECs, nor how other 431-N10 codes for those
-TEST/BILL numbers might "map" to the various CLECs which might choose
to provide 431 NPA -TEST/BILL numbers.

SAIC-CNA's webpage for downloadable documents on Manitoba's 204/431 NPA
Overlay is: http://www.cnac.ca/npa_codes/relief/204/relief_204.htm

The CNA/etc. has been preparing a draft Planning Letter which will be
eventually finalized and subsequently forwarded to NeuStar-NANPA at a
later date for NANPA to upload to their website as a NANP Planning Letter.

More details as they become available.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

What is the current Government system in place in the event of a national
disaster?

On Wednesday 21-July-2010, I wrote in
"PA-PUC Approves Overlay to 570 Area Code":

> The Pennsylvania-PUC has unanimously approved (5-0) an OVERLAY for the
> 570 area code region in north-central and north-eastern Pennsylvania.
> The PA-PUC had actually approved the overlay last week, on Thursday
> 15-July-2010. There is a Press Release at the PA-PUC's website:
>
>
http://www.puc.state.pa.us/General/press_releases/Press_Releases.aspx?ShowPR=256\
3
>
> and there are media reports at various local area radio/TV/newspaper
> websites.
>
> The PA-PUC's press release indicates that the new overlay area code
> will be needed by 3-Q/2011, and hopes that the telco industry will
> have the overlay implemented by 01-March-2011. At present, 7-digit
> dialing is still possible for local intra-570 calls, so there will
> have to be what is probably going to be an expedited transition to
> mandatory ten-digit intra-570 local dialing.
>
> [ ... ]
>
> The new area code digits are NOT indicated at this current PA-PUC
> press release of Thursday 15-July-2010 ...
>
> ... but my *GUESS* is that 272 will be the new overlay area code.

Today, Friday 30-July-2010, the PA-PUC is now reporting that 272 is
indeed going to be the overlay relief area code for the existing 570
area code.

http://www.puc.state.pa.us/General/press_releases/Press_Releases.aspx?ShowPR=258\
3

Radio/TV/Newspaper/etc. media/press/news websites are also now reporting
272 as the relief overlay area code, per the PA-PUC announcement.

NeuStar-NANPA's "Planned NPAs Not Yet in Service" webpage,
http://www.nanpa.com/nas/public/plannedNpasNotInServiceReport.do?method=displayP\
lannedNpasNotInServiceReport
also indicates 272 as the forthcoming overlay to 570 in Pennsylvania.
Actually, the page at NANPA's website was referencing 272 for 570 since
last week, as early as Wednesday 21-July-2010 (maybe even earlier?),
but it was only today that the PA-PUC and subsequently the press/media
(radio/TV/newspapers/etc) first publicly announced that 272 is to be the
new area code.

> [ ... ]
>
> The other two area codes in Pennsylvania (both dating back to the
> official "origins" of the NANP/Area Code Format of October 1947),
> have also had area code "relief" planning by the telco industry and
> regulatory. 814 for northwestern PA and western south-central PA, and
> also 717 which is still retained by eastern south-central PA following
> the 717/570 split of 1998/99 -- both have relief petitions pending
> before the PA-PUC, overlays area requested in both cases by the telcos.
> No indication of when the PA-PUC will make any kind of announcements
> as to split vs. overlay (overlays are likely), and obviously not the
> codes themselves, but my *GUESS* is for:
>
> 582 as the relief code for 814,
> and 223 to overlay 717.

[ ... ]

> I expect that NeuStar-NANPA and/or the PA-PUC will announce the actual
> code digits for the overlay to 570, within another several weeks, and
> as mentioned above, my *GUESS* is that 272 will be the overlay. Also,
> I tend to think that the PA-PUC will be making their split vs. overlay
> decisions and subsequent announcements on 814 and 717 later this year,
> in Fall 2010.

Well, NANPA was reflecting 272 on the "Planned NPAs Not Yet in Service"
webpage since as early as Wednesday 21-July-2010, and now (today, Friday
30-July-2010) it is being announced by the PA-PUC and news/press/media
sources as well.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

I'm looking for a soft copy of the 1998 MN PUC Order for the split of
NPA 612 (creating 651) or the 2000 order that split 612 three ways
creating NPAs 763 and 952. Anyone know where I can find a soft copy?
I've searched the MN PUC web site and googled it but can't find it.

Thanks for any help.

In Spring 2007, the KY-PSC approved a split for Area Code 270 in western
Kentucky, where "far western" Kentucky would have split to the new 364
Area Code, while 270 would be retained by the eastern part of the
existing 270.

270 itself was a split from 502 for all of western Kentucky, back in
1999. 502 was retained by the Louisville KY extended area.

As for the 270/364 split, it has been postponed several times. The most
recent dates for permissive dialing was to have taken effect in late
2011 (although the KY-PSC "official" permissive date was for
01-January-2012... the telco industry wanted to have permissive begin
earlier, before the Christmas/etc. Holidays of 2011/2012, to have the
telco network already prepared for permissive dialing), and there was
NO currently announced date for mandatory dialing.

But as of the April 2010 NeuStar-NANPA (semi-annual) "NRUF" projections
of Area Code exhaust (US and Canada), 270 would likely exhaust sometime
in 2014. And on Friday 13-August-2010, the KY-PSC yet again postponed
the pending 270/364 Area Code split -- now even the permissive dialing
date is still to be determined later on.

NeuStar-NANPA Planning Letter 408, dated today Thursday 19-August-2010
addresses this:
http://www.nanpa.com/pdf/PL_408.pdf

The KY-PSC document from last Friday (13-August-2010) regarding this:
http://www.psc.ky.gov/pscscf/2006%20cases/2006-00357/20100813_PSC_ORDER.PDF

This is presently the ONLY area code split "pending".

Hopefully this recent (yet again) postponement will eventually be
turned into an OVERLAY as has happened in other states, especially in
California (as well as Utah 801/385 and West Virginia 304/681).

Even the previously postponed splits in California --
the 619/935 split for the areas east of San Diego CA Metro (the second
half of what was to be a STAGGERED 3-way split of 619 for 1999-2001),
and the staggered 3-way split of 707 along the northern California
coast which was scheduled for 2000-02, both having been postponed, could
likely be OVERLAYS whenever relief is needed. 707 has never been split
at all, it dates back to 1959, the only pre-1995 area code in California
which so far has never been split or overlaid -- even some of the
post-1995 area codes in California have had additional split or overlay
relief since.

When planned for in 1999, the 818/747 relief in California was to have
been a split at a TBD date, but in 2007/08 planning for implementation,
it was decided that it was to be an overlay which took effect in 2009.
And the previously planned for 760/442 split was changed to an overlay.
760 (which covers the old, pre-1982 714) is the largest area code
geographically in California, even though large areas are unpopulated or
sparsely populated, but when the CA-PUC changed relief from a split to
an overlay in 2008 (taking effect in 2009), it was determined that there
would probably never be another split in California -- all future NPA
relief would be overlay, since the largest geographic code was now
overlaid.

There always "could" be further splits approved by one state or another.
But right now, all NPA relief planning which is close to being approved
by the specific state, is being planned for by the telco industry as an
overlay, and is likely to be approved by the state regulatory agency as
an overlay:

603 / ?? 946 ?? NH
812 / ?? 930 ?? IN
814 / ?? 582 ?? PA
717 / ?? 223 ?? PA

876 Jamaica in the NANP-Caribbean might need relief in another several
years, and it is likely that this might be an overlay as well.

All pending relief in Canada is for overlays -- there have been several
overlays in Canada, in 2001, 2006, 2008, 2010, and future. But the last
split in Canada was the Alberta 403/780 split in early 1999.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina

The new 579 area code "officially" overlaid the 450 area code in
southwestern Quebec (outside of the immediate Montreal QC 514/438
Metro Area) on Saturday 21-August-2010. At the time, the _ONLY_
579-NXX c.o.codes that were assigned and "worked" were the four
579-N10 codes for testing purposes (579-610 for Bell Canada ILEC,
579-710 for Telus-Quebec CLEC, 579-810 for Allstream-CLEC, and
579-510 for Rogers-CallNet CLEC).

At some point in the past few days, SAIC-CNA (Canadian Numbering
Administration) has assigned the first 579-NXX "POTS" c.o.codes,
thirteen of them, to (OCN 2243) the CLEC-side of Telus-Quebec.
Telus-Quebec, formerly GTE's "QuebecTel" is also the ILEC for about
two or three large discontiguous segments of eastern Quebec in the
418/581 area codes (although Bell Canada is also the ILEC for other
segments of that 418/581 region, and there are some small independent
telcos here/there as well in 418/581).

I don't know the exact date "when" SAIC-CNA assigned these 579-NXX
codes, but it was probably in the past two days (since Labor Day,
and Canada does have Labor Day on the same date that the US does),
nor do I know when Telus-Quebec intends on putting these c.o.codes
into effect, but it could be within another two months, certainly
before the end of 2010.

But here are the assignments as they are indicated at the 579-NXX
webpage for the CNA: http://www.cnac.ca/data/ac579.htm

579-230 Boucherville QC
579-231 Chomedey QC
579-232 Granby QC
579-233 Le Gardeur QC
579-234 Longueuil QC
579-235 Mascouche QC
579-236 Pont-Viau QC
579-237 Ste-Rose QC
579-238 Ste-Therese QC
579-239 St-Hyacinthe QC
579-240 St-Jerome QC
579-241 St-Lambert QC
579-242 St-Vincent-de-Paul QC

Also, the 450-NXX CNA webpage: http://www.cnac.ca/data/ac450.htm
shows that there are still several 450-NXX c.o.codes available for
assignment, the 450 "base" area code.

Some of these codes available for assignment are, however, reserved for
assignment only to "new entrant" wireless/CLEC/etc. providers, or at
least a "new entrant" wireless/CLEC/etc. provider to a specific exchange
area (ratecenter).

Here in the US, there are still several recently implemented overlay
area codes where there are still no active NXX c.o.codes in the overlay
(other than the test-number c.o.codes which might still "work"), but
there is also one "officially effective" overlay which has been in place
for over nine years now that still has no (POTS) c.o.codes...

That is the 878 overlay to southwestern Pennsylvania, overlaying both
412 for the immediate Pittsburgh PA Metro Area _AND_ the 724 outer area
of southwestern PA. Ten-digit intra-home-NPA local dialing has been
mandatory throughout the 412 and 724 area codes since July 2001, and the
"official" effective date of the 878 overlay was in August 2001, but
there are still not yet any "POTS" 878-NXX c.o.codes.

HOWEVER, the 724 NPA only has about nine remaining 724-NXX codes still
available for assignment. It doesn't seem that there will be any 878-NXX
codes activated (nor even assigned) by the end of 2010, but I do think
that by Spring or Summer 2011, there will finally be some 878-NXX codes
when the 724 NPA does eventually "run out". And at that time, new
878-NXX c.o.codes will likely be assignable also to the 412 "core"
region as well as the 724 "outer" region, even though there are still
quite a number of 412-NXX codes available.

This is how the assignment process was last year (Fall 2009) when 872
finally took effect with actual 872-NXX codes in the City of Chicago IL.
After several splits in the 1990s-era, 312 has shrunk down to just the
downtown "Loop" area, while 773 has split for the neighberhoods, but
only within the city limits. (Suburbs/etc. outside of the city limits
have their own area codes which split off from other area codes in the
1990s-era). 773 ran out of 773-NXX codes in Fall 2009, while 312 still
has several 312-NXX codes available for assignment. Back in the late
1990s, (Lockheed-Martin at the time) NANPA assigned 872 for "eventual"
overlay to BOTH 312 AND 773, whenever either 312 or 773 "ran out", but
the overlay applied simultaneously to both "base" area codes at the
point whenever either "base" area code "ran out".

At the present time (September 2009), there aren't all that many 872-NXX
c.o.codes assigned/active in the City of Chicago (IL), but only one of
them is actually assigned to "Zone-01" which is also the 312 "base" NPA
region for the downtown (Loop) region. The other (few) 872-NXX c.o.codes
are assigned to other "Zones" which are the 737 "base" NPA region for
the neighberhoods within the city limits.

The Atlanta GA metro area had another overlay assigned for "official"
implementation in September 2001 (nine years ago), the 470 area code.
However, there were still several 404-NXX codes for the Atlanta "core"
ratecenter, and also several 678-NXX codes for ALL of the 404/770/678
metro area. It was only early this year (2010) when 678 ran out of
c.o.codes available, and thus 470-NXX c.o.codes finally were assigned to
both the "770" region as well as the "404" region. However, at this time
(September 2010), there are only TWO "POTS" 470-NXX codes assigned,
470-200 to a CLEC for the Conyers GA ratecenter, and 470-201 to a
wireless provider for the Gainesville GA ratecenter. There are still not
yet any "POTS" 470-NXX codes assigned to the Atlanta "Central" 404-base
ratecenter.

The 760 NPA in California was "officially" overlaid with 442 last Fall
(2009). There are about a dozen remaining 760-NXX codes available at
this time (Fall 2010), but not yet any (POTS) 442-NXX codes.

And this year, there were two other overlays which are already now
"officially" effective, but still no "POTS" c.o.codes assigned in the
new overlay area code --

there are not yet any "POTS" 938-NXX c.o.codes in the 256 "base" area
code in northern/northeastern Alabama, nor are there yet any "POTS"
534-NXX c.o.codes in the 715 "base" area code in northern Wisconsin.

Next year (April 2011), the 402 area code in Nebraska will "officially"
be overlaid with the new 531 area code, but recently the Nebraska PSC
issued an order that _NO_ 531-NXX (POTS) c.o.codes can be assigned by
NeuStar-NANPA to requesting telecom service providers, until the supply
of available 402-NXX c.o.codes remaining for assignment has dropped to
ten or fewer. This is documented in the recent NANPA Planning Letter
#410.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA formerly of New Orleans LA pre-Katrina

On Wednesday 08-September-2010, I wrote:

> The new 579 area code "officially" overlaid the 450 area code in
> southwestern Quebec (outside of the immediate Montreal QC 514/438
> Metro Area) on Saturday 21-August-2010. At the time, the _ONLY_
> 579-NXX c.o.codes that were assigned and "worked" were the four
> 579-N10 codes for testing purposes (579-610 for Bell Canada ILEC,
> 579-710 for Telus-Quebec CLEC, 579-810 for Allstream-CLEC, and
> 579-510 for Rogers-CallNet CLEC).
>
> At some point in the past few days, SAIC-CNA (Canadian Numbering
> Administration) has assigned the first 579-NXX "POTS" c.o.codes,
> thirteen of them, to (OCN 2243) the CLEC-side of Telus-Quebec.

[ ... ]

> I don't know the exact date "when" SAIC-CNA assigned these 579-NXX
> codes, but it was probably in the past two days (since Labor Day,
> and Canada does have Labor Day on the same date that the US does),
> nor do I know when Telus-Quebec intends on putting these c.o.codes
> into effect, but it could be within another two months, certainly
> before the end of 2010.
>
> But here are the assignments as they are indicated at the 579-NXX
> webpage for the CNA: http://www.cnac.ca/data/ac579.htm
>
> 579-230 Boucherville QC
> 579-231 Chomedey QC
> 579-232 Granby QC
> 579-233 Le Gardeur QC
> 579-234 Longueuil QC
> 579-235 Mascouche QC
> 579-236 Pont-Viau QC
> 579-237 Ste-Rose QC
> 579-238 Ste-Therese QC
> 579-239 St-Hyacinthe QC
> 579-240 St-Jerome QC
> 579-241 St-Lambert QC
> 579-242 St-Vincent-de-Paul QC
>
> Also, the 450-NXX CNA webpage: http://www.cnac.ca/data/ac450.htm
> shows that there are still several 450-NXX c.o.codes available for
> assignment, the 450 "base" area code.
>
> Some of these codes available for assignment are, however, reserved
> for assignment only to "new entrant" wireless/CLEC/etc. providers,
> or at least a "new entrant" wireless/CLEC/etc. provider to a
> specific exchange area (ratecenter).

I spoke with one of my Canadian telco contacts, and they told me that
these thirteen "first" 579-NXX POTS c.o.code assignments (to Telus
Quebec CLEC) were made on Friday 03-September-2010, and that the
effective date for implementation/activation in the telco network is
for Friday 29-October-2010, a little over two months following the
"official" effective date for the 579 area code "itself" on Saturday
21-August-2010.

> Here in the US, there are still several recently implemented overlay
> area codes where there are still no active NXX c.o.codes in the
> overlay (other than the test-number c.o.codes which might still
> "work"), but there is also one "officially effective" overlay which
> has been in place for over nine years now that still has no (POTS)
> c.o.codes...
>
> That is the 878 overlay to southwestern Pennsylvania, overlaying
> both 412 for the immediate Pittsburgh PA Metro Area _AND_ the 724
> outer area of southwestern PA. Ten-digit intra-home-NPA local
> dialing has been mandatory throughout the 412 and 724 area codes
> since July 2001, and the "official" effective date of the 878
> overlay was in August 2001, but there are still not yet any "POTS"
> 878-NXX c.o.codes.
>
> HOWEVER, the 724 NPA only has about nine remaining 724-NXX codes
> still available for assignment. It doesn't seem that there will be
> any 878-NXX codes activated (nor even assigned) by the end of 2010,
> but I do think that by Spring or Summer 2011, there will finally be
> some 878-NXX codes when the 724 NPA does eventually "run out". And
> at that time, new 878-NXX c.o.codes will likely be assignable also
> to the 412 "core" region as well as the 724 "outer" region, even
> though there are still quite a number of 412-NXX codes available.

[ ... ]

> The Atlanta GA metro area had another overlay assigned for
> "official" implementation in September 2001 (nine years ago), the
> 470 area code. However, there were still several 404-NXX codes for
> the Atlanta "core" ratecenter, and also several 678-NXX codes for
> ALL of the 404/770/678 metro area. It was only early this year
> (2010) when 678 ran out of c.o.codes available, and thus 470-NXX
> c.o.codes finally were assigned to both the "770" region as well as
> the "404" region. However, at this time (September 2010), there are
> only TWO "POTS" 470-NXX codes assigned, 470-200 to a CLEC for the
> Conyers GA ratecenter, and 470-201 to a wireless provider for the
> Gainesville GA ratecenter. There are still not yet any "POTS"
> 470-NXX codes assigned to the Atlanta "Central" 404-base ratecenter.
>
> The 760 NPA in California was "officially" overlaid with 442 last
> Fall (2009). There are about a dozen remaining 760-NXX codes
> available at this time (Fall 2010), but not yet any (POTS) 442-NXX
> codes.
>
> And this year, there were two other overlays which are already now
> "officially" effective, but still no "POTS" c.o.codes assigned in
> the new overlay area code --
>
> there are not yet any "POTS" 938-NXX c.o.codes in the 256 "base"
> area code in northern/northeastern Alabama, nor are there yet
> any "POTS" 534-NXX c.o.codes in the 715 "base" area code in northern
> Wisconsin.

Actually, there is also a THIRD overlay for this year (2010), where
there are still _NO_ "POTS" c.o.codes assigned in the overlay area
code, that being the Oregon (except northwest) 541/458 area code
overlay. I had overlooked it at the time when I was preparing the
original post on Wednesday evening! Ten-digit intra-541 local dialing
is now mandatory, and the 458 NPA is "officially" in effect overlaying
541 in Oregon since February 2010 but it could be quite some time
before there are yet any actual "POTS" 458-NXX c.o.codes assigned and
activated in effect within the 541/458 area code overlay region.

> Next year (April 2011), the 402 area code in Nebraska will
> "officially" be overlaid with the new 531 area code, but recently
> the Nebraska PSC issued an order that _NO_ 531-NXX (POTS) c.o.codes
> can be assigned by NeuStar-NANPA to requesting telecom service
> providers, until the supply of available 402-NXX c.o.codes remaining
> for assignment has dropped to ten or fewer. This is documented in
> the recent NANPA Planning Letter #410.

I don't think that Alabama or Wisconsin regulatory (nor California
regulatory) has mandated that the "base" area codes be used up
(virtually) completely before any c.o.codes could be assigned out of
the new overlay area code, though... but in the 878 overlay to 412 and
724 in Pittsburgh PA Metro and the rest of southwestern PA, the PA-PUC
did indeed order that (at least one of the) "base" area codes be used
up almost completely before the 878 overlay area code could have any
actual 878-NXX c.o.codes assigned/activated. However, mandatory
ten-digit local dialing within 412 and within 724 was made effective
and has been so since Summer 2001, nine years ago.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA formerly of New Orleans LA pre-Katrina

I recently posted about how the 579 NPA in southwestern Quebec
(outside of Montreal PQ Metro) overlaying the 450 NPA (as of Saturday
21-August-2010, "officially"), just recently had its first 579-NXX
"POTS" c.o.codes (thirteen of them total) assigned by SAIC-CNA on
Friday 03-September-2010, effective activation date for Saturday
29-October-2010.

In those posts, I mentioned about how there are some additional
overlay NPAs (in the US) which are "officially" in service, yet still
don't have any "POTS" NXX c.o.codes assigned/active within those
overlay NPA codes.

This includes:

- the 878 NPA overlaying BOTH 412 (Pittsburgh PA Metro) AND 724 (the
rest of southwestern PA), overlay has been "official" (along with
mandatory ten-digit local dialing) since Summer 2001 (nine years ago).
there are (at this time) only NINE 724-NXX c.o.codes which are
available for assignment (there are still several 412-NXX codes which
can still be assigned in the Pittsburgh PA Metro area though), so it
is likely that 878-NXX codes will begin to be assigned/activated soon,
probably in early 2011 (I don't think that there will be any for the
remainder of 2010 though, but you never know). NOTE that back in
2000/01, the PA-PUC ordered that 724 OR 412 be (almost) "all used up"
before NeuStar-NANPA could assign any 878-NXX c.o.codes.

- the 442 NPA overlaying 760 in southeastern and eastern California,
this overlay was "official" (with mandatory [1+] ten-digit local
dialing) since last Fall (2009). There are twelve 760-NXX codes still
available for assignment at this time. I don't remember any
regulatory action from the CA-PUC in 2008/09 regarding how 760 had to
be (almost) "all used up" before 442 could be opened up for assignment
of "real/POTS" 442-NXX codes though. Checking NANPA's (US) NPA-NXX
c.o.codes website, I see that there _ARE_ some recent assignments of
442-NXX "POTS" codes! More on that further down.

- also this year, the 541/458 overlay (Oregon except northwestern OR/
Portland OR metro), the 256/938 overlay (northern/northeastern Alabama),
and the 715/534 overlay (northern Wisconsin), all being "official" at
one point or another during 2010, along with mandatory ten-digit local
dialing, still don't yet have any "POTS" c.o.codes assigned. I don't
think that there is any state regulatory action in any of these
requiring the old/base NPA code to be "almost all used up" though. But
at this time, there are still no NXX c.o.code assignments in any of
the new overlay NPA codes. AND, there are still numerous NXX c.o.codes
in the old/base which are still available for assignment.

In the early part of next year (March/April 2011), there will be
(officially) four NPA overlays: 705/249 in northeastern/eastern
Ontario (Canada), 402/531 in eastern Nebraska, the 929 overlay to
718/347/pt.917 for New York City (NOT Manhattan), and the 918/539
overlay in northeastern Oklahoma. All four "base/old" NPAs, 705 (ON),
402 (NE), 918 (OK), 347 (NY), will still have numerous NXX c.o.codes
available for assignment, even after mandatory ten-digit dialing
takes place (in New York City, [1+]ten-digit mandatory local dialing
has been in place since Feb/March 2003) and the overlays have become
"official". But again, I don't know of any state regulatory action
requiring that the "old/base" NPA code be (almost) "all used up"
before NANPA can begin assigning (real/POTS) c.o.codes out of the new
overlay NPA codes, with one exception. Recently the Nebraska-PSC
ordered that the 402 NPA code must be "run down" to only ten or fewer
402-NXX c.o.codes still unassigned before NANPA can begin assigning
new 531-NXX "POTS" c.o.codes. Also, similar to Illinois' pending
overlays (708/464 in the Chicago southern/southwest suburbs, 217/447
for south-central Illinois, 618/730 for southern Illinois), the
570/272  NPA overlay in northeastern Pennsylvania is also "pending",
with no "officially announced dates" for the overlay, mandatory
ten-digit local dialing, nor assignment/activation of POTS 272-NXX
c.o.codes, since the PA-PUC ordered that NANPA submit monthly reports
of how the 570 NPA remains as far as 570-NXX code assignments.

Anyhow, back to 442 in California:

I have checked the 442-NXX c.o.code page at NANPA's website. There ARE
NOW THREE 442-NXX c.o.codes assigned as of Monday 16-August-2010.
These are all scheduled to take effect within the network on Thursday
21-October-2010, in the Oceanside:Oceanside-DA ratecenter (abbreviated
as OCSD:OCSD), all to (OCN 339F) "Telecentris". I don't know if this
is a CLEC or a VoIP provider, or what, but that is who the "default"
assignee is. The three codes assigned are 442-333, 442-777, 442-888.
The CLLI I found for these 442-NXX codes is SNDGCA02XQZ, which is
strictly a "point-of-interconnection" CLLI (NOT an actual "switch" as
such), in nearby San Diego CA. It appears that the actual underlying
switch is Telecentris' Los Angeles CA based (and in a different LATA)
LSANCAJWCA2 known as a "call agent" technology (whatever that is), the
actual manufacturer/equipment/model itself being a CISCO BTS-10200.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina