Cisco Cisco Customer Voice Portal 8.0(1)
D-9
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
ASR/TTS Server Configuration
Example D-6
Defining Application Servers Groups group appservers
add destination service appserver1
add destination service appserver2
add destination service appserver3
vip address 10.1.1.8
Activate Services, Group and Rules
Activate each service and group of application servers.
Voice Gateway Configuration
The Customer Voice Portal Application Server names are defined inside the vxml documents which are
passed to the Voice Gateway for processing. The names are hard-coded within the initial bootstrap.vxml
vxml document housed on the Gateway.
passed to the Voice Gateway for processing. The names are hard-coded within the initial bootstrap.vxml
vxml document housed on the Gateway.
Note
For more information, see
For a CSS implementation, the host name embedded within the bootstrap document is “Customer Voice
Portal-vxml”. You must ensure that the host name isn-vxml is set to resolve to the virtual ip address of
the content rule for the application servers setup on CSS. This is configured within each voice gateway
using the command:
Portal-vxml”. You must ensure that the host name isn-vxml is set to resolve to the virtual ip address of
the content rule for the application servers setup on CSS. This is configured within each voice gateway
using the command:
ip host cvpserver 10.86.130.90
where 10.86.130.90 is the VIP address servicing the Application Server content rule.
ASR/TTS Server Configuration
If your Customer Voice Portal deployment includes the use of ASR/TTS resources for call processing,
the ASR/TTS servers must also be configured within CSS. If your ASR/TTS deployment utilizes a
multi-tier architecture to separate MRCP requests from recognition and vocalizer functions (such as a
multi-tier Nuance configuration), only the MRCP servers are load-balanced by CSS. The RTSP traffic
generated as part of MRCP will be routed around CSS, rather than through it. While this is generally
handled by default within MRCP, it may be necessary in some MRCP configurations to specifically
instruct the server to pass the RTSP address. Consult your ASR/TTS documentation for specific details.
the ASR/TTS servers must also be configured within CSS. If your ASR/TTS deployment utilizes a
multi-tier architecture to separate MRCP requests from recognition and vocalizer functions (such as a
multi-tier Nuance configuration), only the MRCP servers are load-balanced by CSS. The RTSP traffic
generated as part of MRCP will be routed around CSS, rather than through it. While this is generally
handled by default within MRCP, it may be necessary in some MRCP configurations to specifically
instruct the server to pass the RTSP address. Consult your ASR/TTS documentation for specific details.
Note
When using ASR/TTS services with the CSS, you must enable the following global command on the
CSS. This prevents the CSS from tearing down the mrcp connection after some period of time:
CSS. This prevents the CSS from tearing down the mrcp connection after some period of time:
flow permanent port1 554
In order to route the voice stream around CSS rather than through it, you need to configure the mrcpclient
rtpsetup enable on the Gateway.
rtpsetup enable on the Gateway.