All MIBs › OPCD-CCXML-MIB-V2
Category: VoIP/Telephony
Description: Monitors CCXML voice application engine status and session statistics on OpenCode VoIP/IVR platforms.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is OPCD-CCXML-MIB-V2?
OPCD-CCXML-MIB-V2 is an OpenCode Technologies SNMP module for monitoring the CCXML (Call Control XML) voice application engine used on OpenCode's VoIP/IVR communication platforms. It exposes fault and event data generated by the CCXML engine, including which host produced the fault, how severe it is, and free-text descriptions of the condition. This makes it primarily a software-status and fault-monitoring MIB: it is used to track whether the voice application engine is healthy, whether call-control scripts are executing correctly, and whether errors are occurring in session processing rather than reporting hardware sensors. It likely depends on a shared OpenCode base/common MIB, as the 'mcr-' prefixed fault objects suggest a common fault-reporting convention reused across the OPCD-* MIB family rather than standing alone. It would typically be deployed in carrier or enterprise VoIP/IVR platforms where administrators need real-time visibility into call-control application failures across distributed OpenCode media servers. Engineers can download the OPCD-CCXML-MIB-V2 file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in OPCD-CCXML-MIB-V2. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- OpenCode VoIP/IVR media server
- OpenCode CCXML voice application engine
Monitoring Examples
An administrator would poll or trap on mcr-Host to identify which node in a multi-server OpenCode deployment reported a problem, cross-referencing mcr-Severity to triage whether the event is informational or a critical failure, and reading mcr-Text for the human-readable fault description. A rising count of high-severity mcr-Severity events tied to a specific mcr-Host would indicate that a particular CCXML application server is experiencing session-processing failures and needs investigation or failover. This pattern is typical of software fault-reporting MIBs layered on top of a shared enterprise fault-record schema.
What Can Be Monitored
- fault-reporting host name
- fault severity level
- fault description text
- CCXML voice application engine error events
Imported Objects
From OPCD-SUPPORT-MIB-V2
| opencode-systems |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| enterprises |
From SNMPv2-TC
| DisplayString |
OIDs
RFC description
Vendor-private MIB for OPCD CCXML (Call Control XML) v2 management and monitoring.
Start monitoring OpenCode VoIP/IVR media server (CCXML call-control engine faults) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.