[VoiceOps] [External] Re: [External] Re: 9-8-8 dialing when an outside line access code (9) is being used
hf0002+nanog at uah.edu
Mon Jul 18 02:43:29 EDT 2022
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.
We don't support 7 digit (we killed it at the same time Ma Bell did in
> 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.
More information about the VoiceOps