onthewebtaya.blogg.se - Plantronics hub change language

The client applications can range from Soft phone (SP) and Media Player (MP) modules to other third party applications that want to interface with devices directly. The Hub Session Manager will be responsible for handling all incoming client sessions. From the Plantronics SDK application developers also have access to the current connected device IDevice and can register for all the events exposed in the device manager SDK. Once successfully loaded, soft phone and media player modules will register with Hub and use the Hub ICallCommand, ICallEvents and ISessionManagerEvents interfaces to send commands and to receive events from Hub. Soft phone and media player components are required to implement a common interface IPlugin and, based on the Hub configuration XML (PURE.XML), Hub will dynamically load these modules as part of the process start up. The Hub Plug-in is the single entry point for all external application interactions. The function of each module is described in following sections.

The Hub SW stack is depicted above and has several functional modules such as Device Manager, Device Listener, Call manager, Session Manager etc. This requires your application or Plantronics integration component to target. NET support for COM Service is via an Interop Assembly called "". Languages supported today by Plantronics API: The SDK comes with 4 Plantronics APIs - which one do I use with my application? The diagram below shows how these APIs are exposed by the Plantronics software. You can add Plantronics headset support to your application by using one of the four APIs included in the Plantronics SDK: In addition to the features supported by non display devices, display devices support caller ID for incoming and outgoing calls, ability to make call and send DTMF digits while on a call.

Display device : Display devices can be single or multiple interface devices and have a display and key pad on the device.

PSTN connection via a hard-phone and also may act as a BT endpoint for mobile phone to pair with.

Multiple interface device (VOIP, PSTN, Mobile): Multiple interface devices connect to the host via USB and also have connectivity with another interface e.g.

Single interface device ( VOIP Only ): Single interface devices connect to the host via USB and provide only VOIP call control with all supported soft phones in Hub.

Hub supported devices (corded or cordless) fall into the following categories: Docked/Undocked, Don/Doff, multiline call mangement etc.

Device state change notification support ( eg.

Pause, Stop media player while on a call ) Remote ring detection,hook switch control and dialpad) With the SDK, Hub supported Plantronics devices provide many features to endusers such as: The SDK exposes events for device button presses and device state changes, and also a set of commands that the host can send to the device. The Plantronics SDK provides an abstraction for many application needs, including soft phone and media player integration. The Plantronics SDK and Plantronics Hub (runtime engine) expose a set of interfaces for application developers to interact with Plantronics current and future devices.