You seem to have two issued here:
1. AE Services is showing active DMCC sessions that the application(s) think have been closed. For this, I suggest you use the Session IDs to match which sessions are not ending. Check the application logs to make sure they were shutdown correctly. As there is more than one session active, I presume this is something like an agent pop-up application - with a GUI running on each agent's PC. Maybe some agents are clicking the X to close the GUI, rather than logging out and disconnecting correctly. In this case, the session will remain active on AE Services for several minutes.
2. I presume the application uses setAgentState() to log the agent in/out. In this case, you may find the TSAPI traces more informative than the DMCC traces. There are instructions in the Devconnect Product FAQ "What is the procedure for enabling and accessing the AE Services logs for TSAPI (trace, tracing, g3trace, csta_trace)?".
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/tsapi/index.gsp#10
You will also find the document "TSAPI for Avaya Communication Manager Programmer's Reference" useful.
Martin
|