Obi 110 power light goes red and unit floods network
Ad_Hominem:
I own several Obi 110s and several Obi 100s.
On several occasions over the last month, I've observed that, from time to time, the power light on one of my Obi 110s will turn red. At the same time, it floods my network with packets that prevent other devices on the network from communicating. When this happens, the Obi no longer provides dial tone to the attached phones, and the web interface stops working as well.
I have my Obi 110 configured to act as an FXS and an FXO for my FreePBX system. I'm running the latest firmware (1.3.0 (Build: 2824)).
This has happened on at least two of my Obis, that are located 800 miles apart, and which register to different FreePBX systems.
The call history log on the Obi shows nothing unusual at the time the incident occurred. My asterisk logs show only that the extension and trunk associated with the Obi became unreachable.
Has anyone else experienced this? Is this a known bug? Any workaround?
sdb-:
It would be helpful if you configured your OBi's to send their syslogs to a server. Most likely you can configure your asterisk server to receive them.
Some people may not like it, but I found with my OBi110 that it really needed a reboot every day or two. It is easy enough to schedule with cron, and it is polite enough to wait for idle after receiving a reboot request, that I see no reason NOT to do a daily reboot
Something like this with the proper values in the $VARIABLEs does the job for me:
Code:
curl --digest -u "$ADMIN:$PASSW" -s http://$OBI/rebootgetconfig.htm
Ad_Hominem:
Thanks for the suggestions. I was considering a timer switch, but the curl option looks even better.
Just out of curiosity, what is prompting you to reboot your Obi 110 daily? And have you found a similar need for Obi 100 and other devices?
Obi support has suggested a factory rest and reconfigure. I'm guessing that something may have gone wonky when I updated the firmware with an existing configuration...
ProfTech:
You may also want to be sure the ethernet port on the Obi is locked to 100/Full duplex. It is factory set to 10/half which has been documented way back when as causing a huge issue with some routers. Also note that the 110 by design will reboot if it's IP address changes. Since it comes from the factory set to use DHCP its IP can change at any time. I use a static IP and my 110 never gets rebooted unless the AC goes off or I change a setting and reset it as directed. I did get some random reboots but after shutting off DNS Server redundancy with CallCentric the issue stopped.
sdb-:
I observed some spontaneous reboots with my '110, a couple of times right when a call came in.
I found that trying to save the config usually created a corrupt XML file unless right after a reboot. The call history also was corrupt but not often.
I don't have experience with other OBi's. However I did just upgrade to a '202 and after some discussion here, a couple of days ago I disabled the reboot just to see how it will behave. So far, so good (fw 3-0-1-4142) but other people have reported issues.
I do have my ethernet set 100/fd just because I see no reason for the slower speed. And I have my router set to reserve and assign the same IP address via DHCP.
Navigation
[0] Message Index
[#] Next page