Cisco Cisco Customer Voice Portal Downloads

Page of 104
16. ICM Service passes connect to agent request to SIP Service.
17. A disconnect VRU request passes from SIP Service to SIP Proxy Server.
18. A disconnect request is passed from SIP Proxy Server to Egress Gateway.
19. Egress Gateway passes TDM hangup request to VRU.
20. SIP Service passes connect to agent request to SIP Proxy Server.
21. SIP Proxy Server passes connect to agent request to Unified CM.
22. Unified CM informs Unified ICME that call was received by agent.
SIP Coresident with VRU PG
In relatively low volume Call Director call flow scenarios, the SIP Service can be installed
together with the ICM Service directly on a VRU PG. (That is, the VRU PG becomes the Call
Server. Installation of the IVR Service and H.323 Service is also allowed, though these parts
of the Call Server are inactive in the present case.) This provides a streamlined deployment
option for customers who need little more than to SIP-enable their Unified ICME call control.
H.323-Based Call Director Scenario
Table 4: Components Used for H.323-Based Call Director Scenario
Not Used
Installed (but
Inactive)
Optional
Required
Component
X
SIP Service (part of Call Server)
X
IVR Service (part of Call Server)
X
ICM Service (part of Call Server)
X
H.323 Service (part of Call
Server)
X
VXML Server
X
Call Studio
X
Ingress Gateway
X
VXML Gateway
X
SIP Proxy Server
X
Gatekeeper
X
Operations Console
X
Reporting Server
X
ASR/TTS
X
Media Server
X
DNS Server
Planning Guide for Cisco Unified Customer Voice Portal Cisco Unified Customer Voice Portal 4.1(1)
31
Chapter 3: Choosing a Deployment Model
Call Flow Models