Cisco Cisco Customer Voice Portal 8.0(1)

Gateway will time-out its SIP Session Timer (default: 1800
seconds), and issue a new Invite via the SIP Service to the
VXML Gateway. SIP Service will not be able to forward
the Invite, and will return a 5xx message to the Ingress
Gateway, containing a non-Normal reason code. The call
will then be handled by the Survivability script.

If IVR Service does not receive a new request from the
VXML Gateway within 7200 seconds, it will terminate the
call. If the IOS Voice Browser does not get a response from
the IVR Service within 7320 seconds, it will terminate the
call. The call will then be handled by the Survivability
script.

Non-Call Handling Components

The sections above deal with call-oriented availability requirements. The Unified CVP Solution
also contains components that are not strictly call-handling components, but which have their
own high availability requirements nonetheless.

- If any Call Server or VoiceXML
Server loses connectivity to its

Each Call Server and each VoiceXML
Server can be associated with only one

Reporting events from Call Server and
VoiceXML Server to the Reporting
Service

Reporting Service, it will send an

Reporting Service. Reports cannot span
multiple Informix databases.

SNMP event, and start persisting
reporting events on disk, until a
preconfigured file size threshold is
reached. At that point it will issue
another SNMP event, and begin
dropping reporting events.

- If a Reporting Service loses the ability
to write to a database management
system, it will disconnect from its
reporting event sources, causing those
servers to begin storing their events.
Since events travel asynchronously, it
is possible for the Reporting Service to
receive (and store) some number of
additional events before they stop
coming. When the links are restored,
all reporting event sources begin
draining their stored events in FIFO

Planning Guide for Cisco Unified Customer Voice Portal 4.0(1)