Jabra provides a range of SDKs for different integrations. This page gives an overview about all aspects of choosing the most suitable SDK variant for your specific integration task.
Gen.2 vs. Gen.3
Gen.2 SDK variants are the first choice for most integration projects. These SDKs are stable, maintained and provide full feature support for a wide range of professional Jabra devices.
Gen.3 SDK variants should be used only for specific integrations like Call Control running in a browser. This generation supports newest features like WebHID and Easy Call Control. But it is restricted to Call Control as the main feature. Which means that advanced device features like Data Telemetry are not supported.
Supported Client Platforms
SKD variants differ in platform support:
|SDK Variant||Generation||Integration Option||Windows||macOS||Linux||ChromeOS|
|SDK for Browser||Gen.2||Web Application with Chrome Host||✔||✔|
|SDK for Linux||Gen.2||Native Desktop Application||✔|
|SDK for macOS||Gen.2||1) Native Desktop Application||✔|
|2) Objective-C Desktop Application||✔|
|SDK for Node.js||Gen.2||Node.js Desktop Application||✔||✔||✔|
|SDK for Windows||Gen.2||1) Native Desktop Application||✔|
|2) .NET Desktop Application||✔|
|SDK for .NET||Gen.3||.NET Desktop Application||✔|
|2) Web Application with WebHID||✔||✔||✔||✔|
|3) Contingency Integration
- Web Application with Device Connector
- Web Application with WebHID
|4) Node.js Desktop Application||✔||✔||✔|
|SDK for PanaCast||Independent||1) Native Desktop Application||✔|
|2) .NET Desktop Application||✔|
* Runs only as "Web Application with WebHID" under ChromeOS.
SDK feature support mainly depends on the SDK generation:
|SDK Feature||Gen.2 SDK||Gen.3 SDK||Panacast SDK||Description|
Call Control provides various options to control calls via hardware button presses. Please compare the Call Control documentation for details.
Call Control is demanding to integrate but suitable even for complex use cases.
|Easy Call Control||✔||Easy Call Control is an optional helper module for the integration of Call Control.|
|Camera Features||✔||Controls features like:
Telemetry can provide a deep insight into the use of Jabra devices. It is based on datapoints delivered by compatible devices.
All supported datapoints are documented in the Telemetry Datapoint documentation.
Device Settings control various settings of Jabra devices.
This feature can improve user experience and call efficiency for specific use cases.
|Firmware Management||✔||Monitor firmware versions, download new firmware and update devices via Jabra Firmware Updater.|
|Button Customization (Remote MMI)||✔||
Button Customization takes control of busy lights and programmable buttons in Jabra devices.
Customized buttons and busy lights can speed up and simplify common user interactions with applications.
Device Discovery identifies a Jabra device, its serial number and its affiliation to a specific user or PC.
Areas of application:
This feature is especially useful in enterprise environments with a large number of devices.
|WebHID for Call Control||✔||This supports direct interaction for Call Control with Jabra devices via a browser-client.
Example SDK Gen.2 (without WebHID support):
You develop a browser-based application based on SDK Gen. 2. Every client, that uses this application, needs to install additional software locally (Jabra Browser Extension and Jabra Chrome Host).
Example SDK Gen.3 (with WebHID support):
You develop a browser-based application based on SDK Gen.3. All clients can use your browser-based application without additional software.
The integration of PanaCast devices differs from other Jabra devices like headsets or conference speakers.
PanaCast devices are supported by selected SDK variants:
|SDK Variant||PanaCast (2019 model)||PanaCast 20 & PanaCast 50|
|SDK for PanaCast||✔|
|SDK for Linux||✔|
|SDK for macOS||✔|
|SDK for Windows||✔|
Feature support depends on the PanaCast model:
|PanaCast Feature||PanaCast 20||PanaCast 50||PanaCast (2019 model)|
|Image controls (1)||✔||✔||✔(2)|
|Pan, tilt, zoom||✔||✔||✔(2)|
(1) Brightness, contrast, saturation, sharpness, white balance.
(2) Only available through the USB Video Class (UVC), not the SDK libraries.
(3) Zooms onto the speaker.
(4) Zooms onto the speaker or audience.
(5) Only available through the PanaCast SDK
Feature support depends on more factors than just the chosen SDK variant.
Relevant factors are for example:
|Device model||The feature Programmable Buttons requires devices that actually have such a button. The hardware controllers for Engage 50, Engage 50 II and Engage 40 provide corresponding buttons.|
|Device variant||Most devices are available as UC Client and as MS Teams variant. Depending on the software environment, these devices may behave differently.|
|Firmware||New firmware versions for a device fix can detected bugs and provide support for additional features.|
|Device connection||You can connect Bluetooth devices either with supported Jabra bluetooth dongles or with a native Bluetooth connection or a generic Bluetooth dongle. But only supported Jabra bluetooth dongles are compatible with Jabra SDK.|
|Device setup||Jabra Engage 50 II: You can use this headset with or without the hardware controller Jabra Engage Link 50 II. The controller adds functionality like programmable hardware buttons to the headset.|
|SDK version||Newer versions of SDK variants can provide additional functionality or device compatibility compared to older versions of the same SDK. Please check the Release Notes of the respective SDK for details.|
|Implementation choices||Jabra SDK for Windows supports two different programming environments (native applications and .net applications). Feature support varies accordingly.|