No call info available on extension issue

[avc874769614550]

We are getting this error repeatedly, however, this issue is occurring frequently and we are unable to find the solution as the IVR is getting completely down

Please give us the resolution asap.
Getting the error “No observer on extension: 2031",
This error seems to indicate that there is a failure in the communication between the IVR system and the extensions on the Avaya system. The absence of an observer likely points to an issue where the expected service, application, or listener is not correctly initialized or not available on this extension.

[avc874769614550]

We are getting this error repeatedly, however, this issue is occurring frequently and we are unable to find the solution as the IVR is getting completely down

Please give us the resolution asap.
Getting the error “No observer on extension: 2031",
This error seems to indicate that there is a failure in the communication between the IVR system and the extensions on the Avaya system. The absence of an observer likely points to an issue where the expected service, application, or listener is not correctly initialized or not available on this extension.

[yangh]

This typically indicates an error that AESConnector didn't receive events from JTAPI client in time. If you're using latest OD and OD Runtime environment, the JTAPI client ported by default, 8.1.3.5.0.8, has known defects. https://support.avaya.com/css/public/documents/101088763

You'll need to ensure JTAPI client 8.1.3.6.0.8 is used to replace the default JTAPI client 8.1.3.5.0.8.

You may also want to add tsDevicePerformanceOptimization=true to your TSAPI.pro file to further improve the JTAPI client efficiency to avoid multiple unnecessary queries sent to AES (refer AES-28240 in the latest AES release note)

Please note: the JTAPI client 8.1.3.6.0.8 also has a defect on its logging - when the debug level log is set to 0, it writes everything to default console - that means the catalina.out of the Tomcat hosting your AESConnector, in this scenario. So we should always set log level to 1 or higher if we do want to set the log level explicitly.