[VoiceOps] [External] Re: [External] Re: 9-8-8 dialing when an outside line access code (9) is being used

[Jay Hennigan]

On 7/17/22 23:43, Hunter Fuller wrote:
> On Mon, Jul 18, 2022 at 1:19 AM Jay Hennigan <jay at west.net> wrote:
>> Kinda, sorta. 7-digit local dialing is supposed to have been phased out,
>> with all NANP numbers represented as 1+NPA-NXX-XXXX.
> 
> But, speaking of en-banc dialing on cell phones, do you find that
> users typically enter the 1? I certainly don't. 10-digit is the most
> common form I see.

Cell phones seem to be very forgiving.

NPA-NXX-XXXX
1-NPA-NXX-XXXX
011-1-NPA-NXX-XXXX

all work. Out of habit, I generally dial the 1.

> We don't support 7 digit (we killed it at the same time Ma Bell did in
> our area).

I think this is pretty much the case for most of the NANPA region, but 
it's handy if you aren't in an overlay area.

>> This means that after your trunk access 9, you should expect a 1
>> (followed by ten digits for a regular phone number), a 0 for operator or
>> 011 international, or a three-digit code starting with 2 or 9 that until
>> this week always ended in 11.
>>
>> Program 88 as a sequence to re-insert the stripped 9 and send
>> immediately on trunks accessed by a 9, just like you do with 11.
> 
> The problem is, right now, you are right. If someone dials 9 then 8,
> they get fast busy immediately (because there should have been a 1).
> But after the change you mention, if they are trying to dial the very
> common toll-free NPA 888 and forget the 1, they will instantly be
> talking to the suicide hotline.

But if they can't dial 9-8[anything] now and never have been able to, 
they aren't likely to start doing so trying to reach toll-free 9-888 in 
the future.

And by failing after 9 then 8, you're breaking Dig Alert. Likewise 
you're probably breaking the other N-1-1 codes as well such as 7-1-1 for 
TDD, etc.

-- 
Jay Hennigan - jay at west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV