andrewgroup Posted November 15, 2011 Report Share Posted November 15, 2011 On the two release versions immediately prior to release 18.104.22.16825 we've experienced at least 4 occasions where phones will not properly register until the PBX is rebooted. I've read the release notes on the newer versions including the 4.3 release, but I see no mention of a bug fix related to phones being registered. We are happy to upgrade to the latest, but would like to know if the condition I speak of has been seen and addressed in ..4025 or the 4.3 release? To help, just prior to a reboot, we've captured a TCPDUMP file from a specific phone IP address and attempted a re-register after the PBX reboot, we captured the same successful file... reviewing these in Wireshark, they look amazingly similar, but someone with a lot more experience may be able to determine the issue, and perhaps this might indicate a potential bug... On one PBX the failure occurred after about 45 days of uptime..... and 700 calls.... Lots of available space plus no logging going on... Any advice is appreciated.... A scheduled reboot once per week would be helpful, but I understand CRON is not in the PBX OS.... any suggestions for a weekly scheduled reboot? Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.