I am currently using this website to get the following information:

   Area Code/City/LATA/V & H #s/ ILEC info/NPA prefixes.... Is there an easy was
to get all of this info in an Excel spreadsheet?   I am needing area codes 201
to 999.  Any help is appreciated.
   Thanks!


---------------------------------
No need to miss a message. Get email on-the-go
with Yahoo! Mail for Mobile. Get started.

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

In Yahoo: local-calling-guide, Lisa Nunez (l1phonecall_8) wrote:

> I am currently using this website to get the following information:
>
> Area Code/City/LATA/V&H/ILEC/NPA-NXXes....
> Is there an easy was to get all of this info in an Excel
> spreadsheet? I am needing area codes 201 to 999.Any help
> is appreciated. Thanks!

Well, there is no area code 999, and for that matter, there
are no area codes 990, 991, 992, etc. The highest purely
numeric area code within the NANP is 989 in Michigan.

Neustar-NANPA has lists of all assigned US-based NPA-NXX
codes in various formats, including web, text, and excel.
US jurisdictions inlcude all 48 conterminous US states as
well as the District of Columbia, and also the states of
Alaska, Hawaii, and the other US possessions of Puerto Rico,
the US Virgin Islands, Guam, the Mariana Islands of Saipan/
Tinian/Rota, and American Samoa. ALL of these US-jurisdictions
are now in the NANP.

There are various sub-menus you can click at NANPA's website
from http://www.nanpa.com/reports/reports_cocodes.html
and then choose the types and formats of info you might want
from these submenus, regarding US-based "POTS" central office
codes.

If you are also interested in c.o.codes in SPECIAL area codes
such as 456, 500, 900, see some of the following pages/sections
at Neustar-NANPA's website:

http://www.nanpa.com/number_resource_info/500_codes.html
http://www.nanpa.com/number_resource_info/900_codes.html
http://www.nanpa.com/number_resource_info/456_codes.html

The only "known" c.o.code assigned within the US Government's
Special Area Code 710 is 710-627. Virtually all other possible
710-NXX combinations have also been officially "reserved" to
the US Federal Government, but there is no publicly "known"
assignments for these 710-NXX codes other than 710-627 which
is assigned to the DHS/FEMA/NCS/GETS/etc.

Detailed Canadian NPA-NXX information can be obtained from SAIC-CNA's
website at: http://www.cnac.ca/co_codes/co_code_status_map.htm

Click on the Canadian area code you want info on, and you'll get
a "web" html chart of NPA-NXXes in that Canadian NPA code.

The 600 Special Area Code for use in Canada -- you can find the
current 600-NXX code assignment list in html chart form at
SAIC-Candaian Numberign Administration's website, at:
http://www.cnac.ca/other_codes/600/600-nxx_codes.htm

If you want info on NXX c.o.codes within the toll-free area codes
800/888/877/866, for the most part, with a very few exceptions,
all possible 8YY-NXX codes are available for assginment for line-
numbers, without any specific regard to carrier or geography, due
to full/wide portability.

As for the c.o.codes in the NANP-Caribbean NPAs, those which are
NOT "US", i.e., NANP-Caribbean locations other than the US'
Puerto Rico and US Virgin Islands, I don't know of any single
"official" site that posts this info, although individual island
telecom numbering administrations do have charts at their websites,
or downloadable doc/pdf/etc. files from their websites. Unofficial
lists of non-US NANP-Caribbean NPA-NXX c.o.codes can be found from
the Local Calling Guide website you're currently using as well as
other "public" sources on the web, such as telcodata.us and such.
But remember that the "unofficial" sites might not be nearly as
updated/accurate as any official lists that might be available.

mjc

Sounds as if it is time to go visiting late at night with a big crowbar!

There was a nice C&P telephone heavy metal sign on  the Williamsport MD
CO for the longest time.
Sad part is that right across the street was a waffle house where the
local cops loved to hang out and catch speeders, so I never got the
chance. Now it is a flat VeriZon sign


John Novack

Mark J. Cuccia wrote:
> Today when I was in Baton Rouge, I noticed that at several BellSouth
> central office locations, while the logo/lettering on the buildings
> still have the 1970s-era "Bell" logo and the post-divestiture font/
> lettering for "BELLSOUTH", I did notice that there were either repair
> vans parked on the property, or vans pulling-in or pulling-out of
> the property, which have "the new at&t" globe logo, sort of like a
> "half-globe" painted on the sides of the vans towards the back, the
> "half-globe" almost looking like a "rising sun".
>
> As for the MAIN Baton Rouge building downtown, the last time I saw it
> "up close" was in August 2006. It houses an AT&T-LL 4ESS toll switch
> that dates back to pre-divestiture Bell System days, as well as the
> BellSouth "Main" switch for the business/government district downtown.
> There is an "old" building as well as a newer modern addition. The
> BellSouth logo/signage was on the left side of the front entrance to
> the new/modern addition, and the 1983-2005 "divestiture" AT&T
> (uppercase) logo was on the right side of the front entrance to the
> new/modern addition. Also, at the very-top, roofline, of the multi-
> story modern/new addition was the 1983-2005 AT&T uppercase logo.
> Next time I'm in Baton Rouge, I'm going to try to see if there have
> been any changes to either or both the BellSouth and 1983-2005 AT&T
> uppercase logos.
>
> And I'm always "on the lookout" elsewhere in south Louisiana where
> there might be BellSouth buildings or vehicles to see if they've
> begun adding or changing to "the new at&t" on logos/brandings/signage.
>
> Has anyone else in BellSouth territory noticed if BellSouth has begun
> rebranding/signing their buildings or trucks/vans/cars, etc. with
> "the new (lowercase) at&t" yet? I know that the envelope for the paper
> billings are now "co-branded/signed" with both logos, the BellSouth
> name/logo on the front of the envelope in the return address part, and
> "Welcome to the new at&t" on the back flap of the envelope.
>
> I haven't really paid attention to cingular-wireless sales offices
> that much lately to see if they've begun adding "the new at&t" logos
> or window-size fliers/banners, etc. to their cingular banners.
>
> Mark J. Cuccia
> markjcuccia at yahoo dot com
> Lafayette LA, formerly of New Orleans LA pre-Katrina
> both places are also at&t/BellSouth/South Central Bell/Southern Bell/
> Cumberland Tel & Tel/etc.
>
>
>
> Group web page: http://groups.yahoo.com/group/singingwires
> The TCI web site is at http://www.telephonecollectors.org
> TCI Picture Place: http://www.telephonecollectors.org/pictures/
>  (Picture posting password: tciphotos )
>   No password is required to see the pictures.
> Yahoo! Groups Links
>
>
>
>
>


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

Today when I was in Baton Rouge, I noticed that at several BellSouth
central office locations, while the logo/lettering on the buildings
still have the 1970s-era "Bell" logo and the post-divestiture font/
lettering for "BELLSOUTH", I did notice that there were either repair
vans parked on the property, or vans pulling-in or pulling-out of
the property, which have "the new at&t" globe logo, sort of like a
"half-globe" painted on the sides of the vans towards the back, the
"half-globe" almost looking like a "rising sun".

As for the MAIN Baton Rouge building downtown, the last time I saw it
"up close" was in August 2006. It houses an AT&T-LL 4ESS toll switch
that dates back to pre-divestiture Bell System days, as well as the
BellSouth "Main" switch for the business/government district downtown.
There is an "old" building as well as a newer modern addition. The
BellSouth logo/signage was on the left side of the front entrance to
the new/modern addition, and the 1983-2005 "divestiture" AT&T
(uppercase) logo was on the right side of the front entrance to the
new/modern addition. Also, at the very-top, roofline, of the multi-
story modern/new addition was the 1983-2005 AT&T uppercase logo.
Next time I'm in Baton Rouge, I'm going to try to see if there have
been any changes to either or both the BellSouth and 1983-2005 AT&T
uppercase logos.

And I'm always "on the lookout" elsewhere in south Louisiana where
there might be BellSouth buildings or vehicles to see if they've
begun adding or changing to "the new at&t" on logos/brandings/signage.

Has anyone else in BellSouth territory noticed if BellSouth has begun
rebranding/signing their buildings or trucks/vans/cars, etc. with
"the new (lowercase) at&t" yet? I know that the envelope for the paper
billings are now "co-branded/signed" with both logos, the BellSouth
name/logo on the front of the envelope in the return address part, and
"Welcome to the new at&t" on the back flap of the envelope.

I haven't really paid attention to cingular-wireless sales offices
that much lately to see if they've begun adding "the new at&t" logos
or window-size fliers/banners, etc. to their cingular banners.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina
both places are also at&t/BellSouth/South Central Bell/Southern Bell/
Cumberland Tel & Tel/etc.

Well, it finally happened. It was announced back in early January
that effective 01-March-2007, that at&t/SBC would discontinue the
1-800-522-2020 Calling Card Dial-up Access Number. I forgot to
make test-dials on Wednesday 28-Feb-2007 or Thursday 01-March-2007
but I did make a call early on Saturday 03-March-2007. It now goes
to an English-Only announcement about the fact that the at&t
800-522-2020 calling cards were discontinued on the first of March.

This does NOT mean that legacy AT&T-LL 1-800-CALL-ATT or other
AT&T-LL calling card/operator access methods have been discontinued.
In fact, in some cases, AT&T-LL OSPS has taken over other ILEC
calling card services, those ILECs being once known as SBC.

The 1-800-522-2020 access was branded as Pacific*Bell for both
Pacific*Bell of California and Nevada*Bell, both Pacific*Telesis
RBOC entities, back in the 1990s. I don't know the exact history
of this or other SBC-ILEC 800 card access numbers prior to the
later 1990s, but I do know that by the late 1990s, after SBC tookover
Pacific*Telesis, both legacy Pac*Bell/NV*Bell 1-800-522-2020 and
legacy SWBell 1-800-600-BELL used Sprint-LD's DMS-250-based network
for the actual handling of their respective calling card dial-up
numbers. Brandings for initial card calls on the platform were from
SBC for Pac*Bell or SWBell, but if you made any "errors" in keying
destination numbers, etc., you could get vacant code announcements
that were most certainly Sprint-LD's rather than SBC. By the later
1990s, both 1-800-522-2020 and 1-800-600-BELL accepted my BellSouth
ILEC calling cards, both line-number and RAO-based.

Also in the later 1990s, SBC bought out Ameritech. There was an
800 calling card dial-up that was branded Ameritech, 1-800-AMERITECH.
The final '24' from the last two letters 'C-H' were really unnecessary
when trying to access the calling card platform. I forget who actually
provided the BACKBONE network, whether it was Frontier-LD, Qwest-LD,
"first generation" Wil-Tel before being completely consolidated into
Worldcom/MCI, but the actual "backbone" network providing Ameritech's
card-access was NOT Sprint-LD. I don't remember offhand, but I don't
think that 1-800-AMERITECH accepted my BellSouth ILEC cards.

Sometime around 2002 or 2003, SBC made announcements that both
the legacy Southwestern Bell 1-800-600-BELL and Ameritech's
1-800-AMERITECH would be discontinued. I think that they put
announcements on both 800 numbers that customers should migrate
over to using 1-800-522-2020. I don't know who the toll-free resporgs
might be for 1-800-263-7483, but I think that Sprint or Embarq might
still be the resporg for 1-800-600-2355. In some parts of the US,
1-800-600-2355 is answered by some kind of card or customer service
platform of either Sprint or Embarq. However, all I get on this 800
number is a re-order.

Also at the time that SBC migrated things into legacy Pac*Bell's
1-800-522-2020, circa 2002/03, the backbone was changed from Sprint-LD
over to a "different other common carrier". I was told that it was
the "second generation incarnation" of Wil-Tel, an entity created by
the Williams family a few years after Worldcom/MCI had completely
consolidated the legacy earlier 0555 WilTel into Worldcom/MCI. And
then even "Wil-Tel Part Two" has since been sold to Level Three, yet
another CLEC and emerging "other LD provider".

All along, 1-800-522-2020 has accepted "most" US/Canada ILEC-issued
cards including BellSouth.

Additionally, SNET in Connecticut has provided a calling card access
dial-up platform on 1-800-555-5321. By the late 1990s or early 2000s,
both 0333 Sprint-LD and 0288 AT&T-LL seem to have been the "backbone"
providers. My BellSouth line-number and RAO-based cards have been
accepted on this platform. SBC bought out SNET circa 1997/98 shortly
after having taken over Pacific*Telesis' Pac*Bell/NV*Bell. The
"branding" on this 1-800-555-5321 platform had been "S-N-E-T Long
Distance" until circa 2002/03, when it was changed to "S-B-C Long
Distance East". And then it was changed to "a-t-and-t Long Distance
Easst" about a year ago in early 2006. But it was still handled out
of SNET's legacy card platform and both Sprint-LD and AT&T-LL as
the "backbone", in Connecticut. That is, until sometime in Dec.2006,
when SBC/at&t migrated 1-800-555-5321 over to AT&T-LL's 212-0T OSPS
in Manhattan NY. The current 1-800-555-5321 operation at AT&T-LL's
212-0T OSPS does *NOT* accept AT&T-LL-issued calling cards -- it
only accepts most US/Canada ILEC-issued cards, even though it does
"run-off-of" an AT&T-LL OSPS! But it "sounds" a lot like legacy
AT&T-LL OSPS Calling Card operations.

In early January 2007, legacy Pac*Bell 1-800-522-2020 began to have
a LONG English/Spanish pre-amble before giving you the basic card
menu, that "at&t", which I would assume to mean the legacy SBC-ILEC,
was no longer going to issue 800-522-2020 type calling cards by
February, and that on the first of March 2007, the existing cards
would no longer work. And now as of March 2007, the 800-522-2020
platform has stopped working altogather, with a message that the
service is now discontinued. I don't know exactly who is providing
that announcement that it is discontinued, if it is at&t/SBC, or
if it is Level-3. I don't know who the current toll-free "resporg"
is for 800-522-2020. And I don't know what the ultimate future is
going to be for what 800-522-2020 will route to, in the way of any
announcement or platform.

I also wonder if in legacy Pac*Bell, SWBell, Ameritech areas, if
you can call up the *ILEC* business office and order a line-number
ILEC calling card? What about the cards that have been out there
for years? I assume that SBC/at&t LEC still has a 0- and 0+ TOPS
for local/intra-LATA. And if legacy SNET 1-800-555-5321, which is
now based on the AT&T-LL 212-0T OSPS, still works, accepting legacy
SNET and legacy BellSouth cards, and I assume MOST US/Canada ILEC
issued cards, then most likely an Ameritech/SWBell/Pac*Telesis-issued
line-number or RAO-based LEC card will also still work on legacy
SNET's 1-800-555-5321. But I don't know if at&t/SBC has issued any
announcements somehow, that customers of Pac*Telesis, Ameritech,
SWBell, can now use legacy SNET's 1-800-555-5321.

At present, BellSouth's legacy 1-800-BELLSOUTH, although the final
'84' from the last two letters 'T-H' are really unnecessary when
trying to access the calling card platform, still works, and still
brands "BellSouth" and ONLY as BellSouth. I don't know who the
"backbone" provider is for BellSouth-Long-Distance in this platform.
Maybe it is now really running off 0288 AT&T-LL??? In the later 1990s,
it ran off of a rather "shady" entity known as "Teltrust", a company
which owned COCOT private payphones and provided private DIS-trustful
"operators" for private payphone and "guest" type PBXes, such as
Hotels/Motels, Hospitals, and other lodging facilities, maybe also
even for prison phones. By 2000, 1-800-BELLSOUTH was using operators
who were really Qwest. The preamble on 1-800-BELLSOUTH actually
changed the branding from "carrier services provided by Teltrust"
over to "carrier services provided by Qwest". But at present, there
is no mention. MOST US/Canada ILEC-issued cards seem to be accepted
on 1-800-BELLSOUTH though.

One thing that I'm sad to see about the passing of 1-800-522-2020,
is that this was the only remaining platform that I had access to,
since it accepted my BellSouth cards, which also routed, possibly
by its backbone Level-3, to the "additional overlay" test-numbers
in Philadelphia Metro. The 445 overlay to 215-already-with-267-in-
overlay for the "city", and the 835 overlay to 610-already-with-
484-in-overlay for the suburbs, were both to take effect in early
2001. But prior to that date, PA-state-regulatory suspended the
further overlays as "unnecessary at the time". Of course, since
there are already overlays in effect, ten-digit local dialing has
been mandatory since those original overlays began in 1999.

However, the 445-355-TEST and 835-355-TEST numbers have still been
working by VZ/BA/Bell-of-Pa, if you can use a LD-provider which
still translates-and-routes correctly to both 445-355 and 835-355.
And it seems that Level-3 has still translated/routed to these
test-number NPA-NXX c.o.codes, but at present, I don't have access
to any them with the disappearance of 1-800-522-2020, nor any other
carrier which "might" route to 445-355 and 835-355. Neither AT&T-LL
0288/etc., nor 0222/etc. MCI, nor 0333/etc. Sprint-LD, nor even
Qwest-LD 0432, and so forth, seems to translate/route to 445-355
and 835-355. I don't have access to VZ-LD's service, and it's also
possible that VZ-LD doesn't even recognize 445-355 and 835-355 --
it's the ILEC VZ, legacy Bell Atlantic/Bell-of-Pennsylvania, which
still provides an test/validation announcement on 445-355-TEST
and 835-355-TEST, on the actual local switches in the southeast PA
area.

But after all these years, 1-800-522-2020 no longer works. However,
the ILEC side of SBC/at&t still runs the legacy SNET 1-800-555-5321,
but since Dec.2006 is running it off of the AT&T-LL 212-0T OSPS but
NOT accepting AT&T-LL issued cards, while it does accept MOST
US/Canada-ILEC-issued calling cards, including at&t/BellSouth.

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

There is a notice at at&t/BellSouth's "Carrier Notifications" website
dated 01-March-2007, regarding expanded EAS in the Mobile AL area,
effective for Monday-16-April-2007.

http://www.interconnection.bellsouth.com/alerts_and_notifications/carrier_notifi\
cations/assets/pdf/91087014.pdf

This notification makes specific mention that EAS will apply to calls
placed over *BELLSOUTH*. Even though in theory, this EAS is to apply
to CLECs in the affected ratecenters, you never know if some CLECs
might keep calls originated on their networks as toll. Usually,
BellSouth and the ILECs will apply the EAS for calls originated on the
ILEC and placed to a CLEC or wireless provider, as long as the
non-ILEC destination is also in an "EAS ratecenter". In some cases,
CLECs have their own EAS which is "better/improved" over what the ILEC
offers! Regarding calls originating on wireless providers, that's a
whole different story as well, since there might be minutes packages,
airtime, and such.

The Tanner-Williams MS ratecenter in NPA 228 is served out of an
at&t/BellSouth switch located in the Mobile AL ratecenter, and the
Tanner-Williams MS ratecenter is also associated with the Mobile AL
LATA #480. In all expanded EAS, Tanner-Williams MS 228-641 will be
treated "as if" it is also part of the Mobile AL ratecenter.

There is to be flat-rate EAS between Mobile AL/Tanner-Williams MS and
Bay Minette AL. Presently, there is only "measured rate" between
Bay Minette AL and Mobile AL/Tanner-Williams MS, although I would
expect that subscribers to optional Area Plus have had these calls as
"unlimited".

There is also to be EAS between Bay Minette AL and Fairhope AL.
Again, there is presently only "measured rate" between these two AL
ratecenters.

Fairhope AL and Mobile AL/Tanner-Williams MS already have "flat rate"
EAS w-r-t each other.

There is also to be EAS between McIntosh AL and Mobile AL/Tanner-
Williams MS. At present, McIntosh AL is local ONLY UNTO ITSELF!

And, there is to be EAS between Citronelle AL and Mt.Vernon AL.
Both of these ratecenters presently have EAS with Mobile AL/Tanner-
Williams MS, but nothing else. Now they will have EAS w-r-t each
other.

All of the above ratecenters are at&t/BellSouth/South Central Bell
for the ILEC.

Mobile AL/Tanner-Williams MS does have additional EAS with other
south/south-western AL ratecenters, including some CenturyTel
ratecenters in southwestern AL. The southwestern corner of Alabama
outside of Mobile Metro, was Contel until GTE took them over, then
temporarily VeriZon with 2000, but in 2002, VZ sold off all of their
legacy GTE and legacy GTE/Contel ratecenters in Alabama to CenturyTel.
The barrier island of Dauphin Island out in the Gulf of Mexico south
of Mobile, or what exists of Dauphin Island post-Katrina, post-Ivan,
and post-other recent hurricanes, is also part of that one-time
Contel, one-time VZ/GTE, now-CenturyTel service area.

East of Mobile AL and Mobile Bay, going southward, and then further
east towards the Florida stateline, there is some Gulf Telephone Co.
service area. Illinois-based Madison River Communications bought out
Gulf Tel. Co. a few years back -- they own a few other independent
telcos in the midwest and southeast. Recently, Louisiana/Arkansas-
based CenturyTel announced that they are buying out the Madison River
telco/holding company, which I assume includes Alabama's Gulf Telco,
NC's Mebane Telco, etc.

I don't think that Mobile Metro has any EAS with this area of southern
Alabama south and east of Mobile Bay near the Florida stateline.
However, BellSouth's optional Area Plus plan will allow unlimited or
"virtually unlimited" calling, since all of these ratecenters, both
Bell, Contel/GTE/VZ/CenturyTel, Gulf Telco/Madison River/CenturyTel,
etc. are all in the Mobile AL Metro LATA #480.

As for the expanded EAS, I haven't found anything yet at the Alabama
state regulatory agency's website. And as for media announcements,
I haven't yet done any "google" searches to see of local radio/TV/
newspaper websites have reported yet.

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

For the most part, when divestiture came about in 1984, in a BOC LATA,
intra-LATA toll origination from a small independent ratecenter/
exchange area was handled by the dominant BOC for that LATA,
especially when it comes to 0+ type of traffic. There could be
instances where 1+ intra-LATA sent-paid toll traffic between two
different ratecenters/exchange areas of the same small independent
ILEC would be carried by direct trunks between the two ratecenters
owned by that small non-Bell ILEC. But 0+ type of traffic would need
to route to a TOPS switch or similar type of operator-services switch,
and most smaller independent telcos don't really provide their own
operator services anymore, not even '0-' (dial '0') operators, but
ely on the BOC or larger "GTE" type of independent ILEC in that LATA.

A few years ago, I seem to remember reading that in Washington state,
either the BOC Qwest/US-West, or maybe it was GTE-VeriZon, was going
to "withdraw" from being the "intra-LATA toll carrier of last resort"
for originating traffic from independent ratecenters in that LATA.
This was several years ago, and right now, I cant' seem to find any
readily available documentation at the Washington Utilities and
Transportation Commission's website.

*IF* this is indeed the case, I wonder how 0- and intra-LATA 0+
services and traffic is provided from small independent ILEC
exchanges/ratecenters in those "BOC" LATAs?

When I was looking through the Alabama Public Service Commission's
website this weekend for any published details on the forthcoming
expansion of EAS within/around the Mobile AL Metro Area, I cam on
the following at the Telecommunications Division's "New Items" page,
http://www.psc.state.al.us/Telecom/NewItems/

"CHANGES IN THE PRIMARY CARRIER PLAN: Affected independent telephone
company local service customers will soon receive a notice advising
them to select a new long distance provider. Click on the link at
right for an explanation of what is going on and INFO that may help
you choose another long distance provider", dated 26-Jan-2007,
http://www.psc.state.al.us/telecom/newitems/Changes_in_Primary_Carrier_Plan-FAQ.\
pdf

The very beginning of this document states:

"This page provides information and resources so that Alabama
telephone subscribers may more fully understand the differences in
long distance service and be better informed before selecting one or
more carriers for their long distance calling.

"It is likely that you are here because your telephone company
notified you of the requirement to select another long distance
carrier."

The document then goes on to give basic information about divestiture
in 1984, LATAs, inter-LATA PIC-ing, intra-LATA PIC-ing, 101-XXXX+
carrier code dialing for both intra-LATA and intra-LATA although they
mis-print it as 10-10-XXXX which is one-too-many digits, etc.

Also, I don't know if the 26-Jan-2007 date for this document means
that this is a brand new document ever, or if there is some kind of
a change "somewhere" in this document, i.e., that it has existed for
some time, but there is a recent change as of Jan-2007 buried
somewhere in this document.

Of paritcular interest is question #4 in this "FAQ":

"Why Can’t I Keep BellSouth as My IntraLATA Long Distance Provider?

"Response: BellSouth had an arrangement with your independent local
telephone company to offer pre-subscribed intraLATA long distance
service to non-BellSouth local service customers. BellSouth has
chosen not to continue that arrangement. If you want the convenience
of presubscribed intraLATA long distance service, BellSouth is no
longer an available option for you. There are long distance plans
available from other long distance carriers and your local telephone
company may offer a long distance plan of its own. The choice is up
to you to either pre-subscribe to another intraLATA long distance
provider or not pre-subscribe at all. Should you choose to not
pre-subscribe to a long distance carrier by the deadline provided in
the notice sent to you from your local telephone company, you can do
so at any future date. However, after the deadline you will be unable
to direct dial an intraLATA long distance number from your phone and
will receive a recorded message advising you that you cannot do so
without pre-subscribing to a long distance provider."

I wonder if BellSouth's intra-LATA CIC/CAC of 101-5124+ as a
DIALAROUND code, will continue to work for 1+/0+/0- intra-LATA
services from that independent telco's c.o.switch/wirecenter/
ratecenter/exchange area, if 101-5124+ ever indeed really work!?

Similarly, if Qwest/US-West has also ideed "withdrawn" from such for
intra-LATA 1+ presubscribed services from independent telco areas
within those Qwest/US-West Washington State-based LATAs, I wonder
if US-West/Qwest-LEC's intra-LATA CIC/CAC of 101-5123+ as a
DIALAROUND code, has continued to wirk, if it ever indeed did work,
for 1+/0+/0- intra-LATA services from those independent telcos'
c.o.switches/wirecenters/ratecenters/exchange areass?

How would that independent telco deliver all kinds of originating
intra-LATA toll traffic, 1+ and 0+, to BOC ratecenters? How are 0-
(zero minus) "dial 0" operator services handled in those situations
from small non-Bell telcos' ratecenters, since most such small
non-Bell telcos don't do '0' operator services anymore, if they ever
indeed had their OWN dial-0 operators in "recent decades"? Similarly,
how are 0+ intra-LATA calls, collect, 3rd-pty, calling card, etc.,
handled if a 101-XXXX+ CAC isn't dialed first? Does the independent
ILEC come up with a way that THEY provide such under their own name,
but still using jointly owned trunks between them and the BOC of that
LATA? That could work for 1+ sent-paid traffic, but what about 0+/0-
intra-LATA traffic?

Of course, when I talk about 0+/0- intra-LATA dialing without any
101-XXXX+ CAC prefix first dialed, I'm referring to basic residential
and non-PBX business lines, and also possibly from telco-owned coin/
pay/public telephones. Private COCOT payphones, as well as PBXes, and
even cellular originations, are another category altogather, which
"play by their own 'rules'".

Has anyone heard of the dominant BOC/ILEC completely "withdrawing"
from being the traditional/default intra-LATA toll provider for
traffic/services originating from independent ILEC ratecenters/
exchange areas in that LATA, in other states?

As for the 0+/0-, it's always possible that one can use toll-free
800/888/etc. "dial-up" numbers for the carrier of their choice when
placing card/collect/etc. calls -- especially for those who are
travelling through that non-Bell ratecenter in that BOC LATA in those
states where this has happened. BellSouth has provided
1-800-BELLSOU(th) for card/operator services, and this number works
from most-if-not-all of the US and Canada. However, this does NOT
route to any "REAL" BellSouth TOPS, but rather to some contract
company, which had been the A-O-Sleze "Teltrust" at one time, and then
Qwest-LD (not to be confused with US-West) around 1999/2000. But I
don't know WHO is the underlying actual provider of 1-800-BELLSOU(th)
these days. Also 1-800-BELLSOU(th) is not restricted to intra-LATA.

SBC's 1-800-522-2020 which WAS originally Pac*Bell, and SWBell's OLD
1-800-600-BELL, and Ameritech's OLD 1-800-AMERITE(ch) routed to some
contract companies, NOT the true intra-LATA BOC DMS-TOPS services.
Prior to Dec.2006, I don't know how legacy SNET actually handled their
1-800-555-5321 card/operator access though -- since Dec.2006, it is
handled off of the AT&T-LL 212-0T OSPS in Manhattan, but when using
this particular access, AT&T-LL-issued cards are NOT accepted, only
most US/Canada ILEC-issued calling cards.

As for an "inter-LATA" entity, AT&T-LL's actual OSPSes *IS* accessable
with 1-800-CALL-ATT and other AT&T-LL OSPS 800/888/etc "dial-up"
numbers. This is NOT a "contract company" but rather the REAL AT&T-LL
OSPS. AT&T-LL-issued calling cards *ARE* accepted, as well as MOST
US/Canada ILEC-issued calling cards. And intra-LATA calling billed
to card/collect/etc. is also possible.

So, one can always place calling card and other specially billed calls
both intra-LATA toll and inter-LATA, with 800/888/etc type dial-up
numbers. But who is really handling 1+ sent-paid traffic from basic
resi- & business lines if the dominant BOC/ILEC does withdraw as the
traditional/default carrier originating from small independent telco
ratecenters in those BOC/ILEC LATAs?

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA,
the Lafayette ratecenter being at&t/BellSouth, but the Lafayette LATA
does have a LOT of CenturyTel and other small independent and mostly
rural-type ratecenters

Does anyone know if there is a contact for the "Local Calling Guide" website?
   Thanks!


---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.

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

Thanks so much!

"Mark J. Cuccia" <markjcuccia@...> wrote:          In Yahoo:
local-calling-guide, Lisa Nunez (l1phonecall_8) wrote:

> I am currently using this website to get the following information:
>
> Area Code/City/LATA/V&H/ILEC/NPA-NXXes....
> Is there an easy was to get all of this info in an Excel
> spreadsheet? I am needing area codes 201 to 999.Any help
> is appreciated. Thanks!

Well, there is no area code 999, and for that matter, there
are no area codes 990, 991, 992, etc. The highest purely
numeric area code within the NANP is 989 in Michigan.

Neustar-NANPA has lists of all assigned US-based NPA-NXX
codes in various formats, including web, text, and excel.
US jurisdictions inlcude all 48 conterminous US states as
well as the District of Columbia, and also the states of
Alaska, Hawaii, and the other US possessions of Puerto Rico,
the US Virgin Islands, Guam, the Mariana Islands of Saipan/
Tinian/Rota, and American Samoa. ALL of these US-jurisdictions
are now in the NANP.

There are various sub-menus you can click at NANPA's website
from http://www.nanpa.com/reports/reports_cocodes.html
and then choose the types and formats of info you might want
from these submenus, regarding US-based "POTS" central office
codes.

If you are also interested in c.o.codes in SPECIAL area codes
such as 456, 500, 900, see some of the following pages/sections
at Neustar-NANPA's website:

http://www.nanpa.com/number_resource_info/500_codes.html
http://www.nanpa.com/number_resource_info/900_codes.html
http://www.nanpa.com/number_resource_info/456_codes.html

The only "known" c.o.code assigned within the US Government's
Special Area Code 710 is 710-627. Virtually all other possible
710-NXX combinations have also been officially "reserved" to
the US Federal Government, but there is no publicly "known"
assignments for these 710-NXX codes other than 710-627 which
is assigned to the DHS/FEMA/NCS/GETS/etc.

Detailed Canadian NPA-NXX information can be obtained from SAIC-CNA's
website at: http://www.cnac.ca/co_codes/co_code_status_map.htm

Click on the Canadian area code you want info on, and you'll get
a "web" html chart of NPA-NXXes in that Canadian NPA code.

The 600 Special Area Code for use in Canada -- you can find the
current 600-NXX code assignment list in html chart form at
SAIC-Candaian Numberign Administration's website, at:
http://www.cnac.ca/other_codes/600/600-nxx_codes.htm

If you want info on NXX c.o.codes within the toll-free area codes
800/888/877/866, for the most part, with a very few exceptions,
all possible 8YY-NXX codes are available for assginment for line-
numbers, without any specific regard to carrier or geography, due
to full/wide portability.

As for the c.o.codes in the NANP-Caribbean NPAs, those which are
NOT "US", i.e., NANP-Caribbean locations other than the US'
Puerto Rico and US Virgin Islands, I don't know of any single
"official" site that posts this info, although individual island
telecom numbering administrations do have charts at their websites,
or downloadable doc/pdf/etc. files from their websites. Unofficial
lists of non-US NANP-Caribbean NPA-NXX c.o.codes can be found from
the Local Calling Guide website you're currently using as well as
other "public" sources on the web, such as telcodata.us and such.
But remember that the "unofficial" sites might not be nearly as
updated/accurate as any official lists that might be available.

mjc





---------------------------------
Have a burning question? Go to Yahoo! Answers and get answers from real people
who know.

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

On Friday, regarding how most of at&t/BellSouth's central office
locations in Baton Rouge LA still have the BellSouth name/logo on
them, I wrote:

SNIP

> As for the MAIN Baton Rouge building downtown, the last time I saw
> it "up close" was in August 2006. It houses an AT&T-LL 4ESS toll
> switch that dates back to pre-divestiture Bell System days, as well
> as the BellSouth "Main" switch for the business/government district
> downtown. There is an "old" building as well as a newer modern
> addition. The BellSouth logo/signage was on the left side of the
> front entrance to the new/modern addition, and the 1983-2005
> "divestiture" AT&T (uppercase) logo was on the right side of the
> front entrance to the new/modern addition. Also, at the very-top,
> roofline, of the multi-story modern/new addition was the 1983-2005
> AT&T uppercase logo.

And that AT&T 1980s-vintage deathstar logo at the top roofline was
black-and-white.

BTRGLAMA--- is at 333 North Sixth Street for the modern building
addition. The older buidling is at 555 Florida Ave at N. Sixth St.
Sort of ironic, the address being 555, and I guess that at one-time,
the local directory/information operators on 411 and "What City?
Baton Rouge" 504-555-1212 were also located at this location!
Baton Rouge is now area code 225, which split from 504 in Oct.1998,
mandatory April 1999. It is also LATA #492, the "Baton Rouge LA Metro
LATA".

> Next time I'm in Baton Rouge, I'm going to try to see if there have
> been any changes to either or both the BellSouth and 1983-2005 AT&T
> uppercase logos.

I was in Baton Rouge briefly this Monday morning, and while I didn't
get an "up-close-and-personal" view of the AT&T/South Central Bell
main building downtown, I did get a better view than I did on Friday.
I only saw the left side of the buidling, actually the OLD building in
the complex, while passing on I-10 several blocks away. But today, I
got a "somewhat better" front-view of the modern building while
passing on I-110 a few blocks away. I couldn't see the street-level
ground floor entrance from I-110, but I did see the Microwave tower
assembly, which is easily visible from I-10 and I-110, and I also did
see the top roofline of the modern building addition.

The have replaced the 1980s-vintage black-and-white deathstar logo
with a MUCH LARGER blue-and-white modern 2005+ wannabee deathstar
"globe" logo.

However, from the distance I was viewing it, I couldn't tell if the
older uppercase AT&T letters were still displayed, or if the new
lowercase at&t letters have replaced the older uppercase lettering.

Next time I'm actually in downtown Baton Rouge, I'm going to check to
see if the ground-floor BellSouth and 1980-vintage AT&T logos on
either side of the main entrance on the exterior of the modern
building addition have been removed, replaced with the 2005+ modern
wannabe deathstar logo and lowercase at&t lettering.

And I'm also curious as to what the main AT&T/South Central Bell
building in downtown New Orleans currently looks like as far as logos.
NWORLAMA--- is a complex of buildings at 840 Poydras at 500-520
Baronne Street. At 820 Poydras is a 1920-era white brick building that
is now a Drury Suites and Inns, but it was once a telco bulding as
well, originally Cumberland Tel & Tel, all the way through South
Central Bell. There was also another OLDER buidling, now torn down
since the early 1980s, which was built almost 100 years earlier in
the 1890s, at 501 Carondelet at 800-810 Poydras, which was a telephone
company facility. And across Carondelet Street, possibly at
500 Carondelet Street and the upper-700's block of Poydras was yet
another one-time telephone company building built in either the 1880s
or 1890s, which was torn down YEARS ago, the location is now the
parking lot behind the current New Orleans Federal Reserve Bank
buidling in the 500-block of St.Charles Avenue.

But telco still has the 518-520 Baronne Street building constructed
in the 1920s/30s, and the 1960s/70s-vintage 500-510 Baronne at
840 Poydras building, as the New Orleans "Main" building.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina
both places are also at&t/BellSouth/South Central Bell/Southern Bell/
Cumberland Tel & Tel/etc.

Ever since it was announced at the end-of-2006/beginning-of-2007
that SBC's at&t and BellSouth are actually going to merge, or more
likely, that SBC's at&t will takeover BellSouth, whenever I login
to my AT&T-LL account for AT&T-LL 1+ Calls, Calling Card Calls, etc.
including my AT&T Personal toll-free 800 number... at,

https://www.customerservice.att.com/

At the moment I've finished entering the area code of the telephone
number for my account, when it is JUST the area code, which is 337
for southwest Louisiana, a "red text" section pops up on that screen:

"BellSouth customers: Click here to log in."

and the URL that I'm taken to *IF* I click on the word "here" is,

http://www.bellsouth.com/login/

which is the long-time website to login to one's BellSouth landline
ILEC account!

I've been billed for my 0288 AT&T 1+ and Card Calls *SEPARATELY*
since about 1999. At the time, when I changed to a better AT&T-LL
discount plan, I was told by AT&T-LL that I *HAD* to be billed
directly by AT&T, that the new discount/package plan that I was
changing over to could *NOT* be billed on an AT&T-LL section of my
monthly BellSouth bill.

When I moved here to Lafayette LA in Fall 2005, following Katrina,
I was not allowed to migrate the AT&T-LL discount plan that I had
been signed up for since 1999, as it was no longer available to new
or moving customers, but I was able to be grandfathered while I
continued to remain at my old New Orleans address. However, there was/
is a plan that is even better, so I signed up for that new one in
2005. I also could choose to be billed by my ILEC, BellSouth... or
I could be directly billed by AT&T-LL. Since I had been directly
billed by AT&T-LL since 1999, I continued with that. Of course, I
still have a BellSouth landline which includes bundled Cingular, and
I'm billed by BellSouth for that.

But my AT&T-LL direct billing and account for AT&T Long Distance must
be handled by AT&T-LL, and not at&t/BellSouth landline, when I'm
viewing my AT&T-LL account/billings online!

I was not prohibited from continuing to key the remaining seven
digits into the field on the AT&T-LL account login, and it indeed
still takes me to my AT&T-LL account.

But I wonder how many people in the nine southeastern states are
"thrown" when trying to login to their AT&T-LL accounts website,
and they key-in the area code and get this "red-text" announcement.

Anyhow, I thought I would try a few OTHER area codes in certain
southeastern US states... i.e., in Florida, 813, 727, 941, 863, 239;
and in North Carolina, 252.

The 252 area code split from 919 back in 1998. The resulting 252 NPA
is in northeastern NC, and contains *ABSOLUTELY NO* BellSouth
ratecenters/exchanges! With the exception of a few small local
independent telcos, as well as a small extension from a switch and
LATA in southeastern Virginia, provided by the GTE-one-time-Contel
side of VeriZon, the 252 area code is *EXCLUSIVELY* Embarq/Sprint/
United/Carolina Tel & Tel.

The five above listed Florida area codes as they exist today were all
a part of the old 813 area code. As of the early 1960s, 813 was
100% *NON* Bell! Prior to the 1960s, 813 did seem to extend a bit to
the north which would take-up some Southern Bell ratecenters/
exchanges, but by 1961 or so, 813 was re-aligned, so that it was
totally GTE in the Tampa/St.Petersburg area, and United in the
Fort Myers area.

Starting in 1995 and continuing, so far, through 2002, there have
been several splits off of either 813 or of something else that split
off from 813 since 1995. Presently, 727 and 813 are 100% VZ/GTE in
the Tampa Bay area. Both 941 and 863 have either VZ/GTE towards the
north and east, and Embarq/Sprint/United towards the south. 239 is
100% Embarq/Sprint/United in the Ft.Myers area.

When I tried keying in any of these 100% independent telco NPA codes
but within a BellSouth state of FL or NC, in the field at AT&T-LL's
login page, I also got the "red-text" about "BellSouth customers
login 'here'". Again I guess one could ignore that message which will
take you to BellSouth ILEC's login page, and still "force" yourself
to the AT&T-LL login....

And while I never thought about this last year during 2006, because
my own 337 NPA code was "okay" at the AT&T-LL page last year, I now
tried keying in some NPAs of "former SBC" states, i.e., SWBell,
Pac*Bell/NV*Bell, Ameritech, SNET. I got a similar "red-text" message
of "Former SBC customers: Click here to log in.", with the "here"
being a hyperlink taking me to:

https://www.customerservice.att.com/sbc/mysbc

which is NOT AT&T-LL direct billing account, but rather legacy SBC
landline ILEC!

BTW, the legacy-SBC landline-ILEC login page has a message regarding
BellSouth as well:

"BellSouth customers access your 'BellSouth My Account'"

and this is a clickable link which takes you to:

https://www.bellsouth.com/apps/cpr/home/login/cprLogin?


Note also, that there can be independent telcos WITHIN an area code
that has BellSouth NXXes/ratecenters. If I were a CenturyTel landline
ILEC customer in Breaux Bridge LA, I could still have a separate
direct-billed long-distance account with AT&T-LL. I could have
337-EDgewood-2- for my telephone number, but once I keyed in the '337'
NPA code on the AT&T-LL billing/account login page, without even
keying in the c.o.code of 332, I would get that "red-text" message!
Yet I wouldn't even be a BellSouth ILEC landline customer in that
ratecenter of Breaux Bridge LA, but rather CenturyTel.

In 513 OH and 859 KY, one might not necessarily be SBC/Ameritech or
BellSouth, but rather Cincinnati Bell!

In 203/CT, there are two ratecenters in the extreme southeastern tip,
Byram and Greenwich, which are NOT at&t/SBC/SNET, but rather
VZ/BA/NYNEX/NYTel!

The VAST bulk of 702/NV in southeastern Nevada is NOT
at&t/SBC/Pac*Tel/NV*Bell, but rather Embarq/Sprint/Centel, with some
other smaller independent telcos as well. at&t/SBC/Pac*Tel/NV*Bell
has only TWO ratecenters in Clark County, 702/NV, Indian Springs,
and Sandy Valley NV.

And just like within BellSouth territory, in area codes which have
both BellSouth and independents, there are area codes in SBC states
which have both legacy-SBC and independents, or at least VeriZon but
it would be the GTE/Contel/etc. side of VZ!

I did try keying in some Canadian area codes, Caribbean area codes,
"special" area codes such as 800/888/877/etc. and 900 and such, as
well as totally NON-EXISTANT area codes, and there was NO "immediate"
flagging of any kind.

Again, I have always been allowed to continue keying in the remaining
seven-digits of my 337+seven-d landline phone number which is also
my account number with AT&T-LL, even though the "red-text" pops up
immediately when I've keyed in NPA 337, and I'm allowed to continue
keying in the password, and I do have full access to my AT&T-LL
account. But I do wonder if anyone has been "thrown/confused" and
actually erroneously mis-directed to BellSouth or legacy-SBC to pay
an AT&T-LL direct billing online, whether or not they are SBC or
BellSouth landline customers, or independent ratecenter customers,
or even CLEC customers, or if they've completely cut the cord and
gone 100% cellular for their "basic" phone service, yet still keep an
AT&T-LL-issued direct-billing calling card for various reasons.

I also wonder as time goes on, if SBC's at&t will try to get me to
combine my legacy AT&T-LL account/billing and my legacy at&t/BellSouth
ILEC landline account/billing, the latter also including at&t/Cingular
billing/accounts.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina
In at&t/BellSouth/South Central Bell/Southern Bell/Cumberland Tel+Tel
ratecenters/territory for both towns.

I hadn't noticed any posting from David Leibold on this, but while
looking thru his "World Telephone Numbering Guide" website,
http://www.wtng.info I found the following mention on the "what's
new" page, http://www.wtng.info/wtng-new.html a blurb dated 1-Feb-2007
that Tristan-da-Cunha, an island group in the South Atlantic off of
the coast of Africa, part of the British Commonwealth, or whatever the
current status/terminology w/r/t Tristan happens to be, is to now be
a part of the existing ITU E.164 Country Code +290 for St.Helena, also
a part of the British Commonwealth, or whatever its current status/
term happens to be.

On the WTNG page for St.Helena, now renamed "St.Helena and Tristan-da-
Cunha", http://www.wtng.info/wtng-290-sh.html there is mention that
Tristan is administered from St.Helena. It is also mentioned that the
UK's OFCOM has made this recent telephone numbering announcement thru
the ITU. Tristan will have the +290-3xxx range, while all other
+290-Xxxx ranges, with the exception of +290-0xxx, will be retained
for St.Helena.

And there is a 2004 numbering-range breakdown at the WTNG:

+290 1xxx  (1xx to 19xx used for domestic short codes)
+290 2xxx  Jamestown numbers
+290 3xxx  telephone services
+290 4xxx  telephone services
+290 5xxx  international premium rate
+290 6xxx  telephone services
+290 70xx  telephone services
+290 71xx  telephone services
+290 72xx  international premium rate
+290 73xx  international premium rate
+290 74xx  international premium rate
+290 75xx  international premium rate
+290 76xx  international premium rate
+290 77xx  international premium rate
+290 78xx  international premium rate
+290 79xx  international premium rate
+290 8xxx  international premium rate
+290 9xxx  international premium rate

The source of this list at WTNG is from the UK's "Cable & Wireless",
via the ITU, http://www.itu.int/itudoc/itu-t/number/s/sth/82409.html

Ofcom's announcement via the ITU regarding Tristan and St.Helena can
be found at:

http://www.itu.int/oth/Default.aspx?lang=en&parent=T02020000ED

MS-Doc files can be downloaded in either English, French, Spanish
from this page, the English language .doc file being:

http://www.itu.int/dms_pub/itu-t/oth/02/02/T02020000ED0004MSWE.doc


--------------------------------------------------------------------
Tristan da Cunha -- Country Code +290
Communication of 06-FEB-2007:

The Office of Communications (Ofcom), London, in consultation with
the Director of TSB, announces that the E.164 Country Code +290
formerly assigned to the Administration of the United Kingdom solely
for the British Overseas territory of Saint Helena, will henceforth
be shared with the British overseas territory of Tristan da Cunha.
The basis of the sharing will be that after the E.164 Country Code
+290, four-digit national numbers commencing with the initial digit
"8" will be assigned to Tristan da Cunha, whilst national numbers
commencing with the initial digits "1, 2, 3, 4, 5, 6, 7, and 9" will
remain assigned to Saint Helena.

Contact:
Mr Wesley Milton
Office of Communications -- Ofcom
Spectrum & International Policy Associate
Riverside House
2A Southwark Bridge Road
LONDON SE1 9HA
United Kingdom
Tel:    +44-20-7783-4291
Fax:    +44-20-7783-3990
E-mail: wesley dot milton at ofcom dot org dot uk
--------------------------------------------------------------------


Thankfully, Ofcom referes to their own Telephone and Fax numbers with
a TWO-digit city code '20' followed by an EIGHT-digit local London
number, the c.o.code being FOUR digits!

London is 20 followed by eight digits, mostly 7XXX-xxxx and 8XXX-xxxx,
with a few more recent assignments 3XXX-xxxx.

London is NOT supposed to be parsed as 0203, 0207, 0208; or +44-203,
+44-207, +44-208; followed by only seven-digits. Locally one MUST dial
ALL EIGHT digits of a London number! I think that within 020 London,
one can also dial 020 followed by the eight digit local number
3XXX-xxxx, 7XXX-xxxx, 8XXX-xxxx; I also think that even within the UK,
one might also be able to dial 00+44+20 followed by the eight-digit
London number. But local numbers in London and some other parts of the
UK itself are now EIGHT digits! with a two-digit city code +44-2X or
domestically 02X.

Note an inconsistancy here -- Dave Leibold's WTNG webpage, as of
mid-day US/Canada time on Wednesday 07 March 2007 indicates that
Tristan will use +290-3xxx, while the UK's Ofcom announcement via
the ITU states that Tristan will use +290-8xxx.

I haven't been to Ofcom's site yet to see if they have any
announcement of their own. I thought I was subscribed to free email
distribution of Ofcom telecom numbering announcements, which I have
received in the past. However, in more recent years, telephone
numbering news/changes/etc. all over the world, including the UK,
Australia, US/Canada/NANP, etc., is very slow when compared to the
second half of the 1990s decade! I remember getting emailings from
Oftel, the predecessor to Ofcom, at least twice a month during the
1995-2001 time period, and I also got frequent emailings from
Australia's numbering/regulator back then too. But in more recent
years, there are only occasional emailing.

Anyhow, now that Tristan is to be integrated into +290 St.Helena,
I wonder if there will soon be something for Pitcairn in the eastern
South Pacific?

Tristan didn't really have any basic/POTS telephone service AT ALL
in the past. They might have had Inmarsat or Iridium/etc. type
satellite telephone service, using the various ITU "Country" Codes
assigned to such satellite services, i.e., +87X, +88X, etc. But it
now seems that REGULAR landline/wired phones are supposed to be
introduced in Tristan, using a "regular" geographically-based ITU
E.164 Country Code, although not one "unique" to them but rather
"sharing" from an already assigned ITU Country Code of another island
location, one within the region, and also one that is associated
politically/jurisdictionally.

As for Pitcairn in the eastern South Pacific, they too are "similar"
to Tristan. Pitcairn has been using Inmarsat/Iridium/whatever
satellite phones with +87X or +88X "country" codes, but they haven't
had any +6XX country code of their own. Pitcairn has had a magneto
partyline system in the past, but I don't know if that set-up is still
in use. I do wonder if +690 Tokelau, another "isolated" island group
in the South Pacific, is going to be used for supplying any future
POTS/geographic numbeirng for Pitcairn? And as is the case with
St.Helena and Tristan, both Tokelau and Pitcairn are historically
associated with the UK in some way, as well as with other historical
UK areas in the Pacific such as New Zealand and Australia.

Tokelau's numbering is +690-Nxxx. There are three islands/atolls in
Tokealu. Pitcairn is even more "sparse" with only about 50 or so
residents!

mjc

It was FIFTY years ago this year, in 1957 that the 504/318 NPA Split
happened here in Louisiana. When the US/Canada Area Code Format was
"finalized" on Wed-22-Oct-1947 in preparation for Nationwide Operator
Toll Dialing and ultimate cusotmer-originated Direct Distance Dialing,
the entire state of Louisiana was given the 504 area code. Official
NPA Maps and Lists published by AT&T/Bell/Telcos from 1957-forward
showed two area codes for Louisiana, the new one being 318.

318 is one of the FEW area codes which had some previous assignment/
use that was subsequently discontinued, and that same code being
re-assigned! 318 was originally used in 1951/52 and possibly into
1953, for Englewood NJ customers who were the first to have some form
of LIMITED "coast-to-coast" DDD, to be able to dial to the
San Francisco and west-bay and north-of-the Golen Gate communities.
Oakland CA and east-bay communities were still dialed from
Englewood NJ with 415 at this time. By 1954, the use of 318 for
identifying calls to points west of San Francisco/Oakland Bay was
discontinued, and both sides of the Bay were "back" to being dialed
with the 415 area code. I have never seen any official/formal
documentation from AT&T or Pacific Telephone, nor New Jersey Bell, as
to exactly WHY San Francisco and other west-bay communities were
identified with 318 during those early 1950s years, nor the "exact
dates" of the start of the special use of 318 and the final date of
such... But I think it had to do with the lack of full six-digit
translation of the full and complete NPA-NXX code. Use of separate 318
and 415 area codes for each side of the bay probably helped out for
better routing, since both sides of the Bay had individual tandem
switches, and the toll or tandem switch which Englewood NJ homed on,
had trunks to both the Oakland and San Francisco tandem or toll
switches. Three-digit translation of just the 415 NPA code as dialed
from an Englewood NJ customer indicated routing via Oakland CA's toll
switch, while an Englewood NJ customer-dialed 318 NPA code would be
simply translated on those three-digits to indicate routing via the
toll switch on the San Francisco CA side.

I do wonder if Englewood NJ customers could still "get through" with
either area code for the either side of the Bay? There was NO
duplicative re-assignments of the NNX c.o.codes within each side's
NPA code. Calls between each side of the Bay were simply dialed as
JUST seven-digits, or rather 2L-5N, without the need for 318 or 415
if dialing between opposite sides of the Bay on a "local" basis. And
while 318 was shown as "separate" from 415 in all customer instruction
booklets at Englewood NJ in 1951/52, including the US/Canada NPA map,
the *OFFICIAL* AT&T/Bell System US/Canada NPA maps as shown in telco
journals of 1951/52, such as Bell Telephone Magazine, Bell System
Tech Journal, Bell Laboratories Record, such as in articles devoted
to forthcoming DDD, Operator Toll Dialing, automated switching and
routing, etc. only indicated 415 for ALL of the central California
coastal area, including BOTH San Francisco and Oakland sides of the
Bay. And I think that OPERATORS who had Operator Toll Dialing
capability for placing calls to the west coast keyed 415+seven-digits
or 415+2L-5N, not only for Oakland, but also for San Francisco.

Anyhow, there were the temporary Mexican NPA codes of 903, as well as
90-5 and 70-6, which had been "reclaimed" and re-assigned elsewhere,
as well as the TWX special area codes 510, 610, 710, 810, 910, and
possibly even a one-time 310 special "data services" area code, all of
which were "reclaimed" and re-assigned elsewhere subsequently, in
addition to the one-time 1951/52 use of 318 for San Francisco's being
dialed by Englewood NJ customers, 318 being re-assigned to the 1957
split of Louisiana's 504.

Unfortunately, I do NOT have the "exact" date of when the 504/318
split took place on a FLASH-CUT basis, most likely at 2:01am Eastern,
1:01am Central, early on some Sunday morning, during 1957. I don't
really trust the indicated dates for a 504/318 split on several
websites. And the split was a FLASH-cut, not one with any official/
formal permissive dialing period. Of course, there was an
"inadvertant" period where both 504 and 318 could have been used for
dialing to those parts of southwestern, west-central, central, and
northern Louisiana that were becoming split off to 318, but that
inadvertant period was probably only for a few hours on that Sunday
morning back in 1957, or mabye for a day or two following, until all
of the translations in various switches in Louisiana and possibly in
other adjacent states, or in major toll switching centers, could all
be arranged to FIRST turn "on" all valid 318-NNX codes, and THEN
to subsequently turn "off" all "matching/counterpart" 504-NNX codes
which were no longer valid under NPA 504 -- that is, until those
specific 504-NNX codes were re-assigned under the "new" or shrunken
post-1957 504 NPA region.

When researching old Louisiana telephone directories, I have NEVER
found any reference to 318 in any 1957 directories, nor in any
pre-1961/1962 issue directories. There was apparantly NO originating
DDD capability by the general public anywhere in Louisiana in 1957,
although it is POSSIBLE that there might have been limited originating
customer DDD from other #5XB local switches in Louisiana, only that it
wasn't widely "known" -- i.e., big business customers served off of a
#5XB office were told about their limited originating customer DDD
capability, but residentail customers knew nothing about it. And until
XB-Tandem switches with CAMA and other things were subsequently
resolved in the early 1960s, circa 1962/63, SXS customers didn't even
have any originating customer DDD capability in Louisiana.

Unfortunately, I don't have ready access to old telephone directories
from other parts of the US/Canada. Nor do I have any "special"
booklets or pamphlets on DDD that might have been issued to those few
but ever-increasing customers in the 1950s-era, those pamphlets
showing full instructions for those customers of their limited
originating DDD capabilities, but those instructions NOT yet published
in the more generally available telephone directory for their area.

At least two cities in south-central Louisiana, Lafayette LA, and
New Iberia LA, had 2L-5N numbering recently introduced, by 1955 or
1956, when both would have still been "officially" part of 504.
There was/ still is, EMerson n-xxxx for New Iberia, and CEnter n-xxxx
for Lafayette. Of course, LOCALLY the customers were still able to
dial JUST the five-digit part of the number, for YEARS to come, until
they were either changed to 1AESS or possibly 5XB, during the 1970s
era. The instructions in the front of local directories when a 2L
exchange name was added to the front of previous five-digit local
numbers, or when 2L+one-digit was added to the front of previous
four-digit local numbers, with little to no changes in any line-number
assignments -- always indicated that one "must" dial the FULL 2L-5N
number, or if ANC was in use, the FULL 7D number, but most locals
served by such smaller town SXS systems "knew" that they could still
get by locally with JUST the last four or five digits!

But since Lafayette LA and New Iberia LA were already "officially"
listed as 2L-5N by 1956, I do wonder if MAYBE other parts of the US
which had limited originating CUSTOMER DDD capability, were able to
actually DIAL to Lafayette and New Iberia as 504+2L-5N? I do wish I
had "easy" access to such places 1950s-era telephone directories,
because MAYBE there was a blurb in the 1956 or 1957 edition that they
were to continue using 504 to dial to Lafayette and New Iberia, until
some "such-and-such" date in 1957 that they were now to change to
using 318+ the 2L-5N local number!

The south-central and southwest part of 318, i.e., the Lafayette &
Lake Charles LA LATA #488, split from 318 into the new 337 NPA code
in October 1999 permissive, July 2000 mandatory. The 318 NPA code
was retained "roughly" by the Shreveport-Alexandria-Monroe LA LATA
#486.

The 504 NPA code as it existed from 1957-forward, at least until
1998, was roughly what would become the Baton Rouge LA LATA #492
and the New Orleans LA LATA #490.

In 1974 or 1975, the town of Melville LA, which retained 504 since
1957, was changed over to NPA 318. It retained its NNX c.o.code of
623 when it changed from 504 to 318 in the mid-1970s. I think that
there was a "re-home" from the Baton Rouge tandem in 504, to the
Opelousas LA or Lafayette LA tandem in 318 at that time.

What's interesting about Melville LA, is that it is WEST of the
Atchafalaya River, and in St.Landry Parish, that Parish also being
completely west of the Atchafalaya. Just to the east of the
Atchafalaya, just east of Melville LA, is Pointe Coupee Parish which
is completely east of the Atchafalaya. Most, if not all, of Pointe
Coupee Parish, retained 504 but is now 225, and part of the Baton
Rouge LA LATA. Melville LA is part of what is now NPA 337 and is part
of the Lafayette-Lake Charles LA LATA. I don't know if the boundaries
of the Melville LA ratecenter and central office coverage area might
actually "spill over" to any residents and businesses in the vicinity
but just east of the Atchafalaya and in Pointe Coupee Parish. There
is no automobile bridge crossing the Atchafalaya at Melville, but
there is a Railroad bridge; Also a car/passenger ferry boat, toll,
and it is indicated to connect both sides of La.Hwy 10. But the east
side of the Atchafalaya River at that point is part of the Atchafalaya
Basin Spillway, which can be opened up to divert high waters of the
Mississippi River to the east and north whenever the Mississippi River
might get "too high" in the Spring/Summer. This would flood a large
section of plains land east of the Atchafalaya River for a large
region of south central Louisiana. Much of it is swamp anyhow.

Melville LA also has a "community of interest" more so with
Opelousas LA, Krotz Springs LA, Port Barre LA, Leonville LA, etc.,
all of which had split to 318 in 1957, and subsequently to 337 in
1999/2000. Melville does NOT really have much of a "community of
interest" with Baton Rouge which retained NPA 504 but subsequently
split to 225 in August 1998 permissive, April 1999 mandatory.

There is also one other ratecenter that is really west of the
Atchafalaya River that retained 504 with 1957. The ratecenter of
Patterson LA is west of the Atchafalaya, but is immediately adjacent
to the Morgan City LA ratecenter east of the Atchafalaya. Morgan City
has two at&t/BellSouth landline c.o.switches, Inglewood "Main", and
Amelia. Patterson also has two at&t/BellSouth landline c.o.switches,
"Main", and Bayou Vista. These are a part of the New Orleans LA LATA.
These also split to the new 985 NPA when there was the 504/985 split
during 2001. Both are also a part of St.Mary Parish. However, just to
the west-northwest of the Patterson LA ratecenter, and also within
St.Mary Parish are the Centerville LA and Franklin LA ratecenters/
wirecenters, which had split to 318 in 1957, now part of NPA 337,
and with divestiture became associated with the Lafayette/Lake Charles
LA LATA. It was in 2001 or 2002 that the La.PSC and BellSouth
introduced Parish-wide EAS/Local calling throughout all of St.Mary
Parish, including across the LATA and NPA boundary. Ten-digits are
required for local/EAS calling if it crosses the NPA and LATA boundary
in most "inter-NPA" local/EAS calling situations where they do exist
in Louisiana.

Roughly, the boundary between 504 and 318, or now 985/225 and 337/318,
is the Atchafalaya River/Basin, with the Patterson LA ratecenter
exception west of the Atchafalya but still within 985 once 504.

However, the Atchafalaya Spillway Basin ITSELF is mostly swamp and
more or less a "no man's land". It really could be thought of as
"open area", not really associated with any wirecenter/ratecenter,
LATA, NPA, etc. within Louisiana. It *IS* surrounded by actual
populated areas of the Lafayette/Lake Charles LA LATA #488 and now
NPA 337, the Baton Rouge LA LATA #492 and now NPA 225, and the
New Orleans LA LATA #490 but part of that part which is now NPA 985
not 504.

Mark J. Cuccia
markjcuccia at yahoo dot com
Lafayette LA, formerly of New Orleans LA pre-Katrina
In at&t/BellSouth/South Central Bell/Southern Bell/Cumberland Tel+Tel
ratecenters/territory for both towns.

The 815/779 NPA Overlay in northern Illinois outside of Chicago Metro
and northeastern Illinois, is "officially scheduled" to take effect
tommorrow, Saturday 17-March-2007, as far as when new pre-assigned
non-test "POTS/geographic" 779-NXX c.o.codes could begin to take
effect. However, there is presently only ONE such pre-assigned 779-NXX
c.o.code, 779-435, for at&t/SBC/Ameritech/IL-Bell, in the Joliet IL
ratecenter and the JOLTILJODS1 c.o.switch, and its effective date is
for Monday 19-March-2007.

There are also four 815-NXX c.o.codes which are still possible for
assignment: 815-270 which is one that had previously been assigned,
but must have recently been returned to, or reclaimed by, Neustar-
NANPA; and also 815-779, 815-800, 815-815, which have never been
previously "assigned".

Mandatory ten-digit / 1+ten-digit intra-815 local dialing took effect
a month ago, on Saturday 17-February-2007. However, while there was
approval by state regulatory for an overlay three years ago, back in
Feb/March 2004, with the effective date still TBD at the time, and
there has been public notification for many months now, and in the
early 2000s or late 1990s, there were public hearings as to what type
of relief would be used... there were still some local municipal
officials especially in Rockford IL, and some Illinois state
legislators/senators who are trying to "challenge" the ten-digit
mandatory dialing and ultimate overlay, and want state regulatory,
the Illinois Commerce Commission, to "un-do" the ten-digit dialing and
associated 779 overlay. Obviously, that isn't going to happen, but
hopefully, the ICC and telecom industry can try to quell the
unsubstantiated "fears" of politicians pandering to the public, that
an overlay is "unsafe for those trying to reach 911 when there are
multiple overlays". That simply is NOT the case, since there are
proper ANI deliveries and sometimes dedicated trunk groups to a 911
"PSAP" in overlay areas. And there are already NUMEROUS successful
overlays throughout other parts of the US and in parts of Canada as
well.

As for the 630/331 NPA Overlay in the western/southwestern Chicago IL
Metro area suburbs, the regulatory "rules" are that all possible
assignable 630-NXX geographic/POTS c.o.codes must be completely "used
up", BEFORE Neustar-NANPA can set a firm date for mandatory
1+ten-digit intra-630 local dialing, and the opening up of
"pre-assignment" of geographic/POTS non-test 331-NXX c.o.codes.

Thus, at the moment, it is still not known as to the EXACT date when
mandatory 1+ten-digit dialing takes effect for local calls within 630
nor when the first 331-NXX non-test geographic/POTS c.o.codes can be
"pre-assigned" or ultimately take effect.

At present, there are only TWO remaining available such 630-NXX
c.o.codes, possible for assignment as geographic/POTS non-test
c.o.codes: 630-630 and 630-666.

Both of them can seem "undesirable", the first being a duplication of
the NPA's digits as the c.o.codes, and while not technologically
impossible, it "could" cause confusion to some of the public. The
second, 630-666, uses the "devil's number" 666, and is undesirable for
that reason.

I wonder if Neustar-NANPA and/or at&t/SBC/Ameritech/IL-Bell will
request from the Illinois Commerce Commission, that 331-NXX c.o.codes
should NOW begin to be "pre-assigned" with an announced earliest-
possible "activation date"?

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

About two months ago, I had made a few posts regarding the La.PSC
and at&t/BellSouth's proposal to merge several southeast Louisiana
ratecenters into the New Orleans LA ratecenter, including several
which had split-off to NPA 985 since the 504/985 NPA Split back in
2000. Those NPA 985 ratecenters which were to be consolidated into
the New Orleans ratecenter would become localities under the larger
overall New Orleans ratecenter, and also have their 985-NXX codes
changed "back" to 504-NXX codes, using the same NXX c.o.code
combination under NPA 504 which they had since pre-2001, if still
available under NPA 504.

There are two cases where the 985-NXX c.o.code could NOT be used
as a corresponding 504-NXX code, since the 504-NXX code was
"re-assigned" in one case, and in the other case, the 985-NXX code
was a NEW assignment after the "corresponding" 504-NXX code.

On Wednesday 21-March-2007, the Louisiana Public Service Commission,
La.PSC, actually did approve this ratecenter consolidation and NPA
boundary change, what could be called a "reverse split", in
Special Order 10-2007.

The following ratecenters will be consolidated into the New Orleans
ratecenter:

- Lake Catherine LA
in the easternmost part of Orleans Parish/City of New Orleans.
The Lake Catherine c.o.building was completely destroyed with
Hurricane Katrina, and the associated Nortel Remote switch was
apparantly washed away. Any remaining/returning customers in this
area have since been "rewired" to the New Orleans "Michoud" DMS-100
switch, which was the host switch for the Lake Catherine Remote.

- St.Bernard LA
- Ysclowsky LA
- Delacroix LA
these three in outer St.Bernard Parish. St.Bernard LA was a full 5ESS
switch, while Ysclowsky and Delacroix were Nortel-Remotes hosted by
the New Orleans "Michoud" DMS-100. There was severe damage to all
three of these, and since Katrina, these areas have been "rewired"
to the New Orleans "Chalmette" 5ESS-Remote switch. There had been a
1AESS at Chalmette prior to Katrina, but with damage to Chalmette-1A,
this new 5E-Remote was installed instead, and has also taken over
these additional outlying areas.

The above four ratecenters retained NPA 504 back in 2001, so there is
nothing more than revising paper records and databases in the telco
industry, such as those of the LD-carriers, at&t/BellSouth,
Telcordia-TRA, Neustar-NANPA, NECA Tariff Filings, etc. for their
504-NXX codes' associated ratecenter.

Further downriver, in Plaquemines Parish, there are four ratecenters
since 2001 in the "new" 985 NPA code, to be changed "back" to NPA 504,
with three of these four ratecenters to be consolidated into the
New Orleans. The one ratecenter, Venice LA, at the very end of the
Mississippi River, on the west bank of lower Plaquemines Parish,
while changing "back" to NPA 504, will at this time, continue to be
a unique/separate ratecenter.

On the east bank of lower Plaquemines Parish, there is Pointe-a-la-
Hache LA. Since Katrina, any remaining/returning customers have been
"rewired" to the New Orleans "Chalmette" 5E-Remote. The BellSouth
landline customers in Pt-a-la-Hache have had the '333' c.o.code since
the mid-1950s when it was 504-EDison-3-. It did change to 985-333
with 2001, and since then, the 504-333 code was "reassigned" to other
providers within New Orleans upriver. Those remaining/returning/etc.
BellSouth landline customers with 985-333 will need to be changed to
something DIFFERENT than 504-333. I was told by one of my contacts in
New Orleans with South Central Bell, that they might also give these
customers different line-numbers as well, using existing 504-ARabi-x-
(504-27x) c.o.codes traditionally associated out of the New Orleans
"Chalmette" c.o.switch. Pointe-a-la-Hache LA as a ratecenter is to be
consolidated into the New Orleans LA ratecenter.

On the west-bank of lower Plaquemines Parish, there are the
Port Sulphur and Buras ratecenters, which will be both changed "back"
to NPA 504, as well as consolidated into the New Orleans LA
ratecenter. It appears that Cingular's 985-238 c.o.code, which also
has thousands shared with the CLEC Network Telephone, is a new,
post-2001 assignment, which "conflicts" with a pre-2001 assignment of
504-238 for New Orleans which is used by several CLECs/wireless
sharing different thousands. I don't know what Cingular's nor Network
Telephone's plans are for any customers with 985-238 numbers.

And as previously mentioned, the Venice LA ratecenter further
downriver on the west bank of lower Plaquemines Parish, near the
"mouth" of the Mississippi River, will continue to remain a unique
ratecenter, not to be consolidated into the expanding New Orleans LA
ratecenter at this point in time, but Venice LA will change "back" to
the 504 NPA. The c.o.switch and building for Venice LA somehow
miraculously "survived" Katrina apparantly unscathed. And this was
even closer to the Gulf of Mexico/etc. than any of the other
ratecenters' c.o.switches and buildings!

At this time, there is nothing "upfront" at the La.PSC's website
regarding their recent order of this past week, but you can "search"
for it at their website.

At the main page, http://www.lpsc.org/ click on "Document Access" in
the left-hand menu. You'll be taken to a "secure" page with a
LOOOONNNNNNGGG URL. At that page, click on the link in the
"Guest Sign-In" box. On the next page, click on "Orders", and then
click on "Order Number Search". On the next page, enter '10-2007'
in the "Order Number" box, and then use the drop-down below that to
change to "Special Order", and then click "SEARCH".

The result should be a similar page with a spot to click on "10-2007"
under the header "TITLE", near the bottom of the page, which should
take you to the .tif document. You might experience something trying
to update or install "JAVA" as well. You can also right-click on the
"10-2007" reference under the "TITLE" header near the bottom of that
page to download the .tif document, about 2.3 megs, to your own
hard-drive.

The actual dates for implementation of ratecenter consolidation and
NPA/Boundary change is as follows:

Sunday 29-July-2007, is the effective date for those ratecenters to be
consolidated into the New Orleans LA ratecenter, both those which have
always been under NPA 504 -- Lake Catherine LA in outer Orleans Parish
as well as the three in outer St.Bernard Parish: St.Bernard LA,
Delacroix LA, Ysclowsky LA ... as well as three of the four lower
Plaquemines Parish ratecenters which had changed to the new 985 NPA
back in 2001: Pt-a-la-Hache LA on the east bank of the Mississippi
River, and both Port Sulphur LA and Buras LA on the west bank of the
Mississippi River.

Also on this date of Sunday 29-July-2007, all four areas of lower
Plaquemines Parish which changed to NPA 985 with 2001, will be changed
BACK to NPA 504, with a nine-month permissive dialing period,
including both those which are to be merged into the New Orleans LA
ratecenter such as Pt-a-la-Hache LA on the east bank, as well as
Port Sulphur LA and Buras LA on the west bank... and also the
outermost Venice LA ratecenter downriver on the west bank of lower
Plaquemines Parish which is not at this time being merged into the
New Orleans LA ratecenter -- it will still be its own separate
ratecenter -- but it will change "back" to NPA 504.

Nine months later, on Thursday 01-May-2008, mandatory use of 504 will
begin for dialing to the Venice LA ratecenter; as well as for calling
those lower Plaquemines Parish localities now part of the New Orleans
LA ratecenter which were once their own unique ratecenters prior to
August 2007, i.e., Pt-a-la-Hache LA, Port Sulphur LA, Buras LA, and
which along with Venice LA had all been "temporarily" under NPA 985
since 2001.

The Jesuit Bend LA Stromberg-Siemens DCO c.o.switch and building, on
the west bank of "upper" Plaquemines Parish, forming the Jesuit Bend
LA ratecenter, was apparantly unaffected as such by Katrina. It also
retained NPA 504 back in 2001. While it has the same local/EAS calling
area as New Orleans, it is not being consolidated into the New Orleans
LA ratecenter -- at least not at this time. And as I mentioned, the
Venice LA ratecenter, while changing "back" to NPA 504 at this time,
is not at this time to be consolidated into the New Orleans ratecenter
nor are its lines to be "rewired" into some "upriver" c.o.switch.

The other two ratecenters which retained 504 back in 2001, Kenner LA,
upriver in Jefferson Parish, straddling both sides of the River, and
the Lafitte LA ratecenter on the west bank of Jefferson Parish, which
is "outlying" to some degree, are NOT being consolidated into the
New Orleans LA ratecenter, at least not at this time. And unless
at&t/BellSouth and the La.PSC have any intended pending tariff
changes, I don't think that Kenner/Lafitte have EAS with Venice.
Since 2001, the "shrunken" 504 NPA has had NO "home-NPA" toll! But
it might "reappear" if the "returned to 504" Venice LA ratecneter
will continue to have TOLL with Kenner and Lafitte! Kenenr and Lafitte
do have local/EAS with each other though. And both, including
New Orleans, but NOT Venice, have EAS with some futher upriver
ratecenters in St.Charles Parish and St.John Parish. These five
ratecenters have EAS with easch other, as well as with New Orleans,
Kenner, Lafitte:

- Norco LA in St.Charles Parish east bank

- Laplace LA in St.John Parish east bank

- Luling LA in St.Charles Parish west bank,
which includes two c.o.switches, Hahnville and Boutte

- Paradis LA in St.Charles Parish west bank,
further outbound near Des Allemands LA and upper Lafourche Parish

- Edgard LA in ST.John Parish west bank,
which also has inter-LATA EAS with the Vacherie LA ratecenter in
St.James Parish west bank and the Baton Rouge LA LATA #492, NPA 225.

These five ratecenters in St.Charles Parish and St.John Parish did
change to NPA 985 in 2001, and will continue to be NPA 985, but they
have had EAS with Kenner/Harahan for YEARS, and had new EAS with
New Orleans and Lafaitte starting in 2001 when they also switched from
504 to 985. Actually Edgard LA was local ONLY UNTO ITSELF until 2001
when it finally got its current EAS/Local Calling expansion.

Also on the east bank of St.John Parish is the independent Reserve LA
Telephone Company, with the Reserve LA and Garyville LA c.o.switches
and ratecenters, local calling with each other. But they don't
presently have EAS with anything but themselves.

If one doesn't have basic EAS, there are also numerous other options
from both at&t/BellSouth, wireless, CLECs, LD-carriers, etc.

I don't know about any current plans for any other coastal/outlying
areas in south Louisiana, as regards how at&t/BellSouth, Lafourche
Telephone Company, Kaplan Telephone Company, Delcambre Telephone
Company, or Cameron Telephone Company plan to consolidate switches
and/or ratecenters. There are several other outlying ratecenters and
c.o.switches in south Louisiana, out in the swamps/bayous, and near
the Gulf Coast. It might be that over time, these are "rewired" into
more inland switches over time to protect those customers from losing
their only c.o.switch.

LATELCO, Lafourche Telephone Company, is the ILEC for lower Lafourche
Parish, and there are the Grand Isle LA ratecenter actually in the
outermost part of Jefferson Parish, and the Leeville without an 's' LA
ratecenter in Lafourche Parish, which are very much "outlying". These
are in the New Orleans LA LATA #490, NPA 985 since 2001.

BellSouth also has Montegut LA and Dulac LA near Houma LA in LATA 490,
and NPA 985 since 2001. These outlying c.o.switches are in outer
Terrebonne Parish.

In the Lafayette/Lake Charles LA LATA #488, NPA 337 since 1999/2000,
there are the following "outlying" c.o.switches/ratecenters, some of
them were heavily affected by Hurricane Rita in September 2005:

- Weeks Island LA in outer St.Mary Parish and Iberia Parish,
at&t/BellSouth

- Delcambre LA in Vermillion Parish and Iberia Parish,
independent Delcambre Telco

- Forked Island LA
- Pecan Island LA
both in Vermillion Parish,
independent Kaplan Telco

- Grand Chenier LA
- Creole LA
- Cameron LA
- Johnson's Bayou LA
all four of these in Cameron Parish,
independent Cameron Communications

And well over a year after Hurricane Rita, the coastal parts of
Cameron Parish served by Cameron Communications are still in a major
state of disrepair. There was severe damage to entire settlements and
communities in Rita-affected coastal Cameron Parish -- entire houses
and buildings ripped from their foundation slabs or pilings. I don't
know how much service has been restored to the outlying areas served
by independent Cameron Communications -- even if there has been much
of a return by displaced residents.

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

About two months ago, back in January, I had posted that the
Canadian Numbering Administrator, SAIC-CNA, had created a
"place-holder" page at their website for forthcoming NPA Relief
Planning for NPA 418 in Eastern Quebec:

http://www.cnac.ca/npa_codes/relief/418/relief_418.htm

At the time, back in January, and until earlier this past week,
it simply stated "Coming Soon".

While the CNAC/CSCN/CISC and CRTC/etc. haven't yet officially
started NPA Relief Planning for eastern Quebec's 418 area code,
there is a recent "NRUF" document, forecasting the possible
exhaust of the 418 NPA at October 2008! See:
http://www.cnac.ca/npa_codes/relief/418/nruf/Draft_2007_R-NRUF_Aggregate_NPA_418\
.xls

With the "track record" in Canada over the past 7 years, I will
expect that an OVERLAY of 418 will take place. If that does happen,
then the entire Province of Quebec will have mandatory ten-digit
dialing for all of their local/EAS calls!

514 for Montreal Metro was officially overlaid with 438 this past
November 2006, although at present there are no non-test geographic/
POTS 438-NXX c.o.codes. But there *IS* mandatory ten-digit intra-514
local dialing, and ten-digit dialing for any local calls to the
adjacent 450 NPA.

Similarly, while 450 and 819 don't have any overlays at present, and
probably won't have any overlays for a LOOONNNGG time to come, all
local calling within 450 or 819, as well as from and to 450 and 819
with other adjacent area codes, is done as mandatory ten-digits.

Two POSSIBLE relief NPA codes for 418 could be 431 or 581. However,
with an overlay and mandatory ten-digit dialing, it really doesn't
matter so much, even if the overlay NPA code's numerics is also that
of an existing 418-NXX c.o.code! However, there are about 20 or 30
NPA code combinations "reserved" for future use within Canada. And
the SAIC-CNA/etc. have developed some criteria for choosing specific
relief codes for specific existing area codes within Canada.

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

at&t/BellSouth has added a new "Carrier Notification" at their
website dated 23-March-2007, regarding new EAS/Local Calling
between Decatur AL and Huntsville AL, effective for Monday
07-May-2007.

http://www.interconnection.bellsouth.com/alerts_and_notifications/carrier_notifi\
cations/assets/pdf/91087015.pdf

There is already existing EAS between Huntsville AL and other
ratecenters nearby to Huntsville, as well as between Decatur AL
and other ratecenters nearby to Decatur, but with one exception,
none of these will become EAS with the other, nor with other
ratecenters already EAS'd with the other "base" ratecenter.

The one exception being Madison AL, which already has EAS with
Huntsville AL close-by, and is "on the way" between Huntsville AL
and Decatur AL -- Madison will also now have new EAS/Local Calling
with Decatur AL.

This EAS in the Huntsville AL / Decatur AL region is in the 256 NPA
Code, and also in the Huntsville AL/etc. LATA #477.

The actual tariff pages for when these become effective can be
found at:
http://cpr.bellsouth.com/pdf/al/filings/pend/AL2007-008.pdf

Similarly, actual tariff pages for when the EAS in the Mobile AL/
Bay Minette AL area takes effect can be found at:
http://cpr.bellsouth.com/pdf/al/filings/pend/AL2007-009.pdf

And regarding some of the forthcoming EAS expansions in Louisiana
from at&t/BellSouth, the following pending tariff pages can be
found at:

http://cpr.bellsouth.com/pdf/la/filings/pend/LA2007-010.pdf
for the expanded "Northshore" Louisiana EAS -- i.e., the new EAS
between Washington Parish, Tangipahoa Parish, St.Tammany Parish

http://cpr.bellsouth.com/pdf/la/filings/pend/LA2007-016.pdf
for the expanded EAS in Iberville Parish in Louisiana.

I'm still waiting for further details on EAS in Shreveport LA/
northwestern LA, and any possible inter-LATA EAS between Florien LA
in the Shreveport/Alexandria/Monroe LA LATA and Leesville Vernon
Parish LA in the Lafayette/Lake Charles LA LATA.

There is also supposed to be some expanded EAS regarding the
Baton Rouge LA Metro area to the west, north, and east...
the expanded EAS w/r/t Iberville Parish is south of Baton Rouge.
SOME details on the expanded Baton Rouge LA Metro EAS forthcoming
can be found from the Baton Rouge Morning Advocate newspaper, at:
http://www.2theadvocate.com/news/6502922.html?showAll=y&c=y

And there's also some possible EAS expansion in Louisiana in
Terrebonne Parish, Assumption Parish, northern Lafourche Parish,
all three in the New Orleans LA Metro LATA #490 and NPA 985; and
also some forthcoming EAS expansion in St.James Parish in the
Baton Rouge LA Metro LATA #490, NPA 225. I'm still waiting for
some kind of documentation from the La.PSC, at&t/BellSouth, and/or
the local media -- radio/TV/newspapers/etc.

Further EAS regarding these and other at&t/BellSouth ratecenters,
as well as just about any ratecenter/EAS/Local Calling throughout
the US and Canada parts of the NANP can be found from Ray Chow's
"Local Calling Guide" website, http://www.localcallingguide.com/

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

I thought that there  was some number to dial that would tell you who
was providing local telephone service.  Does anyone know that number?
  Also, is there some number to dial that would tell you what the long
distance service provider is for a particular phone?

Thanks:

Jack

611 will usually give you a clue for local service.
For LD I have used (700) 555-4141


b

--- In local-calling-guide@yahoogroups.com, "Jack" <cyberfool@...> wrote:
>
> I thought that there  was some number to dial that would tell you who
> was providing local telephone service.  Does anyone know that number?
>  Also, is there some number to dial that would tell you what the long
> distance service provider is for a particular phone?
>
> Thanks:
>
> Jack
>

Jack <cyberfool at hotmail dot com> wrote:

> I thought that there  was some number to dial that would tell you
> who was providing local telephone service.  Does anyone know that
> number?

There is a reserved standard number for use in the US and Canada,
but I doubt that anyone has activated it.

It is supposed to be 1+ your own area code and then 555-0055.
Since it is possible that some/many/most telephone companies will
try to route this to directory assistance, a chargeable call, I
wouldn't attempt this number at this time, until there is more
publicity about its proper implementation.

611 for Repair is NOT universally implemented. In some cases, it
could route to the actual provider of dialtone, not really the
provider of "re-sold/billed local service". Similarly trying to dial
'0' for the operator might route to the operator of the actual
provider of the dialtone, and she/he might not really be able to tell
you who your local telco is if it is "re-sold" service.

You might attempt to try to get your local telephone service switched
over to something, for sake of arguement let's say "Economy Reconnect
Telco". They are really a RE-seller, who bills you for your service.
But they don't really provide your dialtone. They instead buy dialtone
from the larger incumbent, Bell or some independent, or maybe they
too buy dialtone from a large facilities-based CLEC such as Cox Cable,
Charter Cable, etc., i.e., a Cable-TV company that is now providing
local service.

Dialing '0' or '611' is more than likely going to route to the
operator that the facilities-based telco has, or uses, and that
operator may or may not know that you are really buying your service
from "Economy Reconnect Telco".

And if you call the business office of the incumbent telco and give
them your number, which might have actually been "their" number at
one time, since you now no longer have a direct account with them,
they probably can't help you, unless you are attempting to switch
"back" to them.

Whenever the telco industry figures out how to properly implement
1+ home area code+ 555-0055, as a FREE call, the intent is that it
will quote you the name of the telephone provider that you have the
account with, i.e., the telco who bills you, regardless of who the
actual provider of dialtone or operator service is.


> Also, is there some number to dial that would tell you what the long
> distance service provider is for a particular phone?

In Canada, 1-700-555-4141 is supposed to quote you the provider of
your chosen primary long distance provider.

In the US, there are two possible types of toll or long distance
providers you can have on your line, as to intra vs. inter LATA.
Canada doesn't have LATAs. The US has had LATAs ever since the
break-up of the Bell System in the mid-1980s.

Intra-LATA calls can be summarized as "short-haul" long-distance calls
while "long-haul" long-distance calls can be thought of a inter-LATA.

To find you who your primary/chosen provider for inter-LATA, long-
haul, long distance is, it is the same number indicated as used in
Canada for "all" Long Distance, 1-700-555-4141.

To find out who your primary/chosen provider for intra-LATA short-
haul, long distance is, you dial 1+ your own area code+ 700-4141.
There are a few exceptions to this -- if you are calling from within
the 847 area code in the northern Chicago suburbs, you are supposed
to dial 1+312-700-4141, since there was already a pre-assigned 847-700
code prior to the use of "own area code"+700-4141 for verifying your
intra-LATA toll provider.

If you are calling from within the 213 or 818 area code in the Los
Angeles area, you are supposed to dial 1+805-700-4141, since there
were already pre-assigned 213-700 and 818-700 codes prior to the
use of "own area code"+700-4141 for verifying your intra-LATA toll
provider.

Even with these "rules", there are still some exceptions. These might
not work from a cellphone. Choosing a main LD provider is mainly a
landline thing, not really something available for cellular phones
anymore. And even with competitive landline local telcos, use of these
codes/numbers isn't always guaranteed to work properly/consistantly.
Similarly, there are rural or independent telcos which might not have
properly impelemented 1-700-555-4141 for 1+home-area-code+700-4141
from their local switches!

And in some cases, if you have changed your LD provider to a company
which re-sells AT&T or such, dialing 1-700-555-4141 will give you the
valdiation recording from AT&T or the "big company" which is
actually providing the backbone service, not the validation
announcement of the company YOU have signed up with! You might find
out from small print, or from further inquiries with that re-seller
that they say for you to dial 1-700-555-and then some other last four
digits! Such as -4110 or -4112.

But in MOST cases, 1-700-555-4141 is for finding out who your chosen
LD provider is for inter-LATA toll calls if in the US, or who your
chosen LD provider is for toll calls if in Canada....
and if in the US, 1+your own area code+700-4141 works in MOST US
area codes for finding out who your chosen intra-LATA toll provider
actually is.

mjc

The Baton Rouge Morning Advocate newspaper has another news article
on expanded local calling for Baton Rouge and vicinity, for those
areas to the north, west, and east of Baton Rouge... as well as
expanded local calling for Iberville Parish just to the south of
Baton Rouge Metro.

"One local call to ring St. Gabriel, Plaquemine, White Castle",
dated yesterday, Tuesday 27-March-2007
see: http://www.2theadvocate.com/news/6719862.html

The article's headline/subject is referring to Iberville Parish,
but it then does go on to mention the expanded EAS forthcoming for
other parts of Baton Rouge Metro.

And then it continues, stating that there are other to be several
other local calling area expansions throughout the state,
to be announced later this year:

"AT&T is creating expanded local calling areas for 18 communities
around the state. Each of the five PSC regulators will have three
or four communities in their district that will be phased into
expanded local calling areas during 2007, Canale said. Changes to
Acadiana and north Louisiana phone exchanges are expected later
this year."

Canale refers to Debbie V. Canale mentioned earlier in the article,
a regulatory director for at&t/BellSouth for Louisiana. She is
most likely based at BellSouth's now at&t's Louisiana HQ, at their
"One Canal Place" office building at the foot of Canal Street in
downtown New Orleans.

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

The Baton Rouge Morning Advocate newspaper has another news article
on expanded local calling for Baton Rouge and vicinity, for those
areas to the north, west, and east of Baton Rouge... as well as
expanded local calling for Iberville Parish just to the south of
Baton Rouge Metro.

"One local call to ring St. Gabriel, Plaquemine, White Castle",
dated yesterday, Tuesday 27-March-2007
see: http://www.2theadvocate.com/news/6719862.html

The article's headline/subject is referring to Iberville Parish,
but it then does go on to mention the expanded EAS forthcoming for
other parts of Baton Rouge Metro.

And then it continues, stating that there are other to be several
other local calling area expansions throughout the state,
to be announced later this year:

"AT&T is creating expanded local calling areas for 18 communities
around the state. Each of the five PSC regulators will have three
or four communities in their district that will be phased into
expanded local calling areas during 2007, Canale said. Changes to
Acadiana and north Louisiana phone exchanges are expected later
this year."

Canale refers to Debbie V. Canale mentioned earlier in the article,
a regulatory director for at&t/BellSouth for Louisiana. She is
most likely based at BellSouth's now at&t's Louisiana HQ, at their
"One Canal Place" office building at the foot of Canal Street in
downtown New Orleans.

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

Yahoo Groups is having problems with duplicate/multiple copies
of posts being re-generated. This has been happening since
Wednesday night/Thursday morning with several Yahoo Groups that
I read, including Yahoo: Central Office, Yahoo: Strowger, and
Yahoo: Singing Wires.

It now seems to be happening with Yahoo: Local Calling Guide,
with my post regarding another article in the Baton Rouge Morning
Advocate newspaper regarding expanded local calling, being
duplicated. It might actually be multiplied numerous times, NOT
by me, but by Yahoo's servers....

Yahoo IS aware of the problem!

This banner started to display at the top of all of the "main"
webpages of all Yahoo Groups, sometime Wednesday night/Thursday
morning:

"We are aware that some groups are experiencing a duplicate
post problem and are working on a fix. Please refer to the
Yahoo! Groups Team Blog, http://blog.360.yahoo.com/y_groups_team
for the latest information on this issue."

mjc

As of March 23rd 2007 the new AT&T is now assigning att.net email
addresses rather than sbcglobal. Today I was finally able to select an
att.net email address. I had to disconnect my sbcglobal.net DSL for
five days and have it reconnected. This change also effects users with:
@snet.net, @ameritech.net, @pacbell.net, @nvbell.net, @swbell.net,
@prodigy.net, @flash.net, @wans.net...   When I attempted to register
is still populated the choice with an sbcglobal.net address but the
tier one person gave me an IP address ending with /register so it
forced the system to give me att.net choices.

Justin <jb_92104 at att dot net> wrote:

> As of March 23rd 2007 the new AT&T is now assigning att.net email
> addresses rather than sbcglobal. Today I was finally able to select
> an att.net email address. I had to disconnect my sbcglobal.net DSL
> for five days and have it reconnected. This change also effects
> users with:
>
> @snet.net, @ameritech.net, @pacbell.net, @nvbell.net, @swbell.net,
> @prodigy.net, @flash.net, @wans.net... When I attempted to register
> is still populated the choice with an sbcglobal.net address but the
> tier one person gave me an IP address ending with /register so it
> forced the system to give me att.net choices.


So, does this mean that legacy email addresses with older domains
such as swbell.net, sbcglobal.net, snet.net, ameritech.net,
pacbell.net, nvbell.net, etc. are going to "have" to be changed to
new att.net addresses? Will email sent to the old domain address
begin to "bounce"? If legacy uses of the old domains MUST be changed,
how long of a transition or "permissive/parallel dialing" is going to
be allowed?

I know that someone that I emailed, who works at Pac*Bell-then-SBC-
now "the new at&t" -- I emailed him in Fall 2005, before the AT&T/SBC
merger took effect officially, but only a month or two before.

I emailed him with an sbc.com address in Fall 2005.

I think I emailed him during 2006 with the sbc.com address domain.

But I recently emailed him, maybe in late February, and simply
copied/pasted his sbc.com address. It bounced! I re-sent the email
using the att.com domain, and it went through okay.

I wonder how long before bellsouth.net and bellsouth.com and also
cingular-based domains, will eventually "disappear", or else there
will be no "new" assignments for new customers/employees???

mjc

I got the following email from the "Yahoo Groups Alert" group service
indicating that Yahoo Groups seems to have fixed the problem of
multiple re-generated copies of individual postings. In another
similar notice from them, it also mentions that although they think
that they have fixed the problem, there might still be additional
duplicate/multiple copies of individual messages still being held in
"queue", and which might still be emailed out, due to the delay in
email distribution of posts, which is related to this erroneous
duplication/multiplication of single posts.

Anyhow, I hope that we won't see a rerun of anything like this in the
near future!

Here is the text of the email I got from Yahoo:


> We sincerely apologize for the mail delivery bug that caused many
> group members to receive multiple copies of group mail. This bug
> was introduced when we were working to increase mail delivery
> speed, one of our biggest user requests.
>
> We pushed a fix at midnight March 29 Pacific time, but unfortunately
> at that point a backlog of mail was still being delivered. We're
> confident that the bug is fixed on our end— however some ISPs may
> still be delivering backlogged mail to some users.  We're monitoring
> your comments and appreciate you letting us know your group's status
> on the Groups Team Blog: http://blog.360.yahoo.com/y_groups_team
>
> The Groups product team has also posted a response to user feedback
> regarding IFrames and group description in the latest blog entry.
>
> We appreciate your patience and again we're very sorry for the
> inconvenience.
>
> -- The Yahoo! Groups Team

--- In local-calling-guide@yahoogroups.com, "Mark J. Cuccia"
<markjcuccia@...> wrote:
>
> Justin <jb_92104 at att dot net> wrote:
>
> > As of March 23rd 2007 the new AT&T is now assigning att.net email
> > addresses rather than sbcglobal. Today I was finally able to
select
> > an att.net email address. I had to disconnect my sbcglobal.net DSL
> > for five days and have it reconnected. This change also effects
> > users with:
> >
> > @snet.net, @ameritech.net, @pacbell.net, @nvbell.net,
@swbell.net,
> > @prodigy.net, @flash.net, @wans.net... When I attempted to
register
> > is still populated the choice with an sbcglobal.net address but
the
> > tier one person gave me an IP address ending with /register so it
> > forced the system to give me att.net choices.
>
>
> So, does this mean that legacy email addresses with older domains
> such as swbell.net, sbcglobal.net, snet.net, ameritech.net,
> pacbell.net, nvbell.net, etc. are going to "have" to be changed to
> new att.net addresses? Will email sent to the old domain address
> begin to "bounce"? If legacy uses of the old domains MUST be
changed,
> how long of a transition or "permissive/parallel dialing" is going
to
> be allowed?
>
> I know that someone that I emailed, who works at Pac*Bell-then-SBC-
> now "the new at&t" -- I emailed him in Fall 2005, before the
AT&T/SBC
> merger took effect officially, but only a month or two before.
>
> I emailed him with an sbc.com address in Fall 2005.
>
> I think I emailed him during 2006 with the sbc.com address domain.
>
> But I recently emailed him, maybe in late February, and simply
> copied/pasted his sbc.com address. It bounced! I re-sent the email
> using the att.com domain, and it went through okay.
>
> I wonder how long before bellsouth.net and bellsouth.com and also
> cingular-based domains, will eventually "disappear", or else there
> will be no "new" assignments for new customers/employees???
>
> mjc
>

Everyone can keep their existing email addresses from whatever
provider they were on before it became att.net...    It is only the
new DSL accounts that are assigned att.net addresses. I wanted to get
rid of the sbcglobal.net email address so I had to disconnect my DSL
to reregister for att.net

The sbc.com addresses are (telco) company addresses and they became
att.com (telco) email addresses. Residential and business customers
cannot get the .com email addresses; they are assigned the att.net
addresses.

JB

Hello everyone,

I was wondering if anyone could tell me whether the
IMTC (International Mobil Termination Charge) rates
are pretty much standard or if they vary by vendor
(e.g. Verizon).

If standard, what would be the best source to get this
information?

Thanks in advance.

-Luis.



________________________________________________________________________________\
____
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos.
http://autos.yahoo.com/new_cars.html

The IMTS rates differ by vendor. They can be found in each carrier's Service
Guide.

   Ed


---------------------------------
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list.

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

Thank you, Ed.

-Luis.
--- Ed Sullivan <sully0673@...> wrote:

> The IMTS rates differ by vendor. They can be found
> in each carrier's Service Guide.
>
>   Ed
>
>
> ---------------------------------
> We won't tell. Get more on shows you hate to love
> (and love to hate): Yahoo! TV's Guilty Pleasures
> list.
>
> [Non-text portions of this message have been
> removed]
>
>




________________________________________________________________________________\
____
The fish are biting.
Get more visitors on your site using Yahoo! Search Marketing.
http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php