Cisco Cisco Unified Customer Voice Portal 10.0(1)
D-1
Cisco Internet Service Node (ISN) Configuration and Administration Guide
OL-1251-03
A P P E N D I X
D
Configuring Cisco Content Services Switch (CSS)
for Use with ISN
for Use with ISN
This section outlines the general approach and configuration specifics for using CSS with ISN
deployments. Users should be familiar with the general concepts of configuring a Cisco Content Services
Switch outlined in the CSS Administration Guide.
deployments. Users should be familiar with the general concepts of configuring a Cisco Content Services
Switch outlined in the CSS Administration Guide.
Hardware: The CSS Model 11500 is used for this implementation.
Software: Version 7.10 of the CSS 11500 should be installed on all CSS switches planned for use.
General Approach
In this application of CSS, the engine is used primarily to direct initial session requests for a particular
type of service. Sticky and/or stateful connections are not generally configured, primarily because the
failover and retry logic for ISN voice applications is maintained within other components of the system.
type of service. Sticky and/or stateful connections are not generally configured, primarily because the
failover and retry logic for ISN voice applications is maintained within other components of the system.
For example, if the callflow of a particular IVR interaction requires the playing of media, the ISN 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.
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 ISN component type. Specific
component-type configuration is covered in the following sections.
component-type configuration is covered in the following sections.
Services—One CSS Service is configured for each type of ISN component. For general step-by-step
guidelines for configuring Services, please see Chapter 1 of the CSS Basic Configuration Guide.
guidelines for configuring Services, please see Chapter 1 of the CSS Basic Configuration Guide.
Rules—A content rule should be established for each ISN 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, and ASR/TTS 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.
rule, a content owner must be defined on the Content Switch. (See Chapter 2 of the CSS Basic
Configuration Guide.) Media Servers, Application Servers, and ASR/TTS 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.
Groups—It may be necessary to define source groups for each service. Group configuration will vary
depending upon whether a single VLAN or multiple VLANs are used for the CSS’ inbound and
outbound traffic from the voice gateway and the ISN component servers. If the servers and the voice
gateway clients are on the same VLAN, then destination services will need to be specified. This
configuration is sometimes referred to as a ‘one-arm’ configuration because all traffic passes through
one interface. Please see the online documentation for the Cisco Content Switch entitled “How to
Configure the CSS to Load Balance Using One Interface”. At the time of this writing, the document was
located here:
depending upon whether a single VLAN or multiple VLANs are used for the CSS’ inbound and
outbound traffic from the voice gateway and the ISN component servers. If the servers and the voice
gateway clients are on the same VLAN, then destination services will need to be specified. This
configuration is sometimes referred to as a ‘one-arm’ configuration because all traffic passes through
one interface. Please see the online documentation for the Cisco Content Switch entitled “How to
Configure the CSS to Load Balance Using One Interface”. At the time of this writing, the document was
located here: