Sometimes it's nice to see which steps, a call executed, very quickly, without needing to recreate the call flow and performing a risky Reactive Debug session. Here are the steps to do so:
Step 1: Enable Engine Debugging
In order for this feature to work, you will need to enable ENG debugging under trace configuration within CCX Serviceability.
Step 2: SSH in to Master Node
You are free to use any SSH client you like. Keep in mind that this is the platform administrator account, and not the same one you use for RTMT or CCX Administration. Although, in many environments the username and password pair are the same for all of these accounts. It's common for this username to be one of: Administrator, administrator, osadministrator, or osadmin. Note the case on the first two.
Step 3: Find the implId
Start by running the following command to get the Implementation ID for the call, which we will use in the next step to find the Task ID. Replace the example phone number with your calling party number.
Find when the implId gets associated to the Task ID. Use the implId from the previous step, within this command, to find your Task ID. We'll then use the Task ID from this step, in the next step, to find all of the executed steps for this call.
trunc...MediaId:4654465/3 Task:42000000286 associated with Task ID: 42000000286...
Step 5: Find All Script Steps
Find all of the script steps your call executed by supplying your Task ID, from the previous step, in this command.
Note that Call Subflow borrows the same implId and Task ID, so you'll see Sub Flow step executing, an advantage over Reactive Debugging. (Hence the max executed step counter does not reset upon call subflow)
Also note that, a call which transfers from script to script will begin a new call, keep the same implId, but get a new Task ID, and therefore its own set of executed script steps. (Hence the max executed step counter resets upon transfer)
Say the script was holding a transfer extension in a variable. While you'll see the variable name in the above steps, you will not see the String value. So, to get the extension you actually transferred the caller to, use this step in addition to the above.
This is how you get the Agent User ID, name and extension who answered the call. So, tieing back into the above bonus step, there is a value in there that you'll need, which is the "session=" number. Let's pretend the number was 53000095261.
Hi Everyone: I am trying to figure out a Consider If Formula for an Agent ID/Peripheral Number associated with a Skill Group. Basically, I am trying to queue to an agent, and if my agent is not available, I want to queue to a skill group this a...
Hello,we have deployed on-premise Cisco Jabber 12.9 and we get the contact's picture from AD successfully but the user's picture is not showed in "My profile and settings"we have tested Cisco Jabber 14.0 too.our jabber-default.xml file is:<?xml version...
We have Cisco ISR4331 with the following IOS and CME versionIOS Version: IOS XE Software, Version 16.06.04CME Version: Version 12.0 (SIP)We would like to know if the following version of SDK is compatible with CME version in order to develop the integrati...
Hello community, I am currently reading the newest CLOR 350-801 Cisco Press book. There is a section in the SIP-Protocols description which recaps how early offer and delayed offer works. Here is an excerpt from the book about early offer: The O...
Hello, I am a beginner in CUCM, and our company inherited a few clients that use it. I know how to add phones, add/update DNs, create translation patterns, etc..., but I've been having this issue. Whenever I make a change to a DN, the phone unregiste...