OBiwifi Wireless Adapter
Mack002:
I found a way to connect to Callcentric and make calls using the Jetpack internet connection.
I unplugged the Obiwifi, power cycled the Obi, plugged an ethernet cable from my computer to the WAN on the Obi, setup internet connection sharing on the computer. Then, the Obi registered with Callcentric and I can make and receive calls.
My hope is that Obi will find the glitch in the 4330 firmware that prevented the Obi from connecting wirelessly. Just using the Obiwifi to connect is much easier - when it works.
Thanks for the questions and help.
giqcass:
I wouldn't try 4303. This is a link to the most recent firmware I would consider trying as an alternative to 3-0-1-4330
3.0.1 (4269) for OBi2 & OBi3 Series: http://fw.obihai.com/OBi202-3-0-1-4269.fw
Personally I am still using 3.0.1 (4142).
drgeoff:
It looks like the OP manually assigns IP addresses. I would have checked that the OBi hadn't 'forgotten' the gateway and/or DNS server settings when the firmware was upgraded.
Mack002:
Quote from: drgeoff on March 17, 2014, 04:50:58 am
It looks like the OP manually assigns IP addresses. I would have checked that the OBi hadn't 'forgotten' the gateway and/or DNS server settings when the firmware was upgraded.
I'm the OP. I've never used static IP addresses - especially with the Jetpack, it just passes the addresses to each device that signs on. I guess the reference is to my statement "When dialing ***1 the response gives me Obi's IP and states that DHCP is disabled.". I found the fact that DHCP was disabled odd as well.
When I connected the Obi to my computer via an ethernet cable to share internet access (from the Jetpack connected to that computer) the Obi connected immediately using that shared internet access without any issues. I did not changed any Obi settings; I just unplugged the ObiWifi and plugged in the ethernet from my computer.
drgeoff:
In which case I would definitely point a web browser at the OBi's local IP address and have a good look at the network config settings.
It used to be an unwritten rule that immediately following a firmware upgrade any device should be reset to factory defaults and re-configured. Most times you will get away without that hassle .....
Navigation
[0] Message Index
[#] Next page
[*] Previous page