![]() The Call Manager creates an outgoing call instance and manages it based on user action. The Device Listener will get the call request and propagate it to the Call Manager. Display devices with keypad, contact list or call log can make call requests to the Device Manager. The Call Manager also handles outgoing calls initiated from a device. A well defined behavior for talk and flash button presses and to round robin between multiple calls across soft phones is implemented in the Call Manager. The Call Manager will be able to support multiple calls from the same soft phone or from different soft phones. There will be only one active call that can go through transitions based on the user action on the device or on the soft phone. The Call Manager will also manage instances of active and held calls. The Call Manager will support devices with single (VoIP only) and multiple channels (VoIP, PSTN, Mobile). The Call Manager interfaces with the Device Listener and the Session Manager and provides call control functionality. Interfaces with the Call Manager and the Device Listener and propagates events and commands from and to the Plantronics API clients.Handles all incoming Plantronics API client requests.The Session Manager provides the following functionality: The Session Manager will expose interfaces for call handling, device state and events, sending alters, and media player control. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |