Re: Avaya Jtapi Issue

sabitha aboobacker <[email protected]>
Newsgroups gmane.comp.java.sun.jtapi
Message-ID <[email protected]>
dave,
i'm new to jtapi stuff and dont know about Avaya's implementation of Jtapi.
regards,
sabitha.

>From: "David E.Ybarra" <[email protected]>

>Reply-To: Discussion list for Java Telephony API <[email protected]>

>To: [email protected]

>Subject: [JTAPI] Avaya Jtapi Issue

>Date: Thu, 22 Apr 2004 18:55:07 -0600

>

>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".

----------
Post Classifieds on MSN classifieds. Buy and Sell on MSN Classifieds.
===========================================================================
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".
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.