Cisco Cisco Unified Customer Voice Portal 10.0(1)
D-4
Cisco Internet Service Node (ISN) Configuration and Administration Guide
OL-1251-03
Appendix D Configuring Cisco Content Services Switch (CSS) for Use with ISN
General Approach
Keepalive Times
Because these services are directly involved in processing voice calls, the shortest possible failover and
re-activation times are desired. As such, set the following keepalive parameters:
re-activation times are desired. As such, set the following keepalive parameters:
keepalive retryperiod 2
keepalive maxfailure 1
Groups
Define a group for the participating media servers if your configuration requires source groups (see the
discussion of Groups in the
discussion of Groups in the
section above for details.)
Example 0-3
Defining Media Servers Group
group mediaservers
add destination service mediaserver1
add destination service mediaserver2
add destination service mediaserver3
vip address 10.1.1.4
add destination service mediaserver2
add destination service mediaserver3
vip address 10.1.1.4
Activate services, group and rules:
Activate each service and group of media-servers.
Voice Gateway Configuration
The ISN 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:
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:
ip host media 10.1.1.4
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.
<<-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.
ip host media-backup 10.1.1.4
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.
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.