Anveo

Started by ceg3, February 21, 2013, 06:28:16 AM

Previous topic - Next topic

ceg3

Just a quick word of praise for E911 from Anveo.  I had not seen the link in my dashboard until I read about it in the forum, but as a Google Voice user I had been wanting some form of 911.  Click on the link, fill in few blanks, log into PayPal, and immediately my OBI updated itself and it was done.  Could not have been easier for 12.00 a year.  Called 911 this morning to double check and I'm covered. Word of warning. Note that you only get 5 911 calls for the 12.00.  Certainly, I hope I don't need to call them even once. ;D

Shale

Anveo also has 933 as a test for 911. It is automated. It reads back to you the address that it has in its database, and it records you speaking, and then it plays back your speech to be sure that audio goes both ways successfully.

The ObiTalk Anveo configuration knows about this, and will configure 933 to route the same as 911.

dhfobi

I use Anveo E911 on my OBi100 but it doesn't respond to 933, what is the proper config to obtain this feature?

Shale

#3
Quote from: dhfobi on March 25, 2013, 06:48:57 AM
I use Anveo E911 on my OBi100 but it doesn't respond to 933, what is the proper config to obtain this feature?

If you had set up Anveo using ObiTalk recently, it should have been done for you during the process. If you don't want to re-setup, then edit all of the strings that reference 911 to add a similar part with 933.

Here is my OBi202 (two phone ports) Phone 1  OutboundCallRoute:
{911:sp2},{933:sp2},{([1-9]x?*(Mpli)):pp},{(<#:>):ph2},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}

So if you had, as part of your OutboundCallRoute,  {911:sp2},, you would change that portion to {911:sp2},{933:sp2},

dhfobi

Thanks, works perfectly now.

wilberfan

Quote from: ceg3 on February 21, 2013, 06:28:16 AM
Note that you only get 5 911 calls for the 12.00.  Certainly, I hope I don't need to call them even once. ;D

I wish this call limit had been discussed on the OBitalk reference page BEFORE I signed up for the service with Anveo. 

The setup was completely painless, and my '933' test call worked fine, first try....but it would have been nice to know about it BEFORE I signed up, and not AFTER.

Koby

Quote from: Shale on March 13, 2013, 11:16:56 PMThe ObiTalk Anveo configuration knows about this, and will configure 933 to route the same as 911.

That could be an issue if you have 7 digit dialing enabled and try to call a number in the 933 exchange, which is actually in use in many area codes.  I hope there is at least a timeout on 933, where it waits to see if you're going to dial more digits.

Shale

Quote from: Koby on May 14, 2013, 06:52:45 AM
Quote from: Shale on March 13, 2013, 11:16:56 PMThe ObiTalk Anveo configuration knows about this, and will configure 933 to route the same as 911.

That could be an issue if you have 7 digit dialing enabled and try to call a number in the 933 exchange, which is actually in use in many area codes.  I hope there is at least a timeout on 933, where it waits to see if you're going to dial more digits.

That's a very good point. I do not have 7 digit dialing enabled, so I don't know how that would have affected the setup by OBiTalk.
My phone 1 OutboundCallRoute starts this way:
{911:sp3},{933:sp3},{([1-9]x?*(Mpli)):pp},{(<#:>):ph2},
Maybe for 7-digit dialing it could be
{911:sp3},{933S9:sp3},{([1-9]x?*(Mpli)):pp},{(<#:>):ph2},
so that you could press 933# to test in a hurry.



Koby

Shale, if I am not mistaken, on Obihai devices timeouts go in the DigitMap, not the OutboundCallRoute.  So in DigitMap, do you see an entry such as |933S9| ?  If not, there should be such an entry.  Then as you say, you could use 933# when making a test call.