Cisco Cisco Customer Voice Portal 8.0(1)
D-1
Cisco Customer Voice Portal (CVP) Release 3.1(0) Configuration and Administration Guide
A P P E N D I X
D
Configuring Cisco Content Services Switch (CSS)
for Use with Customer Voice Portal
for Use with Customer Voice Portal
This chapter explains how to configure a Cisco Content Services Switch (CSS) for use with Customer
Voice Portal (Customer Voice Portal) components. You should be familiar with the general concepts of
configuring a Cisco Content Services Switch outlined in the CSS Administration Guide. For information
about specific hardware and software versions, refer to the Cisco Customer Voice Portal (Customer
Voice Portal) Software Bill of Materials.
Voice Portal (Customer Voice Portal) components. You should be familiar with the general concepts of
configuring a Cisco Content Services Switch outlined in the CSS Administration Guide. For information
about specific hardware and software versions, refer to the Cisco Customer Voice Portal (Customer
Voice Portal) Software Bill of Materials.
General Approach
In this application of CSS, the engine is used primarily to direct initial session requests for a particular
type of service. There are four types of services:
type of service. There are four types of services:
•
http prompts
•
ASR/TTS
•
Customer Voice Portal application server
•
Customer Voice Portal VoiceXML Server
Sticky and/or stateful connections are only maintained for Customer Voice Portal VoiceXML Server
since the same Customer Voice Portal VoiceXML Server must process all VXML requests for a
particular call. Sticky connections are not required for the other three types of services.
since the same Customer Voice Portal VoiceXML Server must process all VXML requests for a
particular call. Sticky connections are not required for the other three types of services.
For example, if the callflow of a particular IVR interaction requires the playing of media, the Customer
Voice Portal call model will initiate separate http requests for each prompt expected to be played. As
such, the Content Switch will not track state, or necessarily maintain a sticky connection for concurrent
requests from the client.
Voice Portal call model will initiate separate http requests for each prompt expected to be played. As
such, the Content Switch will not track state, or necessarily maintain a sticky connection for concurrent
requests from the client.
The following general approach will apply to configuring each Customer Voice Portal component type.
Specific component-type configuration is covered in the following sections.
Specific component-type configuration is covered in the following sections.
Services—One CSS Service is configured for each type of Customer Voice Portal component. For
general step-by-step guidelines for configuring Services, please see Chapter 1 of the CSS Basic
Configuration Guide.
general step-by-step guidelines for configuring Services, please see Chapter 1 of the CSS Basic
Configuration Guide.
Rules—A content rule should be established for each Customer Voice Portal component type. In order
to define a content rule, a content owner must be defined on the Content Switch. (See Chapter 2 of the
CSS Basic Configuration Guide.) Media Servers, Application Servers, ASR/TTS Servers and Customer
Voice Portal VoiceXML Servers may each have their own content rules defined. For general step-by-step
guidelines for configuring content rules, please see Chapter 3 of the CSS Basic Configuration Guide.
to define a content rule, a content owner must be defined on the Content Switch. (See Chapter 2 of the
CSS Basic Configuration Guide.) Media Servers, Application Servers, ASR/TTS Servers and Customer
Voice Portal VoiceXML Servers may each have their own content rules defined. For general step-by-step
guidelines for configuring content rules, please see Chapter 3 of the CSS Basic Configuration Guide.