Re: Avaya Jtapi Issue

9.5 SP 4.

-----Original Message-----
From: Discussion list for Java Telephony API
[mailto:[email protected]] On Behalf Of Elliot Otchet
Sent: Friday, April 23, 2004 08:28 AM
To: [email protected]
Subject: Re: [JTAPI] Avaya Jtapi Issue


Dave,

What version of CT are you using?

Regards,

Elliot

-----Original Message-----
From: Discussion list for Java Telephony API
[mailto:[email protected]] On Behalf Of David E.Ybarra
Sent: Thursday, April 22, 2004 8:55 PM
To: [email protected]
Subject: [JTAPI] Avaya Jtapi Issue

I recently ran into an issue with Avaya's implementation of Jtapi where
some sort of network event causes the communication between a client
application and the server to stop. No events are delivered to the
provider yet it seems like the underlying socket is closed. I tried to
implement a thread that continuously calls provider.getState() once a
minute or so but that still returns IN_SERVICE. At some point when the
user tries to make a call a whole bunch of uncaught runtime exceptions are
logged by the final classes that Avaya uses like ae, etc. So my question
is has anyone ever experienced anything like this before? If so, is there
a way to detect this condition and recover? Thanks in advance.

Dave

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JTAPI-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JTAPI-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JTAPI-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".