Quantcast
Channel: Plantronics Developer Connection: Message List
Viewing all 377 articles
Browse latest View live
↧

Re: How to Mute headset controlled by other program?

January 27, 2014, 4:34 pm
$
0
0

HI Simon,

 

I am trying to determine if what you are seeing is a hardware or software issuel I did the following test:

  1. Run Lync without Spokes or any other software,
  2. Send an incoming call to Lync.
  3. Answer with Legend device and audio path is on.
  4. Remove device from ear.
  5. Manually mute from Lync user interface, the device is muted.
  6. Place device back on ear and device remains muted.
  7. Unmute from Lync or device mute button, device is unmuted;

 

Can you try doing the same test as above with your headset? If you are not getting the same results, do you have a second device to repeat the same test?

 

In the mean time I will do more tests on the software end.

 

Thanks,

 

Wei Chu


↧
Search

Re: DeviceStateChanged event with value DeviceState_RemovePending on removing device from PC

January 31, 2014, 2:25 am
$
0
0

Hi Viktor,

 

There is a problem with your archive - I cannot extract it. Could you try sending again?

 

Thanks,
Lewis.

↧
↧

Help!! Concept1 device on a Mac Virtualbox Host and Win7 Guest

February 1, 2014, 12:18 pm
$
0
0

Hello,

I am missing a step here trying to get the Concept1 motion tracking sample working on a Win7 Guest on a Mac running Virtualbox. I need one of the support folks to help!!

 

I followed the directions outlined in this blog below and successfully ran the Spokes Easy Demo v1.1.0.3 with the same BT300 USB and it can detect the Concept1 device

How to run Spokes in a mac or linux machine (for development)

 

 

I am now stuck here with the concept1 motion tracking sample. I successfully compiled it using Visual Studio 2012 Express but when I run it, it thinks there is no device connected.

 

13:18:17.374: Window_Loaded(): Head Track Demo - window loaded

13:18:17.374: Window_Loaded(): About to instantiate PLTLabsAPI object (version: 0.4)

13:18:17.499: DebugListAvailableDevices(): List of available devices:

> No device. (Waiting for Plantronics "Concept 1" head tracking device to be switched on and paired with PC dongle...)

 

 

Am I missing a driver install? Why does this sample not recognize the Concept1 whereas the other Spokes Easy Demo sample does?


Thanks

Anand

↧

Re: Help!! Concept1 device on a Mac Virtualbox Host and Win7 Guest

February 1, 2014, 6:36 pm
$
0
0

I need to add that I am currently trying to use Spokes SDK 2.8.38701.2 . Could that be the reason that the Concept1 samples does not recognize the device but  the EasyDemo v1.1.0.3 detects the device and do I need Spokes PreRelease 3.0 for the Concept1? If so, where do I download Spokes SDK 3.0 (so I can attempt the Concept1 samples).

 

Thanks in advance

Anand

↧

Re: Help!! Concept1 device on a Mac Virtualbox Host and Win7 Guest

February 4, 2014, 12:59 pm
$
0
0

Hey Anand,

 

Sorry for the delay in my reply.

 

Yes, there is actually a private space for the Wearable Concept 1.  I have added you to this private space.

 

Make sure you are logged in to your account and then go here....  Wearable Concept 1

 

Yes, you are correct, the Wearable Concept 1 only works with Spokes 3.0.  You can download Spokes 3.0 on the Wearable Concept 1 page.  I have also added you to our Spokes 3.0 Beta page found here --> SDK Beta Private Space (this has documentation and sample code)

 

Make sure you uninstall Spokes 2.8.2 first.

 

Feel free to send me a message or email me directly at greg.rose (at) Plantronics dotcom if you have any questions or need technical support.

 

Once again, sorry for the delay in my reply (and also not reaching out to your sooner)

 

Talk to you soon.

 

Greg.

↧
↧

Status of Spokes SDK for Mac OS X?

February 9, 2014, 6:55 am
$
0
0

What is the status of providing a Spokes SDK for Mac OS X? A forum post from a year ago said it's "coming soon" but no updates or hints since. An update would be most appreciated.

↧

Re: Status of Spokes SDK for Mac OS X?

February 10, 2014, 3:31 am
$
0
0

Hi,

 

Thanks for your question to PDC.

I will try to find out when the Mac SDK will be available and update you shortly...

 

Thanks,
Lewis.

↧

Bad LED behaviour with C310 and SpokesSDKComSample

February 10, 2014, 3:25 pm
$
0
0

Hi all,

 

I am experimenting with Blackwire C310 and the SpokesSDKComSample and there is some bad behaviour.

 

To simulate a call pickup and release I go through the following steps:

 

1. I plug the C310 in the USB

2. I run SpokesSDKComSample

3. The green LED immediately turns ON. this is undesirable, why it happens ?

4. I type the command "incoming" with any given contact name and call id

5. Correctly the green LED blinks and a ringtone sounds on the headset.

6. Also the screen issues:

      Session Event: Event Kind (Unknown) Call State (CallRinging) Call Id (1)

      SM Event: EventKind (Unknown) Call State (CallRinging) Call Id (1)

7. I pick up the call pressing the upper headset button

8. Correctly the green LED turns on and the ringtone stops.

9. Also the screen issues:

      Device Event: TalkPressed

      ***Suppressing dial-tone in IDeviceListener.

      Device Listener Event: HeadsetButton Talk

      Session Event: Event Kind (Unknown) Call State (AcceptCall) Call Id (1)Device Event: ButtonPressed Talk

  

      Session Event: Event Kind (Unknown) Call State (CallInProgress) Call Id (1)

      SM Event: EventKind (Unknown) Call State (CallInProgress) Call Id (1) 

10. To end the call I press again the upper button 

11. The screen issues:

      Device Event: TalkPressed

      ***Suppressing dial-tone in IDeviceListener.

      Device Listener Event: HeadsetButton Talk

      Session Event: Event Kind (Unknown) Call State (TerminateCall) Call Id (1)

      Device Event: ButtonPressed Talk

      Session Event: Event Kind (Unknown) Call State (CallEnded) Call Id (1)

      Session Event: Event Kind (Unknown) Call State (CallIdle) Call Id (1)

      SM Event: EventKind (Unknown) Call State (CallEnded) Call Id (1)

      SM Event: EventKind (Unknown) Call State (CallIdle) Call Id (1) 

12. BUT the green LED remains ON. this is also undesirable.

13. Also I don't understand the meaning of the event shown above:    

      "SM Event: EventKind (Unknown) Call State (CallIdle) Call Id (1)"

  

For me there is bad behaviour in (3) and (12): the green LED should not be ON in those steps.

That doesn´t happen if I Use C310 with Skype integration. Green LED does as I expect turning OFF when due.

 

What I need to do with SpokesSDKComSample to solve that ?

 

Best regards,

Julio.

↧
Search

Re: Bad LED behaviour with C310 and SpokesSDKComSample

February 11, 2014, 3:39 pm
$
0
0

Hi Julio,

 

I looked into the issue as you reported, but I was unable to reproduce the issue with SpokesSDKCOMSample and C310 device. If this is a software issue then it should show up not only on the C310, but any other Blackwire devices. I checked with our QA team and here had not been a report of this issue on record with any device. Without being able to reproduce that, all I can do is to speculate and suggest reinstalling the latest SDK and rebuilding the sample code and retry and see if you are still getting the same problems. Do you also have another Blackwire device that you can try reproducing this problem?

 

In Spokes the same activity may trigger events to happen in different Spokes object layers.

 

            Session Event: Event Kind (Unknown) Call State (CallIdle) Call Id (1)

            SM Event: EventKind (Unknown) Call State (CallIdle) Call Id (1)

 

means that the call state changed event (to Call Idle) triggered a Session event and a Session Manager event (sm event).

 

Wei

 

↧
↧

Re: Status of Spokes SDK for Mac OS X?

February 12, 2014, 6:14 am
$
0
0

Hi again,

 

I have the following update regarding Spokes SDK for Mac OS X: "we will publish our plans on PDC in early March for multi-platform SDK roadmap, they are currently under development."

 

Thanks,

Lewis.

↧

Re: Bad LED behaviour with C310 and SpokesSDKComSample

February 12, 2014, 1:42 pm
$
0
0

Hi Wei,

 

  I reinstalled the latest SDK 86496-00_Plantronics_Spokes_SDK_2.8.38701.2 and rebuilded the SpokesSDKCOMSample.

  As the sln that comes with SDK is for Visual Studio 2008, and I have only VS2010 and VS2012 I loaded the sln in both versions (with the inevitable upgrades). The results were the same:

 

  The sample running in VS2010 shows the LED problem I described in the original post.

  The sample running in VS2012 also shows the LED problem I described in the original post.

 

  For now I have only one unit of Blackwire headset with me, the mentioned C310.

 

  I should add that the green LED turns off correctly in the following cases:

  (a) When we the use command "endcall" BEFORE the user picks up the call (a call cancelation),  and

  (b) When we the use command "endcall" AFTER the user picks up the call (a call release "from the remote end")

 

  The problem of LED staying ON only happens, as described in the original post:

  (c) When the user presses the upper button to end the call AFTER he picked up the call (a call release "from the near end")

 

 

  It's a fact that when I run in another PC (with the deployment PlantronicsURE 2.8.38701.2, same version as SDK's, installed) this C310 works perfectly with Skype in all respects, including the LED behaviour.

 

 

  Any ideas ?

 

Best regards,

Julio.

↧

Re: Bad LED behaviour with C310 and SpokesSDKComSample

February 13, 2014, 7:26 am
$
0
0

Hi Julio,

 

I have taken a look at this also with Blackwire C320 and find some slightly strange result.

 

I also tested with SpokesSDKComSample, result:

- LED came on when first running.

- Incoming call test flashed LED, rang headset

- Answer: LED is on

- Terminate: LED went off the first time

- Repeating the above steps the LED stays on at the end of the call

 

Now I repeated the whole test with C++CallControl sample code (available here):

- Note: if LED was stuck on from before, make a Skype call to clear it

- LED remained off when running sample

- Type: incoming

- LED flashed, rang headset

- Answer: LED is on

- Terminate: LED went off ok

- Repeated above test and it seems to be ok

 

Both sample codes use same Spokes COM Service API. Therefore it is possible that SpokesSDKComSample has something in it that is causing a problem with the Spokes C300 Series device behaviour in Spokes.

One thing that SpokesSDKComSample does have is a hack to try to suppress Lync dialtone functionality. It is possible that is affecting the behaviour with this device.

 

Try both samples and compare the implementations, and read about the dialtone hack, then see if you can get C310 working better.

 

Let us know how you get on ,

Lewis

↧

Softphone incoming call contact....

February 13, 2014, 2:44 pm
$
0
0

Scenario:

 

Softphone - In the integration with Spokes, the softphone makes call to m_spokes.IncomingCall(callid, contact)

 

Other app - OnCall gets raised with callid, but where/how can I get contact?

 

Thanks

↧
↧

Facing a problem with Savi 7xx and C++ COM Service

February 14, 2014, 12:36 am
$
0
0

Hi All,

 

We use Spokes SDK (2.7.14092.0) COM Service in order to get Savi 7XX events and manages its state from our C++ application running on Windows 7.

When our application start-up, it creates a SessionManager as indicated in C++ Samples you provide:

 

      // initialize COM

      ::CoInitializeEx(NULL, COINIT_MULTITHREADED);

 

      m_trace.info (_T("Connecting to SPOKES session manager"));

      // Get session manager from

      HRESULT hr = S_OK;

      if (SUCCEEDED(hr = ::CoCreateInstance(CLSID_SessionComManager, NULL,CLSCTX_LOCAL_SERVER, IID_ISessionCOMManager, (LPVOID*)&sessMgr )))

      {

 

If PlantronicsURE.exe startup while Savi 7XX ISDN line is opened, CoCreateInstance never returns and our application remain stuck in this function call.Savi7XX.jpg

 

I’ve tried to upgrade Spokes SDK to the latest available version (2.8.38701.2) but issue still occurs.

 

Currently, the uncomfortable work-around we’ve found is:

  • To terminate our application
  • Kill PlantronicsURE.exe process
  • Press ISDN line button on the Savi7XX base in order to turn the line off (led switched off)
  • Restart our application

 

Case 5005000000QVWZS has been opened yesterday by sending mail 'pdcsupport@plantronics.com'.

 

Regards,

Chris.

↧

Re: Facing a problem with Savi 7xx and C++ COM Service

February 14, 2014, 10:46 am
$
0
0


>>If PlantronicsURE.exe startup while Savi 7XX ISDN line is opened, CoCreateInstance never returns and our application remain stuck in this function call.


This looks like a bug in our COM Server implementation. We will have a bug logged and investigate this issue.

↧
Search

Re: Facing a problem with Savi 7xx and C++ COM Service

February 15, 2014, 1:01 pm
$
0
0

Thank you Ramesh.

 

Please, keep us informed about bug resolution.

Is there a periodic cumulative patch release?

When shall we expect a fix build?

 

Chris.

↧

Re: Bad LED behaviour with C310 and SpokesSDKComSample

February 17, 2014, 4:31 am
$
0
0

Hi Lewis,

 

  I got solved the problem from the OP, but I still have an issue.

 

  I read about the hack, then ran the CallControl sample: the LED showed right behaviout. Fine!

 

  Then I went back to SpokesSDKCOMSample and verified that inside KeepDialToneSuppressed(), commenting out the line "deviceListener->InCall(true);" was enough to solve the LED problem. Very Fine !

 

  The issue that remains shows up as follows (in either SpokesSDKCOMSample or CallControl programs):

  - Type "incoming" in the sample program.

  - Pick up the call pressing hook button. Events show up in screen, green LED turns ON. Fine.

  - Type "endcall" to simulate a termination caused by the remote side. Events show up in screen, green LED turns OFF. Fine.

  - The issue is that from that moment on, pressing the hook button does not cause any Device events to happen (don't show up in the screen)

    For the application this is a sort of bug. I noticed, however, that if one presses any other headset button, the hook button starts to generates events again.

  

  I found out that if one adds an invocation to KeepDialToneSuppressed(true) after executing "callcommand->TerminateCall( call );" inside

  the processing of command "endcall" the program can overcome this new issue.

 

  I dont understand why "deviceListener->SuppressDialTone(true)" relates to hook button events notification!

  What is happening in this scenario ?

 

  Also I am worried that these workarounds fail once in a while.

 

Best regards,

Julio.

↧
↧

Calisto P240 questions

February 18, 2014, 12:23 am
$
0
0

First of all, sorry for my English.

 

I'm Windows softphone application developer. The softphone works with numerous USB phones. Calisto P210M was very good USB phone because of it's hardware quality. It was supported by our softphone as raw HID device, as well as the other USB phones. The main inconvenience about P210M was unavailability of detecting key press time, but overall impression of the device was very good.

 

Now P210M is discontinued and I'm searching for replace. Our company bought P240 (actually they sold us P240-M) and I tried to use it. I've tried to use it as raw HID device, I've tried to use Spokes SDK, I've used it with Skype. I've got some questions:

 

1. How could I make this phone to send numpad key press events just after key press, without waiting for "Dial" key?

2. Can the phone work with Cyrillic symbols?

 

Actually I'd like to work with USB phone with no logic, no phone menu (set every pixel of dot-matrix display from PC, receive every key press event for all phone keys, etc.) Almost every prevalent China USB phone works like this, and it's very comfortable for us to work with such phones. However, hardware quality of that phones usually is low, so I'm posting my questions here.

↧

Re: Softphone incoming call contact....

February 18, 2014, 10:07 am
$
0
0

Hi Jose,

 

A softphone application uses the Spokes SDK IncomingCall method to notify Spokes about an incoming softphone call. (Refer to section 2.11.4.1 in this document: Spokes SDK 2.7 Documentation)

The contact parameter provides the softphone with a way to let Spokes know who the caller id/name of the incoming call is, and Spokes may then subsequently display that information on a Plantronics "display device" (Calisto 800 / Calisto P240).

 

When another Spokes-supported softphone goes on a call, for example Skype or Lync, the Spokes SDK provides call state events (via ISessionCOMManagerEvents_Event CallStateChanged events) that include the unique call id of that call that Spokes is using to track it. However, Spokes does not expose the contact information (caller id/name) via the Spokes SDKs (COM Service / COM Service .NET Interop / REST Service).

 

However, if you install the full Spokes software from Plantronics | Support | Downloads & Apps and during install choose a Custom install and add the "Logging" component (normally is not installed), this component will log in near realtime call events to a log file called:

 

%localappdata%\Plantronics\logs\SpokesLog.xml

 

For some of the Spokes-supported softphones you can find the caller id/name in the <ContactInfo> tag in this file.

 

Have fun!

Thanks,

Lewis.

↧

Re: Softphone incoming call contact....

February 19, 2014, 12:03 pm
$
0
0

Maybe a "nice to have" for the next release of Spokes?  I understand about the xml file, however, I am looking for a real-time solution, not a near one.  Horseshoes anyone?  :-)

↧
Viewing all 377 articles
Browse latest View live
Search