Hi

My JTAPI application gets "shutting down provider" error multiple times a day randomly and causing severe disruptions.
After I enabled trace logs, the exception associated with every shutdown is below.
Attached file has the details of events leading to shutdown.
Please take a look and let us know if you have any idea what might be causing this.

JTAPI client version: 4.2.474
AES server version: 4.2

com.avaya.jtapi.tsapi.TsapiPlatformException: Decoder: INTEGER/ENUMERATED value is too long at com.avaya.java.asn1.ASN1.decodeInt(ASN1.java:26) at com.avaya.java.asn1.ASNEnumerated.decode(ASNEnumerated.java:21) at com.avaya.java.csta1.ExtendedDeviceID.decodeMembers(ExtendedDeviceID.java:118) at com.avaya.java.asn1.ASNSequence.doDecode(ASNSequence.java:21) at com.avaya.java.csta1.ExtendedDeviceID.decode(ExtendedDeviceID.java:103) at com.avaya.java.csta1.CSTAEstablishedEvent.decodeMembers(CSTAEstablishedEvent.java:42) at com.avaya.java.asn1.ASNSequence.doDecode(ASNSequence.java:21) at com.avaya.java.csta1.CSTAEstablishedEvent.decode(CSTAEstablishedEvent.java:21) at com.avaya.java.tsapiInterface.TsapiSession.decodePDU(TsapiSession.java:1013) at com.avaya.java.tsapiInterface.TsapiSession.handleRead(TsapiSession.java:619) at com.avaya.java.tsapiInterface.oio.TsapiChannelOio$OioChannelThread.run(TsapiChannelOio.java:223)

AE Services and JTAPI 4.2 have both been obsolete for several years. You should upgrade them.

Your error seems to say that the value of the (presumably) Trunk Member is larger than the decoder expected. Perhaps your Communication Manager supports more trunk members than JTAPI 4.2.

One option that you could try is to use a newer version of the JTAPI client (5.x or 6.x). Maybe these will support the Member value being sent from Communication Manager.

Martin