Jabra Evolve2 55 + Link 390: Headset buttons don't work on the first incoming call (PWA)

[wl.makup]

Hi everyone,

I'm experiencing a reproducible issue with the 3CX PWA and a Jabra Evolve2 55 using a Jabra Link 390 USB dongle.

Environment​

• 3CX PWA (latest version)
• Google Chrome (latest)
• Windows 11 (fully updated)
• Jabra Evolve2 55
• Jabra Link 390
• Latest Jabra firmware
• Jabra Direct installed
• Headset integration enabled and set to Jabra

Problem​

After a Windows reboot, everything appears to be connected correctly:

• Windows recognizes the headset.
• Audio playback works normally.
• The Jabra headset is selected as the default playback and communication device.
• The PWA detects the headset.

However, the headset answer button does not work for the first incoming call.

If I answer the first call with the mouse, all subsequent incoming calls can be answered using the headset button without any issues.

Additional observations​

• During the first incoming ring, there is a very short audio interruption in the headset, as if the communication channel or HID interface is being initialized.
• After this happens once, everything works perfectly until the next reboot.
• The exact same behavior occurs in both Chrome PWA and Edge PWA.
• The issue also disappears if I make a short outgoing call immediately after startup. After that, the headset buttons work correctly for the rest of the session.
• Even more interesting: If I simply click on the Dialer/Keypad in the 3CX PWA without placing a call, the headset buttons immediately start working. Looking at Chrome DevTools, clicking the Dialer triggers additional JavaScript activity. Immediately afterwards, the Jabra headset buttons work correctly, even without making or receiving a call. This suggests that the Jabra/WebHID headset integration may only be initialized when the Dialer component is loaded, rather than when the PWA starts.
• The problem is not limited to a single computer. It occurs on all of our Windows notebooks using the same setup, so it does not appear to be hardware-specific.

What I've already tried​

• Latest 3CX version
• Latest Chrome
• Latest Windows updates
• Latest Jabra firmware
• Latest Jabra Direct
• Re-paired the Link 390
• Reset Chrome WebHID permissions
• Different USB ports
• Disabled USB power saving
• Delayed PWA startup after Windows login

None of these changed the behavior.

Question​

Has anyone experienced the same issue?

It almost seems as if the WebHID/Jabra call-control connection is only initialized when the first user interaction with the dialer or the first incoming/outgoing call occurs, instead of when the PWA starts.

Has anyone found a workaround or can someone from the 3CX team confirm whether this is expected behavior or a known issue?

Thanks!

 

[KyriacosS_3CX]

Hello,

Sounds like a power saving feature, that maybe got activated/changed after the latest windows or Jabara update - instead of doing any PBX/telephone activity, simply play an audio file (or video) on the PCs, and see if that is enough to wake the headset up fully, ready to answer using buttons.

 

[wl.makup]

Hi,

Thanks for the suggestion. I already tried that, but unfortunately it didn't make any difference.

The problem only disappears once the Dialer/Keypad has been opened at least once after starting the 3CX PWA.
It doesn't even require a call to happen. Simply opening the Dialer/Keypad once is enough. As soon as the Dialer has been opened, the headset buttons work correctly, even for the first incoming call.

This strongly suggests that opening the Dialer triggers the initialization of the headset integration, which otherwise does not happen when the PWA starts.


If I close the 3CX PWA and open it again (without opening die Dialer manually), the problem immediately returns: the answer button on the headset does not work for the first incoming call.

 

[KyriacosS_3CX]

Hi,

I have passed the details to the team and they are checking up on it.

 

[wl.makup]

Another strange behavior with the 3CX PWA – ringtone only works after the first user interaction

One of my colleagues noticed another reproducible issue with the 3CX PWA that may be related to the initialization problems we've already reported.

Steps to reproduce​

1. Close the 3CX PWA completely and start it again.
2. Do not click anywhere inside the PWA window.
3. Minimize the PWA window immediately.
4. Receive an incoming call.

Result​

• The Windows notification appears as expected.
• No ringtone is played.

Now simply open the 3CX PWA again, click anywhere inside the window (there's no need to open the Dialer/Keypad or perform any other action), and minimize it again.

After that:

• The Windows notification appears as expected.
• The ringtone is now played correctly, even while the PWA is minimized.

The click does not have to be on any specific button. A single click anywhere inside the PWA window is enough, and this only has to be done once after starting the PWA.

This makes it look like some part of the PWA (possibly the audio or background notification handling) is only fully initialized after the first user interaction.

In our case, this mainly affects colleagues who have the 3CX PWA configured to start automatically with Windows and immediately minimize the window after logging in. Because they never interact with the PWA before the first incoming call, the first call only shows the Windows notification without playing the ringtone.