All MIBs › OPCD-CONNECTORS-MIB-V2
Category: VoIP/Telephony
Description:
Monitors external system connector status and message throughput on OpenCode VoIP/IVR platforms.
Imported Objects
From OPCD-SUPPORT-MIB-V2
| opencode-systems |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| enterprises |
From SNMPv2-TC
| DisplayString |
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.
What Can Be Monitored
- connector configuration/definitions
- connector status variables
- connector fault host/severity/description
- connector failure trap notifications
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.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| occonnectors | 1.3.6.1.4.1.30374.16 | |||
| occonnectors_traps | 1.3.6.1.4.1.30374.16.1 | |||
| definitions | 1.3.6.1.4.1.30374.16.1.0 | |||
| NTF occonectors_LdapConnector | 1.3.6.1.4.1.30374.16.1.0.2 | LDAP Connector is down! | ||
| NTF occonectors_LdapConnector_Canceled | 1.3.6.1.4.1.30374.16.1.0.3 | LDAP Connector is down-Canceled | ||
| NTF occonectors_MmlConnector | 1.3.6.1.4.1.30374.16.1.0.4 | MML Connector is down! | ||
| NTF occonectors_MmlConnector_Canceled | 1.3.6.1.4.1.30374.16.1.0.5 | MML Connector is down-Canceled | ||
| NTF occonectors_UcpConnector | 1.3.6.1.4.1.30374.16.1.0.6 | UCP Connector is down! | ||
| NTF occonectors_UcpConnector_Canceled | 1.3.6.1.4.1.30374.16.1.0.7 | UCP Connector is down-Canceled | ||
| NTF occonectors_UcipConnector | 1.3.6.1.4.1.30374.16.1.0.8 | UCIP Connector is down! | ||
| NTF occonectors_UcipConnector_Canceled | 1.3.6.1.4.1.30374.16.1.0.9 | UCIP Connector is down-Canceled | ||
| NTF occonectors_CaiConnector | 1.3.6.1.4.1.30374.16.1.0.10 | CAI Connector is down! | ||
| NTF occonectors_CaiConnector_Canceled | 1.3.6.1.4.1.30374.16.1.0.11 | CAI Connector is down-Canceled | ||
| NTF occonectors_SoapConnectorTimeout | 1.3.6.1.4.1.30374.16.1.0.12 | SOAP connector timeout. | ||
| NTF occonectors_SoapConnectorTimeout_Canceled | 1.3.6.1.4.1.30374.16.1.0.13 | SOAP connector timeout-Canceled | ||
| NTF occonectors_SoapConnectorLimit | 1.3.6.1.4.1.30374.16.1.0.14 | SOAP connector session limit is exceeded. | ||
| NTF occonectors_SoapConnectorLimit_Canceled | 1.3.6.1.4.1.30374.16.1.0.15 | SOAP connector session limit is exceeded-Canceled | ||
| NTF occonectors_CorbaSib | 1.3.6.1.4.1.30374.16.1.0.16 | Cannot connect to CORBA-CIB server. | ||
| NTF occonectors_CorbaSib_Canceled | 1.3.6.1.4.1.30374.16.1.0.17 | Cannot connect to CORBA-CIB server-Canceled | ||
| NTF occonectors_CorbaSmaf | 1.3.6.1.4.1.30374.16.1.0.18 | Cannot connect to CORBA-SMAF server. | ||
| NTF occonectors_CorbaSmaf_Canceled | 1.3.6.1.4.1.30374.16.1.0.19 | Cannot connect to CORBA-SMAF server-Canceled | ||
| NTF occonectors_CorbaSih | 1.3.6.1.4.1.30374.16.1.0.20 | Cannot connect to CORBA-SIH server. | ||
| NTF occonectors_CorbaSih_Canceled | 1.3.6.1.4.1.30374.16.1.0.21 | Cannot connect to CORBA-SIH server-Canceled | ||
| NTF occonectors_XMLConnectorTimeout | 1.3.6.1.4.1.30374.16.1.0.22 | XML connector timeout. | ||
| NTF occonectors_XMLConnectorTimeout_Canceled | 1.3.6.1.4.1.30374.16.1.0.23 | XML connector timeout-Canceled | ||
| NTF occonectors_XMLConnectorLimit | 1.3.6.1.4.1.30374.16.1.0.24 | XML connector session limit is exceeded. | ||
| NTF occonectors_XMLConnectorLimit_Canceled | 1.3.6.1.4.1.30374.16.1.0.25 | XML connector session limit is exceeded-Canceled | ||
| NTF occonectors_ORACLEConnector | 1.3.6.1.4.1.30374.16.1.0.26 | Oracle connector is down | ||
| NTF occonectors_ORACLEConnector_Canceled | 1.3.6.1.4.1.30374.16.1.0.27 | Oracle connector is down-Canceled | ||
| NTF occonectors_MYSQL_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.28 | No connection to MYSQL server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to MySQL server. 3.Check MySQL logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_MYSQL_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.29 | No connection to MYSQL server-Canceled | ||
| NTF occonectors_SMPP_SERVER_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.30 | No connection to SMPP server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to SMPP server. 3.Check SMPP server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_SMPP_SERVER_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.31 | No connection to SMPP server-Canceled | ||
| NTF occonectors_TELNET_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.32 | No connection to TELNET server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to TELNET server. 3.Check TELNET server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_TELNET_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.33 | No connection to TELNET server-Canceled | ||
| NTF occonectors_CORBA_SMAF_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.34 | No connection to CORBA SMAF server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to CORBA SMAF server. 3.Check CORBA SMAF server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_CORBA_SMAF_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.35 | No connection to CORBA SMAF server - Canceled | ||
| NTF occonectors_CORBA_SIH_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.36 | No connection to CORBA SIH server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to CORBA SIH server. 3.Check CORBA SIH server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_CORBA_SIH_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.37 | No connection to CORBA SIH server-Canceled | ||
| NTF occonectors_CORBA_CX_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.38 | No connection to CORBA CX server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to CORBA CX server. 3.Check CORBA CX server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_CORBA_CX_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.39 | No connection to CORBA CX server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to CORBA CX server. 3.Check CORBA CX server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_CORBA_CIB_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.40 | No connection to CORBA CIB server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to CORBA CIB server. 3.Check CORBA CIB server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_CORBA_CIB_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.41 | No connection to CORBA CIB server-Canceled | ||
| NTF occonectors_CORBA_ALCATEL_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.42 | No connection to CORBA(Alcatel) server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to CORBA(Alcatel) server. 3.Check CORBA(Alcatel) server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_CORBA_ALCATEL_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.43 | No connection to CORBA(Alcatel) server -Canceled | ||
| NTF occonectors_CAI_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.44 | No connection to CAI server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to CAI server. 3.Check CAI server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_CAI_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.45 | No connection to CAI server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to CAI server. 3.Check CAI server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_BROADCAST_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.46 | No connection to MYSQL server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to MySQL server. 3.Check MySQL logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_BROADCAST_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.47 | No connection to MYSQL server-Canceled | ||
| NTF occonectors_LDAP_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.48 | No connection to LDAP server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to LDAP server. 3.Check LDAP logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_LDAP_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.49 | No connection to LDAP server-Canceled | ||
| NTF occonectors_DIAMETER_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.50 | No connection to DIAMETER server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to DIAMETER server. 3.Check DIAMTER server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_DIAMETER_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.51 | No connection to DIAMETER server-Canceled | ||
| NTF occonectors_HTTPCLIENT_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.52 | No connection to HTTP server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to HTTP server. 3.Check HTTP server logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_HTTPCLIENT_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.53 | No connection to HTTP server-Canceled | ||
| NTF occonectors_BOOKMARK_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.54 | No connection to MYSQL server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to MySQL server. 3.Check MySQL logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_BOOKMARK_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.55 | No connection to MYSQL server-Canceled | ||
| NTF occonectors_CORBA_INPAYMENT_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.56 | No connection to IN(Payment) server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to IN server. 3.Check IN logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_CORBA_INPAYMENT_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.57 | No connection to IN(Payment) server-Canceled | ||
| NTF occonectors_CORBA_PPSERVER_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.58 | No connection to CORBA PP server 1.Check the connector's log file in order to find the reason for this alarm. 2.Check if there is ping to CORBA server. 3.Check CORBA logs for the possible reason for refusing connections from the connector | ||
| NTF occonectors_CORBA_PPSERVER_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.59 | No connection to CORBA PP server-Canceled | ||
| NTF occonectors_ecm_CONNECTOR_CRASHED | 1.3.6.1.4.1.30374.16.1.0.60 | Connector monitored by ECM crashed | ||
| NTF occonectors_ecm_CONNECTOR_CRASHED_Canceled | 1.3.6.1.4.1.30374.16.1.0.61 | Connector monitored by ECM crashed-Canceled | ||
| NTF occonectors_ecm_CONNECTOR_DISABLED | 1.3.6.1.4.1.30374.16.1.0.62 | Connector disabled. | ||
| NTF occonectors_ecm_CONNECTOR_DISABLED_Canceled | 1.3.6.1.4.1.30374.16.1.0.63 | Connector disabled-Canceled | ||
| NTF occonectors_MMLAUC_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.64 | No connection to MML server | ||
| NTF occonectors_MMLAUC_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.65 | No connection to MML server | ||
| NTF occonectors_ecm_CONNECTOR_PROBLEM | 1.3.6.1.4.1.30374.16.1.0.66 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF occonectors_ecm_CONNECTOR_PROBLEM_Canceled | 1.3.6.1.4.1.30374.16.1.0.67 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF mcr_HTTP_SERVER_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.68 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF mcr_HTTP_SERVER_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.69 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF mcr_SPEECHLAB_TTS_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.70 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF mcr_SPEECHLAB_TTS_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.71 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF mcr_CIMD2_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.72 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF mcr_CIMD2_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.73 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF mcr_SOAP_CLIENT_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.74 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF mcr_SOAP_CLIENT_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.75 | The alarm is turned ON if any connector is not working properly: 1.all subconnectos or all IPC connections are not working 2.it exited unexpectedly 3.it is disabled by ECM because of too much retries to start | ||
| NTF mcr_BLRATING_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.76 | Alarm of type 'CONNECT' is ON when connector can't connect to MySQL server or when connected to it and lost connection later. This alarm is set OFF when connection is restored. | ||
| NTF mcr_BLRATING_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.77 | Alarm of type 'CONNECT' is ON when connector can't connect to MySQL server or when connected to it and lost connection later. This alarm is set OFF when connection is restored. | ||
| NTF mcr_DMS_CLIENT_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.78 | Alarm of type 'CONNECT' is ON when connector can't connect to HTTP server or when connected to it and lost connection later. This alarm is set OFF when connection is restored. | ||
| NTF mcr_DMS_CLIENT_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.79 | Alarm of type 'CONNECT' is ON when connector can't connect to HTTP server or when connected to it and lost connection later. This alarm is set OFF when connection is restored. | ||
| NTF mcr_SMPP_EX_connector_CONNECT | 1.3.6.1.4.1.30374.16.1.0.80 | - All sessions for all configured clients are broken. - The connector exited unexpectedly. - The connector is disabled by ECM. | ||
| NTF mcr_SMPP_EX_connector_CONNECT_Canceled | 1.3.6.1.4.1.30374.16.1.0.81 | - The connector has at least one connected session. | ||
| NTF mcr_SMPP_EX_connector_CLIENT_SESS | 1.3.6.1.4.1.30374.16.1.0.82 | - One configured SMPP session is broken. | ||
| NTF mcr_SMPP_EX_connector_CLIENT_SESS_Canceled | 1.3.6.1.4.1.30374.16.1.0.83 | - All configured SMPP sessions are connected. | ||
| NTF mcr_SMPP_EX_connector_CLIENT_CONN | 1.3.6.1.4.1.30374.16.1.0.84 | - All sessions for one configured client are broken. | ||
| NTF mcr_SMPP_EX_connector_CLIENT_CONN_Canceled | 1.3.6.1.4.1.30374.16.1.0.85 | - At least one session is connected for this client. | ||
| NTF mcr_SMPP_EX_connector_SERVER_CONN | 1.3.6.1.4.1.30374.16.1.0.86 | - Server cannot be started. | ||
| NTF mcr_SMPP_EX_connector_SERVER_CONN_Canceled | 1.3.6.1.4.1.30374.16.1.0.87 | - Server is started. | ||
| vars | 1.3.6.1.4.1.30374.16.1.1 | |||
| STR mcr_Host | 1.3.6.1.4.1.30374.16.1.1.1 | DisplayString | accessible-for-notify | String containing hostname of fault node. |
| INT mcr_Severity | 1.3.6.1.4.1.30374.16.1.1.2 | INTEGER | accessible-for-notify | Alarm severity. |
| STR mcr_Text | 1.3.6.1.4.1.30374.16.1.1.3 | DisplayString | accessible-for-notify | String containing text of the alarm. |
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.