Need Help with Obi200 DigitMap Setup
n4mwd:
Thanks again for getting back to me.
I forgot to mention that the ObiBT interface works ok when I dial the **8 prefix. That is with or without a network connection. The only glitch is that the remote phone starts ringing about 15 seconds before I hear the three beeps and a ring signal on the Obi phone.
I checked X_NoRegNoCall and it did not activate the automatic failover when I unplugged the network cable. I still get a SIT tone followed by a voice message - something like "Network Failure - IP address - code 000".
The changes in regards to the phantom delays were only partially successful. I changed the NANPA string to include the exclusionary rule "![2-9]11 [2-9]xx xxxx". The idea was that the obi was getting hung up in the "<1>[2-9]xx [2-9]xx xxxx" rule waiting for other digits after 911. The result of this change only succeeded in making 911 calls go through without the delay. 411 calls, even with the s0, still have a delay. 800 numbers, with or without the 1, also still have the delay. However, 10 and 11 digit NANPA numbers are processed immediately. 7 digit local numbers also still have the delay, but I doubt anything can be done to fix them.
Since this Obi is going to be used by elderly people who can't dial at normal speeds, the 2 second short interdigit delay will likely be lengthened to something like 15 seconds. So shortening it is not an option. However, its working sufficiently well since toll free and 3 digit numbers are rarely dialed.
n4mwd:
UPDATE: Regarding the claim to be able to use the ObiBT as a failover, it seems that I may have been persuing an untamed ornithoid. I just found this thread...
https://www.obitalk.com/forum/index.php?topic=3985.10;wap2
Excerpt:
Quote
mrjoe:
I can confirm that the Obi202 cannot work with a Trunk group for Failover the way the Obi110+Xlink does.
This is because the ObiBT cannot work in a Trunk Group.
So now I am starting to lose hope for the Obi ata since 911 failover is mandatory for my situation. I wish I had found that thread before I invested all this time and money on this thing.
azrobert:
I just tried a call with BT via a trunk group on my OBi200 and it worked.
I didn't test it with failover, but it should work.
I just placed bt first in the trunk list.
Make sure you are at the current firmware level (4738).
n4mwd:
I got another sit message "There is no service to connect your call".
HardwareVersion 1.4 help
SoftwareVersion 3.0.1 (Build: 4420)
I think you mean the build number. I'll see if I can download the latest version somewhere and get it installed.
UPDATE:
I now have...
HardwareVersion 1.4
SoftwareVersion 3.0.1.4738
By putting only bt1 in the group, the calls will go out the cell phone. However, I unplugged the network cable and it still gives a SIT error "Network status: IP address failure".
I'm going to try unplugging the cable modem and leave the obi plugged in and see if that makes a difference.
n4mwd:
It seems to be working better now. I unplugged the cable modem and caused a network failure upstream from the router. When I did that, the bluetooth failover seems to work - albeit buggy. The first call was my fault because I called my own phone and the voip phone system needs a network connection to work. However, callcentric routed the call to my other cell phone.
One thing I noticed is that obi cell phone doesn't disconnect right away. In fact, on the second attempt, I dialed a local time service number that went through ok, but when I hung up the obi phone, I kept hearing the guy talk. Turns out, it was coming from the obi cell phone. Looks like the obi is disconnecting the audio and not the call when I hang up and the obi cell phone kept the call going.
So anyway, thanks for the help. The firmware is clearly buggy. Pulling the network cable from the obi should still work for services that don't need a network connection such as obiBT and obiLINE. As such, the Bluetooth failover should also still work.
Navigation
[0] Message Index
[*] Previous page