Hello,

I have been using PhonerLite with a Jabra Evolve 65 + Link 360 for about 8 years, until the headset physically broke (headband failure).

I replaced it with a new Jabra Evolve2 65 UC bundle including the Jabra Link 390, but I noticed some differences/problems compared with my old setup.

My tests:

• Incoming call ringtone in headset
  
  With Evolve2 65 + Link 390:
  
  • Incoming calls are received correctly (green led flashing on headset), but the ringtone is not played in the headset.
  • I enabled "Ringtone in headset (Bluetooth)" in Jabra Direct, but it has no effect.
  • In PhonerLite I tried different ringtone configurations:
    
    • PC audio device + HID event
    • Jabra Link 390 as ringtone output
    • Different Windows default audio device settings
  • None of these configurations make the ringtone play in the headset.
  
  
  With the same Evolve2 65 paired with my old Link 360:
  
  • The ringtone works correctly in the headset.

• Call connected / call ended sounds
  
  With Evolve2 65:
  
  • I no longer hear the typical headset feedback sounds when the call starts or ends.
  • This happens both with Link 390 and with the updated Link 360.
  
  
  However:
  
  • With my old Evolve 65 headset, these sounds were always present.
  • With the old Evolve 65 paired to Link 390, the call connected/end sounds are still present.
  
  
  So I am not sure if these sounds are generated by the headset firmware, by the Jabra SDK/API, or by the softphone integration.

• Answer call using boom arm rotation
  
  The Evolve2 65 has the option "Answer with boom arm rotation".
  
  
  • With Link 360: this function works correctly.
  • With Link 390: this function does not work.
  • The headset answer button also seems less reliable with Evolve2 65 compared with my old Evolve 65.

I contacted Jabra support and had a long email exchange. Their answer was basically that PhonerLite should integrate the latest Jabra SDK/API, and that these features depend on the softphone integration.

My question is:

Are these behaviours expected because PhonerLite does not use the latest Jabra SDK/API, or are some of these functions (for example headset-generated call tones or boom arm rotation events) supposed to work independently from the softphone integration?

I am trying to understand whether this is a PhonerLite integration issue or a Jabra firmware/headset compatibility issue.

Thank you.

Thank you for your explanation.

I completely understand that PhonerLite is a hobby project and that you cannot buy and test every headset on the market.

My goal was not to ask for Jabra SDK integration or new features. I simply wanted to understand which headset functions are expected to work with the standard HID implementation provided by PhonerLite, and which ones depend on the headset vendor's SDK/API or firmware.

The questions came from a few behaviours I observed with my new Jabra Evolve2 65, such as the headset ringtone not working with the bundled Link 390 dongle (while it works with my older Link 360), and the missing call connected/call ended tones.

This helps me understand whether the behaviour is a limitation of the headset, the dongle, or the software integration.

Thank you again for your time and for maintaining such a useful softphone.

Hi,

thank you for the suggestion.

I tested the HID page you linked (`Statistics -> HID events`).

When I select the Jabra device for both recording and playback, all HID LEDs (Ring, Off Hook, Speaker, Mute, Hold, etc.) can be triggered manually by clicking on them, and they turn green correctly in **all** of my test configurations:

• Jabra Evolve2 65 + Link 390
• Jabra Evolve2 65 + Link 360
• Jabra Evolve 65 TE + Link 390
• Jabra Evolve 65 TE + Link 360

However, the actual headset behavior is different.

Only the combination **Evolve 65 TE + Link 360** produces the expected headset actions (ring tone, call connect/disconnect tones and reliable answer button behavior). The other combinations still miss some or all of these functions, even though the HID events are clearly being generated by PhonerLite.

So it seems that PhonerLite is correctly sending the standard HID commands, but the final behavior depends on how the specific Jabra headset/dongle/firmware combination interprets them.

In the meantime I decided to return the Evolve2 65 and I purchased an Evolve 65 TE instead. Interestingly, even the new Evolve 65 TE does **not** work correctly with its bundled Link 390 dongle, while it works perfectly with the older Link 360 from my original Evolve 65.

One additional note: I have **not** updated the firmware of the new Evolve 65 TE, and I do **not** intend to do so. According to Jabra's release notes, the latest firmware introduces a Bluetooth security change that enforces a minimum 128-bit encryption key length and may no longer be compatible with older Bluetooth adapters. Since the headset is working perfectly with my Link 360, I preferred to keep the original firmware to avoid introducing another variable into my testing.

Thank you again for your help and for taking the time to reply.