$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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 first activate headset controls and then connect your headset.

Activate headset controls

To activate headset controls, enable the setting in WebRTC Options. Go to Settings in ContactPad and click WebRTC options. The available options appear in a new browser tab. Within Advanced in WebRTC options, select to enable Activate headset controls (beta).

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. (If Connect headset is not available, you must activate headset controls. For information about activating headset controls, see Activate headset controls earlier in this page.) 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.

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.

Using multiple softphone and meeting applications at the same time may lead to conflicts with the headset controls as all the applications might be connected to and interacting with the headset.

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.

  • No labels