Cisco Cisco Customer Voice Portal 8.0(1)

Page of 104
Note that ASR is not generally used with either Standalone Branch version. This is because
ASR requires G.711 encoding, which is very bandwidth intensive, and bandwidth from branch
offices to data centers is usually at a premium. Users who require this capability should contact
their Cisco support representative.
Note, however, that TTS is not affected by the restriction that applies to ASR.
Physical Models
Physical models are essentially hardware configurations. They describe which logical servers
are installed on which physical servers. Physical models are to a large extent determined by
what geographic model you are following, the size of your system, and your performance
requirements. With regard to these considerations, see the discussion of geographic models
above, the Hardware and Software System Specification for Cisco Unified Customer Voice
Portal Software Release 4.1(1)
, and the Cisco Unified Customer Voice Portal (CVP) Release
4.0 Solution Reference Network Design (SRND)
 document.
There are four basic physical models.
1. Typical for Unified ICME Integrated:
- Call Server (with IVR/H.323/SIP/ICM Services or combinations thereof)
- VXML Server
- Reporting Server
- Operations Console
2. Typical for Standalone:
- Call Server (with only ICM Service activated) on PG (if using ICM Lookup)
- VXML Server
- Reporting Server
- Operations Console
3. Streamlined for SIP Call Director:
- Call Server (with only SIP and ICM Services activated) on PG
- Reporting Server (possible, though unlikely)
- Operations Console
4. Laboratory (All-in-a-Box):
This model, in which all Unified CVP components can be installed on a single physical
machine, is intended solely for testing purposes and is not supported as a deployed system.
Planning Guide for Cisco Unified Customer Voice Portal Cisco Unified Customer Voice Portal 4.1(1)
45
Chapter 3: Choosing a Deployment Model
Physical Models