Extension widget (NONE) not updating in real time

Hi everyone,

We are running VitalPBX Call Center 4.5.3-3 (PBX Engine 20.18.2-1) with hotdesking on PJSIP extensions. We created an extension widget using technology NONE to overlay these PJSIP hotdesking extensions.

The issue: during shift changes (agent logout/login), the widget does not update in real time. Extensions sometimes remain frozen and only update much later (up to 1 hour), or suddenly appear after a long delay. This happens intermittently, mostly when agents change shifts. Restarting nginx or the vpbx-monitor service does not permanently fix the issue.

Environment:

  • VitalPBX Call Center 4.5.3-3
  • PBX Engine 20.18.2-1
  • Hotdesking with PJSIP devices (CallCenterXX)
  • Extension widget created with technology NONE

Symptom:

  • Widget does not reflect agent logins/logouts immediately.
  • Updates are delayed or frozen, even though agents are logged in queues.

Question: Has anyone experienced this behavior? Is there a patch or recommended fix to ensure the extension widget (NONE) updates correctly in real time after hotdesking logins/logouts?

Thanks, Edson

Our dev team will run tests to confirm whether the issue exists!

Thank you for your reply! As shown in the screenshots below, the shift change at 1:00 PM has not yet reflected the extensions logged in during the afternoon.


What feature are they using to login/logout from queues? or are they just dialing *80 to update the Hot Desking extension?

Agents are using *80 to activate hot desking, followed by *52 to access their respective queues.

This problem is not constant—it usually occurs during shift changes, when several agents enter and leave the switchboard simultaneously.

During this period, the switchboard displays inconsistent extension states (missing or inactive extensions), but after some time (about 30 to 40 minutes), the situation automatically normalizes without any manual intervention. Any tips on where to start investigating? Considering that restarting the main Vpbx-monitor / nginx reload services on Asterisk doesn’t instantly fix the behavior described above.

We might have found the issue! We will work on the fix!

Stay tuned!

1 Like

After updating to the new VitalPBX Call Center release 4.5.3-4
PBX Engine 20.19.0-1, the problem has been resolved. Thank you for your attention!