DPNSS-MIB
File:
DPNSS-MIB.mib (50637 bytes)
Imported modules
Imported symbols
Defined Types
DpnssSigEntry |
|
SEQUENCE |
|
|
|
|
dpnssSigIndex |
INTEGER |
|
|
dpnssSigIfIndex |
InterfaceIndex |
|
|
dpnssSigTrkCount |
Integer32 |
|
|
dpnssSigInfoTrapEnable |
INTEGER |
|
|
dpnssSigEndPtType |
INTEGER |
|
|
dpnssSigL2ReTxns |
Integer32 |
|
|
dpnssSigL2ReTxnTimeout |
Integer32 |
|
|
dpnssSigL2ReTxnAckTimeout |
Integer32 |
|
|
dpnssSigLinkOperStatus |
INTEGER |
|
|
dpnssSigL2InCallsConn |
Counter32 |
|
|
dpnssSigL3InCallsConn |
Counter32 |
|
|
dpnssSigL2OutCallsConn |
Counter32 |
|
|
dpnssSigL3OutCallsConn |
Counter32 |
|
|
dpnssSigL2AttemptedConns |
Counter32 |
|
|
dpnssSigUnprocessedUIs |
Counter32 |
|
DpnssDLCEntry |
|
SEQUENCE |
|
|
|
|
dpnssDLCSigIfIndex |
InterfaceIndex |
|
|
dpnssDLCNum |
INTEGER |
|
|
dpnssDLCInfoTrapEnable |
INTEGER |
|
|
dpnssDLCReTxns |
Integer32 |
|
|
dpnssDLCReTxnTimeout |
Integer32 |
|
|
dpnssDLCReTxnAckTimeout |
Integer32 |
|
|
dpnssDLCOperStatus |
INTEGER |
|
|
dpnssDLCType |
INTEGER |
|
|
dpnssDLCFrmErrs |
Counter32 |
|
|
dpnssDLCUnprocessedUIs |
Counter32 |
|
DpnssTrkEntry |
|
SEQUENCE |
|
|
|
|
dpnssTrkIfIndex |
INTEGER |
|
|
dpnssTrkSigIfIndex |
InterfaceIndex |
|
|
dpnssTrkNum |
INTEGER |
|
|
dpnssTrkInfoTrapEnable |
INTEGER |
|
|
dpnssTrkOperStatus |
INTEGER |
|
|
dpnssTrkOpulseType |
INTEGER |
|
|
dpnssTrkDir |
INTEGER |
|
|
dpnssTrkIfAddress |
DisplayString |
|
|
dpnssTrkCallSetupTime |
TimeStamp |
|
|
dpnssTrkCallConnectTime |
TimeStamp |
|
Defined Values
dpnssMib |
1.3.6.1.2.1.10.999 |
The MIB module to describe the
management of DPNSS interfaces. |
MODULE-IDENTITY |
|
|
|
dpnssSigTable |
1.3.6.1.2.1.10.999.1 |
DPNSS Signaling Table containing configuration and
statistical parameters for all DPNSS signaling channel
interfaces on this managed device. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
DpnssSigEntry |
|
dpnssSigEntry |
1.3.6.1.2.1.10.999.1.1 |
An entry in the DPNSS Signaling Channel Table. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
DpnssSigEntry |
|
|
dpnssSigIndex |
1.3.6.1.2.1.10.999.1.1.1 |
The index value which uniquely identifies an entry
in the dpnssSigTable. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
INTEGER |
1..2147483647 |
|
dpnssSigIfIndex |
1.3.6.1.2.1.10.999.1.1.2 |
The ifIndex value of the interface associated with this
signaling channel. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
InterfaceIndex |
|
|
dpnssSigTrkCount |
1.3.6.1.2.1.10.999.1.1.3 |
The total number of DPNSS Trunks(bearer channels)
managed by this signaling channel. For E1 this will
be 30 and for T1 it will be 24. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
1..65535 |
|
dpnssSigInfoTrapEnable |
1.3.6.1.2.1.10.999.1.1.4 |
Indicates whether dpnssMibCallInformation traps
should be generated for calls on this signaling
channel. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
enabled(1), disabled(2) |
|
dpnssSigEndPtType |
1.3.6.1.2.1.10.999.1.1.5 |
This object shall be used such that the two PBXs at
each end of the transmission link shall be designated A
& B by arrangement at configuration as specified in
BTNR 188. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
a(1), b(2) |
|
dpnssSigL2ReTxns |
1.3.6.1.2.1.10.999.1.1.6 |
This is the minimum retransmission count limit
designated as 'NL' in BTNR 188. This is the minimum
number of retransmissions of a command frame, which
must take place if the correct acknowledgment is not
received. BTNR recommends a value of 64 for this
parameter. If set to a value of -1 (or any other
negative value) this parameter is rendered redundant.
In such cases the NL value should be set/read on a per
DLC basis from the dpnssDLCTable. If set to a value
other than -1 (or any other negative value) it will be
applicable to all the DLCs. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
-32768..32767 |
|
dpnssSigL2ReTxnTimeout |
1.3.6.1.2.1.10.999.1.1.7 |
This is the minimum retransmission period designated as
'NT1' in BTNR 188. This is the minimum period of time
for which a command frame must be retransmitted if not
acknowledged. BTNR 188 recommends this value to be
500ms. If set to a value of -1 (or any other negative
value) this paramter is rendered redundant. In such
cases the NT1 value should be set/read on a per DLC
basis from the dpnssDLCTable. If set to a value other
than -1 (or any other negative value) it will be
applicable to all the DLCs. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
-32768..32767 |
|
dpnssSigL2ReTxnAckTimeout |
1.3.6.1.2.1.10.999.1.1.8 |
This is the minimum post retransmission acknowledgment
delay designated as 'NT2' in BTNR 188. This is the
minimum period of time after the expiry of NL and NT1
during which an acknowledgement is awaited before
reporting a retransmission failure to DPNSS Layer 3.
When DPNSS is used via a satellite link, BTNR 188
recommends a value of 520ms for NT2 and 0 otherwise.
If set to a value of -1 (or any other negative value)
this parameter is rendered redundant. In such cases the
NT2 value should be set/read on a per DLC basis from
dpnssDLCTable. If set to a value other than -1 (or any
other negative value) it will be applicable to all the
DLCs. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
-32768..32767 |
|
dpnssSigLinkOperStatus |
1.3.6.1.2.1.10.999.1.1.9 |
Parameter specifying the different DPNSS Signaling
channel states.
The maintenance states - bsy, inb and offline does not
directly correspond to a DLC state in the DLC table. In
this state the DLCs state should be either one of oos
or resetAttempt.
oos - Out Of Service
This State can be entered immediately following power
up or due to a maintenance action, eg following reset
failure. It is the state in which all DLCs exist before
activation of the Data Link Layer. A DLC remains in the
'Out of Service' state if it is not being used across a
particular physical link. In this state all received
frames are ignored. The oos status in the dpnssSigTable
indicates that all the corresponding DLCs are in oos
state.
idle
This is the state which a DLC enters from the OOS state
while awaiting to be started. In this state reset
requests from the remote PBX are not ignored, as in the
Out of service state. If a DLC is reset remotely the
local data link layer does not need to reset it. When a
DLC is started up locally it moves from this state to
Reset Attempted. The idle status in the dpnssSigTable
indicates that all the corresponding DLCs are idle
state.
resetAttempted
This is the state which a DLC enters when a reset
request is sent on it. The DLC enters the Reset
Complete state on completion of the reset procedure.
The resetAttempted status in the dpnssSigTable
indicates that all the corresponding DLCs are in
resetAttempted state.
resetComplete
This is the state of a DLC which has just been
successfuly reset. In this state, all the state
variables are set to 0. The resetComplete status in the
dpnssSigTable indicates that all the corresponding DLCs
are in resetComplete state
overload
This indicates that a DLC is not able to process the L2
messages due to various overload reasons which can
result for example when the layer 2 peer DLC is sending
messages at a rate faster than the what the near-end
can handle. The overload status in the dpnssSigTable
indicates that all the corresponding DLCs are in
overload state.
recvOverrun - receive overrun
This indicates that the DLC is receiving layer 2
messages from a peer at a rate faster than it can
buffer/process. The recvOverrun status in the
dpnssSigTable indicates that all the corresponding DLCs
are in recvOverrun state.
babbling
This indicates the receipt of an unexpected 'glitch-
message' on all the DLCs.
crptMsg - corrupt message
This indicates the receipt of a corrupt (but correctly
framed) DPNSS Layer 2 message on all the DLCs catered
by this DPNSS signaling channel.
The states - oos, idle, resetAttempted,
resetComplete, infoTransfer and overload of this table
is applicable to all the DLCs & reflects the status of
all the DLCs. This value should match the corresponding
OperStatus of the DLC Table. This option is provided so
that the implentors have the flexibility of
setting/reading the states of all DLCs in one shot
rather than walking through all the entries of the DLC
table.
bsy - busy
Indicates a maintenance operation status of the
signaling channel during which this link will not be
used for signaling. Generally this is the value
during some maintenance actions on the DPNSS link.
inB - installation Busy
Indicates a maintenance operation of the signaling
channel during which, apart from this channel not being
available for signaling, the configuration parameters
(mostly ds0 characteristics of this interface) can be
changed. The implementor may chose to just use the bsy
state as a superset state instead of inB in which case
this state will be rendered redundant.
offLine -
Indicates a maintenance operation of this signaling
channel during which, apart from this channel not
being available for call processing, the dpnss link
interface configuration parameters also cannot be
changed. This state is used to completely delete this
interface and configure it as some interface or re-
configure this interface. The vendor may just chose to
just use the inB state as a superset state instead of
offline in which case this state will be rendered
redundant.
pInSv - Partial Inservice
This indicates that some DLCs (atleast 1 DLC) are
in Reset Complete, Information Transfer or Idle state.
pOverload - Partial Overload
This indicates that some DLCs (atleast 1 DLC) is in
overload state. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
oos(1), idle(2), resetAttempted(3), resetComplete(4), infoTransfer(5), recvOverrun(6), babbling(7), crptMsg(8), overload(9), bsy(10), lockout(11), inb(12), offLine(13), pInSv(14), pOverload(15) |
|
dpnssSigL2InCallsConn |
1.3.6.1.2.1.10.999.1.1.10 |
The number of peer SABMR frames successfully received
on this interface. This is the number of peer-initiated
new connections on this interface. This does not
include the SABMR frames that were received but were
not processed. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter32 |
|
|
dpnssSigL3InCallsConn |
1.3.6.1.2.1.10.999.1.1.11 |
The number of incoming calls on this interface which
were actually connected. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter32 |
|
|
dpnssSigL2OutCallsConn |
1.3.6.1.2.1.10.999.1.1.12 |
The number of SABMR frames sent from this
interface. This is the number of new connections
initiated from this interface. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter32 |
|
|
dpnssSigL3OutCallsConn |
1.3.6.1.2.1.10.999.1.1.13 |
The number of outgoing calls on this interface which
were actually connected. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter32 |
|
|
dpnssSigL2AttemptedConns |
1.3.6.1.2.1.10.999.1.1.14 |
The number of peer SABMR frames received on this
interface. This is the number of peer-initiated
new connections on this interface. This also includes
the SABMR frames that were received but could not be
procesed resulting in unsuccessful Layer 2 connection
attempts. This count gives the SABMR frames received
for on all the DLCs. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter32 |
|
|
dpnssSigUnprocessedUIs |
1.3.6.1.2.1.10.999.1.1.15 |
The number of peer UI frames received on this
interface but could not be processed successfully (e.g.
due to layer 2 overload). This count gives the
unsuccessful UI frame count for on all the DLCs. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter32 |
|
|
dpnssDLCTable |
1.3.6.1.2.1.10.999.2 |
DPNSS DLC table containing configuration and DLC
characteristic parameters for all DPNSS DLCs on this
managed device. One Entry for each Lap (total of 60
Entries). There is no ifEntry for a DPNSS DLC in the
IfTable. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
DpnssDLCEntry |
|
dpnssDLCEntry |
1.3.6.1.2.1.10.999.2.1 |
An entry in the DPNSS DLC Table. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
DpnssDLCEntry |
|
|
dpnssDLCSigIfIndex |
1.3.6.1.2.1.10.999.2.1.1 |
The ifIndex value corresponding to the DPNSS signaling
channel that is responsible for this DLC. It is
important to note that this is also the index for the
dpnssDLCTable. Since the DLC does not have a
corresponding ifEntry, this is the only link between
the DPNSS DLC table and the DPNSS Signaling table
provided by this MIB |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
InterfaceIndex |
|
|
dpnssDLCNum |
1.3.6.1.2.1.10.999.2.1.2 |
The identifier being used by the signaling protocol
to identify this DLC, also referred to as
'Link Access Protocol (LAP) Number'. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
1..60 |
|
dpnssDLCInfoTrapEnable |
1.3.6.1.2.1.10.999.2.1.3 |
Indicates whether dpnssMibCallInformation traps
should be generated for calls on this DLC. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
enabled(1), disabled(2) |
|
dpnssDLCReTxns |
1.3.6.1.2.1.10.999.2.1.4 |
This is the minimum retransmission count limit
designated as 'NL' in BTNR 188. This is the minimum
number of retransmissions of a command frame which must
take place if the correct acknowledgment is not
received. BTNR recommends a value of 64 for this
parameter. If set to a value of -1 (or any other
negative value) this parameter is rendered redundant.
In such cases the NL value should be set/read from the
dpnssSigTable. This value should not be -1 in the
dpnssSigTable and dpnssDLCTable at the same time. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
-32768..32767 |
|
dpnssDLCReTxnTimeout |
1.3.6.1.2.1.10.999.2.1.5 |
This is the minimum retransmission period designated as
'NT1' in BTNR 188. This is the minimum period of time
for which a command frame must be retransmitted if not
acknowledged. BTNR 188 recommends this value to be
500ms. If set to a value of -1 (or any other negative
value) this paramter is rendered redundant. In such
cases the NT1 value should be set/read from the
dpnssSigTable. This value should not be -1 in the
dpnssSigTable and dpnssDLCTable at the same time. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
-32768..32767 |
|
dpnssDLCReTxnAckTimeout |
1.3.6.1.2.1.10.999.2.1.6 |
This is the minimum post retransmission acknowledgment
delay designated as 'NT2' in BTNR 188. This is the
minimum period of time after the expiry of NL and NT1
during which an acknowledgement is awaited before
reporting a retransmission failure to DPNSS Layer 3.
When DPNSS is used via a satellite link, BTNR 188
recommends a value of 520ms for NT2 and 0 otherwise.
If set to a value of -1 (or any other negative value)
this parameter is rendered redundant. In such cases the
NT2 value should be set/read from dpnssSigTable. This
value should not be -1 in the dpnssSigTable and
dpnssDLCTable at the same time. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
-32768..32767 |
|
dpnssDLCOperStatus |
1.3.6.1.2.1.10.999.2.1.7 |
Parameter specifying the different DPNSS Layer 2 DLC
states.
oos - Out Of Service
This State can be entered immediately following power
up or due to a maintenance action, eg following reset
failure. It is the state in which all DLCs exist before
activation of the Data Link Layer. A DLC remains in the
'Out of Service' state if it is not being used across a
particular physical link. In this state all received
frames are ignored.
idle
This is the state which a DLC enters from the OOS state
while awaiting to be started. In this state reset
requests from the remote PBX are not ignored, as in the
Out of service state. If a DLC is reset remotely the
local data link layer does not need to reset it. When a
DLC is started up locally it moves from this state to
Reset Attempted.
resetAttempted
This is the state which a DLC enters when a reset
request is sent on it. The DLC enters the Reset
Complete state on completion of the reset procedure.
resetComplete
This is the state of a DLC which has just been
successfuly reset. In this state, all the state
variables are set to 0.
overload
This indicates that a DLC is not able to process the L2
messages due to various overload reasons which can
result for example when the layer 2 peer DLC is sending
messages at a rate faster than the what the near-end
can handle.
recvOverrun - receive overrun
This indicates that the DLC is receiving layer 2
messages from a peer at a rate faster than it can
buffer/process.
babbling
This indicates the receipt of an unexpected 'glitch-
message' on all this DLC.
crptMsg - corrupt message
This indicates the receipt of a corrupt (but correctly
framed) DPNSS Layer 2 message on this DLC. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
oos(1), idle(2), resetAttempted(3), resetComplete(4), infoTransfer(5), overload(6), recvOverrun(7), babbling(8), crptMessage(9) |
|
dpnssDLCType |
1.3.6.1.2.1.10.999.2.1.8 |
Indicates whether it is a real or virtual DLC. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
real(1), virtual(2) |
|
dpnssDLCFrmErrs |
1.3.6.1.2.1.10.999.2.1.9 |
Number of L2 Framing Errors. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter32 |
|
|
dpnssDLCUnprocessedUIs |
1.3.6.1.2.1.10.999.2.1.10 |
The number of peer UI frames received on this
interface but could not be processed successfully (e.g.
due to layer 2 overload). This count gives the
unsuccessful UI frame count for on all the DLCs. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Counter32 |
|
|
dpnssTrkTable |
1.3.6.1.2.1.10.999.3 |
This table defines port specific operational,
statistics and active call data for DPNSS Trunks.
Each entry in this table describes one DPNSS Trunk
channel. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
DpnssTrkEntry |
|
dpnssTrkEntry |
1.3.6.1.2.1.10.999.3.1 |
Operational and statistics information relating to
one port. A port is a single DPNSS (Trunk). |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
DpnssTrkEntry |
|
|
dpnssTrkIfIndex |
1.3.6.1.2.1.10.999.3.1.1 |
The index value which uniquely identifies an entry
in the dpnssTrkTable. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
1..2147483647 |
|
dpnssTrkSigIfIndex |
1.3.6.1.2.1.10.999.3.1.2 |
The ifIndex value corresponding to the DPNSS signaling
channel that serves as the signaling channel for this
trunk. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
InterfaceIndex |
|
|
dpnssTrkNum |
1.3.6.1.2.1.10.999.3.1.3 |
The identifier being used by a signaling protocol
to identify this trunk, also referred to as
trunk number. If the Agent also supports the DS0
MIB, the values of dpnssTrkNum and dsx0Ds0Number
must be identical for a given DPNSS Trunk. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
1..30 |
|
dpnssTrkInfoTrapEnable |
1.3.6.1.2.1.10.999.3.1.4 |
Indicates whether dpnssMibCallInformation traps
should be generated for calls over this Trunk. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
enabled(1), disabled(2) |
|
dpnssTrkOperStatus |
1.3.6.1.2.1.10.999.3.1.5 |
The Different DPNSS DPNSS trunk States as specified by
BTNR 188. Also incorporates maintenance operation
states that.
icSetupReq - Incoming Setup Request
Indicates that there is an incoming setup request (ISRM
receipt).
ogSetupReq - Outgoing Setup Request
Indicates that there is an outgoing setup request
outgoing ISRM).
icSetupComp - Incoming Setup Complete
Indicates that the trunk in inSetupReq state has
sent a successful Ack (sending of DPNSS Number
Acknowledge (NAM) message).
ogSetupComp - Outgoing Setup Complete
Indicates that the trunk in ogSetupReq state has
received a successful acknowledgement(incoming NAM).
inSetupCompBuf - Incoming Setup Complete Buffer
Indicates the receipt of a message received on a trunk
in inSetupComp state and being buffered (example, the
received EEM(I)s may be buffered till the receipt of
EEM(C)s before being processed.
ogSetupCompBuf - Outgoing Setup Complete Buffer
Indicates the receipt of a message received on a trunk
in ogSetupComp state.
inAns - Incoming Answer
Indicates the sending of an of an answer message
(incoming DPNSS Call Connected Message (CCM)).
ogAns - Outgoing Answer
Indicates the receipt of an answer message on a trunk
that is in ogSetupComp state(outgoing CCM).
Clearing
Indicates the sending of an clearing message
(outgoing DPNSS Clear Request Message (CRM). The trunk
will return to idle state or the receipt of a DPNSS
Clear Indication Message from the peer PBX in response
to the CRM.
idle
Default working state when no call attempt or call in
progress on this trunk.
bsy - busy
Indicates a maintenance operation status of the trunk
during which this trunk will not be used for call
processing. Generally done to perform some maintenance
on the DPNSS trunk.
LockOut
Indicates that the corresponding Layer 2 DLC is Out Of-
Service.
inB - installation Busy
Indicates a maintenance operation of the trunk during
which, apart from this trunk not being available for
call processing, the configuration parameters (like
dpnssTrkDir etc) of the trunk can be changed. The
implementor may chose to just use the bsy state as a
superset state instead of inB in which case this state
will be rendered redundant.
offLine -
Indicates a maintenance operation of the trunk during
which, apart from this trunk not being available for
call processing, the trunk interface configuration
parameters also cannot be changed. This state is used
normally to completely delete this interface and
reconfigure as some other interface. The vendor may
just chose to just use the inB state as a superset
state instead of offline in which case this state will
be rendered redundant. Further, the DS1 interface over
which the DPNSS trunks and signaling channel is
configured cannot be shared across another protocol
(e.g. ISDN - Primary Rate Interface) interface - this
further reduces the usefulness of this state but the
parameter is provided in favour of implementation
flexibility. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
icSetupReq(1), ogSetupReq(2), icSetupComp(3), ogSetupComp(4), icSetupCompBuf(5), ogSetupCompBuf(6), icAns(7), ogAns(8), clearing(9), idle(10), bsy(11), lockout(12), inb(13), offLine(14) |
|
dpnssTrkOpulseType |
1.3.6.1.2.1.10.999.3.1.6 |
Indicates the type of digit outpulsing that will be
done for a call-setup over this trunk. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
enblock(1), overlap(2) |
|
dpnssTrkDir |
1.3.6.1.2.1.10.999.3.1.7 |
The direction of the trunk call that will be supported
over this trunk.
ic - Allow only Incoming calls over this trunk
og - Allow only Outgoing calls over this trunk
twoW - Allow both incoming and outgoing calls
over this trunk. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
ic(1), og(2), twoW(3) |
|
dpnssTrkIfAddress |
1.3.6.1.2.1.10.999.3.1.8 |
Interface address if any, in IA5 format of the DPNSS
trunk Interface |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
DisplayString |
|
|
dpnssTrkCallSetupTime |
1.3.6.1.2.1.10.999.3.1.9 |
The value of sysUpTime when the DPNSS setup message
[DPNSS Initial Service Request Message (ISRM)] for the
current or last call was sent or received. If since
system startup there has been no call on this
interface, this object has a value of zero. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TimeStamp |
|
|
dpnssTrkCallConnectTime |
1.3.6.1.2.1.10.999.3.1.10 |
The value of sysUpTime when the DPNSS connect message
[DPNSS Call Connect Message (CCM)] for the current or
last call was sent or received. If since system startup
there has been no call on this interface, this object
has a value of zero. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TimeStamp |
|
|
dpnssTrkMappingTable |
1.3.6.1.2.1.10.999.4 |
The dpnssTrkMappingTable is used for quick look-up to
associate a dpnss trunk with the corresponding
dpnss signaling channel. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
DpnssTrkMappingEntry |
|
dpnssTrkMappingEntry |
1.3.6.1.2.1.10.999.4.1 |
This is an entry in the DPNSS Trunk Mapping table.
There is a entry in this table corresponding to each
DPNSS trunk ifEntry. This table is intended to
facilitate mapping from DPNSS signaling channel
ifEntry/DPNSS trunk number to the DPNSS trunk ifEntry.
(e.g. mapping (DPNSS signaling channel ifIndex, DPNSS
trunk number) -> DPNSS trunk ifIndex.
While this table provides information that can also be
indirectly derived from the ifStackTable using the ds0
& ds1 MIBs, it provides the same information with a
single table lookup, rather than by walking through
the ifStackTable to find the various constituent ds0
ifTable entries, and testing various ifEntry leaf
nodes like ifName etc. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
DpnssTrkMappingEntry |
|
|
dpnssTrkMappingIfIndex |
1.3.6.1.2.1.10.999.4.1.1 |
This object indicates the ifIndex value assigned
by the agent for the individual dpnss trunk ifEntry
that corresponds to the given dpnss trunk number
(specified by the INDEX element dpnssTrkNum) of the
associated dpnss signaling interface (specified by
INDEX element ifIndex). |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
InterfaceIndex |
|
|
dpnssMibCompliances |
1.3.6.1.2.1.10.999.6.1.1 |
The compliance statement for entities which implement
the DPNSS MIB. |
Status: current |
Access: read-only |
MODULE-COMPLIANCE |
|
|
|
dpnssMibSigGroup |
1.3.6.1.2.1.10.999.6.2.1 |
A collection of objects providing configuration and
statistical information applicable to all DPNSS
signaling channel interfaces. |
Status: current |
Access: read-only |
OBJECT-GROUP |
|
|
|
dpnssMibTrkGroup |
1.3.6.1.2.1.10.999.6.2.2 |
A collection of objects providing configuration,
statistical & signaling channel - trunk mapping
information applicable to all DPNSS trunk interfaces. |
Status: current |
Access: read-only |
OBJECT-GROUP |
|
|
|