1. Forum
  2. Usenet
  3. COMP.DCOM.TELECOM

  • Configuring my VoIP box for 988 [telecom]

    From Steve Watt@21:1/5 to All on Thu Jul 21 22:42:00 2022
    Greetings all! Old reader of the Digest, but feeling pretty out of touch - haven't done telecom-related work in about 20 years.

    With the rollout of 988 supposedly fully live in NANPA, I've been poking
    around trying to figure out if I need to do anything to my home setup. I
    have a Poly (sigh) Obi200 using Google Voice (SP1) and PunchAlert (SP2 for E911).

    So is there something I need to do to make 988 work on my configuration? It seems likely, but in my digging, there doesn't seem to be quite the right combination of information to figure out *what* I need to do.

    Thanks all! Please cc: (after deobfuscating) on replies.

    --
    Steve Watt KD6GGD PP-ASEL-IA factories.words.yappy
    Don't let your schooling get in the way of your education
    --
    Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.5" / 37N 20' 15.3"
    Internet: steve @ Watt.COM Whois: SW32-ARIN
    Free time? There's no such thing. It just comes in varying prices...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From GlowingBlueMist@21:1/5 to Steve Watt on Sat Jul 23 01:57:56 2022
    On 7/21/2022 5:42 PM, Steve Watt wrote:
    Greetings all! Old reader of the Digest, but feeling pretty out of touch - haven't done telecom-related work in about 20 years.

    With the rollout of 988 supposedly fully live in NANPA, I've been poking around trying to figure out if I need to do anything to my home setup. I
    have a Poly (sigh) Obi200 using Google Voice (SP1) and PunchAlert (SP2 for E911).

    So is there something I need to do to make 988 work on my configuration? It seems likely, but in my digging, there doesn't seem to be quite the right combination of information to figure out *what* I need to do.

    Thanks all! Please cc: (after deobfuscating) on replies.

    You might want to post the question over on www.dslreports.com in the
    "VOIP Tech Chat" forum as they still have active members who configure
    and modify the firmware for the OBI/Poly series of VOIP devices. You
    can post anonymously or create an account and go on from there.


    ***************************** Moderator's Note *****************************

    A. Because it disrupts the intuitive top-to-bottom flow of a written conversation.

    Q. Why is top-posting a bad practice?

    Bill Horne
    Moderator

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Levine@21:1/5 to It appears that Steve Watt on Fri Jul 22 23:22:46 2022
    It appears that Steve Watt <telecom.removethis@steve.wattlink.net> said:
    have a Poly (sigh) Obi200 using Google Voice (SP1) and PunchAlert (SP2 for >E911).

    So is there something I need to do to make 988 work on my configuration? It >seems likely, but in my digging, there doesn't seem to be quite the right >combination of information to figure out *what* I need to do.

    When I look at the manual, starting around page 197 it describes the way you define the dial plan, which probably not by coincidence looks just like the
    way you define dial plans on a Cisco/Linksys adapter.

    Somewhere in the config the dial plan for each line is something like this:

    (1234;<+>567.;....;911S0)

    It's list of digit patterms separated by semicolons. You need to add
    988S0 to ths list, which means recognize 988 and put the call through immediately (zero second timeout). The patterns are evaluated in
    parallel so it doesn't matter where in the list it goes.

    This assumes that your carriers know what to do with 988. If not, thie
    should work, dialing the actual 800 number of the 988 provider
    instead:

    <988S0:180027388255>

    If your dial plan still lets you dial local calls with seven digits
    (mine does) you might want to undo that if you care about being abie
    to call 988-XXXX numbers in your area code.

    R's,
    John

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)