Cisco Cisco Customer Voice Portal 8.0(1)
•
Unified CVP Call Server
•
VXML Server
Note: CSS doesn't work with Helix Streaming Server.
The following general approach will apply to configuring each Unified CVP component type
for use with CSS. Specific component-type configuration is covered in the following sections.
for use with CSS. Specific component-type configuration is covered in the following sections.
Note: For the following topics, refer to
(http://
www.cisco.com/en/US/products/hw/contnetw/ps792/
products_installation_and_configuration_guides_list.html).
products_installation_and_configuration_guides_list.html).
Services—One CSS Service is configured for each Unified CVP component that needs CSS
load balancing.
load balancing.
Rules—A content rule should be established for each Unified CVP component type. In order
to define a content rule, a content owner must be defined on the Content Switch. (Refer to CSS
Documentation.) Media Servers, Call Servers, ASR/TTS Servers and VXML Servers might
each have their own content rules defined.
to define a content rule, a content owner must be defined on the Content Switch. (Refer to CSS
Documentation.) Media Servers, Call Servers, ASR/TTS Servers and VXML Servers might
each have their own content rules defined.
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 Unified CVP 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. Refer to
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 Unified CVP 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. Refer to
(http://www.cisco.com/en/US/products/hw/contnetw/ps789/
products_configuration_example09186a0080093dff.shtml)f.
Also, refer to
(http://www.cisco.com/en/US/products/hw/
contnetw/ps792/products_installation_and_configuration_guides_list.html) for help determining
whether your setup will require destination services. The examples in the next section incorporate
the use of destination services.
whether your setup will require destination services. The examples in the next section incorporate
the use of destination services.
Keepalives—Each Unified CVP component type will also have a varying type of keepalive
defined. The CSS keepalive definitions will allow for an appropriate method of determining
whether the component is functional and able to participate in receiving requests.
defined. The CSS keepalive definitions will allow for an appropriate method of determining
whether the component is functional and able to participate in receiving requests.
Server Groups
A Server Group is a dynamic routing feature that enables the originating endpoint to have
knowledge of the status of the destination address before attempting to send the SIP INVITE.
Whether the destination is unreachable over the network, or is out of service at the application
layer, the originating SIP user agent can have fore-knowledge of the status through a heartbeat
mechanism.
knowledge of the status of the destination address before attempting to send the SIP INVITE.
Whether the destination is unreachable over the network, or is out of service at the application
layer, the originating SIP user agent can have fore-knowledge of the status through a heartbeat
mechanism.
Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 8.0(1)
478
Chapter 14: Configuring High Availability for Unified CVP
Server Groups