Controlling a WebRTC call in ContactPad using compatible headset

The headset control feature enables you to control a WebRTC call using the buttons on compatible headsets when using Chrome on Windows and Mac operating systems. Most headsets should be compatible, but we have only tested headsets of the following brands: Jabra, Poly (Plantronics), Logitech, and EPOS (Sennheiser). If you have turned on the feature in WebRTC settings and connected the headset, you can use the headset buttons instead of using buttons in ContactPad. You can accept a call — if auto-answer is not enabled — mute and unmute your microphone, and hang up at the end of the call. Also, if your headset supports it, you can also reject the call.

To control WebRTC calls using a headset you must connect a compatible headset.

Connect WebRTC to your headset

To connect to the headset, you must have a WebRTC tab open. For information about opening a WebRTC tab, see the Popping out the active ContactPad section in Identifying which webpage contains the active ContactPad. On the WebRTC tab, click Connect headset. In the dialog box that appears, select the compatible headset you want to use to control WebRTC calls and click Connect. Refresh the WebRTC tab to activate the connection.

When connected, the next time you receive or make a call, you can control the call using the appropriate buttons on your headset. When a call arrives for you — if auto-answer is not enabled — you may hear ringing in your headset and lights may flash indicating a waiting call.

Using headsets with multiple applications

When using a headset to control WebRTC calls in ContactPad, you can't simultaneously use the same headset to control calls in any other application. Attempting to do so will send control messages to both applications, resulting in unpredictable behavior. To avoid this issue, ensure that the headset is used exclusively with this ContactPad for call control purposes.

Unexpected headset behavior

If you press the button used to make or receive a call on your headset in the absence of a call, your headset will be connected to a call that doesn't exist. If you then get a real call in ContactPad and accept it, your headset controls may not function correctly as it is now connected to two calls. When the call ends, your headset is disconnected from both calls. You can use the headset as normal on the next call. This behavior is most common in Jabra headsets.

If you refresh the page while on a call, your headset may be connected to two calls. Your headset controls may not function correctly. When the call ends, your headset is disconnected from both calls. You can use the headset as normal on the next call. This behavior only occurs in Jabra headsets.

Limitations

Only Chrome and Edge browsers are supported.

Only Windows OS and Mac OS are supported.

WebRTC can only work with one headset at any time. You can pair multiple headsets, but you must have only one plugged in for headset control to work.

Transfer, hold, and other headset controls are not supported.

Not all headsets from the supported vendors will work. Some behave differently or do not support all call functionality.

Vendor-specific software, such as Plantronics Hub, prevents the headset from working with ContactPad.

Bluetooth headsets are not supported.

Support and documentation feedback

For general assistance, please contact Customer Support.

For help using this documentation, please send an email to docs_feedback@vonage.com. We're happy to hear from you. Your contribution helps everyone at Vonage! Please include the name of the page in your email.