Hi Everyone,

I am facing issue with AES Connector application after i exported the aesconnector.war from Avaya OD 8.1.1 into the client environment in aesconnector.logs, i am getting as
No Observer found on extension : 1005

And In validate page in while browsing in tomcat web page i am getting AES Connector Servlet is not setup or not running

kindly suggest me what can be done to resolve this issue.

AES version is 10.1.x.x
OD Vesrion is 8.1.1

Hi.

Take a look at these old threads:

https://www.devconnectprogram.com/forums/posts/list/24395.page#p162377

https://www.devconnectprogram.com/forums/posts/list/23730.page#p159814

https://www.devconnectprogram.com/forums/posts/list/17953.page#p73103

Hi ,

Already checked but i cannot find the proper solution to resolve this.
Can anyone help me resolving this, how to check the AES Connector servlet setup is running or not.

Ok.

Did you try to restart the app server ?

After the restart, does the issue still continue ?

Same has been done still this issue is persisting.
Do you have any other scenario that can be test.

- Are you facing calls dropping ?

- In the AES/CTI connector log, do you see a couple of messages as follows

DEBUG - ProviderMonitor:AES-S-IVR got an exception getting date/time attempt:1 error:client not in service

DEBUG - ProviderMonitor:AES-S-IVR got a null getting date/time attempt:1

?

You can also enable TSAPI Tracing (there is a FAQ on doing so) on the AES side and see if there is evidence of the issue there.
You can enable tracing in the JTAPI client (there is a FAQ on doing so) on Experience Portal and review the logs of the connection attempt
If you are using unsecure connections, you can get a packet capture and troubleshoot the connection attempt as well.
You can use any JTAPI client (including theJTAPI exerciser contained within the JTAPI SDK) and test the connection and figure out if the problem is with AES, or with EP side of things.

A lot of this class of issue with secure connections is caused by the certificates. Often regenerating them and re-installing them addresses the issue.