Hi all,
I have configured the OBi110 for Google Voice, and it works great. But now I have to power cycle the device almost every day in order it to work perfectly, as long I see my OBi110 data activity LED is rapidly blinking green (no phone is used). Then I know I cannot call out or outside cannot call in.
Can someone please help me out why the data activity LED is rapidly blinking even no phone is used? I have a AT&T 6Mbs DSL service, I have no issue to use GV at all, the sound quality is excellent when it works. Please help!
Thank you
When you log into your system's status page what does it say under status for your GV provider when you see the rapidly blinking activity light?
When the data activity LED is rapidly blinking in the Obi110 device, I even cannot login to the device. What's more, it also effect all my wired computers Ethernet connection, but not effect the wireless connection. My two computers wired to my router cannot go online, but my laptop use wireless can go online. I see my router and modem activity LED rapidly blinking for the port that connected to the OBi110 device. In order I have Ethernet connection back, I have to power cycle the OBi110 device. It works everytime once power cycle. Now I can login to the system's status page, it shows SPI Service Status: Connected.
It never had this issue before, it started about a month ago. I will try again wen the OBi110 device data activity rapidly blinking and try to login to the system's status page. Will let you know.
Thank you
Hi Steam,
You might try changing the port speed on your OBI using the phone attached to the OBI. It might help. :) It might not help. :( Here are the instructions copied straight from a RonR post:
"You might try changing the OBi Ethernet port from 10 mb/s half-duplex to 100 mb/s full duplex to see if that helps:
1. Dial *** 0
2. Enter option 27 and press #
3. Press 1 to set a new value
4. Enter a value of 1 and press #
5. Press 1 to confirm/save
6. Hang up
7. Wait for the OBi to reboot"
This sounds a lot like a network loop.
I would suggest you check your wiring and make sure you don't have your switch plugged back into itself somewhere, or if you have two switches that there is only ONE cable between the two -- two cables will cause this problem.
I'm seeing this too. I had my OBI110 for about 10 days now and had to power cycle it 4 or 5 times because of this issue. The data activity ports stars to blink continuously I can't figure out why.
Does anybody's Ethernet Activity light *not* blink continually?
I have had this problem from the getgo with one of my obi110 boxes FOR ABOUT 7 MONTHS. No one has been able to help.
This product works great when it works. BUT ITS RELIABILITY ABSOLUETLY SUCKS. ITS LIKE PLAYING SCHARADES!
ANYONE WHO USES THIS DEVICE FOR PHONE SERVICE FOR THIER BUSISNESS IS CRAZY!!
CHANGING PORT SPEED DOESNT DO S__t . Dont waste your time!
This can also be caused by an error in format of Dial Maps or Call Routes.
If restarting clears the trouble, but it comes back after making a call, it would be a good idea to reset everything (except provider info) back to default and re-enter the data carefully.
Quote from: Shale on February 13, 2013, 11:57:53 PM
Does anybody's Ethernet Activity light *not* blink continually?
Mine only blinks maybe once every 30sec or so when it sends updates. I would check the broadcast status in your network - any machine plugged into the same port (ex a laptop) should see the same port activity and looking at the Eth adapter status you could see if this is traffic accounted for.
There is always Wireshark on the laptop if you feel like CSI :)
This can also be caused by an error in format of Dial Maps or Call Routes.
If restarting clears the trouble, but it comes back after making a call, it would be a good idea to reset everything (except provider info) back to default and re-enter the data carefully.
NOT THE CASE!!! I NEVER FIDDLED WITH ANY SETTINGS. EVEN RESET IT TO DEFAULTS AND IT STILL HAS THIS DISEASE!!!
Mine blinks every second or two. Works great. I am not worried.
Edit: I did install Wireshark on one of my computers. The ARP traffic seems to explain my blinking. Even my TV and thermostat are sending ARP packets. The devices sure have a short memory about what MAC is associated with each IP. That ARP traffic pretty much explains my blinking. Thanks ipse.
Quote from: danaflo on February 17, 2013, 06:38:29 PM
NOT THE CASE!!! I NEVER FIDDLED WITH ANY SETTINGS. EVEN RESET IT TO DEFAULTS AND IT STILL HAS THIS DISEASE!!!
You know, we're all here users like you...not sure if you tried the troubleshooting steps I suggested before pushing CAPS LOCK. :)
Cap locks were intended. Oh guesS what, I just looked at my obi110, ITS OFFLINE...THE DATA LIGHT IS BLINKING RAPIDLY AGAIN!
Quote from: ipse on February 18, 2013, 09:06:51 AM
You know, we're all here users like you...not sure if you tried the troubleshooting steps I suggested before pushing CAPS LOCK. :)
I understand how you could have thought somebody posting here would be interested in troubleshooting. Anyway, I found it to be informative.
I've been working through a similar issue with tech support. Following a reboot or power loss, the Obi110 would occasionally come up normally. More often, I found it with the Ethernet LED flickering, the phone LED off, and the device unreachable on the network. I'm still watching the beast, but after ~24 hours and a couple dozen power cycles I believe the following may have resolved the issue...
Reset the Obi to factory defaults
Set the Ethernet port to 100Mb FDX, if desired
Remove the device from the obitalk.com portal and re-add it
Make any configuration changes from the expert option on the portal
This may work if all changes are done on the device as well, haven't tested that yet. In my case I believe it was using both the portal and local menus to make changes that caused the problem. It appears that this has also resolved issues with local changes reverting to defaults on reboot.
local changes reverting to defaults on reboot
Frustrating until you figure it out. If Obi can push stuff, they should also learn how to read changes back.
I chose to turn of ALL Auto Provisioning options.
My 110 will not work with the FDX option. Power light just blicks with no Ethernet activity at all.
Quote from: zapattack on February 21, 2013, 11:28:20 PM
local changes reverting to defaults on reboot
Frustrating until you figure it out. If Obi can push stuff, they should also learn how to read changes back.
Indeed. To follow up on my previous post, after two days without issue the Obi110 is again going offline after reboot with the data LED flashing. A factory reset and reconfig (with auto-provisioning disabled this time) hasn't helped. Dumping to a syslog server shows nothing unusual. Wireshark isn't seeing anything from the Obi when it is in this state. Dialog with tech support has stalled at "We looked at the device and it is online..." after swapping out the switch, fiddling with port speed & duplex, etc. The warranty runs in two days, and it doesn't appear likely this will be resolved in that time.
It is, I believe, time to bin the beast and move on. I bought it to use as an FSX/FXO for my Asterisk server. I just dumped AT&T, don't need the FXO anymore and reliable ATAs are a dime a dozen. Too bad, the Obi really is a slick piece of hardware. That isn't much good if the device can't recover from power loss without having to cycle it a dozen times.
A factory reset and reconfig (with auto-provisioning disabled this time)
...and ObiTalk Provisioning!!!
Remember the dashboard Expert Configuration Menu has the ObiTalk Default checkmarks.
I thought ObiTalk was a totally separate feature, but now I am not so sure what it means.
Quote from: zapattack on February 26, 2013, 09:28:25 PM
I thought ObiTalk was a totally separate feature, but now I am not so sure what it means.
I disabled ObiTalk provisioning while troubleshooting. Support promptly emailed asking me to enable it again. Didn't say why, though.
To further update the "blinking data" thread... Support issued an RMA. The replacement arrived today. I have it configured but not set up in the portal. Haven't been able to break it yet. Next on the list, add it to obitalk.com see if it continues to work. Firmware is 1.3.0 build 2776. Newest I saw on the firmware thread is build 2774, so that's of some interest.
I have been working with customer support for about a week on this issue and still no resolution. Did a couple of factory resets but the problem comes back after two days. They had me set the IP to static instead of DHCP but didn't help. Can't get the device to stay up for more than 2 days. It feels as if the device goes into a bad state that keeps progressing and blows up after about 2 days.
Quote from: ely62 on March 05, 2013, 05:41:25 PM
I have been working with customer support for about a week on this issue.....
Day six with the replacement here, and zero problems. My Obi110 was stable once it remained online more than a couple minutes after a reboot. Sometimes took nine or ten power cycles to get it to do so, but when it did it worked until rebooted. The replacement reboots faster, and comes up every time.
If troubleshooting hasn't identified any issues with the configuration or network, ask for a warranty exchange.
If you have both SP1 and SP2, another troubleshooting technique is to disable one of them (Voice Services/SPx)and see if the trouble goes away.
I found that the GV port settings can cause the problem described (mine were not default).
Setting Proxy Server Port and Outbound Proxy Port different solved my problem.
Similar issues reported here
http://www.obitalk.com/forum/index.php?topic=2684.0
"my obi110 is crazy, internet led flashing and make home network down"
http://www.obitalk.com/forum/index.php?topic=4839.0
"Obi110 Flood The LAN and Bring My Network DOWN"
https://www.obitalk.com/forum/index.php?topic=3676.0
"Data Activity LED is constantly blinking green "
I have just had this exact problem.
I set-up some packet sniffing on my network, and found that the obi110 was making constant dns requests for a time server which were failing. I reset the time server under network settings and rebooted the obi all is now well :)
Quote from: mgazza on September 07, 2013, 03:05:32 AM
I have just had this exact problem.
I set-up some packet sniffing on my network, and found that the obi110 was making constant dns requests for a time server which were failing. I reset the time server under network settings and rebooted the obi all is now well :)
I'm curious to know if you had a second NTP Server (NTPServer2) stated under "
NTPServer2". In my case, I have always used "
time.nist.gov" from day one as my backup NTPServer2, so if
NTPServer1 fails, it should move on to trying the second. Additionally, what DNS servers are you using under "DNSServer1" and "DNSServer2"?
mgazza, short post but really good detective work and solution. I bet many people's problem would be solved by simply switching the ntp server. Here is my story:
I have been using OBi110 for the last 6 months in the hope of slowly transitioning the family away from a POTS line. The OBi works well most of the time, but there have been time when an outbound call could not be made through google voice. At those time the LED with the phone icon was off and the Obi would should offline in OBiTalk. The OBi would not show in the DHCP lease table of my router. Based on this I switched to a static IP.
The static IP worked well but the device would often enter a state where the network light would flicker fast without a connection and would show as offline in ObiTalk. However, when calling ***1, the static IP was read back properly. Restarting the device with ***9 would work but only for a few hours.
Many folks said that support asked them to switch the router. I had a spare new N-router at hand of different make and model, which I tested with the same result. This pretty much told me that the router is not the issue and that this is a firmware bug.
Stumbling at mgazza's hint of ntp dns queries, I changed the ntp server to time.nist.gov, which I typically use, and all has been well since then.
I have had trouble with ntp.pool.org on my firewall server as well and those problems went away with the same ntp server change.
Thanks again for the debug help. I was never able to get wireshark to spit out the network traffic from the Obi hardwired connection, so this hint was greatly appreciated!
Cheers,
rev
I saw the same issue with OBI110 the day I bought it. Data light flashing and the network was completely down. I read through the forum. I have my own NTP server in the same subnet so it is not an issue. I power cycled the OBI device and the switch and it seems to work for two days. I am using OBI as FXO device connected to ASTERISK server.
If Official tech. support team is reviewing this thread, I believe that there is something in the firmware. Please see this Cisco tech. note. I had just restarted my Asterisk server when this happened. I suspect that the firmware reconnect code is not functioning correctly.
http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6000-series-switches/23563-143.html