The following sections displays a selection of use cases for device integration.
Device integration enables the transmission of control signals between device and UC Client. This enables a UC Client to use hardware functionality like hardware buttons or a hardware ringer.
As an unwanted side effect of device integration, control signals can be misinterpreted by UC Clients. This can cause erratic system behavior in specific settings.
All presented integration example in this section work with:
- Windows operating system
- Two different UC Clients
- A single Jabra Engage 50 headset with hardware ringer and hardware controls
The types UC Clients and the number of calls varies.
Actions can be triggered by:
- Button presses – Manual button presses by the user either on the Hardware Controller or in the UC Client Software.
- Automatic Actions – Triggered by an incoming call or a control signal.
The system should always behave consistent. Consistency means, that an end-user can expect a certain system behavior.
Consistent behavior has been defined as:
- Ringer status – The hardware ringer has to ring for incoming calls, if the device is not busy with an active call.
- Hardware Button Presses should not result in having to active calls in parallel by accident. Appropriate device integration does prevent this.
- Software Button Presses can result in having two active calls in parallel. This is usually not a desired state, but there is no technical way to prevent that. The user has to remember to hang up an active call before accepting another incoming call.
In real-word scenarios, you can configure desired system behavior differently.
Software Buttons are flexible. UC Clients display adapted Software Buttons for specific call situations.
Software Buttons for the presented use cases are:
|Type of Call||Software Button Name|
|Active Call||- End call|
|Incoming Call||- Accept call
- Decline call (often using same button icon as End call)
|No Call||- Start call (often using same button icon as Accept call)|
The functionality of Software Buttons in UC Clients is given without any device integration. Unsuitable device integration, however, may lead to unwanted interference between different UC Clients on the same system.
Hardware Buttons are not flexible. Hardware Buttons are neither dedicated to a certain UC Client nor adapted to a specific call situation.
Example for Hardware Buttons:
- Engage 50 hardware controller: uses the same button e.g. for Accept Call, End Call and Decline Call.
- Engage 75 base station: different buttons for Accept Call and End Call/Decline Call
Device integration is required to enable basic functionality of Hardware Buttons and to ensure the correct interpretation of control signals in UC Clients.