UCCE

https://<server>/unifiedconfig/config/activedirectorydomain
https://<server>/unifiedconfig/config/deployment
https://<server>/unifiedconfig/config/deploymenttypeinfo
https://<server>/unifiedconfig/config/machineinventory
https://<server>/unifiedconfig/config/version
https://<server>/unifiedconfig/config/routingtype
https://<server>/unifiedconfig/config/registry
https://<server>/unifiedconfig/config/status
TCD PeripheralCallKey = (globalCallID_callManagerId * (2 to the 24th)) +  globalCallID_callId
TCD PeripheralCallKey = (globalCallID_callManagerId * (16777216)) +  globalCallID_callId

example:
TCD PeripheralCallKey = (4 * (16777216)) +  70002)
  • CAD Supervisor & Client download from
    • http://<CAD base services IP address>:8088/TUP/CAD/Install.htm
  • CAD Admin from here:
    • http://<CAD base services IP address>:8088/TUP/CAD/Admin.htm
  • CAD SR from here:
    • http://<CAD base services IP address>:8088/TUP/CAD/SR.htm
  • CAD browser edition
    • https://CAD-server/cadbe/CAD-BE.jsp
    • http://CAD-server:8088/cadbe/CAD-BE.jsp

CAD LDAP

  • On a test environment, to understand better how the Cisco CAD LDAP server is setup you can use the following method
    • Download and install the free LDAP client from http://jxplorer.org/
    • This is a Java based program, so requires you install the Java Run Time on your PC
    • Run JExplorer and connect to the CAD server using the following details:
  Version: LDAPv2
  Host: IP address of the Server
  Port: 38983
  Base DN: o=Spanlink Communications
  Security: Anonymous

This example has a “:” as the separator.

Call.PeripheralVariable8 == Variable1:Variable2"

Variable1 == left(Call.PeripheralVariable8,((find(":", Call.PeripheralVariable8))-1))
Variable2 == right(Call.PeripheralVariable8,((len(Call.PeripheralVariable8)-(find(":", Call.PeripheralVariable8)))))
  • Finesse
  • CVP
  • GW
  • CUIC
  • CCE
  • CM

Small Agent / Generic PG: Max of 5 (excluding CTIOS)
Large Agent / Generic PG: Max of 20 (excluding CTIOS)


Reference: Page 326 of UCCE 11 SRND Extract below:
All-Event clients (CTI Server)
Max of 5: For 2 vCPU VMs built from the Small Agent PG OVA. These clients are in addition to the 2 CTI OS connections. You can reduce the number of All-Event clients to support more monitor mode connections.
Max of 20: For 4 vCPU VMs built from the Large Agent PG OVA. These clients are in addition to the 2 CTI OS connections. You can reduce the number of All-Event clients to support more monitor mode connections.

Reason Code Reason Description
-1 Agent reinitialized due to peripheral restart
-2 PG reset the agent - PG Failure
999 A Finesse supervisor forced an agent state change.
-3 Administrator modified the agents extension while the agent was logged in
32767 The agent's state was changed to Not Ready because the agent did not answer a call and the call was redirected to a different agent or skill group.
50002 CTIOS Failure - Agent Logged Out Incorrectly?
50003 The agent was logged out because CUCM reported the agents device as out of service
50004 The agent was logged out due to agent inactivity as configured in agent desk settings
50010 Not Ready - The agent did not receive multiple consecutive calls routed to him/her. The system makes the agent Not Ready automatically so that additional calls are not routed to the agent. By default, the number of consecutive calls missed before the agent is made Not Ready is 2.
50020 Logged Out Due to been Reskilled
50040 The mobile agent was logged out because the call failed.
50041 Not Ready - The agent's state was changed to Not Ready because the call fails when the agent's phone line rings busy.
50042 The mobile agent was logged out because the phone line disconnected when using nailed connection mode.
51004 Not Ready - This reason codes applies if an agent logs onto an extension which already has a call or if the agent is on a call when the PG restarts.