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?