I have a queue-based script where that is not ending at the terminate step. More specifically, if an agent becomes available and the call is dequeued, because it has made the connection, it advances to the terminate step. However, it does not advance to the exit step and the step counter increments until the 1000 mark (whereby the script then fails). This script responds the same way if I have a caller that hangs up while in queue. what I cannot figure out is why this is happening. The End step is directly after the exit step, but it will not advance to that.
This invariably hangs the session which will eventually make the application unusable (after all sessions are hung).
so, when you want ccx to end the call, you use terminate. In my script, when it goes to the terminate step, it does not end the script, but it also won't continue to the next step. To address this, I just send it to end (unfortunately, it sends the caller to the default script and the cisco voice tells the caller we are having system problems).
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...