We may want to do a dx_stopch(), there is no problem doing it even if it is not required.
Julien
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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; 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
_______________________________________________ Bayonne-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bayonne-devel
