[SOLVED] Can't Call OBiTALK Test Number

<< < (3/4) > >>

Stewart:
While I don't see anything obviously wrong with the OutboundCallRoute, it appears that you have changed it (for 911) in the portal and still have updates from the portal enabled, which are overwriting your changes.

If you want to configure the OBi manually (from its web interface), you must set the method (in System Management->Auto Provisioning) for both ITSP Provisioning and OBiTalk Provisioning to Disabled. Save and reboot. Then, you should be able to change OutboundCallRoute as desired.

However, whatever you do, be sure that you end up with a configuration that works properly for 911. If at all uncertain, after calling your police non-emergency number and asking permission, make a test call to 911. Immediately tell them that you do not have an emergency and are just testing. Don't hang up until they have confirmed that, or you'll get a visit from the cops. During your test call, confirm that you have reached the proper PSAP and they show your correct physical address.

Edit: I just noticed that you are directing 911 to SP1, but you also state that you have Google Voice for SP1. GV does not offer 911 service! If you have another provider that does offer 911, you should be sending emergency calls there.

longcliff:
Quote from: Stewart on October 23, 2011, 05:01:39 am

While I don't see anything obviously wrong with the OutboundCallRoute, it appears that you have changed it (for 911) in the portal and still have updates from the portal enabled, which are overwriting your changes.

If you want to configure the OBi manually (from its web interface), you must set the method (in System Management->Auto Provisioning) for both ITSP Provisioning and OBiTalk Provisioning to Disabled. Save and reboot. Then, you should be able to change OutboundCallRoute as desired.

However, whatever you do, be sure that you end up with a configuration that works properly for 911. If at all uncertain, after calling your police non-emergency number and asking permission, make a test call to 911. Immediately tell them that you do not have an emergency and are just testing. Don't hang up until they have confirmed that, or you'll get a visit from the cops. During your test call, confirm that you have reached the proper PSAP and they show your correct physical address.

Edit: I just noticed that you are directing 911 to SP1, but you also state that you have Google Voice for SP1. GV does not offer 911 service! If you have another provider that does offer 911, you should be sending emergency calls there.

I have a cell phone for 911, so I was not trying to direct 911 to Google Voice (SP1).

Do you know where I might have told the OBi to direct 911 to SP1? When I use OBiTALK Dashboard to configure my Google Voice Account (SP1), under the entry for 'Use this service for emergency 911 calls' it simply has a circle with a line through it and a note saying that google voice is not capable of placing or receiving emergency calls. There is no way to select (or de-select) the 911 option for google voice.

longcliff:
Ok, I think I understand how provisioning works now. Rather than disable auto provisioning, I went into the OBiTALK Dashboard 'OBi Expert Configuration' and set Physical Interfaces -> Phone -> OutBoundCallRoute to 'Device Default' Then when the OBi device 'auto provisions' at startup, it takes the settings from expert configuration and applies them to the OBi device (which is why my previous changes from the web interface were being overwritten.)

To confirm this, I logged onto the OBi from the web interface, and sure enough, the OutBoundCallRoute is now at the default selection.

Also, I can make calls through google voice (sp1) and also call the OBiTALK test number **9 222 222 222.

Thanks for all the help!

I still wish I knew why my OutBoundCallRoute had been changed from default in the first place.

Stewart:
Quote from: longcliff on October 23, 2011, 06:57:29 am

I still wish I knew why my OutBoundCallRoute had been changed from default in the first place.
Sorry, that's well beyond my knowledge of the OBi system. Perhaps RonR or Obi support knows what may have happened.

RonR:
Quote from: longcliff on October 23, 2011, 03:58:39 am

Under Physical Interfaces -> PHONE Port -> Outbound Call Route, I did not have the default setting. This is what I have:

{911:sp1},{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

The OutboundCallRoute should be:

{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

As can clearly be seen, there is a nasty bug in OBiTALK Web Protal and/or OBi firmware that's resulting in a highly corrupted OutboundCallRoute containing HTML escape sequences (</>) when Auto Provisioning is used to configure this setting. This leaves all **1/**2/**8/**9 prefixes unusable.

Navigation

[0] Message Index

[#] Next page

[*] Previous page