Cisco Cisco IP Contact Center Release 4.6.1 Leaflet

parent/child is not the same. For a TDM PG, the CTI-Server is connected to the PG ACD, which is part 
of the parent system. This would be the equivalent of having a CTI-Server connected to the Gateway PG. 
To think of it another way, it is like using CTI directly to an ACD instead of the CTI Server, in which 
case network consultative transfer is not possible either. In parent/child deployments, CTI is connected 
to the child PG. Having CTI connected to the child PG does not provide the necessary network call ID 
and other information necessary to allow network consultative transfer.

Note, however, that network blind transfer is still possible using any client (for example, Unified CVP 
or a NIC) on the parent system when a post route is initiated to the parent system from the child.

Unified CCE 7.0 agents can use Unified CM 5.0 SIP phone models 7941, 7961, 7970, and 7971. The 
7940 and 7960 phones support SIP with Unified CM 5.0, but they cannot be used for Unified CCE 
agents. The lower-end Cisco IP phone models and third party phones also cannot be used as SIP phones 
for Unified CCE agents.

Unified IP IVR is notified of caller entered digits (DTMF input) by way of JTAPI messages from 
Unified CM. Unified IP IVR and Unified QM do not support mechanisms to detect inband DTMF digits. 
In deployments with SIP voice gateways or SIP phones that support only in band DTMF (or are 
configured to use inband DTMF per RFC 2833), Unified CM must invoke an MTP resource to convert 
the inband DTMF signaling to out-of band signaling so that the Unified IP IVR can be notified of the 
caller entered digits. Therefore, in environments that include these SIP phones or gateways, it is 
necessary to provision sufficient MTP resources. Keep this in mind if the phones need to interact with 
Unified IP IVR. Likewise, CTI ports do not support in-band DTMF (RFC 2833). The Mobile Agent 
feature relies on CTI ports, so MTP resources are required when in-band DTMF (RFC 2833) is 
negotiated.

Cisco Unified CCE does not support using Q.SIG trunks with the Unified CM deployment.

For deployments using Cisco Unified Mobile Agent, it is important to consider the location of the voice 
gateways that will be used to call agents because their location has design considerations for silent 
monitoring, call admission control, and other areas. For design guidance and considerations for 
implementing Cisco Unified Mobile Agent, see the chapter on 

Cisco Unified CCE 7.5.1 introduces support for multiple instances of CTI OS over a single PG. Prior to 
Release 7.5, only one instance of CTI OS could exist on a Peripheral Gateway/CTI Gateway 
configuration regardless of the number of peripherals configured on the Peripheral Gateway. 
Release 7.5.1 adds support to allow multiple CTI OS servers connecting to a single CTI Server. Up to 
ten CTI OS servers are allowed per PG.