CISCO-CVP-MIB
The CISCO-CVP-MIB provides runtime instrumentation for monitoring the health, performance, and capacity utilization of Cisco Unified Customer Voice Portal services, including SIP, H.323, and VXML components, by exposing real-time statistics on call processing, script execution, and resource consumption. It enables network management systems to correlate service-specific events and status changes across distributed CVP server deployments through structured notifications and service enumeration tables.
Imported Objects
Objects
193 total| Object Name |
|---|
ciscoCvpMIB MODULE-IDENTITY .1.3.6.1.4.1.9.9.590 |
ciscoCvpMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.590.0 |
ccvpCvpEvent NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.590.0.1 |
ciscoCvpMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.590.1 |
ccvpGeneralInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.590.1.1 |
ccvpServerNamero InetAddressDNS (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.590.1.1.1 |
ccvpDescriptionro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.590.1.1.2 |
ccvpVersionro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.590.1.1.3 |
ccvpStartTimero DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.590.1.1.4 |
ccvpTimeZoneNamero SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.590.1.1.5 |
ccvpTimeZoneOffsetHoursro Integer32 (-12..12) UNITS "hours" .1.3.6.1.4.1.9.9.590.1.1.6 |
ccvpTimeZoneOffsetMinutesro Integer32 (-59..59) UNITS "minutes" .1.3.6.1.4.1.9.9.590.1.1.7 |
ccvpOpsConsoleURLro CiscoURLString (CISCO-TC) .1.3.6.1.4.1.9.9.590.1.1.8 |
ccvpSupportToolsURLro CiscoURLString (CISCO-TC) .1.3.6.1.4.1.9.9.590.1.1.9 |
ccvpEnableNotificationsro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.590.1.1.10 |
ccvpLicensingInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.590.1.2 |
ccvpLicRtPortsAvailro Gauge32 UNITS "ports" .1.3.6.1.4.1.9.9.590.1.2.1 |
ccvpLicRtPortsInUsero Gauge32 UNITS "ports" .1.3.6.1.4.1.9.9.590.1.2.2 |
ccvpLicRtPortStatero Enumeration .1.3.6.1.4.1.9.9.590.1.2.3 |
ccvpLicIntLastUpdatero DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.590.1.2.4 |
ccvpLicIntPeriodro Gauge32 .1.3.6.1.4.1.9.9.590.1.2.5 |
ccvpLicIntPortReqsro Gauge32 UNITS "requests" .1.3.6.1.4.1.9.9.590.1.2.6 |
ccvpLicIntAvgPortReqsro Gauge32 UNITS "requests" .1.3.6.1.4.1.9.9.590.1.2.7 |
ccvpLicIntMaxPortsInUsero Gauge32 UNITS "ports" .1.3.6.1.4.1.9.9.590.1.2.8 |
ccvpLicIntPortReqsDeniedro Gauge32 UNITS "requests" .1.3.6.1.4.1.9.9.590.1.2.9 |
ccvpLicAggPortReqsro Counter64 UNITS "requests" .1.3.6.1.4.1.9.9.590.1.2.10 |
ccvpLicAggAvgPortReqsro Counter64 UNITS "requests" .1.3.6.1.4.1.9.9.590.1.2.11 |
ccvpLicAggMaxPortsInUsero Counter64 UNITS "ports" .1.3.6.1.4.1.9.9.590.1.2.12 |
ccvpLicAggPortReqsDeniedro Counter64 UNITS "requests" .1.3.6.1.4.1.9.9.590.1.2.13 |
ccvpLicPortUsageWarningro Gauge32 UNITS "percent" .1.3.6.1.4.1.9.9.590.1.2.14 |
ccvpLicPortUsageCriticalro Gauge32 UNITS "percent" .1.3.6.1.4.1.9.9.590.1.2.15 |
ccvpThreadPoolInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.590.1.3 |
ccvpTPoolRtIdleThreadsro Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.590.1.3.1 |
ccvpTPoolRtRunningThreadsro Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.590.1.3.2 |
ccvpTPoolRtCoreThreadsro Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.590.1.3.3 |
ccvpTPoolRtMaxThreadsAvailro Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.590.1.3.4 |
ccvpTPoolRtMaxThreadsUsedro Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.590.1.3.5 |
ccvpJvmInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.590.1.4 |
ccvpJvmRtMaxMemUsedro Gauge32 UNITS "bytes" .1.3.6.1.4.1.9.9.590.1.4.1 |
ccvpJvmRtCurrMemUsedro Gauge32 UNITS "bytes" .1.3.6.1.4.1.9.9.590.1.4.2 |
ccvpJvmRtMaxMemAvailro Gauge32 UNITS "bytes" .1.3.6.1.4.1.9.9.590.1.4.3 |
ccvpJvmRtCurrMemAvailro Gauge32 UNITS "bytes" .1.3.6.1.4.1.9.9.590.1.4.4 |
ccvpJvmRtCurrThreadsInUsero Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.590.1.4.5 |
ccvpJvmRtMaxThreadsUsedro Gauge32 UNITS "threads" .1.3.6.1.4.1.9.9.590.1.4.6 |
ccvpJvmRtUpTimero Counter64 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.4.7 |
ccvpServices OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.590.1.5 |
ccvpServiceTable SEQUENCE OF CcvpServiceEntry .1.3.6.1.4.1.9.9.590.1.5.1 |
ccvpServiceEntry CcvpServiceEntry .1.3.6.1.4.1.9.9.590.1.5.1.1 |
ccvpServiceIndex CcvpIndex .1.3.6.1.4.1.9.9.590.1.5.1.1.1 |
ccvpServiceTypero CcvpServiceType .1.3.6.1.4.1.9.9.590.1.5.1.1.2 |
ccvpServiceNamero SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.590.1.5.1.1.3 |
ccvpServiceStatusro CcvpServiceStatus .1.3.6.1.4.1.9.9.590.1.5.1.1.4 |
ccvpServiceIntLastUpdatero DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.590.1.5.1.1.5 |
ccvpServiceIntPeriodro Gauge32 .1.3.6.1.4.1.9.9.590.1.5.1.1.6 |
ccvpServiceInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.590.1.6 |
ccvpSipTable SEQUENCE OF CcvpSipEntry .1.3.6.1.4.1.9.9.590.1.6.1 |
ccvpSipEntry CcvpSipEntry .1.3.6.1.4.1.9.9.590.1.6.1.1 |
ccvpSipRtActiveCallsro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.1 |
ccvpSipRtTotalCallLegsro Gauge32 UNITS "call legs" .1.3.6.1.4.1.9.9.590.1.6.1.1.2 |
ccvpSipIntNewCallsro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.3 |
ccvpSipIntConnectsRcvro Gauge32 UNITS "connects" .1.3.6.1.4.1.9.9.590.1.6.1.1.4 |
ccvpSipIntAvgLatency1ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.1.1.5 |
ccvpSipIntAvgLatency2ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.1.1.6 |
ccvpSipIntFailedXferPrero Gauge32 UNITS "transfers" .1.3.6.1.4.1.9.9.590.1.6.1.1.7 |
ccvpSipIntFailedXferPostro Gauge32 UNITS "transfers" .1.3.6.1.4.1.9.9.590.1.6.1.1.8 |
ccvpSipAggNewCallsro Counter64 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.9 |
ccvpSipAggConnectsRcvro Counter64 UNITS "connects" .1.3.6.1.4.1.9.9.590.1.6.1.1.10 |
ccvpSipAggAvgLatency1ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.1.1.11 |
ccvpSipAggAvgLatency2ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.1.1.12 |
ccvpSipAggFailedXferPrero Counter64 UNITS "transfers" .1.3.6.1.4.1.9.9.590.1.6.1.1.13 |
ccvpSipAggFailedXferPostro Counter64 UNITS "transfers" .1.3.6.1.4.1.9.9.590.1.6.1.1.14 |
ccvpSipRtBasicVideoOfferedro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.15 |
ccvpSipRtBasicVideoAnsweredro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.16 |
ccvpSipIntBasicVideoOfferedro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.17 |
ccvpSipIntBasicVideoAnsweredro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.18 |
ccvpSipAggBasicVideoOfferedro Counter64 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.19 |
ccvpSipAggBasicVideoAnsweredro Counter64 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.20 |
ccvpSipIntPostCallAnsweredro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.21 |
ccvpSipIntWhisperAnsweredro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.22 |
ccvpSipIntWhisperFailedro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.23 |
ccvpSipIntGreetingAnsweredro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.24 |
ccvpSipIntGreetingFailedro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.1.1.25 |
ccvpH323Table SEQUENCE OF CcvpH323Entry .1.3.6.1.4.1.9.9.590.1.6.2 |
ccvpH323Entry CcvpH323Entry .1.3.6.1.4.1.9.9.590.1.6.2.1 |
ccvpH323RtCallsInProgressro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.2.1.1 |
ccvpH323RtMemoryInUsero Gauge32 .1.3.6.1.4.1.9.9.590.1.6.2.1.2 |
ccvpH323IntArrivalRatero Gauge32 UNITS "calls per minute" .1.3.6.1.4.1.9.9.590.1.6.2.1.3 |
ccvpH323IntTransferRatero Gauge32 UNITS "calls per minute" .1.3.6.1.4.1.9.9.590.1.6.2.1.4 |
ccvpH323IntMaxNewCallLatencyro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.2.1.5 |
ccvpH323IntAvgNewCallLatencyro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.2.1.6 |
ccvpH323IntMaxXferToAlertro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.2.1.7 |
ccvpH323IntAvgXferToAlertro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.2.1.8 |
ccvpH323IntMaxXferToAnswerro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.2.1.9 |
ccvpH323IntAvgXferToAnswerro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.590.1.6.2.1.10 |
ccvpH323IntNewCallsro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.2.1.11 |
ccvpH323IntTransferredro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.2.1.12 |
ccvpH323IntRedirectedro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.2.1.13 |
ccvpH323IntNotTransferredro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.2.1.14 |
ccvpH323IntPromptsNotFoundro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.2.1.15 |
ccvpH323IntCriticalMediaro Gauge32 UNITS "calls" .1.3.6.1.4.1.9.9.590.1.6.2.1.16 |
CISCO-CVP-MIB Technical Reference Overview
The CISCO-CVP-MIB SNMP MIB module published by Cisco defines 193 managed OID objects, including 165 scalar/column metrics, 7 SNMP tables, and 1 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.590. Key tabular structures include ccvpServiceTable, ccvpSipTable, ccvpH323Table, ccvpIvrTable, ccvpIcmTable, ccvpReptTable. Monitored SNMP traps/notifications include ccvpCvpEvent.
Key OID Definitions in CISCO-CVP-MIB
.1.3.6.1.4.1.9.9.590The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and IP-based contact centers to provide an unparalleled call management and call treatment solution with a self- service, speech-enabled Interactive Voice Rresponse (IVR) option that can use information available to customers on the corporate Web server. With support for automated speech recognition (ASR) and text- to-speech (TTS) capabilities, callers can obtain personalized answers to increasingly complex questions and can conduct business in new and innovative ways ?- all without the costs of interacting with a live agent. CVP is a distributed, self-service IVR application. The solution is comprised of a set of distinct services; each performs a specific function. The services are loosely coupled, which aides its distributed nature, and yet they are tightly integrated. Each service provides a core function and is dependent upon the other services to perform that function. A single CVP server may have one or more services installed on a single server; even in the smallest deployment scenarios, there will be at least two servers Voice XML (VXML) server. The call server, whether it is a single physical server or a virtual set of servers, will include the SIP service, the IVR service and in many cases, the ICM service. Environments desiring the use of the H.323 protocol will have the H.323 service either exclusively or in concert with the SIP service available on the call server. The server providing VXML services will have the VXML server (which executes the IVR scripts, plays prompts and collects digits) and the VXML service which provides the interface between the other CVP services and the VXML server. A reporting server houses a database management system and the CVP reporting service which receives events from other CVP services and writes data to the database. The number of servers that are part of the solution will scale to the expected capacity for that deployment. For many deployments, CVP works in concert with the Cisco Unified Intelligent Contact Management (ICM) Enterprise and/or the Cisco Unified Contact Center Enterprise contact management systems. In this deployment scenario, CVP acts as a self- service and IVR platform and interfaces with the ICM for subsequent call routing, typically to a call center agent (a human resource tasked with answering inbound calls and providing services to callers). Using the aforementioned call control protocols CVP interacts with all these devices to switch the calls to the desired destination. The Cisco Unified Customer Voice Portal (CVP) Management Information Base (MIB) module defines management instrumentation for CVP services. Each distinct CVP service exposes instrumentation related to its specific function. The bulk of this instrumentation is run-time statistics that provide insight into the health, performance and capacity utilization of the CVP solution. Notifications are also a key component of this instrumentation. This MIB also defines a notification format that offers descriptive objects as well as objects that ease the task of correlating events at the management station. The MIB is structured such that at the highest level is a single generic table which enumerates the installed CVP services and provides a description of each as well as a real-time status. The index of this table is used to relate the service entry to an entry in a table of additional instrumentation that is specific to that CVP service type. There are also several groups of objects that are exposed on each CVP server regardless of the services installed. DEFINITION OF TERMS AND ACRONYMS CVP Customer Voice Portal GED-125 A messaging protocol that extends an interface to a Interactive Voice Response (IVR) (AKA Voice Response Unit (VRU)) device. The protocol allows for basic call control and running scripts on the IVR to play prompts and collect user input. IVR Interactive Voice Response JVM Java Virtual Machine OAMP Operations, Administration, Maintenance and Provisioning RTP Real-time Transport Protocol SIP Session Initiation Protocol VRU Voice Response Unit
.1.3.6.1.4.1.9.9.590.1.5.1The service table is a list of Customer Voice Portal (CVP) functional services. A CVP solution includes a collection of interconnected functional services, each of which perform a specific, necessary function of the CVP application. This table enumerates and lists all CVP functional services installed and configured on this server. A single server is permitted to have multiple functional services of a different type, but also multiple services of the same type (although far less likely). The service table is indexed by a unique numeric identifier for each functional service. This service index is arbitrarily assigned by the SNMP agent. These same index values are used in the individual service information tables, thus, the individual service information tables have a sparse dependency relationship with this table. The SNMP agent constructs the service table at startup based upon static data saved in a properties file. Since services can only be configured while the CVP application is stopped, service table entries cannot be added to or deleted from the table at run time. Object values can and will be modified by the agent but not the management station. All objects in this table are read-only to the management station.
.1.3.6.1.4.1.9.9.590.1.6.1The SIP service table lists each Customer Voice Portal SIP service configured on this server. The CVP SIP service is a software module which always resides in the CVP Call Server. The CVP SIP service is a SIP Back-to-Back User Agent (B2BUA). On the front end, it supports two SIP call legs, one incoming and one outgoing. This service does not terminate RTP flows; it only deals with SIP messages. On the back end, the SIP service implements the (GED-125) Service Control Interface (SCI) to the Cisco Intelligent Contact Management (ICM) application for call control functions only (no VRU scripts). The purpose of a B2BUA is to act as an active intermediary for a call, communicating with both the source and the destination legs of the call, and providing 3rd party call control capabilities on behalf of a routing engine (such as the ICM contact router). Because it must track the call throughout its life, it becomes a key source of call-level reporting data and a natural place for moderating call switching resources. Generally speaking, a SIP B2BUA is two User Agents (UAs). The device receives incoming calls in one UA and immediately creates an outgoing call via its other UA. Thereafter, all SIP messages from either one are forwarded to the other. What makes it useful is the fact that it puts ICM in between the two legs. On incoming calls, it asks the ICM where the outgoing call should be addressed. Once the call has been delivered, ICM has the opportunity to end the outgoing leg and reconnect it to a subsequent destination. In practice, there will typically be a delivery to the subsequent agents (call center agents - a human resources tasked with answering inbound calls and providing specific services) or back to the VRU leg. The SIP service table has a sparse dependent relationship with the (generic) ccvpService table. The service index acts as the primary index, relating the entry to the corresponding entry in the ccvpService 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 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.
.1.3.6.1.4.1.9.9.590.1.6.2The H.323 Service table lists each Customer Voice Portal (CVP) H.323 service configured on this server. This service is a software component which always resides on the CVP Call Server. The CVP H.323 service interacts with the CVP IVR service to relay call arrival, departure and transfer instructions between it and other H.323 devices. The CVP H.323 service is a legacy service used only in H.323- based deployments. Although this service started as a true, albeit incomplete, voice browser, its strength was its ability to effect complicated H.323 call control activities with the Gateway and the Cisco Call Manager. Over time, the VXML Gateway's IOS voice browser supplanted it as a voice interaction device and call control became its main focus. SIP is still a young protocol compared to H.323 and there are still certain capabilities which either the gateway, the Call Manager or the protocol itself does not yet support. Users who require these capabilities, as well as those who wish to upgrade without switching from H.323 to SIP will therefore continue to use the CVP H.323 service in place of the CVP SIP service. 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.
.1.3.6.1.4.1.9.9.590.1.6.3The 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.
.1.3.6.1.4.1.9.9.590.1.6.4The ICM Service table lists each Customer Voice Portal ICM service configured on this server. Each entry in the table defines a separate ICM service. The CVP ICM service is responsible for all communication between CVP components and the Intelligent Contact Management (ICM) application. The CVP ICM service implements the GED-125 Service Control Interface (SCI) protocol, and sends and receives messages on behalf of the CVP SIP service, the CVP IVR service, and the CVP VoiceXML service. Users do not explicitly install the CVP ICM Subsystem; it is installed and activated automatically in the CVP Call Server and the CVP VoiceXML Server. This service is visible at the CVP Operations Server, however, since it does require a small amount of configuration. 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.
.1.3.6.1.4.1.9.9.590.1.6.5The Reporting service table lists each Customer Voice Portal reporting service configured on this server. The CVP Reporting Server houses the CVP Reporting service as well as a database management system to persist data. The CVP reporting service receives reporting events from the CVP IVR service, the CVP SIP service, and the CVP VoiceXML service. The service is deployed together with a database management system and it transforms and writes this reporting data into that database. The database schema is prescribed by the CVP product, but it is an open schema in that customers may develop custom reports based on it. There can only be one CVP Reporting Server in a deployment. This does not represent a single point of failure however, because data safety and security are provided by the database management system, and temporary outages are tolerated due to persistent buffering of information on the source components. 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.
.1.3.6.1.4.1.9.9.590.1.6.6The 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.
.1.3.6.1.4.1.9.9.590.0.1A CVP event is a notification that is sent by a functional service of the Cisco Customer Voice Portal (CVP) self service interactive voice response application.
.1.3.6.1.4.1.9.9.590.1.1.1The server name object is the fully-qualified domain name of the Customer Voice Portal server.
.1.3.6.1.4.1.9.9.590.1.1.2The description object holds a textual description of the Customer Voice Portal software installed on this server. This is typically the full name of the application.
.1.3.6.1.4.1.9.9.590.1.1.3The version object identifies the version number of the Customer Voice Portal software installed on this server.
.1.3.6.1.4.1.9.9.590.1.1.4The start time object is thedate and time that the Customer Voice Portal application was started on this server.
.1.3.6.1.4.1.9.9.590.1.1.5The time zone name object specifies the name of the time zone where the Customer Voice Portal server is physically located.
.1.3.6.1.4.1.9.9.590.1.1.6The time zone offset hours object represents the number of hours that the local time, in the time zone where the Customer Voice Portal server is physically located, differs from Greenwich Mean Time (GMT).
.1.3.6.1.4.1.9.9.590.1.1.7The time zone offset minutes object represents the number of minutes that the local time, in the time zone where the Customer Voice Portal server is physically located, differs from Greenwich Mean Time (GMT). This object is combined with ccvpTimeZoneOffsetHours object to represent the local time zone's total offset from GMT.
.1.3.6.1.4.1.9.9.590.1.1.8The ops console URL object holds the URL for the Customer Voice Portal operations Console web server. The operations console offers a web-based, centralized interface for mapping and summarizing the solution network configuration, setting and displaying configuration infomration on a batch or per-node basis and storing local copies of those configurations. Other functions include troubleshooting, health monitoring and direct administration. This object offers a web navigation point from the management station (assuming a web interface) to quickly access the CVP Operations Console web server.
.1.3.6.1.4.1.9.9.590.1.1.9The support tools URL object holds the URL for an enterprise contact center support tools application server. The support tools application server is an optional component of the solution and offers a centralized server for diagnostic and troubleshooting tools. This object offers a navigation point from the management station (assuming a web interface) to quickly access the support tools application server.
.1.3.6.1.4.1.9.9.590.1.1.10The enable notifications object allows the management station to disable and alternatively enable outbound notifications. By default, notifications are enabled.
.1.3.6.1.4.1.9.9.590.1.2.1The real-time port licenses available object is a real-time snapshot metric indicating the number of port licenses available for the processing of new calls. Exactly one port license is used per call, independent of the calls traversal of the individual call server subsystems.
.1.3.6.1.4.1.9.9.590.1.2.2The real-time ports in use object is a real-time snapshot metric indicating the number of port licenses currently in use on the call server. Exactly one port license is used per call, independent of the call's traversal of the individual call server subsystems.
.1.3.6.1.4.1.9.9.590.1.2.3The real-time port state object is a real-time snapshot metric indicating the threshold level of port license usage. There are five levels: 'safe' Port usage is within a safe range. 'unknown' Port usage state is currently unknown. 'warning' Port usage is rising, approaching a level of concern. 'critical' Port usage is precariously close to the limit. 'failure' Port usage has reached or exceeded the maximum allowable and calls are currently being rejected. An administrator may set the required percentage of port licenses in use needed to reach a given threshold level, with the exception of the failure level which is reached when the number of ports checked out is equal to the total number of licenses ports.
.1.3.6.1.4.1.9.9.590.1.2.4The interval last update object holds the date and time of the last refresh of interval and aggregate statistic object values. Interval and aggregate statistics are reported at a regular interval (the interval held by the interval period object).
.1.3.6.1.4.1.9.9.590.1.2.5The interval period object defines the number of minutes of accumulated values for the 'interval' and 'aggregate' statistic objects in this instrumentation group. Once this period elapses, each CVP service reports the next group of accumulated interval and aggregate statistical values.
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.
The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.
The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.
SNMP MIB module
The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.
The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.