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
of SIP
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
can be achieved without a Content Services Switch
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.
Parsed from file CISCO-CVP-MIB.mib
Module: CISCO-CVP-MIB
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
of SIP
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
can be achieved without a Content Services Switch
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.
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
of SIP
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
can be achieved without a Content Services Switch
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.
Parsed from file CISCO-CVP-MIB.my.txt
Company: None
Module: CISCO-CVP-MIB
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
of SIP
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
can be achieved without a Content Services Switch
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.
ccvpIvrTable OBJECT-TYPE SYNTAX SEQUENCE OF CcvpIvrEntry MAX-ACCESS not-accessible STATUS current 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 of SIP 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 can be achieved without a Content Services Switch 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." ::= { ccvpServiceInfo 3 }
ccvpIvrTable OBJECT-TYPE SYNTAX SEQUENCE OF CcvpIvrEntry ACCESS not-accessible STATUS mandatory 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 of SIP 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 can be achieved without a Content Services Switch 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." ::= { ccvpServiceInfo 3 }
Vendor: Cisco
Module: CISCO-CVP-MIB
[Automatically extracted from oidview.com]
ccvpIvrTable OBJECT-TYPE SYNTAX SEQUENCE OF CcvpIvrEntry MAX-ACCESS not-accessible STATUS current 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 of SIP 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 can be achieved without a Content Services Switch 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." ::= { ccvpServiceInfo 3 }
ccvpIvrTable OBJECT-TYPE SYNTAX SEQUENCE OF CcvpIvrEntry MAX-ACCESS not-accessible STATUS current 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 of SIP 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 can be achieved without a Content Services Switch 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." ::= { ccvpServiceInfo 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.590.1.6.3.1 | ccvpIvrEntry | 24 | 24 | Each entry represents a Customer Voice Portal (CVP) Interactive Voice Response (IVR) service configured on the server. The IVR s… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.590.1.6.1 | ccvpSipTable | 1 | 26 | The SIP service table lists each Customer Voice Portal SIP service configured on this server. The CVP SIP service is a software … |
| 1.3.6.1.4.1.9.9.590.1.6.2 | ccvpH323Table | 1 | 20 | The H.323 Service table lists each Customer Voice Portal (CVP) H.323 service configured on this server. This service is a softwa… |
| 1.3.6.1.4.1.9.9.590.1.6.4 | ccvpIcmTable | 1 | 25 | The ICM Service table lists each Customer Voice Portal ICM service configured on this server. Each entry in the table defines a … |
| 1.3.6.1.4.1.9.9.590.1.6.5 | ccvpReptTable | 1 | 9 | The Reporting service table lists each Customer Voice Portal reporting service configured on this server. The CVP Reporting Serv… |
| 1.3.6.1.4.1.9.9.590.1.6.6 | ccvpVxmlTable | 1 | 15 | The Voice XML Service table lists each Customer Voice Portal Voice XML service installed and configured on this server. The CVP V… |