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

I Etoile,

I am using your conference implementation (I like it is convenient)


Look at this script:

# # # # # # # # # # # # # # # # # # # # # # # #
set %confname %pstn.dnid

conference.enter name=%confname attr=periodicTone
 slog.crit "Entering conference: %confname"
 sleep 9999
conference.leave name=%confname
 hangup
return

^hangup
 conference.leave name=%confname
return
# # # # # # # # # # # # # # # # # # # # # # # #


There is one problem is that conference.leave crash when there call is not in conference, I think we shall keep a status in Bayonne layer so that this command can be called without problem even if the caller is not in conf.

I will check this.
Julien



-----Original Message-----
From: Etoile Dièse [mailto:[email protected]] 
Sent: March 18, 2005 5:43 AM
To: [email protected]
Cc: Julien Chavanton
Subject: Re : Slog stops producing traces in syslog/message - got event 89 - TDX_ERROR

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;


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