In article <telecom24.3.6@telecom-digest.org>, Fred Atkinson
<fatkinson@mishmash.com> wrote:
> My father lives in Chapin, South Carolina. I recently got his
> telephone service switched over to Vonage. As Vonage does not have
> an exchange in Chapin (and since all Chapin exchanges are local to
> the Columbia, SC area), we got a Columbia, SC number for him to use.
> Last week, his next door neighbors complained that when they dialed
> his number they got a recording telling them to dial 'one plus the
> area code and the number'. I used their telephone to dial his number
> as seven digits and got the same thing. Vonage's exchange in the
> Columbia area is 233. The neighbors had a number in the 945
> exchange.
> I called Vonage. Turns out that this 945 number is not a Chapin
> number but something else entirely. I'm trying to figure out why
> this retired couple has a number that apparently isn't local to the
> Columbia calling area.
If Vonage told you that 803-945 is not a Chapin, SC, exchange, then
Vonage lied to you.
The 803-945 exchange defaults to BellSouth, and is listed as
CHPNLTLMTN (Chapin/Little Mountain, I would assume), the exact same
rate center as 803-345 and 803-932 (BellSouth), and 803-457, 803-941,
and 803-948 (CLECs).
The 803-233 exchange is indeed rated as Columbia.
If Columbia and Chapin are supposed to be local calls, then the
BellSouth switch CHAPSCCLRS1 needs to be updated to reflect the 803-233
exchange as local.
See what happens from the neighbors phone if you try to dial a number
in the: 210, 212, 213, 214, 216, 231, 251, 252, 253, 254, 255, 256,
264, 296, 312, 333, 343, 344, 354, 373, 376, 382, 400, 401, 407, 419,
434, 462, 540, 544, 545, 551, 561, 576, 612, 647, 691, 695, 699, 714,
731, 732, 733, 734, 735, 736, 737, 738, 739, 741, 742, 743, 748, 749,
750, 754, 755, 758, 763, 765, 771, 772, 776, 777, 779, 781, 782, 783,
786, 787, 788, 790, 791, 794, 796, 798, 799, 806, 822, 865, 896, 898,
926, 929, 931, 933, 935, 936, 939, 955, 975, or 988 prefix (all
belonging to BellSouth), or to the 234 or 381 prefixes (others
belonging to the same CLEC as 803-233). (Obviously, you don't need to
try every single prefix on that list. Any one or two known valid
numbers from among those prefixes will suffice.)
If your neighbors can call the BellSouth prefixes in Columbia as listed
above, and especially if they can call the other two CLEC prefixes, 234
and 381, then they should be able to dial 803-233 as a local 7D call,
and the problem is entirely with BellSouth. The neighbors should call
the repair service (or better yet, you should call repair service from
the neighbors' phone) and report a problem with the translation tables
in CHAPSCCLRS1.
On the other hand, if the neighbors get the "dial 1+" recording when
calling the BellSouth prefixes in Columbia, then obviously they are on
a calling plan that doesn't rate Columbia as local.
If the neighbors can call BellSouth exchanges in Columbia, but not the
Vonage exchanges in Columbia -- or also try CLECs like ITC DeltaCom,
Alltel, or AT&T -- then you should file a complaint against BellSouth
with whatever South Carolina calls its public utilities commission,
because BellSouth has some 'splainin to do.
Exciting details of the prefixes in the 803 area code can be found on
the NANPA web site:
<http://www.nanpa.com/nas/public/assigned_code_query_step1.do?method=res
etCodeQueryModel>
select South Carolina, wait for the NPA menu to slim down, then select
803. (Or select any other state and NPA you want to check on.)
Linc Madison * San Francisco, California * lincmad@suespammers.org
<http://www.LincMad.com> * primary e-mail: Telecom at LincMad dot com
All U.S. and California anti-spam laws apply, incl. CA BPC 17538.45(c)
This text constitutes actual notice as required in BPC 17538.45(f)(3).
DO NOT SEND UNSOLICITED E-MAIL TO THIS ADDRESS. You have been warned.
Linc Madison (lincmad@suespammers.org)