Cisco Cisco Customer Voice Portal 8.0(1)
D-6
Cisco Customer Voice Portal (CVP) Release 3.1(0) Configuration and Administration Guide
Appendix D Configuring Cisco Content Services Switch (CSS) for Use with Customer Voice Portal
Application Server Configuration
To support this, 6 services would be configured within CSS, one service for each media server. Two (2)
content rules would also be configured. Each content rule would map to a different vip address and
contain only those services which match the language the rule is configured for. Finally, the voice
gateways would have separate host entries for the English and Spanish media-server names (and their
–backup version) as set within the ICM scripts. Here is what the content rules would look like:
content rules would also be configured. Each content rule would map to a different vip address and
contain only those services which match the language the rule is configured for. Finally, the voice
gateways would have separate host entries for the English and Spanish media-server names (and their
–backup version) as set within the ICM scripts. Here is what the content rules would look like:
content MEDIA-ENGLISH
vip address 10.2.1.1
protocol any
port 80
url "/*"
add service mediaserver-english1
add service mediaserver-english2
primarySorryServer mediaserver-english3
content MEDIA-SPANISH
vip address 10.2.1.2
protocol any
port 80
url "/*"
add service mediaserver-spanish1
add service mediaserver-spanish2
primarySorryServer mediaserver-spanish3
The following host entries would then appear on the voice gateways:
ip host media-english 10.2.1.1
ip host media-english-backup 10.2.1.1
ip host media-spanish 10.2.1.2
ip host media-spanish-backup 10.2.1.2
Application Server Configuration
CSS should also contain configuration for all application servers used in any IVR leg of a call flow or
for any application server that is used as a routing client in a non-Customer Voice Portal voice browser
call flow.
for any application server that is used as a routing client in a non-Customer Voice Portal voice browser
call flow.
Note
The Cisco Customer Voice Portal Voice Browser maintains a list of its own application servers used as
an interface between voice browser and the ICM for route requests. Retry logic within the Voice Browser
controls requests to the Voice Browser’s application servers for routing requests via the
“ApplicationServerList” Voice Browser definitions. If separate application servers are used for an
Customer Voice Portal Voice-Browser’s interface to ICM for route requests, these Application Servers
do not require configuration within CSS.
an interface between voice browser and the ICM for route requests. Retry logic within the Voice Browser
controls requests to the Voice Browser’s application servers for routing requests via the
“ApplicationServerList” Voice Browser definitions. If separate application servers are used for an
Customer Voice Portal Voice-Browser’s interface to ICM for route requests, these Application Servers
do not require configuration within CSS.