e911, VoIP.ms SP1 Google Voice SP2

[ckck]

I haven't found the solution to this. All the scenarios I've turned up are just a little different.

Here's the setup on my Obi100

SP1: VoIP.ms
Use This Service for Emergency 911 Calls
not primary line for outgoing calls

SP2: Google Voice
not used for 911
primary line for outgoing calls

When I dial 1-555-555-0911 I get a "we could not complete your call" message.

If I dial **1 1-555-555-0911 then it replies with my correct caller ID.

I've had the Obi, with VoIP.ms and Google Voice for several years, but only today did I set up e911. I'm hesitant to swap SP1 and SP2 because I've changed various settings over the years to block SIP scanners.

Scenario #2 from this obihai blog post implies that I can do this, though they have google voice on SP1, and Call Centric on SP2.

I still want to keep all outgoing calls on my Google Voice number, and have only 911 calls go out on my VoIP.ms number.

Any advice?

[ckck]

Replying to my own post to keep the thread alive as I still haven't found a solution.

I found jimates' e911 guide.

In the Configuration for the Obi100 section, I find what looks like a solution:

Setup Wizard > Outbound Settings > Phone OutboundCallRoute

911 and 933 were already prepended to the front of my OutboundCallRoute.

Code Select Expand

{911:sp1},{933:sp1},...
Maybe I did this wayback and didn't document it.

For testing, I prepended

Code Select Expand

{15555550911:sp1}
then submitted and rebooted.

When the Obi100 comes back up, my addition of 1-555-555-0911 to OutboundCallRoute is gone.

So, I still need to dial **1, then 1-555-555-0911 to test that everything is working. Because of this, I can't really trust that 911 will work.

If I dial 933 or **1 933 I get this automated reply:

The number you dialed    933   was rejected by the service provider. Reason is 4 8 4

The auto message might say 4 8 4 or 4 H 4, not sure.

[Taoman]

Are you using OBi Expert Configuration on the Obitalk web portal to make your edits?

Physical Interfaces>Phone 1>OutboundCallRoute

{911:sp1} should be at the beginning of your OutboundCallRoute. (which it apparently is??)

No point in including {933:sp1} as VoIP.ms doesn't support that number for testing 911.

To test that your Caller ID is working properly, you can Dial 1-555-555-0911 from VoIP.ms Network. The system will playback your Caller ID, then make a short pause, and play the test result. To make sure your device/switch is correctly configured for e911, you must ensure that your Caller ID number matches exactly the DID number that is activated for 911. That is the only way to identify you correctly. Otherwise your 911 call will not go through. Correctly formatted Caller ID consist of a 10 digits number, identical to your DID. For example, if your DID is 555.555.1234, your Caller ID number should be 5555551234.

So, I still need to dial **1, then 1-555-555-0911 to test that everything is working. Because of this, I can't really trust that 911 will work.

This is because your PrimaryLine is set to SP2 so that is what is supposed to happen.

Change {933:sp1} to {5555550911:sp1} so you can test E911.

[ckck]

I have it working now. @Taoman, thanks for the response, was very helpful!

I was using the web portal (192.168.1.xxx), but just checked out the online expert configuration page. I hadn't used the expert config page before. I think this exposed the problem.

On the Expert Configuration page,

Physical Interfaces>Phone 1>OutboundCallRoute

is

{911:sp1},{933:sp1},{([1-9]x?*(Mpli)):pp}, ...

So, when I tried to make a change on the Web Portal via

Setup Wizard > Outbound Settings > Phone OutboundCallRoute

it would revert back to the Web Portal's settings.

The reason? I found the VoIP.ms wiki page on setting up the Obi100, specifically the section on Disabling auto-provisioning. I think that before I did this, the Expert Configuration overrides by my Web Portal settings. As well, now in my Expert Configuration, there's a ! beside the OutboundCallRoute value, maybe showing that my Web Portal settings are now overriding the Expert Configuration settings.

However, now my Obitalk dashboard reports that SP1 VoIP.ms is offline, though it is still working fine.

Does this make sense?

No point in including {933:sp1} as VoIP.ms doesn't support that number for testing 911.

I didn't know this. I looked around but didn't find anything explicitly explaining this.

This is because your PrimaryLine is set to SP2 so that is what is supposed to happen.

Change {933:sp1} to {5555550911:sp1} so you can test E911.

Did it, and it works now. I guess I should have been clearer in my original post. I knew it was doing exactly what I was asking since SP2 is my primary line. I just didn't know how to change my config to make certain calls (i.e. 911, 1-555-555-0911) always go out on SP1.


I haven't dialed 911 to test .. don't want to risk the consequences since I can't find anything in my area about rules related to testing. Since 1-555-555-0911 works I'm going to assume that 911 will work too.

Thanks for the the help.

ck