| serialNumber |
.1.3.6.1.4.1.7505.1.1.1 |
|
Unique value assigned to each DPA device.
|
| imageVersion |
.1.3.6.1.4.1.7505.1.1.2 |
|
The version of the main image code that the DPA
is currently running.
|
| loaderVersion |
.1.3.6.1.4.1.7505.1.1.3 |
|
The version of the boot loader code that the DPA
is currently running.
|
| integrationMode |
.1.3.6.1.4.1.7505.1.1.4 |
|
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.
|
| pbxType |
.1.3.6.1.4.1.7505.1.1.5 |
|
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.
|
| receivedCalls |
.1.3.6.1.4.1.7505.1.1.6 |
|
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.
|
| outgoingCallsMade |
.1.3.6.1.4.1.7505.1.1.7 |
|
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.
|
| mwiCommandsReceived |
.1.3.6.1.4.1.7505.1.1.8 |
|
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.
|
| pbxQueuedMWICommands |
.1.3.6.1.4.1.7505.1.1.9 |
|
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.
|
| pbxCompletedMWICommands |
.1.3.6.1.4.1.7505.1.1.10 |
|
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.
|
| pbxMWIErrors |
.1.3.6.1.4.1.7505.1.1.11 |
|
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.
|
| callManagerQueuedMWICommands |
.1.3.6.1.4.1.7505.1.1.12 |
|
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.
|
| callManagerCompletedMWICommands |
.1.3.6.1.4.1.7505.1.1.13 |
|
The number of commands to set or clear a Message Waiting
Indicator which have been successfully sent to Cisco
CallManager.
|
| callManagerMWIErrors |
.1.3.6.1.4.1.7505.1.1.14 |
|
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.
|
| portEntry |
.1.3.6.1.4.1.7505.1.1.15.1 |
|
An entry containing all relevant information for a DPA port.
|
| callManagerConnectionEntry |
.1.3.6.1.4.1.7505.1.1.16.1 |
|
An entry containing all relevant information for a connection
to a Cisco CallManager device.
|
| portIndex |
.1.3.6.1.4.1.7505.1.1.15.1.1 |
|
A unique value for each port. Its value ranges from
1 to the total number of ports.
|
| portType |
.1.3.6.1.4.1.7505.1.1.15.1.2 |
|
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.
|
| portTelephonyLinkState |
.1.3.6.1.4.1.7505.1.1.15.1.3 |
|
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.
|
| portCallManagerLinkState |
.1.3.6.1.4.1.7505.1.1.15.1.4 |
|
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.
|
| portCallState |
.1.3.6.1.4.1.7505.1.1.15.1.5 |
|
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.
|
| portDeviceName |
.1.3.6.1.4.1.7505.1.1.15.1.6 |
|
The device name under which this port is registered with
Cisco CallManager.
|
| portCodecInUse |
.1.3.6.1.4.1.7505.1.1.15.1.7 |
|
If there is a call in progress on this port, this entry gives
the codec in use, otherwise it will return none.
|
| portErrors |
.1.3.6.1.4.1.7505.1.1.15.1.8 |
|
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.
|
| portDacLevel |
.1.3.6.1.4.1.7505.1.1.15.1.9 |
|
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.
|
| cmConnectionIndex |
.1.3.6.1.4.1.7505.1.1.16.1.2 |
|
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.
|
| cmConnectionPortIndex |
.1.3.6.1.4.1.7505.1.1.16.1.1 |
|
Corresponds to portIndex in PortEntry.
|
| cmConnectionCallManagerName |
.1.3.6.1.4.1.7505.1.1.16.1.3 |
|
The host name, if known, of the CallManager to which this
connection refers.
|
| cmConnectionIpAddress |
.1.3.6.1.4.1.7505.1.1.16.1.4 |
|
The IP address of the CallManager to which this connection
refers.
|
| cmConnectionIpPort |
.1.3.6.1.4.1.7505.1.1.16.1.5 |
|
The TCP port number on the CallManager to which this connection
has been made.
|
| cmConnectionState |
.1.3.6.1.4.1.7505.1.1.16.1.6 |
|
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
|
