All MIBs › OPCD-CONNECTORS-MIB-V2
Category: VoIP/Telephony
Description: Monitors external system connector status and message throughput 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-CONNECTORS-MIB-V2?
OPCD-CONNECTORS-MIB-V2 is an OpenCode Technologies SNMP module that monitors the status of external system connectors and message throughput on OpenCode VoIP/IVR platforms, where 'connectors' represent integration points to outside systems such as databases, telephony switches, or messaging gateways. It exposes fault records (host, severity, descriptive text) alongside connector-specific definitions and status variables, giving visibility into both configuration and operational health of these integration links. As a software-status MIB, it is used to detect when a connector to an external system has failed, is misconfigured, or is experiencing degraded message throughput, which is critical since a failed connector can silently break call-control or IVR workflows that depend on it. It shares the same 'mcr-' fault-record convention seen in other OPCD-* MIBs, indicating dependency on a common OpenCode fault-reporting schema across the product's MIB family. It is typically deployed in carrier or enterprise VoIP/IVR environments where connector uptime to back-end systems must be actively monitored. Engineers can download the OPCD-CONNECTORS-MIB-V2 file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in OPCD-CONNECTORS-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 platform
- OpenCode external system connector module
Monitoring Examples
An operator would monitor occonnectors and its associated definitions/vars objects to confirm each configured external connector is active and correctly parameterized, while watching the occonnectors-traps notifications for asynchronous failure alerts. When a connector drops, the shared mcr-Host/mcr-Severity/mcr-Text fault objects would identify which server raised the alert, how severe it is, and a plain-text description of the failure, such as a lost database or gateway connection. Sustained connector faults on a given occonnectors instance would signal an integration outage requiring reconnection or reconfiguration.
What Can Be Monitored
- connector configuration/definitions
- connector status variables
- connector fault host/severity/description
- connector failure trap notifications
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
Opencode connector application monitoring for USSD Browser external connections.
Start monitoring OpenCode VoIP/IVR platform (external system connector 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.