Had a similar issue, posted the workaround here https://www.devconnectprogram.com/forums/posts/list/24660.page
let me know if that solves the issue.

We had this issue a few days ago, it's already solved but someone might find it useful to solve the same problem:

Issue: Simulator doesn't work on OD (any version), with a fresh install of the latest windows 10 or a recently upgraded copy.

If you go to to the error log will see something like :

java.lang.UnsatisfiedLinkError: C:\lib\eclipse\plugins\com.avaya.sceavb_8.0.0.2201\AVBControl64.dll: Can't find dependent libraries

	at java.lang.ClassLoader$NativeLibrary.load(Native Method)

	at java.lang.ClassLoader.loadLibrary0(Unknown Source)

	at java.lang.ClassLoader.loadLibrary(Unknown Source)

Solution: last version of windows changed /c/WINDOWS/SYSTEM32/MSVCR100.dll --> MSVCR130.dll so OD is not able to find it. Just copy or download the MSVCR100.dll library into your SYSTEM32 folder.

I don't know if future OD versions or patches will address this issue, but this workaround works.

I've been trying to generate a SOAP Web Service client using Axis2 connector under OD 7.2.3.

have tried using different installs on different machines with the same result.

even found https://www.devconnectprogram.com/forums/posts/list/558.page which didn't worked.

switched back to OD 7.2.1 and it works perfectly but on OD 7.2.3 something is broken with axis2

1.- create a new Speech APP
2. - add axis2 pluggable connector
3. create axis2 WSOP
4. load URL or WSDL file
5. click on load WSDL

get a message : Could Not initialize class: org.apache.axis2.wsdl.codegen.CodeGenerationEngine (see attached).

I think it is an OD 7.2.3 issue as I've tried on different installs and different pc's with the same result.

please advise.

we did a small test to simulate the behavior, we have an application that plays a transitional audio, then it goes to a transaction (which puts the app to wait to x ammount of seconds) and then plays a beep and ends the call.

in the logs we can see the 'transaction being executed' from 11:31:28:006 to 11:33:06:052. Hold music was only played for 10 seconds.

we were only able to hear the audio for 10 seconds i'm attaching the log from the application and the audio used as hold music

I uploaded a log with 3 or 4 ocurrences of the incident, please note I'm using POM services to get information from a list, this is a reply to a POM campaign but it's being received as an Inbound SMS, so I'm getting some info out of the contactlist.

thank you,

I have an application developed on OD 7.0.1.0804. for SMS running on Experience Portal 7.1.0

It's supposed to receive a SMS response, validate the keyword and do some external process.

The application work as expected but when the other party sends the SMS, an automatic response is received:

The message cannot be processed at this time. Please try again later

however the application receives the message and it's able to process it correctly.

looking at the avaya.text.log the following info is found:

@2019-07-22 16:07:51,785||ERROR|avaya.textbrowser.IncomingRequest|VoicePortal|pool-2-thread-34|Error while processing request:SMS-39, message=error.semantic|####

EventException[help=cvc-id.2: There are multiple occurrences of ID value 'Exit1563826086418'.;com.avaya.textbrowser.textxml.EventException: error.semantic]

        at com.avaya.textbrowser.util.TextXMLProcessor.processTextXML(TextXMLProcessor.java:53)

        at com.avaya.textbrowser.IncomingRequest.submit(IncomingRequest.java:178)

        at com.avaya.textbrowser.IncomingRequest.process(IncomingRequest.java:191)

        at com.avaya.textbrowser.IncomingRequest.run(IncomingRequest.java:214)

        at com.avaya.textbrowser.BrowserImpl.processIncomingMessage(BrowserImpl.java:98)

        at com.avaya.smsbrowser.MessageProcessor.processMessage(MessageProcessor.java:249)

        at com.avaya.smsbrowser.InboundMessageProcessor.run(InboundMessageProcessor.java:48)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

        at java.util.concurrent.FutureTask.run(FutureTask.java:262)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

        at java.lang.Thread.run(Thread.java:745)

there are no error or warnings on the application trace.log

the WAS is indeed using a self signed certificate which is registered in the runtimeconfig App.

attached please find documentation of the issues found and a large aesconnector log

I have the following environment setup:

Experience Portal 7.02
WAS:

Linux OS.
dedicated server
12 GB RAM
tomcat 7
JAVA 7.0.79 (oracle)
OD libraries 7.01.0804
AESCONNECTOR from the same version.

we're not allowed to use http, only https. for about one and a half years we have observed issues with the aesconnector, as we can see in the logs that it receives the information but when the application requests it, the response is "no call info available" even when it is known that the info was already received. This happens mostly in the hours of high traffic.

About three weeks ago, we setup another tomcat instance using http, it has been working flawlessly and little to none issues are observed even in high traffic hours.

the problem is that the use of http was approved as a contingency not as a permanent measure, we need a way to ensure that the aesconnector performs using secure protocols.

the server has been tuned with all parameters and recomendations for OD and it's memory consumption is way below the XMX parameter.

The app logs were taking from an app using DD 5.01.17.02, however the App was recently migrated to OD 7.01.08.04

the described errors occurred on DD and kept occurring since the migration to OD.

from the logs I've seen, it seems that the Events on the AES are correctly timed but the AESConnector is receiving the Events with some delay... the question is why???

thanks for your quick response, attached please find some logs from the AES, aesconnector and the Application

Regards,

Hello,

we have a case where several calls from several applications are receiving the

No call info available for extension xxxxx

a lot of calls where the AESConnector works properly but at some point it start failing, failures are not linked to the hours of high traffic or to other environmental issues, it simply starts failing.

the servers have been restarted and the issue continues to occur, we have isolated some of the information from the logs:

a bad call trace log :

...

12/10/2016 14:55:17:623 DEBUG - 28BD5DACCB1EF23D2476C5A954C0A10E:/UNE_UUI_IVR_INTEGRADO_NOVERDE_V8 : CTICommand.execute:  setting session cookie to 28BD5DACCB1EF23D2476C5A954C0A10E:/UNE_UUI_IVR_INTEGRADO_NOVERDE_V8

12/10/2016 14:55:21:631 DEBUG - 28BD5DACCB1EF23D2476C5A954C0A10E:/UNE_UUI_IVR_INTEGRADO_NOVERDE_V8 : CTICommand.execute: callinfo from Manager is error:CallInfo.doGetCallInfoInitialCall: No call info available for extension 17095

in the Trace.log of the aesconnector, the information found at that time :

12/10/2016 14:55:21:631 ERROR - CallInfo.doGetCallInfoInitialCall: No call info available for extension 17095

...

12/10/2016 14:56:28:170 DEBUG - Ending call on extension 17095

12/10/2016 14:56:28:170 DEBUG - CTICallObserver.removeAllCalls: Callid: id passed from app on extension:17095 is null MRCR: MRCC:

12/10/2016 14:56:28:170 DEBUG - CTICallObserver.removeAllCallsFrom:clearing out MRCR

12/10/2016 14:56:28:170 DEBUG - CTICallObserver.removeAllCallsFrom:removed all calls from extension:17095

12/10/2016 14:56:28:170 DEBUG - CTICallObserver.removeAllCallsFromCache:removed all calls from cache at extension:17095

...

12/10/2016 14:57:20:562 ERROR - CallInfo.doGetCallInfoInitialCall: No call info available for extension 17095

note that the time in the app log and in the aesconnector log is an exact match (12/10/2016 14:55:21:631), later on that log, at 14:59:11 (about 3 mins later than the first request) the AESConnector gets this:

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.removeCall:clearing MRCC:8401 from ext:17095

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.removeCall:removing call:8401 from ext:17095

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 175 is 101 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: got Connection Active Event

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 176 is 106 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: got Connection Created Event for id:9262

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: Saving most recent call created:9262

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.addCall 17095: call id is 9262

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.addCall 17095:  ucid is 00001092621476302116

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.addCall 17095: setting 9262 to state: initiated

12/10/2016 14:59:11:554 DEBUG - CallInfoData.CallInfoData:17095: callid 9262

12/10/2016 14:59:11:554 DEBUG - CallInfoData.CallInfoData:17095: ani 53190733

12/10/2016 14:59:11:554 DEBUG - CallInfoData.CallInfoData:17095: dnis 196

12/10/2016 14:59:11:554 DEBUG - CallInfoData.CallInfoData:17095: ucid 00001092621476302116

12/10/2016 14:59:11:554 DEBUG - CallInfoData.CallInfoData:17095: uui 10200000453190733000000000000000

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.addCall 17095: added call to list

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.addCall  17095:cache is:false

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 177 is 105 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: got Connection Connected Event

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 178 is 206 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent:17095: got Call Control Connection Established Event

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent:17095: Found no connections object

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 179 is 106 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: got Connection Created Event for id:9262

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: Saving most recent call created:9262

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.addCall 17095: call id is 9262 is already added, returning call data

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 180 is 104 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: got Connection Alerting Event

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 181 is 203 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent:17095: got Call Control alerting Event

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.updateCallState 17095: setting call:9262 to state:ringing

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 182 is 116 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: got Terminal Connection Created Event

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 183 is 119 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: got Terminal Connection Ringing Event

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 184 is 218 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: got Call Control Terminal Ringing Event

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 185 is 105 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent17095: got Connection Connected Event

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 186 is 206 for call 9262 Provider:AES3

12/10/2016 14:59:11:554 DEBUG - CTICallObserver.callChangedEvent:17095: got Call Control Connection Established Event

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent:17095: Found no connections object

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 187 is 115 for call 9262 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent17095: got Terminal Connection Active Event

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 188 is 219 for call 9262 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent:17095: got Terminal Connection Talking Event

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent:17095: Found no connections object

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 189 is 216 for call 9262 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent:17095: got Terminal Connection Held Event

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.updateCallState 17095: setting call:9262 to state:held

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 190 is 101 for call 9434 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent17095: got Connection Active Event

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 191 is 106 for call 9434 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent17095: got Connection Created Event for id:9434

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent17095: Saving most recent call created:9434

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.addCall 17095: call id is 9434

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.addCall 17095:  ucid is 00001092621476302116

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.addCall 17095: setting 9434 to state: initiated

12/10/2016 14:59:11:555 DEBUG - CallInfoData.CallInfoData:17095: callid 9434

12/10/2016 14:59:11:555 DEBUG - CallInfoData.CallInfoData:17095: ani 17095

12/10/2016 14:59:11:555 DEBUG - CallInfoData.CallInfoData:17095: dnis 12384

12/10/2016 14:59:11:555 DEBUG - CallInfoData.CallInfoData:17095: ucid 00001092621476302116

12/10/2016 14:59:11:555 DEBUG - CallInfoData.CallInfoData:17095: uui 10200000453190733000000000000000

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.addCall 17095: added call to list

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.addCall  17095:cache is:false

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 192 is 105 for call 9434 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent17095: got Connection Connected Event

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 193 is 208 for call 9434 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent:17095: got an unknown event 208

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 194 is 116 for call 9434 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent17095: got Terminal Connection Created Event

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 195 is 115 for call 9434 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent17095: got Terminal Connection Active Event

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent 17095: Event: 196 is 219 for call 9434 Provider:AES3

12/10/2016 14:59:11:555 DEBUG - CTICallObserver.callChangedEvent:17095: got Terminal Connection Talking Event

12/10/2016 14:59:11:724 DEBUG - No callid found in CTIEnd

because of the ani, extension and information I can tell is the same call, but is getting there 4 minutes late, when asked before the response was 'no call info'

we got reports from AES experts and they say that the information is being sent timely by the AES, all servers are on NTP and have their time/date sync.

Any ideas on how to troubleshoot this issue . thanks in advance

through intensive testing i have new findings :

- recorded many audios using the first app, some of them played and some of them don´t.
- changed the encoding (u-law to a-law) of the audios using a piece of software called sox
- audios that played right showed no problem when converting, audios that have playback problem show the following error when converting :

sox WARN wav: Premature EOF on .wav input file

did some research and that means the information in the audio header does not match the body of the audio file. better explained here http://sourceforge.net/p/sox/bugs/171/

the audios that playback right from the beginning do not show the same warning message


in conclusion, apparently a webbrowser can read a file with this problem but the MPP can not do it.

now the question is how to enforce the recording app to correctly write the files at once. I have no idea why the change in the server OS triggered this but I think that the testing described above narrows down the issue to the moment when the recording is made.

the java versión did change, on windows it was using 1.6.x and on linux it is 1.7.71 always using Oracle Java Releases

by reencode I mean changing the file format using something audio software like goldwave or audacity.

In that specific case the app didn't found an audio, the problematic behavior appears on the same log, line 956

8:<prompt bargein="true" bargeintype="speech" timeout="5000ms">

9:<audio src="http://172.27.30.171:7080/audiosBuzonAlm10/mensajes//export/aplicaciones/buzon/Prueba/431962427020150723083409.wav"> </audio>

if I copy the hole link and put it in a web browser it reproduces that audio. so i can say the link is fine, but i can't hear it in a call.

If the audio is re-encoded and replaced in the server it will be reproduced as it should in the call.

so given that, the problem is how to make the recording app (buzonalm) encode the files properly so they can be reproduced within a call.

attached a new report and trace log for "buzonrep" app with vxml