Introduction
You have two ways to work with SDK for Windows:
| Programming language | Description | Target Application |
|---|---|---|
| C | Direct addressing of the C-library (low level). | Native Desktop Application |
| C# | Indirect adressing of the C-library via C#-wrapper (high level). | .NET Desktop Application |
This introduction covers general topics which are relevant for both approaches.
Known Limitations
This SDK does not work for Windows Apps in Microsoft Store.
Libraries
The extracted .zip-file of SDK for Windows contains several library files.
Relevant library files are:
| File path | Description |
|---|---|
| library/[platform]/libjabra.dll | C-library for the respective platform (x86, x64 and ARM64). |
| library/[platform]/JabraSDK.dll | C#-wrapper (x86 and x64) |
| library/Headers/ | Folder containing all header files for the C-library. Header files contain functions, structures, definitions and descriptions of all C-library features. |
Logging
Logs are essential to monitor your application and especially helpful during troubleshooting.
Log Levels
Log level can be defined by setting the environment variable LIBJABRA_TRACE_LEVEL:
| Log Level | Description |
|---|---|
info |
Normal system event. |
warning |
Indicator of undesired behaviour. This is the default setting for the logs. |
error |
Indicator of erroneous behaviour. |
fatal |
Indicator of unwanted shutdown or other severe malfunction. |
You can set the log level in System Environment Variables in Windows operating system.
Log Storage
Logs are stored in \Users\%USERNAME%\AppData\Roaming\JabraSDK\Logging by default.
- Application log file size is restricted to 10 MB. If a log exceeds this size, a new file will be created.
- 10 latest log files can be stored, after that on new log file creation the oldest log is deleted.
Bluetooth devices and dongles
- Jabra Bluetooth headsets support SDK for Windows only if paired with a compatible Bluetooth dongle.
- The USB dongle and the paired Bluetooth headset are shown as two separate entries in the list of connected devices of the SDK
Jabra Direct
UC Client applications developed with SDK for Windows do not require Jabra Direct on the target system.
Points to Remember
Concurrency
- Concurrency is maintained between all the applications which use SDK for Windows including Jabra Direct
Button Customization (Remote MMI)
- The button configurations should be cleared/reset on device unplug or exit of the application. The application should perform button configuration again on next start up
- The device does not provide any information on configured buttons. This can lead to problems when more than one application uses button customization.
Firmware Management
software developers have to register for the authorization token for the firmware updater
For firmware update feature, firmware updater application (JabraSDKFirmwareUpdater) needs to be installed. It will be downloaded from cloud as part of firmware file download for Jabra device from Jabra_DownloadFirmware API
Jabra_DownloadFirmware API to be called before calling firmware update API to get the firmware file path