The Jabra SDK for Linux contains libraries, examples, and documentation to integrate the digital features of Jabra devices into applications on Linux (Ubuntu and derivatives).
The SDK supports the following environment:
These are the system requirements for running the demo app and the apps built with the libraries.
Make sure the system requirements are met and unzip the SDK archive to a folder on your file system.
You can then launch the demo app present in the demo folder to test the connection to an attached Jabra Device. Please note that for the demo to run, you need to add the SDK folder containing the libjabra.so file to the LIBPATH, or copy the file to a folder that is already in the LIBPATH (see user guide for more details).
1) GN USB HID usage pages always used in communication with devices
*Potential breaking change*
In previous versions of the SDK, the Jabra core library would use the HID usage pages (Standard USB or GN) configured through using the Jabra_SetHidWorkingState function to exchange commands and data with a Jabra device.
From this version, the Jabra core library now always uses the GN HID usage pages to communicate with the device. In fact, this was one of the original design goals of introducing the GN specific usage pages, allowing better support for multiple concurrently running softphone applications on the client computer.
This means that it is no longer possible to communicate with a device through the Jabra SDK libraries using the standard HID USB usage pages. For most application developers, this will make very little difference. Only if you rely on operating through the SDK libraries in standard USB HID protocol for whatever reason will this be a breaking change. However, this also means you can stop using Jabra_SetHidWorkingState to switch to GN HID when you need to communicate with the device, as this is no longer needed.
2) Expanded support for device telemetry:
Reading telemetry data (aka “the logging interface”) can now be enabled for Jabra Engage 50, 65 and 75, as well as Jabra Evolve2 40, 65 and 85.
Note that the scope of telemetry data varies slightly depending on the capabilities of the device. For example, only Jabra Engage 50 supports boom arm position data and defective microphone detection.
3) Support for DECT telemetry from Jabra Engage 65 and 75
A new callback function for DECT reporting has been introduced to allow receiving DECT density and DECT error counters telemetry data from Jabra Engage 65 and 75 devices.
- Various minor incremental bug fixes and enhancements