911 question
M1024:
I use GV as my primary in/out service with an Obi202.
I would like to add 911 support, and I am considering two options
1. The Anveo 911 service.
Pro - my address on file for PSAP to see
Pro - number PSAP can call back at
Con - doesn't work AT ALL if Internet is down
Recurring Cost $15/mo
2. Obtain an ObiBT adapter, pair with an old cellphone which I leave plugged into charger and in a location it can receive GPS signal
Pro - Works regardless of Internet (I have battery backup on everything)
Con - no address on file for PSAP
Con - no callback number for PSAP
One-time cost: (cost of ObiBT)
Recurring cost: none
.. It occurs to me, that what I'd REALLY like to do, is setup both, and I'd like to setup the 202 so that, if 911 is called:
- if the Internet is up and the Anveo service is reachable, use that
- if the Internet is DOWN and/or Anveo is unreachable, failover to the cell via the ObiBT.
Does the 202 support this? How would I set this up?
OzarkEdge:
1. $15/month for 911 seems high. I believe I pay $0.89/month for a DID and $1.50/month for e911 with VoIP.ms.
2. No address!?, no call back?, Bluetooth!?... seems marginal for 911, imo.
My OBi202 dial plan in my notes uses trunk groups for failover. If a trunk is down, OBi routes to the next available trunk in the group. I would simply add trunk digit map (Mbtn) and trunk btn to trunk group digit map (Mtgn) and trunk group TGn respectively. Then confirm it works.
OE
M1024:
Actually, Anveo is $15/year. I entered that wrong.
And yes, as long as the net is up that service is better. But having *some* backup (cell with GPS) is better than nothing.
And do you know if there is a guide somewhere to setting up the failover mechanism you describe?
Quote from: OzarkEdge on August 29, 2015, 07:10:02 am
1. $15/month for 911 seems high. I believe I pay $0.89/month for a DID and $1.50/month for e911 with VoIP.ms.
2. No address!?, no call back?, Bluetooth!?... seems marginal for 911, imo.
My OBi202 dial plan in my notes uses trunk groups for failover. If a trunk is down, OBi routes to the next available trunk in the group. I would simply add trunk digit map (Mbtn) and trunk btn to trunk group digit map (Mtgn) and trunk group TGn respectively. Then confirm it works.
OE
OzarkEdge:
There is an admin guide (linked in my notes) that helps to understand what the OBi can do, but it does not walk you through it. You must study it, learn, and then devise your own solution. And there are forum and blog posts that offer some help. I studied these, discovered how the OBi can be used, and then put together the most elegant dial plan I could. My notes capture what I learned and how I applied this, but they are not a tutorial (there is also a linked dial plan tutorial but I never read it... it came out too late). If you are clever, you can study my dial plan, understand it, and copy/adopt it for your needs. Most of the heavy lifting behind it has been done already.
You can also use Anveo as failover for GV.
For example, your PHONE1 Port Primary Line would be Trunk Group 1:
TG1 Trunk Group1 = sp4,sp1,pp1,bt1
TG1 (Mtg1) = ((Msp4)|(Msp1)|(Mpp1)|(Mbt1))
Where sp1 is Anveo, sp4 is GV, pp1 is OBiTALK, and bt1 is Bluetooth cell phone. All calls go out GV, except 911 and OBiTALK. 911 goes out Anveo. OBiTALK goes out OBiTALK. If GV is down, calls will failover to Anveo. If Anveo is down, 911 will failover to Bluetooth. I prefer to relegate GV to sp4; you can keep it on sp1.
It all starts with knowing/defining your outbound dialing requirements and mapping the respective digit map for each trunk (Msp1), (Msp4), (Mpp1), and (Mbt1). The rest can be configured easily enough, given a working example.
The shortcut approach tends to misplace dial plan elements in the 'wrong' digit map or call route and/or cram everything into the PHONE Port digit map(s) which otherwise do not need to be changed once configured for 'their' outbound dialing requirements.
OE
M1024:
I see. Thank you very much. I will look into this further once I've obtained an ObiBT to test it with.
It seems like it would be a useful function for ObiHai to add as an "automatic configure" in their UI, where if multiple service providers are marked as supporting 911 service, they could be marked as such, each with a "preference" and then the device would automatically use the highest preferred available service.
Quote from: OzarkEdge on August 29, 2015, 08:24:26 am
There is an admin guide (linked in my notes) that helps to understand what the OBi can do, but it does not walk you through it. You must study it, learn, and then devise your own solution. And there are forum and blog posts that offer some help. I studied these, discovered how the OBi can be used, and then put together the most elegant dial plan I could. My notes capture what I learned and how I applied this, but they are not a tutorial (there is also a linked dial plan tutorial but I never read it... it came out too late). If you are clever, you can study my dial plan, understand it, and copy/adopt it for your needs. Most of the heavy lifting behind it has been done already.
You can also use Anveo as failover for GV.
For example, your PHONE1 Port Primary Line would be Trunk Group 1:
TG1 Trunk Group1 = sp4,sp1,pp1,bt1
TG1 (Mtg1) = ((Msp4)|(Msp1)|(Mpp1)|(Mbt1))
Where sp1 is Anveo, sp4 is GV, pp1 is OBiTALK, and bt1 is Bluetooth cell phone. All calls go out GV, except 911 and OBiTALK. 911 goes out Anveo. OBiTALK goes out OBiTALK. If GV is down, calls will failover to Anveo. If Anveo is down, 911 will failover to Bluetooth. I prefer to relegate GV to sp4; you can keep it on sp1.
It all starts with knowing/defining your outbound dialing requirements and mapping the respective digit map for each trunk (Msp1), (Msp4), (Mpp1), and (Mbt1). The rest can be configured easily enough, given a working example.
OE
Navigation
[0] Message Index
[#] Next page