CALISTA-DPA-MIB: View SNMP OID List / Download MIB

Unique value assigned to each DPA device.

The version of the main image code that the DPA is currently running.

The version of the boot loader code that the DPA is currently running.

The integration mode in which the DPA is currently operating: unconfigured the factory setting; the DPA requires configuring before it can be connected to an Octel voicemail system. simple the DPA is connected to only an Octel voicemail system and Cisco CallManager hybrid the DPA is connected to an Octel voicemail system, a PBX system and Cisco CallManager See the DPA Administration Guide for more detailed descriptions of these modes. Enumeration: 'simple': 2, 'hybrid': 3, 'unconfigured': 1.

The PBX type that the DPA is currently emulating in order to communicate with the Octel voicemail system. This also determines the protocol used on the digital telephony links to the PBX, if in hybrid mode.

The number of IP telephony calls made to this DPA. This includes all calls, regardless of whether the Octel answered. This could happen, for instance, if the original caller hangs up before the Octel accepts the call.

The number of calls originated by the Octel which go through the DPA. These include networking calls (communication between peer Octel systems), pager and mobile notifications and fax calls.

The number of commands to set or clear a Message Waiting Indicator received by this DPA from the Octel voicemail system. These commands are relayed to the Cisco CallManager via the virtual port, and, if the DPA is operating in hybrid mode, the attached PBX system.

The number of commands to set or clear a Message Waiting Indicator which are queued within the DPA, waiting to be sent to the PBX. These commands will be issued to the PBX when the appropriate port becomes available. If the DPA is not operating in hybrid mode, this value will always be zero.

The number of commands to set or clear a Message Waiting Indicator which have been successfully sent to the PBX. If the DPA is not operating in hybrid mode, this value will always be zero.

The number of commands to set or clear a Message Waiting Indicator that the DPA was unable to send successfully to the PBX. Such commands will have been discarded, and the cause written to the DPA's error log. If the DPA is not operating in hybrid mode, this value will always be zero.

The number of commands to set or clear a Message Waiting Indicator which are queued within the DPA, waiting to be sent to Cisco CallManager.

The number of commands to set or clear a Message Waiting Indicator which have been successfully sent to Cisco CallManager.

The number of commands to set or clear a Message Waiting Indicator that the DPA was unable to send successfully to Cisco CallManager. Such commands will have been discarded, and the cause written to the DPA's error log.

A list of the available ports on the DPA, with current state information for each.

An entry containing all relevant information for a DPA port.

A unique value for each port. Its value ranges from 1 to the total number of ports.

How this port is currently being used: notInUse not currently in use (may become active later) octel connected to an Octel voicemail system pbx connected to a digital PBX virtual not a physical port; connected only to Cisco CallManager It should be noted that the type of a port is determined when it first becomes active. Significantly, this value will not change back to notInUse if a port is later disconnected; the relevant portTelephonyLinkState value should be read to determine whether the port is currently active. Enumeration: 'octel': 2, 'pbx': 3, 'virtual': 4, 'notInUse': 1.

The state of the digital telephony link. This field only has meaning for physical ports connected to Octel voicemail systems or digital PBX systems. For virtual ports or those currently not in use, the state will be returned as notApplicable. Enumeration: 'down': 2, 'notApplicable': 1, 'up': 4, 'registering': 3.

The state of this port's connection to a Cisco CallManager, if such a connection exists. For ports connected to digital PBX systems (see the portType entry) this will be returned as notApplicable. Enumeration: 'down': 2, 'notApplicable': 1, 'up': 4, 'registering': 3.

Once a port's required link(s) to an Octel / PBX and CallManager have become active, it then becomes available for use placing calls between the two realms. This entry shows the current state of any active call for a port, as described in the DPA Administration Guide. Enumeration: 'outCall': 9, 'callIn': 4, 'unknown': 1, 'callOut': 5, 'onHook': 3, 'transfer': 8, 'notApplicable': 2, 'hangingUp': 10, 'offHook': 7, 'onCall': 6.

The device name under which this port is registered with Cisco CallManager.

If there is a call in progress on this port, this entry gives the codec in use, otherwise it will return none. Enumeration: 'g729a': 5, 'g723dot1': 4, 'none': 1, 'g711MuLaw': 3, 'g711ALaw': 2.

The number of centiseconds during which PBX protocol errors were detected for this port. It is normal for there to be some errors, especially during port initialization, but very large values should only be seen on disconnected ports.

The DAC level for the port; this is related to the voltage level on the digital telephony port, and is only used in diagnosis of internal hardware faults.

A list of all of the Cisco CallManager connections that the DPA is currently maintaining.

An entry containing all relevant information for a connection to a Cisco CallManager device.

Corresponds to portIndex in PortEntry.

The index of this connection; each port can have connections to several Cisco CallManagers, with one active connection and the rest operating in standby mode.

The host name, if known, of the CallManager to which this connection refers.

The IP address of the CallManager to which this connection refers.

The TCP port number on the CallManager to which this connection has been made.

The current state of this connection. The possible values have the following meanings: idle initial state of the link before a connection has been attempted, and the state to which a link changes after teardown connecting a TCP link to a Cisco CallManager system is in the process of being established retryBackOff the attempt to establish to the Cisco CallManager failed; the connection stays in this state for a short while before the DPA tries again connectPending the retry back off period has finished and the DPA is about to re-attempt connection to the Cisco CallManager active the connection has been successfully established; this state signifies that the connection is being used for transmission and reception of Skinny Station Protocol messages standby the connection has been successfully established but it is not currently being used for data traffic; however, it would move into the active state were the currently active connection to go down Enumeration: 'standby': 6, 'idle': 1, 'connecting': 2, 'active': 5, 'connectPending': 4, 'retryBackOff': 3.