Message |
[+]
Server Platform
» TSAPI vs. IP trunk, 20/05/2021 04:27:55
» Go to message
|
|
Hello,
is it possible to obtain from TSAPI events the information about voice RTP identification on IP (SIP or H.323) trunk? I mean something similar like time-slot identification on E1 trunk. I need to assign TSAPI endpoint event to the corresponding voice data on IP trunk. The PBX is connected to he PSTN via IPtrunk.
Thanks.
|
|
[+]
DMCC APIs
» Single Step Conference (SSC) fails., 15/08/2018 03:03:35
» Go to message
|
|
Sorry, could you provide the link to the FAQ: AE Services TSAPI....? Or please navigate how to get there.
Thanks a lot.
|
|
[+]
DMCC APIs
» Single Step Conference (SSC) fails., 26/07/2018 08:25:47
» Go to message
|
|
Hello,
Sometimes, when invoking SSC, the following exception is thrown:
2018-07-25 10:02:35,961 ERROR c.r.l.Log [ServiceProxy-3]
ch.ecma.csta.errors.InvalidCalledDeviceIDException: null
at sun.reflect.GeneratedConstructorAccessor164.newInstance(Unknown Source) ~[?:?]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) ~[?:1.8.0_112]
at java.lang.reflect.Constructor.newInstance(Unknown Source) ~[?:1.8.0_112]
at java.lang.Class.newInstance(Unknown Source) ~[?:1.8.0_112]
at com.avaya.mvcs.proxy.ClientNegAckToException.convertErrorToException(ClientNegAckToException.java:130) ~[proxy.jar:"6.3.1.0.175 September 12 2013"]
at com.avaya.mvcs.proxy.XmlGatewayClient.handleRequest(XmlGatewayClient.java:250) ~[proxy.jar:"6.3.1.0.175 September 12 2013"]
at com.avaya.mvcs.proxy.Pipeline.handleRequest(Pipeline.java:346) ~[proxy.jar:"6.3.1.0.175 September 12 2013"]
at com.avaya.mvcs.proxy.ClientProxy.routeRequest(ClientProxy.java:627) ~[proxy.jar:"6.3.1.0.175 September 12 2013"]
at com.avaya.mvap.svcproxy.ServiceProxy.marshallRequest(ServiceProxy.java:131) ~[proxy.jar:"6.3.1.0.175 September 12 2013"]
at com.avaya.mvap.svcproxy.CallControlServicesProxy.singleStepConferenceCall(CallControlServicesProxy.java:372) ~[proxy.jar:"6.3.1.0.175 September 12 2013"]
What could be the reason for that?
Thanks.
|
|
[+]
DMCC APIs
» An exception after SLH is applied, 26/07/2018 08:18:09
» Go to message
|
|
OK, thanks, it was that.
Thanks again.
|
|
[+]
DMCC APIs
» An exception after SLH is applied, 17/07/2018 03:58:57
» Go to message
|
|
Hello,
What could be the reason for the following exception: ch.ecma.csta.errors.SubscribedResourceAvailabilityException ?
The exception is thrown when SLH (selective listening hold) is applied on the virtual extension which is added into the conference (SSC) with recorded extension. SSC proceeded normally.
Thanks
Vilem
|
|
[+]
DMCC APIs
» SIP vs. H.323 recording, 06/03/2018 02:29:10
» Go to message
|
|
Hello,
We developed recording application that is based on SSC (single step conferencing) method.
There is the issue when the H.323 extension calls the SIP extension. SSC fails.
The opposite scenario (SIP calls H.323) is OK.
dmcc-trace.log contains:
<135>Mar 5 13:43:20 AES1678 DmccMain[28583] +00:00 2018 583 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.mvcs.proxy.CstaMarshallerNode FINE - Returning negative ack to client session (EF385342C402EED94DB6F55D94C40720-17) : ch.ecma.csta.errors.InvalidObjectTypeException: There is incompatible bearer service for the originating or destination address. For example. The originator is administered as a data hotline station or the destination is a data station. Call options are incompatible with this service 18
dmcc-api.log contains:
<135>Mar 5 13:43:20 AES1678 DmccMain[28583] +00:00 2018 583 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.api.cmapi FINE - invokeID= 4408 Sent response ch.ecma.csta.errors.InvalidObjectTypeException: There is incompatible bearer service for the originating or destination address. For example. The originator is administered as a data hotline station or the destination is a data station. Call options are incompatible with this service 18
The problem appears only when SIP extension is the part of communication. There is no problem when there are only H.323 extensions.
Please help.
Thanks
Vilem Pantucek
|
|
[+]
DMCC APIs
» Selective listening Hold failure, 14/12/2017 07:08:09
» Go to message
|
|
Thank you for your response. Predictive dialer is implemented by a third party application (Genesys). So we think, that there is a lack of some system resources. We think that the monitored extension is managed by two applications (predictive dialer + our recording application with SSH&SLH). This may be a reason of SLH failure. Do you have any comments?
By the way, is there the same concept how to obtain stereo records (2xSSC, 2xSLH,..) also in CM ver.7 (AACC 7)?
Thanks
Vilem
|
|
[+]
DMCC APIs
» Selective listening Hold failure, 12/12/2017 02:11:02
» Go to message
|
|
Hello,
We modified our application to invoke SLH after Conferenced event. Unfortunately the issue still remains. In the meantime we found out, that this problem appears on so-called predictive calls. These calls are dialed by automatic dialer. If the system recognizes a live person on the line (on the opposite side) then the call is reconnect to the call-centre agent. Do you have any idea where we should to look at?
By the way, is there the same concept how to obtain stereo records (2xSSC, 2xSLH,..) also in CM ver.7 (AACC 7)?
Best regards
Vilem Pantucek
|
|
[+]
DMCC APIs
» Selective listening Hold failure, 03/11/2017 03:36:40
» Go to message
|
|
Hello,
Invoking SLH (selective listening hold) ends with error message. Application of SSC (single step conference) on the same extension (before SLH) was OK. Pls see the log in the attachment. Any idea?
Thanks
Vilem Pantucek
|
|
[+]
DMCC APIs
» Exception vhen calling SelectiveListeningHold, 13/06/2016 03:56:11
» Go to message
|
|
Hello,
Thanks, In the meantime we moved forward a little. Now the new exception is thrown:
ch.ecma.csta.errors.OutstandingReqLimitExceededException: The client attempted to put athird party (activeCall) on hold (two parties are on hold already) on an analog station
Could you please give some advice what is wrong now?
Regards
Pantucek
|
|
[+]
DMCC APIs
» Exception vhen calling SelectiveListeningHold, 06/06/2016 05:10:16
» Go to message
|
|
Hi.
We try to use a SSC (single step conference) method to record an extension voice communication. In addition we try to use Selective Listen Hold to obtain an agent and a customer conversation separately. When calling Selective Listen Hold an exception is thrown. Pls see a piece of an application log:
2016-06-06 09:39:18,614 TRACE LogToLog:? - <?xml version="1.0" encoding="UTF-8"?>
<SelectiveListeningHold xmlns="http://www.avaya.com/csta"><selectiveListening><subjectConnection><ns1:callID xmlns:ns1="http://www.ecma-international.org/standards/ecma-323/csta/ed3">6293</ns1:callID><ns2:deviceID xmlns:ns2="http://www.ecma-international.org/standards/ecma-323/csta/ed3" typeOfNumber="other" mediaClass="notKnown" bitRate="constant">160069:CM1PRAHAREC::0</ns2:deviceID></subjectConnection><allParties>false</allParties><selectedParty><ns3:callID xmlns:ns3="http://www.ecma-international.org/standards/ecma-323/csta/ed3">6293</ns3:callID><ns4:deviceID xmlns:ns4="http://www.ecma-international.org/standards/ecma-323/csta/ed3" typeOfNumber="dynamic" mediaClass="notKnown" bitRate="constant">T6293#2:CM1PRAHAREC::0</ns4:deviceID></selectedParty></selectiveListening></SelectiveListeningHold>
2016-06-06 09:39:18,614 TRACE LogToLog:? -
2016-06-06 09:39:18,614 DEBUG AvayaDcmmConnector:? - AvayaDcmmConnector.selectiveListeningHold(arg0) :
2016-06-06 09:39:18,677 ERROR Log:129 -
ch.ecma.csta.errors.SubscribedResourceAvailabilityException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
Pls, some advice what is wrong?
Regards
Vilem Pantucek
|
|
[+]
Device, Media and Call Control (Archive - Oct 2013 and earlier)
» DMCC Agent events, 16/10/2013 07:52:07
» Go to message
|
|
We don't receive any agent events in our application (DMCC Java SDK).
In AES log there is a message: FINE: Need to filter AgentStatusEvents because the client is not authorized to receive these events. Please, what is the problem?
Thanks
Vilem Pantucek
|
|
[+]
Avaya Aura Contact Center (Archive - Oct 2013 and earlier)
» IP adress from CCT, 21/06/2013 04:20:47
» Go to message
|
|
We use CCT .NET SDK to design CTI application. Is there any way how to obtain the IP addresses of H.323 phones used by AACC agents? From CCT or somewhere else?
Thanks
Vilem Pantucek
|
|
[+]
Device, Media and Call Control (Archive - Oct 2013 and earlier)
» DMCC Agent Events, 07/03/2013 11:15:14
» Go to message
|
|
Is it possible to monitor extension and AACC agent events through the DMCC (or TSAPI)? We suppose configuration when our customer operates Communication Manager (CM) and AACC. For the call recording application we need a link that monitors AACC extension&agent events.
Regards
Vilem Pantucek
|
|
[+]
Avaya Aura Contact Center (Archive - Oct 2013 and earlier)
» Extension&agents events detection, 07/03/2013 10:32:43
» Go to message
|
|
Hello,
The customer operates Communication Manager (CM) and AACC. For Call centre recording application we need a link for extension&agents events detection. Is it a good practice to combine AES TSAPI and RTD for extension&agents events fetching? Would it be better to use CCT ?
Regards
Vilem Pantucek
|
|