Hi Julio,
It turns out that the firmware to handle the second inbound call (ringing while audio path is open) can be set from Spokes.
Launch PCP and go to Device settings and under the 'headset' tab (see below), there are 3 possible settings under second inbound call: ring continuously, ring once and ring ignored.
Wei Chu
Hi Wei Chu,
I need to configure this setting programatically, not through the use of PCP.
I can find in plantronics.device.common.tlh the method IDeviceSettings::put_ActiveCallRing (ActiveCallRing)
But IDeviceSettings doesn´t figure in the Spokes SDK Documentation and I don't know how to get a pointer to IDeviceSettings interface.
My class code is based in the SpokesSDKCOMSample, so I need a native C++/COM code snippet that gets access to IDeviceSettings interface and then invoke
IDeviceSettings::put_ActiveCallRing (ActiveCallRing::ActiveCallRing_RingContinuous).
Julio.
Hi Team,
As per Supported Products web page (http://www.plantronics.com/uk/support/software-downloads/business-windows.jsp) this Avaya product is not supported.
Product details: Avaya Support - Products - Avaya one-X® Attendant
I've contacted Avaya and requested an update on this. The call reference: SR#1-5116374667
I have also contacted your support team (ref: 03828138).
Could you advise what's the procedure, how can you cooperate with Avaya and implement this feature, please.
Thank you and kind regards,
Gyorgy
Hi,
Basic call control is supported for our headsets on oneX Attendant (r4.0 SP1) and greater, with Spokes installed. If you have other questions I can connect you with someone internally that can shed more light on the details.
Thanks,
Greg.
Hi Julio,
While you can get a pointer to IDeviceSettings by casting:
IDEviceSettings* phc = (IDeviceSettings*) device->hostCommand;
This however does not solve your problem. ActiveCallRing is simply a property of the class IDeviceSettings and put_ActiveCallRing simply assigns a enum value to this property without affecting the firmware or firmware behavior.
I do not know of any API at the SDK level that directly interacts with firmware to change the device behavior. No firmware level API is provided because that is risky as an error may ruin your device. Your best bet may be to configure the Legend device with PCP prior to using it with your applications.
I would check if anyone knows of a work around even though the chance may be remote.
Wei Chu
v
hc = Device.HostCommand asIDeviceSettings;
Debug.Assert(hc != null);
Hi Greg,
Thank you for the update. Unfortunately it's not working for me (the button on the headphone has no affect on the Avaya application). Could you point me in the right direction, please.
Kind regards,
Gyorgy
Please help me in this...
how can i make my heaset auto-answer an incoming call. I am using avaya one-x communicator 6.1. sp9 version.
Hi Guys
Making some good progress and I'm onto testing different call scenario's. One I am stuck on but perhaps it's more my approach that is wrong.
If the user presses the button on the headset to clear the call.. but if the call is not in a state to clear. ( For example in my case if the call is in 'Hold' state locally the softphone API does not allow you to clear the call). , then I get out of sync with the call. Spokes seems to assume the call ended successfully and therefore any further presses of the button do not create a CallEnded event. ( only a button pressed)
What I am used to with CTI development is that the request to do something does not update the state. e.g I should request to clear the call.. and then the event back stating the call has cleared will update the Spokes state so it knows the call has cleared. I guess the call ended event from Spokes is not really a request to end the call.. but just informing the SPOKES call State has changed?
Perhaps this is a limitation / approach due to the way the events are being created in the SpokesWrapper? ( I'm developing in VB.Net)
Your thoughts on what the best approach is would be greatly appreciated.
Thanks again
Rob
Hi,
Your question is not related to integrating the Plantronics SDK (Software Developer Kit).
However, it is my understanding that the Avaya One-x Agent product supports an Auto Answer feature, but the feature has to be enabled in the Communication Manager (back-end software). It would appear this is not supported with Avaya One-x Communicator product.
Thanks,
Lewis
I have simplified the approach.
I now ignore all events from spokes other than the button press. I keep track of the call state ( Or call states when we have multiple calls) in the adapter and then handle the click accordingly.
It means I can create rules around how to handle a 'click' when a call is on hold, when there is more than 1 call etc.
Seems too simple.. but so far it seems to work fine.
Cheers
Rob
Hi Rob,
When you use the High-level call management feature of Spokes, and you have inserted a call into Spokes call state (via IncomingCall/OutgoingCall/CallAnswered functions), if user presses "Talk" button to terminate the call, Spokes does several things:
- It throws away it's record of that call
- It closes the audio link to device (wireless products)
- It notifies your app via "CallStateChanged" Session Manager Event (CallEnded event)
If at this point you didn't want to end the call (call was still active in your softphone), a workaround to automatically reopen the audio link to device would:
- Open a call with Spokes with the same "callid" as was just ended
Below is some C# code based on the EZ Demo sample that in order to test your scenario I added a check box called "preventcalltoterminatewithtalkbuttonChkBox".
- When this check boxed is checked it re-opens the call that was ended with "Talk" button of headset
- The DoReopenCall marshalls the call to Spokes "OutgoingCall" function back onto the GUI thread - this is needed otherwise the OutgoingCall fails.
This is a workaround to be able to reopen the link. It has a problem that if call was previously Incoming direction, the reopened call will show Outgoing direction in the Spokes event, but with same internal "callid".
However, this may not be a problem as your softphone itself will generally know the call direction without Spokes needing to tell it.
I saw from your recent post that you have overcome the problem by just listening for button press only.
The only slight caution I would give on this approach is:
- Our Savi 700 Series product (multi-line device) will pass "Talk" button press events when you are doing call control of Desk phone line or Mobile line. You need to ensure these events don't inadvertently control your softphone line!
Let us know how you get on or if you have further questions!
Thanks,
Lewis
void spokes_CallEnded(object sender, CallEndedArgs e) { LogMessage(MethodInfo.GetCurrentMethod().Name, ">>> User has ended call, call id: " + e.CallId); // if this was My Softphone's call then terminate the audio link to headset if (e.CallId > 0 && e.CallSource.CompareTo(APP_NAME) == 0) { // DEMO - try "re-activating" the call to cover // the scenario where the user is NOT allowed to end the call! if (preventcalltoterminatewithtalkbuttonChkBox.Checked) { DoReopenCall(e.CallId); // reopen SAME call id! } else { m_dummyspeechaudio.SpeakAsyncCancelAll(); m_spokes.SetMute(false); //m_spokes.ConnectAudioLinkToDevice(false); } } else LogMessage(MethodInfo.GetCurrentMethod().Name, ">>> Ignoring spurious call event, call id: " + e.CallId + ", call source = " + e.CallSource); } private void DoReopenCall(int callid) { if (pcLineActiveBtn.InvokeRequired) { StartReopenCallTimerCallback d = new StartReopenCallTimerCallback(DoReopenCall); this.Invoke(d, new object[] { callid }); } else { m_spokes.OutgoingCall(callid); // reopen same call id that was closed! } }Hi Ramesh,
There's been a long time since I've post the original bug description.
Is there any news about the bug resolution?
Chris.
I've reported a Bug in February http://developer.plantronics.com/thread/1423
Is there any way to get a bug number or reference in order to track it and be alerted when a resolution is available?
Hi Chris,
The bug that you reported earlier has been resolved and will be in the next PURE 2.8.3 release in the coming weeks. Greg will alert you when this release is available.
Thanks you for your continuous interest and support of the PURE SDK.
Wei Chu
Thanks Wei Chu.
Please see Wei Chu's answer at the link to the original post here Re: Facing a problem with Savi 7xx and C++ COM Service Thanks!
I have a user constantly getting this error from their plantronics softphone.
It turns out after receiving this error plantronicsure.exe stops functioning correctly. After this error users can no longer answer or hang up calls using their softphone headset. After reopening plantronicsure.exe the user can answer calls until it crashes again.
Hey PDC devs,
The Mac SDK is now available as a beta release! Check this out:
Thanks,
Lewis.
Hi Peter Peter Stewart,
The Mac SDK is now available as a beta release! Please check out this link:
Thanks,
Lewis.