Correct.
The 9-prefixed 8 and 11 digit strings aren't valid anywhere in north
america so they are easily identified. I suppose you could also add a 9
prefixed 12 digit for people who dial 91NPANXXYYYY and 9011X. which is
also free of collisions.
I dont get any pushback on timeouts for 7D as most users are on a
deskphone with a dial button or a mobile app. Cell phones have trained
people to hit send.
-Ryan
On 7/19/2020 9:46 AM, Mike Johnston wrote:
On 2020-07-19 11:21, Ryan Delgrosso wrote:
if there is any pre-9 dialing going on, i just add a 8 digit and 11
digit check for leading 9s and drop them at ingress and then both use
cases are gracefully managed.
Sounds like a form of permissive dialing. Jam digits in, your
translations will sort it out. I like it!
So for example, if I dialed an 8-digit string starting with a 9, such
as...
9-555-2222
...it would strip the 9 and send it out as...
555-2222
...?
And if I dialed an 11-digit string starting with a 9, such as...
9-619-555-2222
...again, it would strip the 9 and send it out as...
619-555-2222
...?
Do you have issues with timeouts, though? Especially in the 7/8-digit
case? However, this new 988 order will require many areas to convert
to 10-digit dialing (including mine), which may make that irrelivent.
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
