Obi200 and ASUS RT-AC68W setup - no connection

<< < (2/2)

SteveInWA:
When we see posts similar to yours, the root cause of the problem is often that the poster has gotten in over their head making customizations to their router and/or firewall.  A typical home wireless router such as yours, using only the default configuration, with no tweaks at all, will reliably connect with an OBi device that also has not been customized in any way.  There are absolutely no port forwarding or DMZ settings that need to be, nor should be, made, to use an OBi.

If you want to reduce your reported frustration level, then:

Factory-reset your router.  Do not make any custom setting changes, other than to change the router's own password to one that is long and random, configure a WiFi password that is very long and random, and confirm that other devices on your network can obtain an IP address and reach the internet.Using a paper clip, find the round, raised bump on the bottom of your OBi 200, and gently press and hold the recessed switch for at least 10 seconds while the power is on.  You should feel a slight click when pressing the switch. Wait for the LEDs to start blinking, then release the paper clip to factory reset the device.Go to this URL to download firmware version 4822:  http://fw.obihai.com/OBi202-3-0-1-4822.fwFollow Robert's instruction above to find your OBi's IP address, and log in from your web browser.  The default user name and password are both "admin"Go to the System Management section, Device update, enter the directory and file name of the firmware file you downloaded above, and click the Update button.  Give it a couple minutes, then log in again and confirm from the System Status page that it's now at firmware version 4822.
Your device should now be working.  If it was previously listed on your portal page, then delete and re-add it.

drgeoff:
Quote from: SteveInWA on September 17, 2015, 07:15:31 pm

In order to use it with the OBiTALK network (**9 xxxxxx) you also need to successfully add it to the OBiTALK portal by using the **5 method. 

That is not correct. The Quick Start Guide has the step of making a **9 222222222 call before the step of **5 xxxx registration on the portal.

drgeoff:
Quote from: latech on September 17, 2015, 06:40:16 pm

My phone goes to busy ringtone as soon as I dial 2 (after **9).

Do you truly mean that dialling **92 gives an immediate tone? Despite the good advice from SteveInWA, there is no way that is caused by your router.

I have just now taken a newish (ie not messed up configuration), unregistered OBi110, powered it up without an ethernet cable plugged in and plugged in an ordinary wired phone that sends the DTMF tones immediately as each key is pressed.

It was not until I pressed the final '2' of **9 222222222 that I got the error tone. If you get it immediately after the first '2', you have a problem with your OBi or phone. A factory reset of the OBi should be your first action. If still getting tone immediately after **92, try another phone. Perhaps the DTMF generator has gone bad.

SteveInWA:
Weelll, the lack of detailed troubleshooting in the original posts, combined with a bogus symptom description (the OBi will generate a SIT [samples:  https://en.wikipedia.org/wiki/Special_information_tones], not a busy signal, when there's no network connection), combined with a downlevel firmware version, and a frustrated user, all led me recommend starting completely from scratch.  Even if the OBi was working properly with no Ethernet cable plugged in (and it isn't), gawd knows what other problems would be caused by an improperly-configured router.

Short answer:  the OBi is FUBAR -- start over.

Navigation

[0] Message Index

[*] Previous page