Saturday, December 19, 2015

UCCX 10.6 Notes

Miscellaneous UCCX v10.6 notes: 


Calling Search Space for Redirect on your triggers by default is set to Default.  This means that UCCX will route calls through the application and script called by the trigger with the caller's CSS, not the trigger's CSS.  If your caller is not capable of reaching the agents or other destinations defined in the application and script directly your call will be rejected.  This is typically not an issue but where you might have PLARs set up with very restricted CSSs, sending the PLAR to a UCCX trigger may fail.  This can be modified per trigger on at least UCCX 8.5 and beyond.  See bug CSCso91760 at 20CSCso91760 for more redirect information.  See regarding basic SCCP PLAR setup.


Finesse log in usernames are still case sensitive at this time. If MS AD says your username is jAnE123, you need to log into Finesse as jAnE123.


To enable support for the Finesse browser based client:
at CLI, run utils uccx finesse activate 
This needs to be run on both master and secondary HA nodes and both servers need to be rebooted


To verify Finesse master node and health:
https://<IP of Master node>:8445/finesse/api/SystemInfo 


To access Finesse client:
https://<IP of Master node>:8445/desktop/ 


The default Finesse agent client on UCCX 10.6 includes an Agent CSQ Statistics Report and an Agent Team Summary Report.  If an agent is assigned to a team (could even be the default team) and there is no CSQ associated with the team, the user will see "Error processing report. Refresh page or contact administrator."  Add CSQs to your teams.  Here's a before and after screenshot:

Broken link to Agent CSQ Statistics Report:
Default Finesse agent page with working Agent CSQ Statistics Report

The default Finesse agent client on UCCX 10.6 includes an Agent CSQ Statistics Report. Your resources / agents must on a team that is assigned a CSQ to see the CSQ statistics. An agent may have a skill that allows them to take a call for a CSQ but they may still not be able to see the CSQ statistics in the Agent CSQ Statistics Report. If an agent has a skill that allows them to take a call for a CSQ, but they are on a team that is not assigned that skill, the user will see "Error processing report.. Refresh page or contact administrator." Again, add CSQs to your teams.

VOIP Monitor Subsystem in PARTIAL SERVICE
A search of Cisco documentation will point you here: but the issue in my case was a bit more devious.  After removing a HA UCCX server from the cluster (long story...) the second server remained an option as a VoIP Monitor Service and Recording and Playback Service.

From UCCX Desktop Administrator you can choose "Remove VoIP/Recording and Playback" link, select the associated server and hit Remove.  I found at that point I still needed to restart the UCCX Engine to return it to FULL SERVICE.


Cisco Tomcat has a maximum inactivity timeout ouf 14400 seconds.  If you are intending on using CUIC as a wallboard, note you will be required to restart the CUIC instance if there is no activity in your call center for 4 hours (i.e. overnight, closed hours, etc.).

You can find some background here:

You can find my dirty workaround here:

If you are creating custom desktop layouts for teams in Finesse and your administrator account is also assigned to that team, that account will be locked out of the Finesse administrator.  Make sure you have an administrator account that is not assigned to a team before customizing Finesse layouts.

See bug CSCur71176.

It looks like this when you hit it:



Finesse sample gadgets for older versions can be found at  There are changes in both the XML and javascript unique to each version.  A nice write up on the same can be found here:


The initial Finesse gadget heights can be set using

The tab name in the WorkFlowScreenPop sample gadget is defined by the Window Name in the Workflow action found in Finesse administration.  You won't find it as-is in the gadget code.



Friday, December 04, 2015

QoS conversions and testing with extended ping commands - version 2

Years ago I posted a tip regarding using Cisco IOS devices' extended ping capabilities to emulate traffic with various QoS / quality of service markings.  You can find the original post here:

Recently I happened upon a great post at that provides a JPG with more complete examples of various DSCP, tos, IP precedence, etc. values.  The latest version current appears at  Thank you to for putting that together.

Here is their current v3 chart:

Below is the body of my post showing how to use the Cisco IOS ping command to tag ICMP traffic with various markings.  Using the TOS values from the table above you should be able to emulate just about any traffic type for QoS class map testing:

QoS conversions for extended pings sample

To emulate DSCP tagged traffic:

ef = dscp 46 = 101110 = tos 0xb8 (184) = ip prec 5
af31 = dscp 26 = 011010 = tos 0x68 (104) = ip prec 3
af32 = dscp 28 = 011100 = tos 0x70 (112) = ip prec 3
cs3 = dscp 24 = 011000 = tos 0x60 (96) = ip prec 3

voice_gw#ping ip
Target IP address:
Repeat count [5]: 100
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface:
Type of service [0]: 184 --->dscp is ef
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.

A simple way to calculate is to put your binary representation of the value into your calculator and add two zeros to the end (i.e. 101110 becomes 10111000).

If you are looking to emulate IP Precedence values, use 224,192,160,128,96,64,32,0 for IPP 7 to 0