Hello

We have noticed something strange - can answer calls with the phone button on the USB headset, however the mute button can cause the call to be hanged up. Sometimes it mutes/unmutes and then the second time muting will hang up the call.

This is using different USB headsets - Microsoft LX-6000 and Logitech H650e. Both headsets correctly mute/unmute the microphone input on Windows when pressing the mute button.

So it looks like something in PhonerLite is causing it to behave incorrectly when pressing mute/unmute. We were even able to answer a call by pressing mute!

Marcus

Thanks - wasn't sure if it was a bug in the software as two different makes of headsets are doing the same thing.

Is there a way to disable PhonerLite reacting to the buttons on the headset as right now we can't make use of the Mute button on the headsets as it can cause PhonerLite to end the call?

Same problem with Plantronics Blackwire C620 & C520.

But it works fine with Jabra UC VOICE 750 & Jabra EVOLVE 40 UC.

So the plantronics are configured to 'default'

I had tested some Jabra headsets and some from Sennheiser. There were not such problems.
It is not easy for me to support such a wide range of hardware. Sorry.

I just tested with a Plantronics CS60 and the latest version of PhonerLite (2.42). When I press the mute button on the headset the recording from the microphone is stopped. After pressing the mute button again the recording device is opened again and the remote party can hear me again. So I can't reproduce the button with that device. Only when pressing the hook button on the headset the connection will be terminated - this is the expected behavior.

Maybe your headsets sends other commands after pressing buttons to PhonerLite. Can you please send me the content of the debug window of PhonerLite after pressing the mute button? There should be some output like: "HID in: [Plantronics] Mute = 1". Please send me that content by e-mail - not here in the forum.

Your headset reports a hook event when pressing the mute button. That is strange!
I don't know what to do. The hook event means call termination (if the call is active) or call answer (incoming ringing call available).

I've got some interesting information. The Microsoft headset has both a mute button and answer call button (both LED backlit).

When the call button is off (LED light is off), I can press mute repeatably and all looks good in the debug log:

13:01:16,282: HID in: [TEL] Phone Mute = 1
13:01:20,729: HID in: [TEL] Phone Mute = 0
13:01:24,434: HID in: [TEL] Phone Mute = 1
13:01:26,177: HID in: [TEL] Phone Mute = 0
13:01:26,681: HID in: [TEL] Phone Mute = 1
13:01:27,729: HID in: [TEL] Phone Mute = 0
13:01:28,082: HID in: [TEL] Phone Mute = 1
13:01:28,529: HID in: [TEL] Phone Mute = 0
13:01:28,833: HID in: [TEL] Phone Mute = 1
13:01:29,082: HID in: [TEL] Phone Mute = 0
13:01:29,778: HID in: [TEL] Phone Mute = 1
13:01:30,234: HID in: [TEL] Phone Mute = 0
13:01:30,482: HID in: [TEL] Phone Mute = 1
13:01:30,979: HID in: [TEL] Phone Mute = 0
13:01:31,178: HID in: [TEL] Phone Mute = 1
13:01:31,833: HID in: [TEL] Phone Mute = 0
13:01:32,530: HID in: [TEL] Phone Mute = 1
13:01:32,834: HID in: [TEL] Phone Mute = 0
13:01:33,833: HID in: [TEL] Phone Mute = 1 

However, if the call button is on (LED illuminated), pressing mute causes the following to happen (a new call opens with no number):

13:05:10,026: HID in: [TEL] Hook = 1
13:05:10,028: Connect Request: 2E 00 01 00 02 80 46 23 01 00 00 00 01 00 00 07 00 80 31 32 30 30 31 00 00 09 01 00 01 00 00 00 00 00 00 00 00 02 91 81 05 00 00 00 00 00
13:05:10,028: Connect Request: 12001 to
13:05:10,028: HID out: [LED] Hook = 1
13:05:10,029: HID in: [TEL] Phone Mute = 1
-------------------------------------------
13:05:10,029: T: 84.45.30.2:5060
STUN requesting...
13:05:10,034: HID in: [TEL] Hook = 1
13:05:10,034: HID in: [TEL] Phone Mute = 0
-------------------------------------------
 

Pressing the call button while it's illuminated and on a call seems to work fine:

13:06:09,571: HID in: [TEL] Hook = 0
13:06:09,588: Disconnect B3 Request: 0D 00 01 00 84 80 E9 25 01 01 01 00 00
13:06:09,588: Disconnect B3 Request
13:06:09,588: HID out: [LED] Hook = 0
13:06:09,588: Disconnect B3 Confirm: 12 00 01 00 84 81 E9 25 01 01 01 00 00 00 00 00 00 00
13:06:09,588: Disconnect B3 Confirm 

Finally, here's a sample case to illustrate the problem. All lights on the headset were off - so I was unmuted and call button was off. I accepted an incoming call. The call light illuminated to show I was on a call. I then pressed the mute button and the call disconnected:

13:07:10,522: HID in: [TEL] Hook = 1
13:07:10,522: HID in: [TEL] Phone Mute = 1
13:07:15,971: HID in: [TEL] Hook = 1
13:07:15,973: Disconnect B3 Request: 0D 00 01 00 84 80 A9 26 01 01 01 00 00
13:07:15,973: Disconnect B3 Request
13:07:15,973: HID out: [LED] Hook = 0
13:07:15,973: HID in: [TEL] Phone Mute = 0
13:07:15,974: Disconnect B3 Confirm: 12 00 01 00 84 81 A9 26 01 01 01 00 00 00 00 00 00 00
13:07:15,974: Disconnect B3 Confirm
 

So just to confirm, when the call button is turned on, pressing mute also causes 'HID in: [TEL] Hook' to be recorded.

Looking at the logs again, perhaps I've figured out what's happening.

Phone Call 1

1) Phone Rings
2) Accept via PhonerLite answer button

15:21:35,430: Connect Active Response
15:21:35,430: Connect B3 Request: 0D 00 01 00 82 80 1B 20 01 01 00 00 00
15:21:35,430: Connect B3 Request
15:21:35,431: HID out: [LED] Ring = 0
15:21:35,431: HID out: [LED] Hook = 1
15:21:35,435: Connect B3 Indication: 0D 00 01 00 82 82 60 86 01 01 01 00 00
15:21:35,435: Connect B3 Indication
...
15:21:35,456: Facility Confirm: 11 00 01 00 80 81 1C 20 01 00 00 00 00 00 01 00 00
15:21:35,456: Facility Confirm (DTMF)
15:21:35,456: Facility Confirm: 11 00 01 00 80 81 1D 20 01 00 00 00 00 00 01 00 00
15:21:35,456: Facility Confirm (DTMF)
15:21:35,456: HID in: [TEL] Hook = 1 

Can see above that PhonerLite sets the Ring to 0 and Hook to 1 as now on a call. For whatever reason, reports HID in too (though no buttons pressed).

3) End call using PhonerLite hangup button:

15:21:38,364: Disconnect B3 Request: 0D 00 01 00 84 80 AE 20 01 01 01 00 00
15:21:38,364: Disconnect B3 Request
15:21:38,366: HID out: [LED] Hook = 0
15:21:38,366: Disconnect B3 Confirm: 12 00 01 00 84 81 AE 20 01 01 01 00 00 00 00 00 00 00
15:21:38,366: Disconnect B3 Confirm 

As can see from the above, PhonerLite specifies Hook = 1 when on a call and Hook = 0 when off a call.

Phone Call 2

I then made another call to myself and answered.

1) Pressed the mute button on the headset while the call LED was correctly illuminated. The headset correctly muted and this shows in the PhonerLite UI with the mute icon beside the microphone. This appears in the log:

15:27:09,226: HID in: [TEL] Hook = 1
15:27:09,227: HID in: [TEL] Phone Mute = 1 

So can see when mute is pressed, the headset reports Mute = 1 and Hook = 1. Both seem logically correct as the hook button is still illuminated. All that's changed is Mute from 0 to 1.

3) I press the mute button again on the headset and the call is dropped. Here's what was in the log:

15:32:38,666: HID in: [TEL] Hook = 1
15:32:38,671: Disconnect B3 Request: 0D 00 01 00 84 80 B7 21 01 01 01 00 00
15:32:38,671: Disconnect B3 Request
15:32:38,671: HID out: [LED] Hook = 0
15:32:38,671: HID in: [TEL] Phone Mute = 0
15:32:38,672: Disconnect B3 Confirm: 12 00 01 00 84 81 B7 21 01 01 01 00 00 00 00 00 00 00
15:32:38,672: Disconnect B3 Confirm 

Here is where the problem lies: the HID in reports Mute = 0 and Hook = 1. Again this seems correct. The hook is still on, but mute has changed from 1 to 0. Rather than PhonerLite reading the current state of buttons (i.e. hook still on, but mute off), it seems PhonerLite instead toggles the current state. You can see after PhonerLite toggles the state of Hook, it disconnects from the call and sends an HID out signal to the headset to turn off the hook.

So to summarise, it seems PhonerLite is toggling the state when buttons are pressed, rather than reading the current state of the buttons.

What do you think?