Both phone ports ring at 10:30am every day
Eric_in_Boca:
At this point, there is one thing that I am certain of.....every day my OBI resets itself. When it resets itself, both lines ring a single ring.
The time it resets itself is the time that it was last rebooted. Unless I make a change that requires rebooting, it never is rebooted. And I have it, and my router, cable modem, and other network equipment connected to a UPS so it is not effected by power outages.
I have the OBI connected to another router. The DHCP lease time in the router is indeed set for 24 hours. So, to test infin8loop's theory, I have this morning set up the OBI to use a static IP address, at right at 10 AM.
I will see if the thing rings tomorrow at 10 AM and post the result in this thread.
Eric_in_Boca:
After setting my OBI to a static IP address, both phone ports are still ringing.
The reason the phones rang, is the OBI reset itself just at 24 hours and 30 minutes after I rebooted it when I changed the IP address yesterday at 10:30 AM.
I have changed the subject of this tread to say "OBI reboots itself approximately every 24 hours".
infin8loop:
Do you make configuration changes via the OBiTalk web portal? In other words is OBiTalk Provisioning Enabled on the device? If so, I see the provisioning Interval is set to 86400 by default. 86400 seconds is 24 hours. I will wonder out loud if the provisioning causes the device to reboot since I don't know. I run my OBi110's (2) with OBiTalk Provisioning disabled and configure locally. I only enabled OBiTalk on one OBi110 to update Google Voice on it when it became "officially supported" and then immediately disabled OBiTalk Provisioning. Most folks probably wouldn't notice a daily reboot if their phone doesn't ring like yours does.
If you do configure using the OBiTalk web portal, I suggest trying to modify the OBiTalk Provisioning Interval (using the portal of course) to maybe 900 seconds (15 min) for a quick test if it allows you to do so. Hopefully you might see a reboot (and a phone ring) in 15 minutes instead of having to wait 24 hours -- if the OBiTalk Provisioning actually does cause a reboot AND whatever criteria is met that would force a reboot in a provisioning event.
This may be a wild goose chase too. I'd test this myself, but I don't want to enable OBiTalk Provisioning!
Eric_in_Boca:
Thanks for the ideas. I do usually use OBiTalk portal to configure, unless I change something like the IP address from DHCP to static, etc.
When I go to OBiTalk.com > System Management > Auto Provisioning, I do not see "OBiTalk Provisioning". However, when I go to my Obi device, I do see OBiTalk Provisioning, and I have set that to 900 seconds.
See the attached screen shots. The first one is directly from the Obi device, the second one is from OBiTalk.com provisioning system.
Eric_in_Boca:
It has now been over 3 hours since I changed the "OBiTalk Provisioning" in the Obi device itself from 86400 seconds to 900 seconds, the device has not rebooted itself.
(It appears this is a change you can make that takes effect without the device having to be rebooted.)
And, it is now over 25 hours since it rebooted itself yesterday, so perhaps just making a change to this parameter has cured the problem....?
I just now changed this parameter to "Disabled", and will report back if this cures the problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page