Connecting two Plantronics devices to the same PC.

5 posts / 0 new

Fri, 10/04/2019 - 08:15

krzysztof.gorcz...

Is it allowed to use two Plantronics devices: SAVI W745 and Calisto 610 on the same PC? I need to connect that devices to single PC and handle call answer/terminate events from both devices separetly in our application. If this is possible, is it enough register for call state changed events as it is described in your Code sample page? ...

_session.onCallStateChanged += _session_onCallStateChanged;
...

Mon, 10/07/2019 - 00:15

lcollins

Hi, If you use the recommended COM or REST APIs then you can support multiple Plantronics headsets attached to same PC. However, the user would select the "primary" meaning call control headset from the Plantronics Hub application on system tray, using the Make Primary option on About page. Only 1 device can be the primary. The recommended code samples are at: https://developer.plantronics.com/article/softphone-integration-code-samples (click the C#/C++ COM/Java or JavaScript Tabs, depending on your language). Also take a look at the further guidance and recommendations below... Thanks, Lewis. -- Details of Hub SDK and recommended sample codes for integration of softphone/contact center solution: SDK download: https://developer.plantronics.com/softphone-integration-hub-sdks Hub download: https://www.plantronics.com/software The Hub APIs for softphone integration are COM (for Windows) or REST (for Windows and Mac). Benefits of using Hub’s COM/REST APIs: Support new products Forward-compatibility to new Hub versions Support multiple products attached to same PC (the primary device is selected via Plantronics Hub GUI) Support multiple softphones on same PC and make your solution multi-softphone aware via Hub call state events Your solution will support Plantronics Manager Pro, read more: https://www.plantronics.com/ae/en/services/plantronics-manager-pro https://developer.plantronics.com/article/so-what-plantronics-hub-and-why-should-i-care-about-it-my-application Hub SDK deployment options: https://developer.plantronics.com/softphone-integration-api-overview#DeploymentOptions The recommended code samples are at: https://developer.plantronics.com/article/softphone-integration-code-samples (click the C#/C++ COM/Java or JavaScript Tabs, depending on your language). Useful design patterns: Consuming COM or REST API in a separate worker thread: C# COM sample: https://developer.plantronics.com/article/advanced-sdk-topic-ensuring-resilience-plantronics-com-api A requirement for COM API is that COM API calls are all on same thread, plus having the integration on a separate worker thread effectively isolates your application from and COM API errors/timeouts, for example when Hub / Hub SDK is not installed! C++ REST sample: https://developer.plantronics.com/article/hubrestsample-new-c-rest-api-sample-pdc For REST API having the REST API calls on worker thread allows retries/reconnects of the API connection for example when there is no headset attached or Hub is not running. Browser-based JavaScript integration, suitable for WebRTC softphones: We also have a “live” demo of browser-based headset integration: (Pre-requisite is that Plantronics Hub is installed). It is located here and allows the partner to play with the API, trying out all the call control features needed for a browser-based WebRTC softphone: https://pltdev.github.io/Plantronics%20JavaScript%20Sample.html

Mon, 10/07/2019 - 07:46

krzysztof.gorcz...

Hi, Thank you for that info. Do you know, if is it possible to set primary device via API? Or the Plantronics Hub software is the only option? In my app, I use code samples taken from: https://developer.plantronics.com/article/softphone-integration-code-samples and C# language.

Mon, 10/07/2019 - 10:10

lcollins

Hi, It is not possible to set via API But you can know which product is attached via api, as per the samples, which receive deviceattached from sessionmanager level events interface for example with product name and product id

Fri, 10/11/2019 - 04:43

krzysztof.gorcz...

Hi, I tested both devices and as you wrote, when one of them is selected as primary, then answer/terminate call events can be easly handled. Howewer it is significant drawback that it is not possible to handle events from both devices separately, or at least select primary device via API. We are trying to develop application which allows to use different kind of audio devices like hands free mode, headset etc. and user should be able to change the active audio device from our application. Using Hub software is bulky for that purposes. Are you going to implement selection primary device via API in the future?

Add new comment