User Guide

•
The System PG presents a single peripheral interface to the IPCC Gateway PG through
consolidated reporting of agent and call states.
•
Scripting and reporting are more intuitive, for example: direct use of Queue to Skill Group
node and integrated IVR and CCM reporting.
•
Device Targets are no longer required.
Interworking the System PG and the IPCC Gateway PG
•
The IPCC Gateway PG is an all-events CTI client receiving consolidated state information
through CTI Server attached to the System PG.
•
The System PG diverts the routing of all calls arriving on controlled DNs to the IPCC Gateway
PG.
•
The System PG feeds most configuration elements to CTI Server for retrieval by the IPCC
Gateway PG (for example: auto-configuration and device monitoring).
•
The System PG ensures consistent reporting by sending events to CTI Server when certain
call attributes change such as call type, queue point.
Summary
•
The System PG can be deployed standalone with a mixture of CCM and IVR peripherals.
•
The System PG presents a single peripheral model to the IPCC Gateway PG.
•
The System PG presents a single routing client interface to Central Controller.
•
The System PG is easier to configure and script than the IPCC Enterprise PG.
•
Combined reporting of agent and IVR activity.
•
CVP is not supported, IP IVR must use SCI.
System IPCC to ICM Object Mapping
Following is a list of ICM objects either not used or renamed in System IPCC:
•
System IPCC does not use or require these ICM objects: services, labels, persons, device
targets, translation routes, dialed number plan, and trunk groups.
•
System IPCC does not support post routing.
•
System IPCC does not support sub skill groups.
•
System IPCC's call variables are equivalent to ICM's expanded call context variables.
Scripting and Media Routing Guide Cisco Unified ICM/Contact Center Enterprise & Hosted Release 7.5(1)
183
Chapter 11: Scripting in an IPCC Environment
System IPCC