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

Etoile,

The problem is a bit more complex then I was thinking:
But it takes place only under certain circumstance when a conference.leave is called before a conference.enter.

I am going to add a protection in the code, a "status variable" that will automatically return from  conference.leave if conference.enter was not called before.

Mar 18 08:33:34 bayonne: dx(147): GCEV TDX_PLAY HDL:302 chdev:303
Mar 18 08:33:34 bayonne: dx(147): step 3 gosub(conf)
Mar 18 08:33:34 bayonne: dx(147): step 3 cleardigits()
Mar 18 08:33:35 bayonne: dx(147): GCEV_DISCONNECTED HDL:302
Mar 18 08:33:35 bayonne: dx(147): step 2 conference.leave(=name,%confname)
Mar 18 08:33:35 bayonne: trace: pid=186551 reason=11
Mar 18 08:33:35 bayonne: trace(0): /usr/local/lib/bayonne/1.2.13/bayonne.bin(stackTrace__Q23ost5Debugi+0x20) [0x8079604]


I see your validation was stronger then I was thinking but still there is something somewhere, I am testing this under heavy stress so maybe this problem did not take place on your servers.

Many thanks,

Julien




-----Original Message-----
From: Julien Chavanton 
Sent: March 18, 2005 9:54 AM
To: '[email protected]'; [email protected]
Subject: 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