DPNSS-MIB: View SNMP OID List / Download MIB

The MIB module to describe the management of DPNSS interfaces.

DPNSS Signaling Table containing configuration and statistical parameters for all DPNSS signaling channel interfaces on this managed device.

An entry in the DPNSS Signaling Channel Table.

The index value which uniquely identifies an entry in the dpnssSigTable.

The ifIndex value of the interface associated with this signaling channel.

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.

Indicates whether dpnssMibCallInformation traps should be generated for calls on this signaling channel.

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.

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.

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.

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.

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.

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.

The number of incoming calls on this interface which were actually connected.

The number of SABMR frames sent from this interface. This is the number of new connections initiated from this interface.

The number of outgoing calls on this interface which were actually connected.

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.

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.

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.

An entry in the DPNSS DLC Table.

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

The identifier being used by the signaling protocol to identify this DLC, also referred to as Link Access Protocol (LAP) Number.

Indicates whether dpnssMibCallInformation traps should be generated for calls on this DLC.

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.

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.

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.

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.

Indicates whether it is a real or virtual DLC.

Number of L2 Framing Errors.

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.

This table defines port specific operational, statistics and active call data for DPNSS Trunks. Each entry in this table describes one DPNSS Trunk channel.

Operational and statistics information relating to one port. A port is a single DPNSS (Trunk).

The index value which uniquely identifies an entry in the dpnssTrkTable.

The ifIndex value corresponding to the DPNSS signaling channel that serves as the signaling channel for this trunk.

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.

Indicates whether dpnssMibCallInformation traps should be generated for calls over this Trunk.

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.

Indicates the type of digit outpulsing that will be done for a call-setup over this trunk.

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.

Interface address if any, in IA5 format of the DPNSS trunk Interface

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.

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.

The dpnssTrkMappingTable is used for quick look-up to associate a dpnss trunk with the corresponding dpnss signaling channel.

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.

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).

This trap/information is sent to the manager under the following conditions: - The dpnssSigLinkOperStatus goes to one of oos, resetAttempted, overload, recvOverrun, babbling, or crptMsg. - the dpnssSigUnprocessedUIs exceeds a preset threshold. The exact value of the threshold is implementor specific. If a threshold is not implemented in the agent, this trap will be generated for any positive value of dpnssSigUnprocessedUIs.

This trap/information is sent to the manager under the following conditions: - the dpnssDLCOperStatus goes to one of overload, recvOverrun, babbling, or crptMsg. - the dpnssDLCUnprocessedUIs exceeds a preset threshold. The exact value of the threshold is implementor specific. If a threshold is not implemented in the agent, this trap will be generated for any positive value of dpnssSigUnprocessedUIs. It is recommended that a different thresholds be implemented for dpnssSigUnprocessedUIs and dpnssDLCUnprocessedUIs. - the dpnssDLCL2FrameErrs exceeds a preset threshold. The exact value of the threshold is implementor specific. If a threshold is not implemented in the agent, the trap will be generated for any positive value of dpnssDLCL2FrameErrs.

This trap/information is sent to the manager under the following conditions: - the dpnssTrkOperStatus goes to one of lockout, inb or offLine.

The compliance statement for entities which implement the DPNSS MIB.

A collection of objects providing configuration and statistical information applicable to all DPNSS signaling channel interfaces.

A collection of objects providing configuration, statistical & signaling channel - trunk mapping information applicable to all DPNSS trunk interfaces.