« Back to TCL-API

Script failing because of UnknownEvent

Combination View Flat View Tree View
Threads [ Previous | Next ]
I'm getting an UnknownEvent that is causing my script to die. This happens about one minute after issuing a leg setup:
 

  Feb 24 01:33:03.228: //19526//AFW_:/AFW_FSM_Drive: FSM no match for (CALLACTIVE[4],UnknownEvent[62])
  Feb 24 01:33:03.228: //19526//SERV:/AFW_Service_Process_Space:  Ill behaved Service script is being closed

 
What could be causing this?
 
thank you

Hi Adolfo,

could you please send us the complete logs to find the issue.

Thanks,
Raghavendra

Hi Adolfo,

i think there are two outgoing leg id's passed to the leg_timer, please try to pass one leg id to the timer.

Feb 24 01:31:32.025: //19526//TCL :/tcl_TimerObjCmd: timer start leg_timer 299 leg_outgoing
Feb 24 01:31:32.025: //19526//TCL :/tcl_TimerStartObjCmd: timer start leg_timer 299 leg_outgoing
Feb 24 01:31:32.025: //19526//AFW_:/vtd_lg_outgoing: argc 4
Feb 24 01:31:32.025: //19526//AFW_:/vtd_lg_outgoing: Legs [19530 19529 ]

Thanks,
Raghavendra

RE: Script failing because of UnknownEvent
Answer
2/27/12 5:16 PM as a reply to Raghavendra Gutty Veeranagappa.
Hi Raghavendra,

thanks for your answer. Yesterday I noticed that same thing you saw, but being a novice with all this, I wasn't sure this was the cause.

I decided to try to fix those two outgoing legs and what I did was that in the place where the outgoing call is disconnected I used to have this:

connection destroy con_all

but now I have this:

timer stop leg_timer leg_outgoing
connection destroy con_all
leg disconnect leg_outgoing


The code I was using is based on a Cisco sample that is in the manual, and that code wasn't calling leg disconnect. I suspect that adding that piece of code is what fixed it for me.


Your suggestion makes me thing that is the case.

Thank you for your time and your help