We have an application which is routing calls using adjunct vectoring/ DMCC route requests. The application is using DMCC to gather route requests and third party call control events from the VDN.
The application has been running for a couple of months now, but recently I have started to encounter seemingly random dropouts of the application session with the AES server.
The following error is appearing in the dmcc-error logs on the AES server at the time of the dropout:
2013-07-08 09.03.32,424 com.avaya.cs.callcontrol.delegs.CCSEventHandler eventDistributorException
WARNING: Unexpected exception from the CCS event distributor. Shutting down session and removing listeners.
java.lang.NullPointerException
at com.avaya.cs.callcontrol.handlers.CallControlConfHandler.handleConf(CallControlConfHandler.java:152)
at com.avaya.jtapi.tsapi.tsapiInterface.TSInvokeID.setConf(TSInvokeID.java:54)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiEventDistributor.handleEvent(TsapiEventDistributor.java:103)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiEventQueue.run(TsapiEventQueue.java:104)
Once the error occurs, the only way to recover is to completely restart the session an monitors, a reconnect results in a response 'Terminated session can not be reconnected. Reason: Tsapi socket closed'.
There doesn't seem to be any pattern or sequence of events in the preceeding requests and events.
At this point I'm trying to gather some information as to whether this is a known issue, and whether an upgrade or patch from our vendor will resolve.
|