Are you referring to the VXML servlet? Do you have documentation which can be referred to?

All the above migration is completed and the code is up and running on 8.0 - but we are struck in the call transfer through SIP. Do we still need to use AES for SIP call transfer ?

Those are the only errors I could see in the tdispatch, hence pasted only that. I don't have the CTI logs.

Is there are changes in JTAPI which needs to be incorporated during the code migration from 7.2 to 8.0?

We are using Java 1.8. We are trying to do SIP transfers and is there a different procedure to achieve the same ?

Hi,

We are upgrading from Avaya OD 7.2 to Avaya 8.0 and we are getting the following error in the tdispatch logs

01/11/2023 11:25:31:724 DEBUG - r23CGdR6u0OQgI3s2TgxJSU:/Dispatch : CTICommand.execute: encrypted value is UKMjgJGwrnLz5/30/oqDn0AqrGVd8BPu
01/11/2023 11:25:31:724 DEBUG - r23CGdR6u0OQgI3s2TgxJSU:/Dispatch : CTICommand.execute: request to manager is https://hld00117:33001/aesconnector/CallInfoInitialCall?extension%3D&k=UKMjgJGwrnLz5%2F30%2FoqDn0AqrGVd8BPu
01/11/2023 11:25:31:724 DEBUG - r23CGdR6u0OQgI3s2TgxJSU:/Dispatch : CTICommand.execute: setting session cookie to r23CGdR6u0OQgI3s2TgxJSU:/Dispatch
01/11/2023 11:25:31:836 ERROR - r23CGdR6u0OQgI3s2TgxJSU:/Dispatch : session id:ALD10140-2023305152048-13 | CallTransfer:getCallInfo | Caught Exception while Initiating CTI Transfer. Performing a Blind Transfer.
01/11/2023 11:25:31:858 INFO - r23CGdR6u0OQgI3s2TgxJSU:/Dispatch : Using SCESession r23CGdR6u0OQgI3s2TgxJSU:/Dispatch servlet : logBlindTransfer
01/11/2023 11:25:31:858 INFO - r23CGdR6u0OQgI3s2TgxJSU:/Dispatch : Assigning [BLIND] to [transferMethod]
01/11/2023 11:25:31:867 INFO - r23CGdR6u0OQgI3s2TgxJSU:/Dispatch : Using SCESession r23CGdR6u0OQgI3s2TgxJSU:/Dispatch servlet : GetDefaultVdn
01/11/2023 11:25:31:868 DEBUG - r23CGdR6u0OQgI3s2TgxJSU:/Dispatch : /CallTransfer.GetDefaultVdn.servletImplementation: Entering method.

I am attaching the TSAPI trace logs as well. Could you let us know what is the issue here ?

I have done the same, and the error occurs when log4j-1.2.15.jar is removed as suggested in the Avaya documentation.

Yes, these two files are present in mentioned lib path. Getting errors at:

import org.apache.log4j.LogManager;
import org.apache.log4.Logger;
import org.apache.log4.BasicConfigurator;
import org.apache.log4.PropertyConfigurator;

which jar should be used? To resolve the errors?

The documentation says to remove log4j-1.2.15.jar and once its removed we are getting the above errors.. Does 8.0 require code changes to get the logger working ?

Thanks for the reply massimo__croci. I did use the same method you mentioned for upgrade and I am getting the following error:

The type org.apache.log4j.Logger cannot be resolved. It is indirectly referenced from required .class files

I exported the runtime files from the export wizard for Websphere and these were the JAR's present related to log4j

log4j-core-2.17.1.jar
log4j-api-2.17.1.jar

Are there any additional log4 jar's that need to be added to the TOMCAT_HOME lib path ?

I am trying to upgrade from OD 7.2 to 8.1 and I have exported the aesconnector.ear files fromt the export wizard for websphere. When I try to deploy the ear on the websphere, I am getting the following error:

[9/21/23 11:11:07:299 EDT] 00000001 ContainerHelp E WSVR0501E: Error creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl@5693dc64
com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.webcontainer.exception.WebAppNotLoadedException: Failed to load webapp: Failed to load webapp: javax.servlet.ServletContainerInitializer: Provider org.apache.logging.log4j.web.Log4jServletContainerInitializer could not be instantiated
at com.ibm.wsspi.runtime.component.WsComponentImpl.join(WsComponentImpl.java:432)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.startCUList(CompositionUnitM

And I have the following logging related libs in the shared libraries.

log4j-core-2.17.1.jar
log4j-api-2.17.1.jar
commons-logging-1.2.jar

Any help on what is causing the issue is appreciated.

Thanks massimo__croci for sharing the document link.

As suggested in the document shared, I did modify the Prosody volume and the prosody rate to 50; but I don't see any difference in the prompt play out - it is still incomplete.

Is there any other work around please suggest.

Thanks in advance

Our application is trying to play a message using TTS - but TTS fails to read out the complete message.
Per observation, message is read for 39 seconds. Is the time for TTS limited to play for around 40 seconds?

If the TTS playout time is configurable, please let me know where to configure the same and increase the playout time.

Thanks in advance!

Please let me know how to disable logging for system.err and system.out on the IBM WAS 8.5 server.