General Options

Device integration enables the communication between UC Client and device via control signals. This is required, for example, to enable Hardware Button control for UC Clients.

There are different options for device integration. Not to use device integration is one of them.

1. No Device Integration

No device integration
No Device Integration: UC Client and device can not communicate with each other. They are not connected.

Device integration for UC Clients is not mandatory. You can fully operate UC Clients via software buttons in the GUI.

Advantages Disadvantages
No integration effort required UC Clients do not react to hardware button presses
No unwanted interference with other UC Clients Control signals send by the device generally have no effect

2. USB HID

A. All Headsets

USB HID integration
Device Integration with USB HID works on operating system level.

USB HID integration uses standard functionality on operating system level. It does not require additional software like Jabra SDK Software Libraries. Microsoft Teams is for example a UC Client that uses USB HID.

USB HID has two Usage Pages:

  • Standard Telephony Usage Page used by non-Jabra applications
  • GN Telephony Usage Page used by Jabra applications

These usage pages require different control signals. Jabra devices are compatible to both usage pages.

Advantages Disadvantages
No additional software or software libraries needed Manual integration is difficult and expensive
  Not suitable for parallel use of two or more UC clients

B. Certified Jabra Headsets for Microsoft Teams

The core functionality of certified Jabra headsets for MS Teams is identical with non-certified headsets. All variants of the headset use USB HID with MS Teams.

Certified Jabra headsets for MS Teams offer additional features like for example:

  • blinking light on Hardware Controller before a MS Teams meeting starts
  • bringing the MS Teams window to the front by pressing a hardware button

These features work out of the box with MS Teams.

3. Jabra SDK

Jabra SDK Integration
Jabra SDK is the recommended method for the integration of Jabra devices.

The Jabra SDK Library adds an abstraction layer on top of USB HID. It addresses the device via GN Telephony Usage Page.

Jabra SDK simplifies the integration process by taking away device complexity from the developer. It is thus much easier and faster to integrate with Jabra SDK than with USB HID.

Advantages Disadvantages
Simple and cost-efficient way to integrate Jabra devices UC Client depends on Jabra software library
Suitable to manage parallel use of two or more UC clients. These UC Clients need to use Jabra SDK for device integration, too.  

Jabra SDK is the only method of device integration that is fully suitable to operate two or more active UC Clients in parallel.

4. Jabra Direct

Jabra Direct Integration
Jabra Direct provides device integration for a range of supported Third-party UC Clients.

Jabra Direct is a desktop application for Windows and macOS operating systems. It provides device integration via Jabra SDK Library for supported UC Clients. Once Jabra Direct is installed, it automatically detects and integrates UC Clients on the system.

Advantages Disadvantages
No manual integration required, just install Jabra Direct Available for Windows and macOS only
Suitable to manage parallel use of two or more UC Clients  

Jabra Direct is compatible to selected UC Clients from manufacturers like:

  • Avaya
  • BroadSoft
  • Cisco
  • CounterPath
  • Microsoft
  • Zoom
  • NEC
  • Mitel

The scope of supported features varies between different UC Clients. Please compare the Jabra Direct datasheet for details.