Interop.Plantronics.COMSessionManager throws exception with Plantronics Hub v 3.8

6 posts / 0 new
Log in or register to post comments
Last post
Fri, 05/20/2016 - 14:21
#1
abhirajgandhi@g...
Interop.Plantronics.COMSessionManager throws exception with Plantronics Hub v 3.8
Our softphone client uses, Interop.Plantronics.dll (Spokes SDK) v3.6, to interact with Plantronics headset. We have tested this spokes DLL with Plantronics Hub v3.6 and v 3.7, and it is working fine. We are able to use supported functionality for headset given in Softphone client. Today, we upgraded our Plantronics Hub from v3.7 to v3.8 and tried to use it. The Plantornics SDK integration of softphone client has stopped working. On looking in to our logs, we found that when we create a instance of  Interop.Plantronics.COMSessionManager, it is throwing a COM exception.. Following is the COM exception. Failed to connect to Spokes ---> System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {750B4A16-1338-4DB0-85BB-C6C89E4CB9AC} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)). Our Interop.Plantronics.dll is of v 3.6 while we have upgraded hub to v3.8. Let me know if you need more information. Thanks, Abhiraj
Top
Sat, 05/21/2016 - 10:15
lcollins
Hi Abhiraj,<br /> <br /> I have just completed the same test compiling a C# .NET sample that references Interop.Plantronics.dll.<br /> I compiled the application with Plantronics SDK v.3.6 installed.<br /> I then uninstalled Plantronics SDK v3.6 and installed Plantronics Hub v3.8 (the current one from www.plantronics.com/software)<br /> <br /> On doing this I am still able to run the application.<br /> <br /> I have attached the sample code I am using: <a href="http://developer.plantronics.com/files/spokes3gsdksampleszip-0">click here.</a><br /> <br /> <br /> Somthing to remember is *you should* embed interop types, and also you should not deploy (distribute) your own copy of Interop.Plantronics.dll.<br /> Your application should find this automatically in the Plantronics Hub (or Plantronics SDK) folder under C:\program files (x86)\plantronics<br /> <br /> These are the settings for referencing the interop dll<br /> [[{"fid":"96","view_mode":"default","type":"media","attributes":{"height":"368","width":"782","class":"media-element file-default"}}]]<br /> <br /> Here is a screenshot of the 3.6 sdk compiled appplication running successfully after Hub 3.8 was installed:<br /> <br /> (<a href="http://developer.plantronics.com/sites/default/files/3.6%20linked%20.net%20app%20runs%20on%203.8%20hub.png">view full image here</a>)<br /> <br /> [[{"fid":"97","view_mode":"default","type":"media","attributes":{"height":"919","width":"1527","class":"media-element file-default"}}]]<br /> <br /> Let me know if that helps<br /> Cheers,<br /> Lewis.
Top
Tue, 05/24/2016 - 13:10
abhirajgandhi@g...
Hi Lewis,<br /> <br /> Thanks for your response.<br /> <br /> The last update shared that issue is getting reproduced with Plantronics v3.8 was actually a configuration issue in design setup and is not the root cause of this issue. The configuration issue was due to Plantronics Hub and softphone app running on different levels of access on my PC. Softphone running on administrator level while Hub was on normal user level. When both were at same level, this issue was not seen. I was misguided by this issue as a real issue, however this was not so. On further investigation, I have identified the issue and it seems to happen with Hub v3.8 We have used spokeswrapper.cs as reference code, to provide support for plantronics headset. for Incoming call we have used following code ..<br /> public bool IncomingCall(int callid, string contactname = &quot;&quot;) { bool success = false; try { if (m_comSession != null) {<br /> ContactCOM contact = new ContactCOM();<br /> contact.SetName(contactname);<br /> CallCOM call = new CallCOM();<br /> call.SetId(callid); m_comSession.GetCallCommand().IncomingCall(call, contact, CallRingTone.RingTone_Unknown, CallAudioRoute.AudioRoute_ToHeadset);<br /> success = true; } } catch (Exception) { success = false; } return success; } <br /> <br /> We pass a incremental number as &quot;callid&quot; for each call in &quot;call.SetId(callid);&quot; However, when we try to retireve the call from hub and the &quot;callid&quot; retrieved is altogether different. It is not the same &quot;callid&quot;, which we had passed and therefore our headsupport to answer an incoming call is getting affected. Would request to have a look and comment further... Following is an update on the question asked by you in the last notes... We are distributing &quot;Interop.Plantronics.dll&quot; v3.6, with our softphone client. I will also recommend the design team to refer this DLL from installation path, rather distributing with the softphone client. But, it use to work with v 3.7 but not 3.8 is hard to understand. Also, here are my settings for referencing the interop DLL. ..\ThirdParty\Plantronics\Interop.Plantronics.dll True Thanks, Abhiraj
Top
Fri, 05/27/2016 - 05:39
abhirajgandhi@g...
Will appreciate a response on this...
Top
Tue, 05/31/2016 - 07:27
(Reply to #4)
lcollins
Please take a look at the comment on your new thread:<br /> <a href="/plantronics-hub-v38-not-working-call-control-softphone-client#comment-151"><span style=""><span id="F40.wrapper"><span class="F40 ControlStyle" id="F40" style="">http://developer.plantronics.com/plantronics-hub-v38-not-working-call-control-softphone-client#comment-151</span></span></span></a>
Top
Thu, 06/02/2016 - 10:26
abhirajgandhi@g...
<span style="color: rgb(72, 72, 72); font-family: Arial, sans-serif; font-size: 13px; line-height: 18px; background-color: rgb(250, 250, 250);">Great to hear, come back to us if you have any more questions!</span>
Top

Add new comment