Resolved: OBI110 GV says "Resolving DNS" in dashboard

(1/4) > >>

Pandora:
I can't get my new OBI110 to work with GV, the status on the dashboard is "Resolving DNS".

I updated firmware, did a device reset (from the web page), removed and re-added my OBI110, yet still can't make calls via google voice.

Searching this forum, there were suggestions to use dns of 8.8.8.8, which was also tried, but has failed.

Edit to add, firmware version is; 1.2.0 (Build: 2102), hardware version is; 2.8

Any suggestions before I return this to Amazon?

RonR:
Can you successfully perform the echo test by dialing **9 222 222 222?

Is the correct time SystemTime being displayed on the OBi's System Status page?

OBiSupport:
The status "Resolving DNS" can mean that the OBi is unable
to reach the DNS server specified, thus fail to contact the Google server.

From the OBi device's webpage, please check the status for "OBiTALK Service Status."

This should shown to be: "Normal."

This, and the ability for you to call **9 222 222 222 indicates
the OBi does not have network connectivity issue.

-Obihai Support Team

Pandora:
Hi Ron and yes the **9 222 222 222 echo test runs without a problem. My router sees the device and assigns it a DHCP address. The router is running the Tomato (Teddy Bear fork), this is a Linux based firmware.

I have run other ATA's and currently have 5 Ooma hubs online 24/7 without problems. Prior to Ooma I ran a Linksys PAP 2T without trouble. My bandwidth down is 24 MB/sec, and the ISP is Comcast HSI Business though I have my own cable modem (SB 6120) and it provides an externally addressable IP address to my router.

After my post, I went out for a few hours to run errands, and got a connecting message on the device instead of resolving DNS. I'd prefer to see if this can be made to work, or maybe it's a bad device. So far, the support and company seem nice enough.

I do see device status from the dashboard at obtalk.com, have made calls via this google account via google chat. The device seems to be conversing well with obi, and with internet generally. It doesn't seem to be working with google for some reason. :(

When setting it up this morning, I updated the firmware from the dashboard via obitalk.com.

RonR:
Since you can perform an echo test with the OBiTALK server, I doubt there's anything wrong with the OBi hardware.

Have you tried a simple manual configuration from factory defaults?:


System Management -> Auto Provisioning -> Auto Provisioning -> Method : Disabled

Service Providers -> ITSP Profile A -> SignalingProtocol : Google Voice

Voice Services -> SP1 Service -> AuthUserName : (Google Voice username)

Voice Services -> SP1 Service -> AuthPassword : (Google Voice password)

Voice Services -> SP1 Service -> X_SkipCallScreening : (checked)

Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service

Navigation

[0] Message Index

[#] Next page