Beta Testers Needed: Polycom “New Year” BLF Issue (Possible Fix)

pbxgeek

Active Member
Jan 19, 2021
634
189
43
38
Hello everyone,

If you’re tired of restarting Polycom phones every January 1st to restore BLF, I may have a fix. I’m looking for a few beta testers who can validate it on live systems (or test environments) to confirm:
  • BLF continues working after the system clock rolls over into the new year, and
  • the fix doesn’t introduce any regressions with existing BLF behavior.
New FS PBX installations include the fix upon installation.

Existing installations: apply the update​

To apply the fix on an existing install, recompile FreeSWITCH by running:

Code:
cd /var/www/fspbx
bash install/install_freeswitch.sh

Then restart FreeSWITCH:
Code:
service freeswitch restart
If you’re able to test this, please share your results (especially after January 1st).

Happy Holidays from the FS PBX team!
 
Feedback from my test environment. I set my server time to 11:55 pm Dec 31, rebooted freeswitch, and pointed my Polycom phone to it. After 12 AM on Jan 1 when the phone refreshed its SUBSCRIBE, the BLF function broke until the phone rebooted.

I then patched the server, set the server time to 11:30 PM Dec 31, rebooted freeswitch so that it picks up the new time, and pointed my Polycom phone to it. After 12 AM on Jan 1 when the phone refreshed its SUBSCRIBE, everything was fine! I let it sit for a few more hours to confirm.

So far so good. Just need to roll this out in production and see how it acts now

Thank you!
 
  • Like
Reactions: RCCradio
We are 90 minutes past 00:00 UTC which is the time set on all our servers. No issues this year! Tested BLF lights as it seemed too good to be true! Thanks for the Christmas miracle!! HNY

Quick AM update: everything is still stable, no abnormal behavior is observed
 
Last edited:
  • Like
Reactions: pbxgeek
While this patch helped resolve the issue at 00:00 on 1/1, there is still another issue that someone else brought up. Long story short, this issue can still be reproduced after the new year when freeswitch gets restarted. So I am recommending to revert back to original code while the developers can figure out a better way to handle this