UCCX Logs

[rjunaid.sh]

Hey experts, am trying to study UCCX i wanted to know logs and trace like are they different from each other? and how can i trace my call like from where it start and from where it end ? I wanted to check on which process my call get diturbed , as i told am totally new i have no idea about anything so please help me to understand and find my calls.

How can i take logs? we can take logs only from CLI or also from GUI?

Are log and trace are different? if they are how to take both?

Any help would be appreciated, thanks in advance.

[Anthony Holloway]

I wonder if this article I wrote will help you:
https://community.cisco.com/t5/collaboration-voice-and-video/uccx-viewing-executed-script-steps-via-cli/ta-p/3162231

[rjunaid.sh]

Hey Anthony, thanks for replying i study what you shared  but that didn't work for me i try to check logs with those command but i didn't get any result idk why but that's what happening with me can you please help

[Anthony Holloway]

I sure can.

First, let's just see if you're system is doing ENG debugging by running this command on the CLI of UCCX (do it on both servers if you have 2 servers).

file search activelog uccx/log/MIVR "execute step of task" ignorecase

Please post the contents of your CLI session (remove sensitive info) for me to see what it did, or did not do.

[rjunaid.sh]

Thanks for replying, am getting this when i run following command

admin:file search activelog uccx/log/MIVR "execute step of task" ignorecase

Searching path: /var/log/active/uccx/log/MIVR

Search completed

admin:file search activelog uccx/log/MIVR "call.received.*94000" ignorecase

Searching path: /var/log/active/uccx/log/MIVR

Search completed

[Anthony Holloway]

So it looks like you are running the command correctly, but there's no output.

Do you have just one UCCX server, or two?

If two, can you run it on the other server as well?

If just one server, can you run this command to see if there are files being updated:

file list activelog uccx/log/MIVR date detail

Also, can you go to UCCX Serviceability > Trace > Configuration and Restore Default, then click ENG Debugging, then save, and then make another test call, followed by running the command again?

[Tanner Jackson]

As far as GUI tracing goes, using Reactive Debugging in UCCX Editor has proven to be the most valuable to me. It will allow you to place a test call to the script in which you can manually "walk" the call step by step through the script to see how the call flows through the script.

CAUTION - Do be careful when you use it on the script, though, as it will intercept the next call placed to it so either copy a script you want to debug and place a test call to the copied version with a new trigger or open the script up after hours to debug if acceptable by the business unit.

Helpful link:

https://developer.cisco.com/docs/contact-center-express/#!using-reactive-debugging/using-reactive-debugging