Hi all. Running FreePBX 13.0.153 with Asterisk 13.9.1
We’re having an issue on this server where BLF keys suddenly stop working. The situation at hand is a small office of four users. Each have Polycom VVX 410’s with BLF keys that show the other three user’s extensions, so they can see when others are on a call or not. What happens after some time is that the BLF keys just stop.
Well after searching the net, I came across the problem here: https://issues.asterisk.org/jira/browse/ASTERISK-21677
The issue seems to be identical, but the bug report is over three years old, and apparently resolved. I posted there too, but because of the age of the post, I won’t be surprised if I don’t hear anything.
The issue is explained, in summary, the device going into a queued state, because “SIP network traces show that once the device goes into queued state, Asterisk will no longer send any NOTIFY messages. It only sends them when it is in non-queued state.”
Anyway, like the first post states, I can fix the issue by taking the endpoints offline and putting them back online, but they eventually go into this queued state again.
If you run “asterisk -vvvvvr | grep queued” you get lots of these type of messages, only after the BFL keys stop working (if there is a user that should be notified, i.e. has a BLF key on their phone monitoring the “changed” extension):
Extension Changed 521[ext-local] new state InUse for Notify User 523 (queued)
Extension Changed 521[ext-local] new state Idle for Notify User 523 (queued)
Extension Changed 521[ext-local] new state Ringing for Notify User 523 (queued)