CCX script debug error:Task16000000137 Acceptstep:trigger is not a Contact Application Trigger

Posted Fri, 11/20/2009 - 2:01pm by harisivaji

Hi,

Iam new to this UCCX domain iam learning my self about scripting techniques.So just i want to familiarize my self with various options in editor for that when i try to debug default script iam getting the error:Task16000000137 Acceptstep:trigger is not a Contact Application Trigger.Iam not doing a reactive debugging.

Can you explain basic details of step by step how to debug an application.

Iam reading Cisco Script editing Vol1,2,3 but i feel its not in detailed

Since i am new i have Heap of Doubts, i will come one by one.

 

Thanks,

Hari

‹ Placing a call from UCCX and using some prompt if successfull CRS Script Editor Crashes after 14% with XP ›

CCX script debug

by harisivaji - Nov 26 2009 - 8:44am

Thanks Alex i will try this out

 

uccx_admin's picture

CCX script debug

by uccx_admin - Nov 23 2009 - 8:24pm

Hari,

The basics of debuging a script are pretty simple.  I am going to attempt to do a video blog showing how to do a debug on a script in the next two weeks.  But here is a brief rundown on how to do it. 

1.  Create a script in the CRS Editor, when you are done make sure you click on "Tools/Validate" and make sure there are no errors in the script. 

2.  Upload the script to the http://[ipofCRSServer]/appadmin page under the Application Scripts tab. 

3.  Your script will need to have a JTAPI trigger and be able to recieve an inbound call.  The script type should be JTAPI not HTTP!, You cannot easily debug an HTTP Trigger. 

4.  Back in the editor, I believe off the top of my head under "edit" you will see a "reactive debug" option, clicking on this will give you 60 seconds to dial into the scripts JTAPI trigger, once you have called the script you will notice the editor will pull up a 2nd pane ( copy of your script ), this copy is a "live debug" of the script.  There will now be the Step into/over/etc buttons in the editor for you to use to step through your script.

5.  While the debug is running you can see the parameters or variables changing in real time according to the scripts actions.

Hope that helps you out,

Alex

Recommended Reading: