RE: Re : Slog stops producing traces in syslog/message- got event 89 - TDX_ERROR

Hi Etoile,

I was going to investigate this because I think there is an intermittent problem with the voice library.

As you say the current way to handle voice event may work but it does not look right to handle Voice library event like this.

TDX_ERROR is regarding the voice resources function problem.
One example is trying to do a dx_setevtmsk() on a busy voice resources.
We may do a dx_stopch() 
I have made correction to do one dx_setevtmsk() during startup since there is no need to call it several time.

*Looking at your web site, I see we are working on the same industry.

Julien


-----Original Message-----
From: bayonne-devel-bounces+j.chavanton=oneworldinteractive.com@gnu.org [mailto:bayonne-devel-bounces+j.chavanton=oneworldinteractive.com@gnu.org] On Behalf Of Etoile Dièse
Sent: March 13, 2005 12:20 PM
To: [email protected]
Subject: [Bayonne-devel] Re : Slog stops producing traces in syslog/message- got event 89 - TDX_ERROR

Hi again,

Last news : adding a break when receiving TDX_ERROR
seems to solve the problem.
The code we are using is now ignoring TDX_ERROR :
Here is the diff that can be applied to  
bayonne1.2.14/driver/globalcall/driver.cpp :

diff driver.new.cpp driver.cpp

767,768d766
<               case TDX_ERROR:
<                       break;
783a782
>               case TDX_ERROR:

Cheers,

-- 
Etoile Dièse - www.etoilediese.com



_______________________________________________
Bayonne-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel