Created by: Aaron Birk on 14-01-2010 08:49:38 PM So I am having a few problems with a script that had been working fairly well for awhile. Just recently, there have been two instances of my script that seems like it is hung. In short, the script accepts a call and the user can enter a 7digit number. The script then tries to make a call to that 7digit number. (its used as a front end for MeetMe conferencing) If the script cannot complete the call, it tries again in 30 seconds. After 15 minutes, the script is supposed to end the call. I have this running on two CMM's running 12.4(25b) IOS. One CMM has had an instance hung since January 7th and the other CMM has one hung from January 13th. I will include my debugs and show commands at the bottom of my post. I have tried a couple different ways of ending the session and have had no luck. I tried, "clear call voice cause 1 id 77E4 (this is the SID of the call)", "call app sess stop id 77E4", "call app sess stop hand meetme (meetme being the name of the script)" Does anyone else know of any other way of closing this call?
CMM1: CMM1#sh call app act sess sum SID Application Name Stat Err Cnt Log Start Time 77E4 meetme Y 3 N Jan 13 09:57:45 7DF5 Default Y 0 N Jan 14 12:58:14 7DF6 Default Y 0 N Jan 14 12:58:28 7DFD Default Y 0 N Jan 14 12:59:40 7E10 Default Y 0 N Jan 14 13:01:43 LOGS..... 13294905: Jan 13 09:57:44.306 CST: //135391//TCL :/tcl_PutsObjCmd: Calling - 43028 13294906: Jan 13 09:57:44.310 CST: 13294907: Jan 13 09:57:52.506 CST: //135391//TCL :/tcl_PutsObjCmd: Too few numbers - 1 13294908: Jan 13 09:57:52.506 CST: 13294909: Jan 13 09:57:59.674 CST: //135391//TCL :/tcl_PutsObjCmd: Meeting number 7274482 13294910: Jan 13 09:57:59.674 CST: 13294911: Jan 13 09:58:02.674 CST: //135391//TCL :/tcl_PutsObjCmd: 13294912: **** act_TerminateSetup 13294920: Jan 13 09:58:42.983 CST: //135391//AFW_:/AFW_FSM_Drive: Tcl_Eval to drive FSM inside Tcl modulespace. code=1 code=ERROR 13294921: Jan 13 09:58:42.983 CST: TCL script failure 13294922: Result: 13294923: CallSetup already active on leg 13294924: Jan 13 09:58:42.983 CST: TCL script failure errorInfo: 13294925: CallSetup already active on leg 13294926: while executing 13294927: "leg setup $destination callInfo leg_incoming 13294928: (procedure "act_CallSetup" line 16) 13294929: invoked from within 13294930: "act_CallSetup" CMM2: CMM2#sh call app act sess sum SID Application Name Stat Err Cnt Log Start Time 1284 meetme Y 19 N Jan 7 10:02:32 1B6A Default Y 0 N Jan 14 10:15:44 1C05 Default Y 0 N Jan 14 13:09:36 1C08 Default Y 0 N Jan 14 13:10:01 1C19 Default Y 0 N Jan 14 13:28:26 LOGS..... 19039: Jan 7 10:02:33.074 CST: //16229//TCL :/tcl_PutsObjCmd: Calling - 7139397700 19040: Jan 7 10:02:33.074 CST: 19043: Jan 7 10:02:46.754 CST: //16229//TCL :/tcl_PutsObjCmd: Meeting number 7241728 19064: Jan 7 10:07:08.750 CST: 19076: Jan 7 10:07:23.950 CST: //16229//AFW_:/AFW_FSM_Drive: Tcl_Eval to drive FSM inside Tcl modulespace. code=1 code=ERROR 19077: Jan 7 10:07:23.950 CST: TCL script failure 19078: Result: 19079: CallSetup already active on leg 19080: Jan 7 10:07:23.950 CST: TCL script failure errorInfo: 19081: CallSetup already active on leg 19082: while executing 19083: "leg setup $destination callInfo leg_incoming 19084: (procedure "act_CallSetup" line 16) 19085: invoked from within 19086: "act_CallSetup"
Subject: RE: Help with hung script Replied by: Yawming Chen on 14-01-2010 10:15:23 PM Did you recently upgrade IOS ? looks like it's trying to setup a call leg but it's already active. Without script it's hard to say what went wrong. You can open a SR on Cisco developer Support. <a>http://developer.cisco.com/web/devservices</a>]
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
