Description | The IVR Service table lists each Customer Voice Portal
Interactive Voice Response service configured on this server.
Each entry in the table defines a separate IVR service; a
single server is permitted to have multiple IVR services.
The CVP IVR service is a software module which always resides
int he CVP Call Server.
The CVP IVR service is responsible for creating the VXML
pages which implement the CVP Microapps based on 'Run Script'
instructions received from the ICM. (The 'Run Script'
instruction is part of the Service Control Interface offered
with the GED-125 messaging protocol.)
The service function as the VRU leg in ICM parlance and calls
must be transferred to it from the SIP service in order to
execute microapps. The VXML pages created by this module are
sent to the VXML Gateway to be executed.
In legacy deployments only -- those which use H.323 instead
of SIP -- the CVP IVR service can act as the switch leg as
well. The deployment includes a CVP H.3232 service which
interacts with the CVP IVR service for call control
activities. Calls still need to be transferred to a VRU leg
before microapps can be executed, however, in legacy
deployments, that transferred leg may end up using the same
CVP IVR service as the switch leg.
The CVP IVR service plays a significant role in implementing
CVP's native failover mechanism -- those capabilities which
can be achieved without a Content Services Switch -- for
Media Servers, ASR/TTS Servers and CVP VoiceXML Servers. Up
to two of each such server are supported and the CVP IVR
service orchestrates retries and failover between them.
This table has a sparse dependent relationship with the
Service table. The service index acts as the primary
index, relating the entry to the corresponding entry in the
Service table.
The SNMP agent constructs this table at startup. Since
services can only be added or deleted when the CVP
application is stopped, service information table entries
cannot be added to or deleted from the table either by the
agent or the management station while the application is
running. The agent will update service information table
objects as their values change when the application is
running. All objects in this table are read-only to the
management station. |