Configuring the DigitMap
libertyspike138:
I had my OBi200 configured for Google Voice on SP1 & Anveo for E911 on SP2 for a long time but I had not realized that my Anveo account had run out of funds and my service was cancelled. Anveo used to charge something like $0.080 a month but now they want $25 a year so as a result I just signed up for GV911 at $12 a year. Here's my problem! Under Google Voice my DigitMap was set to this (!911|*xx|<+>1xxxxxxxxxx|<+1740>[2-9]xxxxxx|<+1>[2-9]xxxxxxxxx|<011:+>xx.|(Mipd)|[^*]@@.) which allowed me to make 7 digit phone calls without dialing "1 740" my local area code first. I followed GV911's directions and replaced my DigitMap on SP1 with (<911:14242798234>S0|<922:14242798235>S0|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.) to properly route the E911 calls but this took away the 7 digit calling. I'm not familiar with the formatting of how a DigitMap works so I need to know how to combine these without messing it up. Thanks!
drgeoff:
Insert
<1740>xxxxxxx
as explained near the bottom of page 198 of the Admin Guide, http://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf
Put it after the <922: .... block and with a | separator.
libertyspike138:
So you are stating that this is the proper order?
(<911:14242798234>S0|<922:14242798235>S0|<1740>xxxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
Thanks for all your help, drgeoff!
drgeoff:
Quote from: libertyspike138 on July 01, 2020, 09:11:42 am
So you are stating that this is the proper order?
(<911:14242798234>S0|<922:14242798235>S0|<1740>xxxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
Thanks for all your help, drgeoff!
Yes, though it is "a" not "the" proper order.
libertyspike138:
Is this the proper order? I had originally put it after the 922 section?
(<911:14242798234>S0|<922:14242798235>S0|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1740>xxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
Navigation
[0] Message Index
[#] Next page