Cisco Cisco Customer Voice Portal 8.0(1)

The Customer Voice Portal media server names are defined inside the vxml documents which are passed 
to the Voice Gateway for processing. The media server name is set within the ICM routing script using 
an enterprise call variable. (Note that for use with the content switch, the default (not specified) media 
server name of “file:\\..\MediaServer” is an invalid option. You must specify a valid media-server name.) 
You must also ensure that the host name that ICM will deliver to the voice gateway as the name of the 
media server resolves to the virtual ip address of the content rule for the media servers setup on CSS. 
For example, if the ICM script sets a Media Server name as <<media>>, then the voice gateways to 
which the request will be delivered must resolve the name <<media>> to the VIP of the media-server 
content rule. This example would then be configured within the voice gateway using the command:

Note that when using CSS, the media server logic will generate vxml documents that contain 
<<-backup>> default backup media-server names. A vxml document returned to the gateway for prompt 
playback contains failover logic within the vxml. For example, if the media server is named <<media>>, 
this failover logic would include instructions for trying a server that would be named 
<<media-backup>>, as the example below reflects. 

Although a properly configured, redundant CSS setup should mean that the gateway will never actually 
be required to access the <<-backup>> host, a <<-backup>> host should still be configured on the 
gateway. This is recommended as a precaution. The gateway should still contain a definition for 
<<media-backup>> that points to the same VIP service since it is defined within the vxml.

You can apply the media-server configuration in a CSS to support a logical division of media based upon 
any reasonable grouping that the design might call for. As long as the ICM routing script can decide and 
set the media server name appropriately, CSS can support multiple media server routing rules. 

For example: If an Customer Voice Portal system deployment includes multiple language prompts, 
English and Spanish, the company may elect to house all Spanish versions of media server prompts on 
3 media servers, and all English prompts on 3 separate media servers.

This choice would be independent of the virtual directory setting, which is controlled by the Customer 
Voice Portal “language” parameter. While this parameter alters the path in the url of media, our example 
assumes that the company further wants to house different languages on different servers—perhaps for 
traffic volume purposes. For more information, on the language parameter, see 

In this example, the ICM routing script that constructs the VRU call flow would identify and set the 
media-server name differently depending upon whether the caller initially has chosen English or 
Spanish. If they choose English, you might re-set the Media Server name to ‘media-english’ and if 
Spanish is selected, ‘media-spanish’.