obi202 needs to be rebooted at least weekly for ip phones to call out
evergreen:
My modest obiplus setup works fine for the most part but I've noticed that my ip phones cannot call out until I reboot my Obi202 on a weekly basis. While downtime's been generally hitting me at good times, I'd still rather have it set up so I don't have to worry about having to reboot the unit. Just as I felt accomplished for having set this up on my own. Any help would be much appreciated. Thank you!
Mango:
Next time you're having the problem, check your OBi202's status page and report if it says anything that could give us a clue about the problem. Also, let us know what service provider and router you are using, if the OBi202 is connected to a router.
drgeoff:
evergreen
You have an OBiPLUS set up. Presumably your IP phones can call each other when everything is working normally. Do they lose that functionality too or just the ability to reach the outside world before you do the required reboot of the 202?
evergreen:
Drgeoff- actually, the IP phones do seem to have an issue with calling each other. didn't think of that!
Mango-unfortunately I wasn't able to find any clues in the status page.
RFC3261:
Quote from: Mango on June 22, 2014, 07:06:11 pm
Next time you're having the problem, check your OBi202's status page and report if it says anything that could give us a clue about the problem. Also, let us know what service provider and router you are using, if the OBi202 is connected to a router.
A bit of a "me too", with some additional (debugging) details:
I have seen a similar problem. In all cases, the IP phones (Cisco SPAs) have shown loss of registration. Looking at the OBI202 itself (via the web interface), it shows the client (IP phone) registration status as expired. Connection to the service provider (anveo in my case) is still shown as active/current. I checked the network, and registration packets are still being sent from the IP phones to the OBI. Just now (when this was happening) I checked and there is a "reboot required" icon on the obi202 web interface (I cannot say that I noticed that before, but I may simply not have been paying attention). I have syslogs from both the OBI202 and the phones, and the last "interesting" log that seems to be sent from the OBI202 just before the phones fail registration is attempts by the OBI202 to obtain name resolution to root.pnn.obihai.com (at least those messages start about the same time as the registration starts failing from the phones) for about 3 minutes, after which dns resolution seems to be completed, but the OBI202 never allows the IP phone re-registration to complete. My "WAG" is that the firmware is too pedantic regarding the OBIPlus license validations in the face of failures to resolve/connect to the obihai servers, and never recovers. A reboot of the OBI202 fixes it until the next time some sort of dns/network/obi_server failure interrupts connectivity to the obihai servers. I suspect I will need to set up a span port and capture the detailed network packets in order to open a ticket.
Navigation
[0] Message Index
[#] Next page