Message |
[+]
JTAPI
» Conference call gets cleared when the shared party leaves the conference, 10/08/2015 07:20:37
» Go to message
|
|
Hi Craig
Thank you for the response. Please see my answers below:
2) So there is a bridged appr of B on C's device? - yes that is right
4) Please explain the "JTAPI join API". - By this, I meant that the shared party joined the call through the application which uses the Avaya JTAPI 'join' API
Please see the attached logs for this test. The call-id was 11062.
Thanks
|
|
[+]
JTAPI
» Conference call gets cleared when the shared party leaves the conference, 29/07/2015 06:54:38
» Go to message
|
|
Hi
We are using JTAPI SDK 6.3.1.154 and AES 6.3.1 for our CTI application.
When we test the following scenario, the entire conference gets cleared.
1) User A calls User B
2) User B's line is shared on User C's device
3) User B answers the call using JTAPI answer API
4) User C joins the call using JTAPI join API. Call is in conference state now.
5) User C drops the call from the application. AT this point, the entire conference call gets cleared and there is no call on the device too.
Any idea why does the entire call get cleared instead of the party who just dropped from the conference.
Thanks
|
|
[+]
JTAPI
» Drop call answered on a shared line from application using JTAPI, 18/06/2015 10:20:22
» Go to message
|
|
Thanks Shantanu for the reply.
We are using disconnect JTAPI method to drop the call.
The error stack trace is: ClearConnection Exception Occured
com.avaya.jtapi.tsapi.TsapiPlatformException: clearConnection failure
at com.avaya.jtapi.tsapi.impl.core.TSConnection.disconnect(TSConnection.java:361)
at com.avaya.jtapi.tsapi.impl.TsapiConnection.disconnect(TsapiConnection.java:172)
|
|
[+]
JTAPI
» Drop call answered on a shared line from application using JTAPI, 18/06/2015 09:36:38
» Go to message
|
|
Hi
Setup:
1. A and B (Primary) share a line
2. C makes a call to B
3. A picks up the call
4. A is unable to end the call using our JTAPI application
However, the call can be cleared from the device using the drop button.
Error received is : 107: Exception occured processing call control by TSAPI
Any help would be appreciated.
Thanks
|
|
[+]
JTAPI
» OCI UCID in case of transfer call from the avaya device, 07/04/2015 07:20:40
» Go to message
|
|
Hi Craig
Yes, by connect, I meant how to co-relate the two calls. When I make calls from the application, the first call has an id which is stored by the application. I then do a consultation call, and at that point I receive the OCI.UCID of the first call as well as the id of the second call. So, I can relate the two calls.
But from the Avaya phone itself, there is no option to do a consultation call, so the second call does not have the OCI.UCID of the first call in the events.
Regarding your question - "You have a station that is the calling party for both calls, and has one on hold and one active."
It is a bit difficult to correlate calls based on the held calls as there might be more than one held call on the device.
|
|
[+]
DMCC APIs
» Button RING_STAT via dmcc, 24/03/2015 09:25:58
» Go to message
|
|
|
|
[+]
DMCC APIs
» Button RING_STAT via dmcc, 24/03/2015 04:24:51
» Go to message
|
|
Thanks for your clarification Martin. It looks like I've misunderstood the use of RING_STAT. I thought I could get the status of the RINGER_OFF button (enabled or disabled) by doing a DMCC buttonpress on RING_STAT. I now see that isn't how it's used.
To find out the status of the RINGER_OFF button (enabled or disabled), I guess I have to set up a listener and catch the right event?
|
|
[+]
DMCC APIs
» Button RING_STAT via dmcc, 23/03/2015 11:35:26
» Go to message
|
|
Environment: The Avaya BDE is 6.0, and the dmcc api is 5.2.3
After much searching for configuration of RING_STAT.....(might be useful to others)
change system-parameters special-applications (screen 3: SA8428 Station User Button Ring Control)
change station 50202 (screen 2: Per Button Ring Control)
change station 50202 (screen 4: add the ring-stat button)
I managed to get the button press to work, however......
RING_STAT is (if i've understood correctly) supposed to give you the RINGER STATUS.
How do I get hold of the value? How is it returned?
|
|
[+]
DMCC APIs
» EC500 forward number through DMCC API, 23/03/2015 11:18:58
» Go to message
|
|
Thanks for the reply.
Shame I can't do this from DMCC and have to use SMS
|
|
[+]
DMCC APIs
» EC500 forward number through DMCC API, 23/03/2015 08:45:00
» Go to message
|
|
Environment: The Avaya BDE is 6.0, and the dmcc api is 5.2.3
I understand that the mobile phone number to ring regards EC500 is configured via "change off-pbx-telephone station"
Through DMCC API calls (directly or via phone display) is there a way of getting the forwarded mobile number configured for EC500?
If not, non DMCC API method exists to get it?
|
|
[+]
DMCC APIs
» buttons RINGER_OFF, 23/03/2015 08:29:32
» Go to message
|
|
Thanks for the confirmation John
|
|
[+]
DMCC APIs
» buttons RINGER_OFF, 22/03/2015 10:41:20
» Go to message
|
|
Environment: The Avaya BDE is 6.0, and the dmcc api is 5.2.3
I'd like to use DMCC api to switch off a ringing phone. I found 'RINGER_OFF' and tried it with sample code which works for otgher buttons. Is there some cofiguration that needs to be done on the AES for this to work?
ButtonPress bpRequest = new ButtonPress();
bpRequest.setDevice(deviceID);
GetButtonInformation biRequest = new GetButtonInformation();
biRequest.setDevice(deviceID);
GetButtonInformationResponse biResponse = physSvcs.getButtonInformation(biRequest);
ButtonList buttonList = biResponse.getButtonList();
for (Enumeration e = buttonList.enumerateButtonItem(); e.hasMoreElements();) {
ButtonItem buttonItem = ((ButtonItem) e.nextElement());
if (buttonFnConstant.equals(buttonItem.getButtonFunction())) {
bpRequest.setButton(buttonItem.getButton());
}
}
ButtonPressResponse bpr = physSvcs.pressButton(bpRequest);
I get the following error:
INFO: SERVICE PROVIDER = com.avaya.mvap.svcproxy.prov.RemoteServiceProvider
Mar 20, 2015 6:08:19 PM com.avaya.mvcs.proxy.CstaMarshaller marshal
WARNING: Invalid Csta object session[null] ch.ecma.csta.binding.ButtonPress@535e7829
ValidationException: The field '_button' (whose xml name is 'button') is a required field of class 'ch.ecma.csta.binding.ButtonPress;
location of error: XPATH: ButtonPress
at org.exolab.castor.xml.FieldValidator.validate(FieldValidator.java:208)
at org.exolab.castor.xml.util.XMLClassDescriptorImpl.validate(XMLClassDescriptorImpl.java:916)
at org.exolab.castor.xml.Validator.validate(Validator.java:127)
at org.exolab.castor.xml.Marshaller.validate(Unknown Source)
at org.exolab.castor.xml.Marshaller.marshal(Unknown Source)
at com.avaya.mvcs.proxy.CstaMarshaller.marshal(CstaMarshaller.java:156)
at com.avaya.mvcs.proxy.CstaMarshallerNode$CstaMarshallerThread.run(CstaMarshallerNode.java:176)
at com.avaya.mvcs.proxy.CstaMarshallerNode.processPacket(CstaMarshallerNode.java:104)
at com.avaya.mvcs.proxy.AbstractPipelineNode.process(AbstractPipelineNode.java:130)
at com.avaya.mvcs.proxy.Pipeline$PipelineSubscriber.inform(Pipeline.java:427)
at com.avaya.common.eventservice.UnfilteredSubscription.notify(UnfilteredSubscription.java:70)
at com.avaya.common.multicaster.Multicaster.notify(Multicaster.java:386)
at com.avaya.common.channel.Channel.publish(Channel.java:115)
at com.avaya.common.eventservice.EventService.publish(EventService.java:123)
at com.avaya.common.eventservice.EventServiceManager.publish(EventServiceManager.java:156)
at com.avaya.common.eventservice.Publisher.publish(Publisher.java:110)
at com.avaya.mvcs.proxy.XmlGatewayClient.handleRequest(XmlGatewayClient.java:175)
at com.avaya.mvcs.proxy.Pipeline.handleRequest(Pipeline.java:346)
at com.avaya.mvcs.proxy.ClientProxy.routeRequest(ClientProxy.java:607)
at com.avaya.mvap.svcproxy.ServiceProxy.marshallRequest(ServiceProxy.java:106)
at com.avaya.mvap.svcproxy.PhysicalDeviceServicesProxy.pressButton(PhysicalDeviceServicesProxy.java:162)
|
|
[+]
JTAPI
» Early media on SIP TRUNKS, 06/03/2015 06:19:03
» Go to message
|
|
Hi Craig
Is this option available on CM 5.2.1?
Thanks
|
|
[+]
JTAPI
» OCI UCID in case of transfer call from the avaya device, 06/03/2015 06:18:13
» Go to message
|
|
From the JTAPI events, when the first call is made, it has UCID in the LucentV5CallInfo.getUCID(). And the V5OCI.getUCID() is 000000000000 as expected. When I hit transfer button from the device, it creates a new call and at that point too the V5OCI.getUCID() is 000000000000 and LucentV5CallInfo.getUCID() is the callid for the 2nd call. At this point, is there a way to connect the 2 calls together?
|
|
[+]
JTAPI
» OCI UCID in case of transfer call from the avaya device, 05/03/2015 14:59:14
» Go to message
|
|
Hi
I have a scenario where a user makes a call A from the phone.
Then press transfer button, which originates a new call. When the second call is established, is there a way to get the UCID of the first call before completing the transfer from the device.
Thanks
|
|