MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 590 (ciscoCvpMIB). 1 (ciscoCvpMIBObjects). 6 (ccvpServiceInfo). 6 (ccvpVxmlTable)
OID : 1.3.6.1.4.1.9.9.590.1.6.6
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoCvpMIB. ciscoCvpMIBObjects. ccvpServiceInfo. ccvpVxmlTable
Enfants
Détails
OID1.3.6.1.4.1.9.9.590.1.6.6
Module CISCO-CVP-MIB (CISCO)
NomccvpVxmlTable
Statuscurrent
DescriptionThe Voice XML Service table lists each Customer Voice Portal Voice XML service installed and configured on this server. The CVP VXML server includes both the CVP VXML service and the VXML server software that executes complex IVR applications by exchanging VoiceXML pages with the VXML Gateway?s built-in voice browser. Like almost all other CVP product components, it runs within a J2EE application server environment such as Tomcat, and many customers add their own custom-built or off-the-shelf J2EE components to interact with back-end hosts and services. CVP VoiceXML Server applications are written using the CVP VoiceXML Studio, and deployed to the Server for execution. They are invoked on an as-needed basis by a special microapp which must be executed from within the ICM routing script. The VXML Server may also be deployed in a standalone configuration ?- one which includes no ICM components. In this model, applications are invoked as a direct result of calls arriving in the VXML Gateway, and a single post-application transfer is allowed. Users may add the CVP VXML service software. This affords standalone applications the additional ability to forward reporting events to a CVP Reporting Server, and to make ancillary routing requests and exchange call context information with an ICM if one is present. However, the integration with ICM is nominal. 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.