Obi Test Call Not Working

[pitcritter]

I've been using my 100 and 110 for quite a while now.

Today, I'm trying to setup a 200 for a friend.  I'm having some strange issues.  I have plugged in the ethernet cable to my router and the phone line to my cordless base and then plugged in the 200's power.  The unit comes up normally with three green LEDs (the network one flickering slightly).  So far, normal.

I follow the directions and try to make a test call to **9 222 222 222.  I get the three rising tones and a message telling me, "The number you dialed was rejected by the service provider. Reason 404."

I try to add the 200 to a new ObiTALK account and get the normal voice prompt in the handset, but the system times out trying to connect.

I check my router config...normal.

I unplug the 100 from  the same router (conflict?)...no difference

I place the IP of the 200 in  the DMZ (always been unnecessary for the 100, but worth a shot)...no difference.

I login to the local webpage using the ip and admin/admin.  Everything shows normal under the status page and Normal (User Mode) (7);ex-addr=74.116.***.***:10000(10000) under oBiTalk Service Status.

I update the firmware manually...no difference.

I'm beginning to think that I have a factory defective unit, but I haven't given up yet.

I unplug the 200 and plug back in my 100.  I try the test call again on my known working 100 and get the identical message.

I plug the 200 back in and attach the phone line to it. Unfortunately, I have only one handset available currently.

I try an ObiTalk call from the 200 to the 100.  I hear ringing, but there's no handset attached to the 100 so I can't be 100% sure.  The web portal page for my 100 shows 1 active call, so I assume it's working.

I manually configure a GV account on SP1 of the new 200.

It works!

I'm at a loss.  It seems that Obi's servers may be having some issues.

Since my friend is not terribly VOIP aware, I'd like to add this device to the web portal so that I can remotely administer it.

Does anyone have any suggestions? Can anyone confirm issues at Obi's end?

[ianobi]

**9222222222 is not working for me either just now. I can call from one OBi device to another using the OBiTALK network.

Your first problem with not being able to add the OBi200 may have been caused by port 10000 needing to be forwarded in your router. This may work now that have you put the OBi200's ip in DMZ. However, if there is a problem with the Obihai servers, then you may have to wait for that to be sorted before you can add the device.

Looks like all is working except for the OBi test number and maybe the "add a device" function.

[pitcritter]

Thanks. Good to know that the test call isn't my issue.

I'll wait to see if the test call capability comes back and then see if I can add the 200 to the web interface.

[azrobert]

I try an ObiTalk call from the 200 to the 100.  I hear ringing, but there's no handset attached to the 100 so I can't be 100% sure.  The web portal page for my 100 shows 1 active call, so I assume it's working.

FYI, when an OBi is ringing the Phone Port LED will flash.

[pitcritter]

Thanks. I noticed that today. Good point to remember for similar situations.

[chovongai]

Got an Obi200 today. Hooked it up; Set up an ObiTalk account to work with GV.
Device added and GV status Connected.
But cannot make test call **9 222 222 222; got the same 404 error.
What do to now other than waiting for Obihai to sort things out?
Is my Obi200 working OK?
TIA.

[pitcritter]

Chances are it's working fine.  Check your PM.  I've sent you my Obi number.  If it's working OK, you'll be able to make the call

[pitcritter]

I just re-read your post. If you've got a GV account showing "Connected" then you should be up and running...call somebody and see.  Then, if that works, have them call you back at your GV#.

[MYOBi]

Obi test call does not work from my end also. Reason 404.

[Lavarock7]

I just tested **9 222 222 222 and it is working for me.

[drgeoff]

I just tested **9 222 222 222 and it is working for me.

Yes, working now, but was not when I tried it 5 hours ago.

[Lavarock7]

It was broken for me too for a few days. I meant to phrase it as "It is NOW working for me".