SOLVED: Tearing my hair out with newbie install
MichiganTelephone:
When you reset the device, it should go back to getting its IP address using DHCP. So pick up the phone that you have plugged into the phone port, and dial * * * then 1 and listen for the current IP address. Then you should be able to go to that address in your browser and have the page come up.
But actually, once you have done a factory reset, if I were you I would stay out of the device's web portal, at least to start with. So ignore what I said above, and go to the OBiTALK portal and add your device there. It will give you a code to dial from the phone and then it will find your device, and then you can do all your configuration right from the OBiTALK portal and you don't even need to know how to access the device's portal. I think that would be a lot easier for you, if you'll try it. As long as you can dial the **9-222-222-222 number and it works, then you should be able to let the OBiTALK portal do all your configuration for you — plus, I suspect it would make it a lot easier for Obihai support to troubleshoot your issue, should that become necessary.
heavyharmonies:
Does the OBi support team do things to the box remotely? This is bizarre.
The support team sent me a ticket asking me about the indicator lights on my router. The indicator lights showed that the OBi was NOT connected. I powered the Obi off, changed router ports, powered on... still no indicator. Swapped out to an ethernet cable of mine in case it was the cable... still no indicator.
As I was sitting here replying to the support ticket, the OBi110 rebooted... and then about a minute later rebooted again (I hadn't done anything)... and the power LED stayed on solid.
I quickly jumped onto Obitalk, re-added the device, and reconfigured Google Voice.
Success!
I was just able to call out and complete a call...
BUT! (1) it's on IP 193, one of the DHCP IPs, (2) it's hooked up to the wrong router and in the wrong place in the room. I'm now deathly afraid of moving or reconfiguring anything. Although without assigning it a static IP, for all I know it might fall off my network again.
MichiganTelephone:
You should have no problems just disconnecting it from one router and moving it to another — UNLESS there's an issue with that other router.
Unless you have some compelling reason, I wouldn't switch to a static IP again quite yet (or ever, if you don't really need it). Granted that you should be able to (and I have with mine) but right now you don't know what caused the issue you had so I'd take it slow so that if something does break, you know exactly what you did before it broke (and aren't trying to guess which of the last ten things you did might have caused the problem).
heavyharmonies:
AUGH!
Son of a...
So I called dear old Mum as a test for call quality, latency, etc. and 10 minutes into the call the call died. The OBi110 started flashing the power LED again. About two minutes later, the OBi110 rebooted on its own. The power and Line LEDs are now both lit solid, but I cannot make any calls and the status indicator at obitalk.com is showing brown instead of green.
I can get to the OBi110 config page from my browser and it has held the DHCP-assigned IP address, but under SP1 status it says "Resolving DNS".
This thing is possessed...
RonR:
Why don't you connect the OBi110 directly to your Comcast cable modem and eliminate your router and anything else on your local network (you'll probably need to reboot your cable modem after making the change). [I would also configure the OBi110 manually for this test, but that's just me.]
If the OBi110 works reliably connected directly to your cable modem, the problems you're having are most likely due to your router not being up to the task.
Navigation
[0] Message Index
[#] Next page
[*] Previous page