-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calling onhookAsync() also fires button press event? #36
Comments
Good question. |
Hello, is there is an answer for this comment? Why do you fired this event? |
@jabra-slawaetz has your investigations resulted in anything you can share with us? The sequence diagrams in the docs suggest that this is the intended behaviour, but it results in a number of faulty situations.
Because there is a pretty noticeable delay between calling
The above scenario makes it very difficult to handle juggling of multiple calls while still supporting Jabra devices. |
Any updates here ? Im also stuck here as it really difficult to handle multiple calls here |
This doesn't seem to be the case with the Jabra 930 pro and the Jabra Handset 450. Seems the events are a bit different for the evolve series than the two i mentioned, but what's written below by @jabra-slawaetz was the solution to my problem :) |
Hello, as per the github readme, these components are primarily support through the Jabra Developer Zone at developer.jabra.com The OP's issue has been dealt with and resolved in the Developer Zone. But please note that we have released a new genration of the JavaScript library in Autumn 2021 that provides a much improved handling of call control, especially in the shape of "Easy Call Control" module. You can find it here: https://developer.jabra.com/site/global/software/integration-components/javascript/index.gsp This does require re-integration as it has a rewritten API, but has many benefits including supporting both node.js and Chrome, as well as WebHID support when running in Chrome. thanks --- Resolution to this specific problem --- Summary: The buttonpress event is not an actual button press, it is a confirmation from the device that it has gone off-hook. For a clear discussion of the request-acknowledge protocol, please see https://developer.jabra.com/fileMedia/download/096501fc-5339-43c1-af98-39b13bc02549 For reference, we copy the detailed resolution responses to the issue here: --- begin ---
--- end --- |
Hi @jabra-slawaetz, thank you for clarifying this and responding. I was looking through the documentation for the latest SDK today and found information about the acknowledgement, and it helped me to make a fix for my issue, and will start looking into the differences in the latest SDK and implementation. I'm looking very much forward for the webHID support. Have a great day, and thank you for your time |
Using
@gnaudio/jabra-node-sdk v3.0.0
Headset:
Jabra evolve 75 with Jabra Link 370
When setting the device onHook it fires the button (btn) press event too. Is that a bug?
What I did.:
device.onhookAsync();
Outputs:
New input from device Jabra Link 370 is received: type 1 OffHook value: false
I understand that setting the device onHook on the device should fire the button event, but why fire a button event when no button was pressed?
The text was updated successfully, but these errors were encountered: