Cisco Cisco IPCC Web Option プリント

Any subsequent call control must be performed from the agent desktop application. The PG will then 
transmit the necessary subsequent call control via JTAPI to Unified CM for the two CTI ports to do 
whatever is needed to the media of the call. (See 

.)

The two CTI ports (local and remote) are logically and statically linked within the PG software via the 
documented naming convention required. The CTI Ports are registered at PG initialization. Call 
observers are added for these two CTI Ports when a mobile agent logs in using these CTI Ports. Call 
control for the CTI Ports (and thus the call) is provided by the PG. As mentioned earlier, the voice path 
is between the two voice gateways.

When a mobile agent is in the office, the agent can log in as a non-mobile agent from a JTAPI monitored 
and controlled phone, using the same agent ID. (This document refers to these non-mobile agents as local 
agents.) Historical call reporting does not distinguish between calls handled as a mobile agent and those 
handled as a local agent.

Unified CCE 7.x and Unified Mobile Agent are supported with Unified CM 4.1(3) and all subsequent 
Unified CM releases.

Unified Mobile Agent functionality is supported with both the System PG and Generic PG.

Queueing calls to mobile agents is supported with both Cisco Unified IP IVR and Unified CVP.

190009

Caller

VPN

Unified CCE
Mobile Agent

Unified CM

Cluster 

Unified CCE

Central Controller

and PG

Unified CCE

AW, HDS

WebView Server

IP IVR/CVP

CTI Ports

Call Control / CTI

VoIP

Circuit Switched Voice