Unable to perform echo test

[GoodBoy]

I've previously setup my Obitalk 110 w/ google voice before but my parents weren't ready to switch. They changed their mind recently and now want to make the switch to a google voice number so I figured I'd redo the setup to avoid any issues.

This time however, after 2 hardware resets, I'm unable to perform an echo test or dial out to add my device. I've used different Ethernet cables and ports but no success.

[MichiganTelephone]

Let me guess — you hooked it up for the first time in a while (after it being offline for more than a week or two), plugged it in, saw the red LED flashing, and pulled the power cord without realizing it was in the middle of a firmware update?

If that's the case, no one here can help you.  E-mail Obihai support (support@obihai.com) and give them the OBiTALK number off the bottom of your device and see what they say.

[Stewart]

Please report what you know about the present condition of your device.

State of indicator lights?

Have dial tone?  If so, what do you hear when attempting echo test?  Does ***1 report an IP address?  If so, can you ping the device at that address?  Access its web page at that address?  If so, what does the System Status page show?

[GoodBoy]

I'm able to access the obitalks IP address but not by using ***1 ( I found the IP address through my router). Anytime  I dial anything out, the echo test # or the # given when adding the device, I get a busy signal. I hear a dial tone but that's about as good as it gets. I'm able to ping it as well.

C:\Users\GoodBoy>ping http://192.168.1.117/
Ping request could not find host http://192.168.1.117/. Please check the name an
d try again.

C:\Users\GoodBoy>ping 192.168.1.117

Pinging 192.168.1.117 with 32 bytes of data:
Reply from 192.168.1.117: bytes=32 time=2ms TTL=80
Reply from 192.168.1.117: bytes=32 time=1ms TTL=80
Reply from 192.168.1.117: bytes=32 time=1ms TTL=80
Reply from 192.168.1.117: bytes=32 time=1ms TTL=80

Ping statistics for 192.168.1.117:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

[Stewart]

ping http... is not valid syntax for Windows.  What error do you get when you type 192.168.1.117 into a web browser?

I suspect that there is a problem communicating with your phone.  Try a different make/model, preferably a line-powered corded one, connected directly to the OBi Phone port (no house wiring).

What exactly to you hear when you dial ***1?  Does the dialtone stop when you press the first *?  Does the device play anything immediately after pressing the 1?  Or, after several seconds delay?

What happens when you dial **0?

[GoodBoy]

Typing in 192.168.1.117 in the web browser takes me to the devices internal settings page(Setup wizard, system status, etc).

When the first * there is still a dial tone. As soon as I type the second * is when the dial tone stops. Finally pressing 1 I immediately get a busy signal.


**0 yields the same results except it takes a second or two to get the busy signal.

If I had another phone in the house I'd try it. The phone I'm currently using is the same one I was using when I had the obitalk working.

[Stewart]

I suspect that you suffered a firmware "upgrade" and the new code is somehow incompatible with your present phone and OBi settings.

Someone else had this problem, but we never found out the cause.  http://www.obitalk.com/forum/index.php?topic=2222.0 .  Your phone make/model?

As a guess, try setting in Physical Interfaces -> Phone Port -> Port Settings, DTMFRxMode to software.

If you were configuring your device through the OBiTalk portal (you may need to double-press buttons, as described in above thread, to get it set up again), try that.

Or, to manage the OBi manually (via its web interface), you must set (in System Management -> Auto Provisioning) both ITSP Provisioning -> Method and OBiTalk Provisioning -> Method to disabled.

Or, perhaps your phone has a setting that will help, e.g. DTMF tone duration.

[GoodBoy]

Thanks! I'm not sure if it was switching the obi from hardware to software or some tone setting on the phone but it's working again. Thank you.