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 ?

Hi.

Which Java version are you using ?

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

Hi.

JRE 1.8 is fine (it seems JTAPI has problems above JRE 1.8).


- Did you post the tdispatch_trace.log ?
You posted a very short time interval (01/11/2023 11:25:31:724 - 01/11/2023 11:25:31:868).
Scrolling the file up and down, do you see something else ?


- The tsapi_trace does not show the exact moment the exception is caught.
Do you have the cti (CTIC) log from the time the call starts ?
There should be something like

ERROR - .... CTIConnectorException: error/exception message

Also the JTAPI log for this call can help.

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?

Avaya recommends a fresh installation of the OD 8.x ( https://www.devconnectprogram.com/fileMedia/download/0727c96d-0c44-4cae-aeca-5994c76be916 on page 5 ).

- changes in JTAPI :

The OD 7.2 was release in July 2017, while the OD 8.0 was release in September 2020 (see attached picture). To know what exactly JTAPI changed between July 2017 and September 2020, you can check the JTAPI forum

https://www.devconnectprogram.com/forums/forums/show/10.page


- which needs to be incorporated during the code migration from 7.2 to 8.0:

I'm not aware of that. The OD 8.0 Release Notes ( https://www.devconnectprogram.com/fileMedia/download/0727c96d-0c44-4cae-aeca-5994c76be916 ) on page 6 just mentions

"AES Connector Does Not Work in FIPS
Due to the limitation in JTAPI, this release does not support AES Connector running in FIPS mode"

In case you need instructions how to upgrade from 7.2 to 8.0, take a look, starting from page 31, at

https://www.devconnectprogram.com/fileMedia/download/548a38c7-4c1c-427d-b472-49a1b1eb6856

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 ?

Hi.

In a SIP scenario, you can use the VXML transfer coming in the palette to do the transfer.

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

No, the VXML transfers (Blind, Consultation and Bridged, first picture below). Take a look at the Developer's Guide for the OD 8.0 on page 630 (there are links to each palette node)

https://www.devconnectprogram.com/fileMedia/download/160975b7-1642-4a32-88c9-50cc25708b60



Let me clarify the two servlets (they are palette nodes, second picture below).

- VXML servlet: node useful when you need your own VXML code into the app (same doc above on page 670).

- Java servlet: node useful to insert a custom Java code into your project (same doc above on page 663).


=> you can use your VXML code to implement a call transfer in a servlet node, anyway the fastest way is a VXML transfer ('faster' does not mean 'out-of-the-box', you have to access the node and setup some stuff ex. grammar, prompt, destination).