|
From: | Etoile Dièse |
Subject: | Re: [Bayonne-devel] Re : Slog stops producing traces in syslog/message- got event 89 - TDX_ERROR |
Date: | Fri, 08 Apr 2005 19:26:37 +0200 |
User-agent: | Opera M2/7.54 (Win32, build 3865) |
We may want to do a dx_stopch(), there is no problem doing it even if it is not required.Julien -----Original Message-----From: address@hidden [mailto:address@hidden On Behalf Of Etoile DièseSent: March 13, 2005 12:20 PM To: address@hiddenSubject: [Bayonne-devel] Re : Slog stops producing traces in syslog/message- got event 89 - TDX_ERRORHi 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; 783a782case TDX_ERROR:Cheers,
Be careful !!!!Following the mail you've just mentionned, I posted something else because that was not the good solution :
Here is what I posted a few days after : _____________________________________________________________________________________ Hi, Following my last mail, it seems that ignoring TDX_ERROR is not a good idea : When this event occurs after having started to play a file, the channel get stucked. It seems better to handle it that way : case TDX_ERROR: event.id = TRUNK_AUDIO_IDLE; trunk->putEvent(&event); break; ___________________________________________________________________________________________ We are using this piece of code on our production servers. But I think you're right, we could do a dx_stopch().We don't, because it seems to work without it (I mean, the next play/record/getdigit
is working). FdR/ED -- Etoile Dièse - www.etoilediese.com
[Prev in Thread] | Current Thread | [Next in Thread] |