|
The most like explanations are:
1. Another application is running which also affects the call. This means that the call may not be in the state that you application expects.
2. Another possibility is that you are experiencing race-conditions. That is, you are receiving events in a different order to what you expect or your requests are received by the AE Services/Communication Manager after something has happened to the call that you were not expecting.
If your application was certified by Devconnect, you can have your customer open a service request with Avaya Global Services to ask them to investigate. Otherwise, you will need to investigate yourself.
You can enable the TSAPI and/or DMCC traces on the AE Services. Either of these traces will show what events and requests are occurring and when. There are instructions on enabling both of these traces in the Product FAQ section of this website. They are called "How can I monitor the XML being sent and received by the AE Services Server (debug, log, trace)?" and "What is the procedure for enabling and accessing the AE Services logs for TSAPI (trace, tracing, g3trace, csta_trace)?".
Enabling these traces should not interfere too much with the loading on your AE Services but the log files will wrap very quickly. You will need to disable the traces as soon as you spot a problem call.
From the trace files, you will be able to see all the events and requests for a given call. From this, you should be able to get a better idea as to what is happening.
Martin
|
