cpmISDNCfgBChanInUseForAnalog
1.3.6.1.4.1.9.10.19.1.1.2
Gauge32
The number of configured ISDN B-Channels that are currently occupied by analog calls.
2005-12-21
Cisco Point Of Presence Management MIB to provide DSX1 and DSX0 facilities management and call summaries.
Download CISCO-POP-MGMT-MIB.txt Open CISCO-POP-MGMT-MIB.txt in a new tab
SCALARS (28) · TABLES (5) · TRAPS (2)
| Name | OID |
|---|---|
| cpmDS0BusyoutNotification | 1.3.6.1.4.1.9.10.19.2.0.1 |
| cpmDS1LoopbackNotification | 1.3.6.1.4.1.9.10.19.2.0.2 |
END OF TOC
1.3.6.1.4.1.9.10.19.1.1.2
Gauge32
The number of configured ISDN B-Channels that are currently occupied by analog calls.
1.3.6.1.4.1.9.10.19.1.1.3
Gauge32
The number of configured ISDN B-Channels that are currently occupied by both Digital and Analog calls.
1.3.6.1.4.1.9.10.19.1.1.4
Gauge32
The number of DS0s that are currently in use.
1.3.6.1.4.1.9.10.19.1.1.5
Gauge32
The current number of active PPP calls received by the managed device
1.3.6.1.4.1.9.10.19.1.1.6
Gauge32
The current number of active V.120 calls received by the managed device
1.3.6.1.4.1.9.10.19.1.1.7
Gauge32
The current number of active V.110 calls received by the managed device
1.3.6.1.4.1.9.10.19.1.1.8
Counter32
The high water mark for number of DS0s that are active simultaneously
1.3.6.1.4.1.9.10.19.1.1.10
Gauge32
The number of configured SW56 B-Channels that are currently occupied by Digital calls.
1.3.6.1.4.1.9.10.19.1.1.11
Gauge32
The number of configured ISDN B-Channels that are currently occupied by Voice calls.
1.3.6.1.4.1.9.10.19.1.1.12
Gauge32
The number of configured CAS Channels that are currently occupied by Voice calls.
1.3.6.1.4.1.9.10.19.1.1.13
Gauge32
The number of ISDN signaling channels which are active.
1.3.6.1.4.1.9.10.19.1.1.14
Counter32 · seconds
The total call duration on all the ISDN B-channels since last system re-initialization.
1.3.6.1.4.1.9.10.19.1.1.15
Counter32 · seconds
The total analog call duration on all the ISDN B-channels since last system re-initialization. Analog call type is identified in cpmDS0CallType.
1.3.6.1.4.1.9.10.19.1.1.16
Counter32 · calls
The total number of calls on all the ISDN B-channels since last system re-initialization.
1.3.6.1.4.1.9.10.19.1.1.17
Counter32 · calls
The total number of analog calls on all the ISDN B-channels since last system re-initialization. Analog call type is identified in cpmDS0CallType.
1.3.6.1.4.1.9.10.19.1.1.18
Counter32
The total number of ISDN-sync PPP calls received by the managed device since last system re-initialization.
1.3.6.1.4.1.9.10.19.1.2.1
Counter32
The number of rejected ISDN calls in this managed device.
1.3.6.1.4.1.9.10.19.1.2.2
Counter32
The number of rejected modem calls in this managed device.
1.3.6.1.4.1.9.10.19.1.2.3
Counter32
The number of connected ISDN calls that have been abnormally cleared, that is, they were cleared by some event other than the following: a - The transmission of a normal disconnect message by the local end. b - The reception of a normal disconnect message from the remote end.
1.3.6.1.4.1.9.10.19.1.2.4
Counter32
The number of connected modem calls that have been abnormally cleared, that is, they were not cleared with the proper modem protocol handshakes.
1.3.6.1.4.1.9.10.19.1.2.5
Counter32
The number of ISDN calls that have been rejected because there is no B-Channel available to handle the call.
1.3.6.1.4.1.9.10.19.1.2.6
Counter32
The number of modem calls that have been rejected because there is no modem available to handle the call.
1.3.6.1.4.1.9.10.19.1.4.1
Integer32 (0..500)
The upper limit on the number of entries that the cpmCallHistoryTable may contain. A value of 0 will prevent any history from being retained. When this table is full, the oldest entry will be deleted and the new one will be created.
1.3.6.1.4.1.9.10.19.1.4.2
Integer32 (0..500) · minutes
The minimum amount of time that an cpmCallHistoryEntry will be maintained before being deleted. A value of 0 will prevent any history from being retained, but will not prevent callCompletion traps being genarated.
1.3.6.1.4.1.9.10.19.1.5.1
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This variable controls generation of cpmDS0BusyoutNotification. When this variable is 'true(1)', generation of cpmDS0BusyoutNotification is enabled. When this variable is 'false(2)', generation of cpmDS0BusyoutNotification is disabled. The default value is 'false(2)'.
1.3.6.1.4.1.9.10.19.1.6.1
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This variable controls the generation of cpmDS1LoopbackNotification When this variable is 'true(1)', generation of these notification is enabled. When this variable is 'false(2)', generation is disabled The default value is 'false(2)'.
1.3.6.1.4.1.9.10.19.1.7.1
Counter32
The number of incoming and outgoing successful ISDN digital data calls (cpmDS0CallType has the value 'digital(4)'), since system startup. A successful call is a terminated call that has a disconnect cause of 'normal call clearing(16)'.
1.3.6.1.4.1.9.10.19.1.7.2
Counter32
The number of incoming and outgoing successful analog data calls which use modem resource (cpmDS0CallType has the value 'analog(3)'), since system startup. A successful call is a terminated call who is cleared by the proper modem protocol handshake.
1.3.6.1.4.1.9.10.19.1.1.1
Index: cpmDS1SlotIndex · cpmDS1PortIndex · cpmChannelIndex
The DS0 usage table is for hardware and software objects not used as interfaces, and not covered in rfc1213. These objects include analog calls coming over ISDN, Channelized T1, and Channelized E1. This table is created for every DS1 line in the device.
1.3.6.1.4.1.9.10.19.1.1.1.1.1
Integer32 (0..2147483647)
The slot index indicates the slot number on the device where the DS1 card resides.
1.3.6.1.4.1.9.10.19.1.1.1.1.2
Integer32 (0..2147483647)
The port index indicates the port number of a specific DS1 on the DS1 card in the slot
1.3.6.1.4.1.9.10.19.1.1.1.1.3
Integer32 (0..2147483647)
The channel index that distinguishes the DS0 timeslot of the DS1 port. The range of the channel index is based on the number of T1/E1 channels: 1-24(T1) and 1-31(E1).
1.3.6.1.4.1.9.10.19.1.1.1.1.4
INTEGER1 = unknown2 = isdn3 = ct14 = ce1 · Integer32
The configured technology for the channel: ISDN(2), Channelized T1 (3) or Channelized E1 (4).
1.3.6.1.4.1.9.10.19.1.1.1.1.5
INTEGER1 = idle2 = unknown3 = analog4 = digital5 = v1106 = v1207 = voice · Integer32
The type of the current call carried by this DS0. idle - This DS0 is currently idle. unknown - The data type of the call currently occupying this DS0 is not one of the types listed here. analog - The data type of the call currently occupying this DS0 is analog, i.e. a modem call. digital - The data type of the call currently occupying this DS0 is digital. v110 - The call currently occupying this DS0 is a V110 call. v120 - The call currently occupying this DS0 is a V120 call. voice - The call currently occupying this DS0 is a voice call.
1.3.6.1.4.1.9.10.19.1.1.1.1.6
INTEGER1 = idle2 = unknown3 = ppp4 = slip5 = arap6 = hdlc7 = exec8 = voice · Integer32
The data link encapsulation of the call currently occuppying this DS0: idle - This DS0 is currently idle. unknown - The encapsulation of the currently active call on this DS0 is not one of the options following. PPP - slip - arap - hdlc - exec - voice - voice encapsulation; IANA type voiceEncap(103)
1.3.6.1.4.1.9.10.19.1.1.1.1.7
Counter32
The number of calls that have occupied this DS0.
1.3.6.1.4.1.9.10.19.1.1.1.1.8
TimeTicks
The amount of time that this DS0 has been in use. This is computed by summing up the call durations of all past calls that have occupied this DS0.
1.3.6.1.4.1.9.10.19.1.1.1.1.9
Counter32
The total number of octets received on this DS0 for data calls (cpmDS0CallType has the value 'analog(3)' or 'digital(4)' or 'v110(5)' or 'v120(6)'). All the received 'raw' octets are counted, including any protocol headers which may or may not be present, depending on the service type of data call.
1.3.6.1.4.1.9.10.19.1.1.1.1.10
Counter32
The total number of octets transmitted on this DS0 for data calls (cpmDS0CallType has the value 'analog(3)' or 'digital(4)' or 'v110(5)' or 'v120(6)'). All the transmitted 'raw' octets are counted, including any protocol headers which may or may not be present, depending on the service type of data call.
1.3.6.1.4.1.9.10.19.1.1.1.1.11
Counter32
The total number of packets received on this DS0 for data calls (cpmDS0CallTyp has the value 'analog(3)' or 'digital(4)' or 'v110(5)' or 'v120(6)').
1.3.6.1.4.1.9.10.19.1.1.1.1.12
Counter32
The total number of packets transmitted on this DS0 for data calls (cpmDS0CallTyp has the value 'analog(3)' or 'digital(4)' or 'v110(5)' or 'v120(6)').
1.3.6.1.4.1.9.10.19.1.1.1.1.13
InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d
This is the value of ifIndex when the specific channel has an active call with a corresponding interface in the ifTable. For example, a digital ISDN call has a value pointing to the B-Channel entry in the ifTable. A modem call over ISDN or CT1/CE1 has a value pointing to the async interface of the modem assigned to this call. If the channel is idle, this value is 0.
1.3.6.1.4.1.9.10.19.1.1.9
Index: cpmDS1UsageSlotIndex · cpmDS1UsagePortIndex
The DS1-DS0-usage table is for hardware and software objects not used as interfaces, and not covered in rfc1213. These objects provide information on timeslots usage for a particular DS1.
1.3.6.1.4.1.9.10.19.1.1.9.1.1
Integer32 (0..2147483647)
The slot index indicates the slot number on the device where the DS1 card resides. The slot index of the first slot is starting from 0 and increment by 1 for the next slot in the device.
1.3.6.1.4.1.9.10.19.1.1.9.1.2
Integer32 (0..2147483647)
The port index indicates the port number of a specific DS1 on the DS1 card in the slot. The port index of the first port is starting from 0 and increment by 1 for the next port on the DS1 card.
1.3.6.1.4.1.9.10.19.1.1.9.1.3
Gauge32
The number of DS0s that are currently in use for a particular DS1.
1.3.6.1.4.1.9.10.19.1.1.9.1.4
Counter32
The highest number of simultaneously actived DS0s on a specified DS1.
1.3.6.1.4.1.9.10.19.1.1.9.1.5
Counter32 · calls
The accumulated number of analog data calls (cpmDS0CallType has the value 'analog(3)') on all ds0s within this DS1 since system startup. The object includes active and terminated calls.
1.3.6.1.4.1.9.10.19.1.1.9.1.6
Counter32 · calls
The accumulated number of digital data calls (cpmDS0CallType has the value 'digital(4)') on all ds0s within this DS1 since system startup. The object includes active and terminated calls.
1.3.6.1.4.1.9.10.19.1.1.9.1.7
Counter32 · calls
The accumulated number of v.110 data calls (cpmDS0CallType has the value 'v110(5)') on all ds0s within this DS1 since system startup. The object includes active and terminated calls.
1.3.6.1.4.1.9.10.19.1.1.9.1.8
Counter32 · calls
The accumulated number of v.120 data calls (cpmDS0CallType has the value 'v120(6)') on all ds0s within this DS1 since system startup. The object includes active and terminated calls.
1.3.6.1.4.1.9.10.19.1.1.9.1.9
Counter32 · calls
The total number of calls on all the DS0s within this DS1 since last system re-initialization. The object includes active and terminated calls. This only includes DS0s configured as bearer channels, not those configured for signaling, such as PRI D-channel.
1.3.6.1.4.1.9.10.19.1.1.9.1.10
Unsigned32 · seconds
The total call duration on all the DS0s within this DS1 since last system re-initialization. This only includes DS0s configured as bearer channels, not those configured for signaling, such as PRI D-channel.
1.3.6.1.4.1.9.10.19.1.1.9.1.11
Gauge32
The total number of DS0s currently in idle state within this DS1. This only includes DS0s configured as bearer and CAS channels, not those configured for signaling, such as PRI D-channel. See cpmDS0OperStatus in the cpmDS0StatusTable for individual DS0s.
1.3.6.1.4.1.9.10.19.1.1.9.1.12
Gauge32
The total number of DS0s in this DS1 currently placed out of service. This only includes DS0s configured as bearer and CAS channels, not those configured for signaling, such as PRI D-channel. See cpmDS0OperStatus in the cpmDS0StatusTable for individual DS0s.
1.3.6.1.4.1.9.10.19.1.1.9.1.13
Gauge32
The total number of DS0s in this DS1 which currently have been requested to be busied out, but are not yet out of service. When an active call on a busied out DS0 terminates, the DS0 will be out of service, this object will be decremented and cpmDS1TotalOutOfService will be incremented. This only includes DS0s configured as bearer channels, not those configured for signaling, such as PRI D-channel. See cpmDS0AdminStatus in the cpmDS0StatusTable for individual DS0s.
1.3.6.1.4.1.9.10.19.1.1.9.1.14
Counter32 · octets
The total number of octets received over all the DS0 bearer channels within this DS1 since last system re-initialization. This value is a sum of all the cpmInOctets objects in the cpmDS0UsageTable for this DS1.
1.3.6.1.4.1.9.10.19.1.1.9.1.15
Counter32 · octets
The total number of octets transmitted over all the DS0 bearer channels within this DS1 since last system re-initialization. This value is a sum of all the cpmOutOctets objects in the cpmDS0UsageTable for this DS1.
1.3.6.1.4.1.9.10.19.1.1.9.1.16
Counter32 · packets
The total number of data packets received over all the DS0 bearer channels within this DS1 since last system re-initialization. This value is a sum of all the cpmInPackets objects in the cpmDS0UsageTable for this DS1. It consists of PPP or PCM voice data packets.
1.3.6.1.4.1.9.10.19.1.1.9.1.17
Counter32 · packets
The total number of data packets transmitted over all the DS0 bearer channels within this DS1 since last system re-initialization. This value is a sum of all the cpmOutPackets objects in the cpmDS0UsageTable for this DS1. It consists of PPP or PCM voice data packets.
1.3.6.1.4.1.9.10.19.1.3.1
Index: cpmActiveCallStartTimeIndex · cpmActiveCallSummaryIndex
The active call summary table is needed to track currently active calls. This table is needed because modem calls are not in CALL-HISTORY-MIB, and the DIAL-CONTROL_MIB is not yet available.
1.3.6.1.4.1.9.10.19.1.3.1.1.1
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The start time of the current call.
1.3.6.1.4.1.9.10.19.1.3.1.1.2
Integer32 (0..2147483647)
Arbitrary small integer to distinguish calls that occured at the same time tick.
1.3.6.1.4.1.9.10.19.1.3.1.1.3
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The User login ID or zero length string if unavailable.
1.3.6.1.4.1.9.10.19.1.3.1.1.4
IpAddress SIZE (4)
The IP address of the call or 0.0.0.0 if unavailable. This object comes directly from IOS.
1.3.6.1.4.1.9.10.19.1.3.1.1.5
INTEGER1 = unknown2 = analog3 = digital4 = v1105 = v1206 = voice · Integer32
The call type: unknown - None of the following analog - Modem call digital - Digital call v110 - V110 Call v120 - V120 Call voice - Voice Call
1.3.6.1.4.1.9.10.19.1.3.1.1.6
Integer32 (0..2147483647)
Identification of modem resource allocated to call. This is the value of cmSlotIndex from CISCO-MODEM-MGMT-MIB. This value along with cpmActiveModemPort uniquely identifies a modem. Value is -1 if call does not utilize a modem.
1.3.6.1.4.1.9.10.19.1.3.1.1.7
Integer32 (0..2147483647)
Identification of modem resource allocated to call. This is the value of cmPortIndex from CISCO-MODEM-MGMT-MIB. This value along with cpmActiveModemSlot uniquely identifies a modem. Value is -1 if call does not utilize a modem.
1.3.6.1.4.1.9.10.19.1.3.1.1.8
TimeTicks
The duration of the current call.
1.3.6.1.4.1.9.10.19.1.3.1.1.9
Integer32 (0..2147483647)
The logical slot in which the DS1 line that the user connected on resides.
1.3.6.1.4.1.9.10.19.1.3.1.1.10
Integer32 (0..2147483647)
The logical port for the DS1 line that the user connected on.
1.3.6.1.4.1.9.10.19.1.3.1.1.11
Integer32 (0..2147483647)
The channel within the DS1 that is allocated to the call.
1.3.6.1.4.1.9.10.19.1.3.1.1.12
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The remote telephone number. For a call into the device, this is the originating number. For a call out of the device, this is the dialed number. If not available the string length is zero.
1.3.6.1.4.1.9.10.19.1.3.1.1.13
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The local telephone number. For a call into the device, this is the dialed number. For a call out of the device, this is the originating number. If not available the string length is zero.
1.3.6.1.4.1.9.10.19.1.3.1.1.14
Integer32
The TTY number associated with this call. This information comes from the IOS 'show line' command.
1.3.6.1.4.1.9.10.19.1.4.3
Index: cpmCallDisconnectTimeIndex · cpmCallStartTimeIndex · cpmCallHistorySummaryIndex
The call history summary table is needed to track ended active calls. This table is needed because modem calls are not in CALL-HISTORY-MIB; the CISCO-ISDN-MIB objects do not contain information about the active calls; and the DIAL-CONTROL_MIB is not yet available.
1.3.6.1.4.1.9.10.19.1.4.3.1.1
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The disconnect time of the call.
1.3.6.1.4.1.9.10.19.1.4.3.1.2
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The start time of the current call.
1.3.6.1.4.1.9.10.19.1.4.3.1.3
Integer32 (0..2147483647)
Arbitrary small integer to distinguish calls that occured at the same time tick.
1.3.6.1.4.1.9.10.19.1.4.3.1.4
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The User login ID or zero length string if unavailable. This object comes directly from IOS.
1.3.6.1.4.1.9.10.19.1.4.3.1.5
IpAddress SIZE (4)
The IP address of the call or 0.0.0.0 if unavailable. This object comes directly from IOS.
1.3.6.1.4.1.9.10.19.1.4.3.1.6
INTEGER1 = unknown2 = analog3 = digital4 = v1105 = v1206 = voice · Integer32
The call type: unknown - None of the following analog - Modem call digital - Digital call v110 - V110 Call v120 - V120 Call voice - Voice Call
1.3.6.1.4.1.9.10.19.1.4.3.1.7
Integer32
Identification of modem resource allocated to call. This is the value of cmSlotIndex from CISCO-MODEM-MGMT-MIB. This value along with cpmModemPort uniquely identifies a modem. Value is -1 if call does not utilize a modem.
1.3.6.1.4.1.9.10.19.1.4.3.1.8
Integer32
Identification of modem resource allocated to call. This is the value of cmPortIndex from CISCO-MODEM-MGMT-MIB. This value along with cpmModemSlot uniquely identifies a modem. Value is -1 if call does not utilize a modem.
1.3.6.1.4.1.9.10.19.1.4.3.1.9
TimeTicks
The duration of the current call.
1.3.6.1.4.1.9.10.19.1.4.3.1.10
Integer32
The physical system slot in which the DS1 line that the user connected on resides.
1.3.6.1.4.1.9.10.19.1.4.3.1.11
Integer32
The logical port for the DS1 line that the user connected on.
1.3.6.1.4.1.9.10.19.1.4.3.1.12
Integer32
The channel within the DS1 that is allocated to the call.
1.3.6.1.4.1.9.10.19.1.4.3.1.13
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The remote telephone number. For a call into the device, this is the originating number. For a call out of the device, this is the dialed number. If not available the string length is zero.
1.3.6.1.4.1.9.10.19.1.4.3.1.14
DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a
The local telephone number. For a call into the device, this is the dialed number. For a call out of the device, this is the originating number. If not available the string length is zero.
1.3.6.1.4.1.9.10.19.1.4.3.1.15
Integer32
The TTY number associated with this call. This information comes from the IOS 'show line' command.
1.3.6.1.4.1.9.10.19.1.5.2
augments cpmDS0UsageTable
Index: cpmDS1SlotIndex · cpmDS1PortIndex · cpmChannelIndex
The DS0 Status Table provides additional DS0 level information and configuration. This table is an extension of the cpmDS0UsageTable.
1.3.6.1.4.1.9.10.19.1.5.2.1.1
INTEGER1 = unknown2 = down3 = idle4 = setup5 = connected6 = test · Integer32
The operational state of the DSO. This object provides more detailed information than the IF-MIB ifOperStatus. unknown - The DSO is in an unknown state down - The DS0 is out of service idle - This DS0 is currently idle setup - A new connection is in the process of being established connected - A active connection exists test - The DSO is undergoing internal testing
1.3.6.1.4.1.9.10.19.1.5.2.1.2
INTEGER1 = noBusyout2 = busyout3 = busyoutImmediate · Integer32
The administratively requested busyout state of the DSO. This object represents the desired busyout state of the DS0, which may or may not be reflected in the operation state, cpmDS0OperStatus. This object may be set via SNMP or the system console. noBusyout - No administrative busyout has been requested busyout - The DS0 will be shutdown when it next transitions to idle(2) cpmDS0OperStatus busyoutImmediate - Immediately transition the DS0 to down(2), terminating any current activity The effect of setting this object to busyout or busyoutImmediate is constrained by the value of cpmDS0BusyoutAllowed. If cpmDS0BusyoutAllowed has a value of false, attempting to set this object to busyout or busyoutImmediate will fail. This object provides more busyout information not available from the IF-MIB ifAdminStatus. This object reflects busyout requests configured on the local system as defined for the object cpmDS0BusyoutSource.
1.3.6.1.4.1.9.10.19.1.5.2.1.3
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
The object indicates if busyout requests for this DSO will be allowed. true - Setting cpmDS0BusyoutAdminStatus to busyout(2) or busyoutImmediate(3) will be accepted false - Busyout requests for this DS0 are not allowed The default value is true(1). If cpmDS0BusyoutAllowed has a value of false(2), attempting to set cpmDS0BusyoutAdminStatus to busyout or busyoutImmediate will fail. This object only constrains setting the value of cpmDS0BusyoutAdminStatus when cpmDS0BusyoutAdminStatus is set via SNMP.
1.3.6.1.4.1.9.10.19.1.5.2.1.4
INTEGER1 = noBusyout2 = busyoutPending3 = busiedOut · Integer32
The busyout status of the DSO. noBusyout - The DS0 is not busied out nor has a busyout pending. busyoutPending - The DS0 has a busyout request pending. It will shutdown when it next transitions to idle(2) cpmDS0OperStatus. busiedOut - The DS0 is out of service due to a busyout request. This object is needed to reflect busyouts initiated other than administrativly, as described in cpmDS0BusyoutSource.
1.3.6.1.4.1.9.10.19.1.5.2.1.5
INTEGER1 = none2 = local3 = internal4 = remote · Integer32
The source of the busyout request either pending or active for the DSO. none - The DS0 is not busied out nor has a busyout request pending local - The DS0 is busied out or has a pending request due to an adminstrative command issued locally. internal - The DS0 is busied out or has a pending request due to internal system processing. remote - The DS0 is busied out or has a pending request due to a request from the peer switch.
1.3.6.1.4.1.9.10.19.1.5.2.1.6
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
Value of sysUpTime when the most recent busyout request was issued for this DS0. The value is zero indicates no busyout request has been issued.
1.3.6.1.4.1.9.10.19.1.5.2.1.7
INTEGER1 = unknown2 = t1CcsSignallingChan3 = t1CcsBearerChan4 = e1CcsSignallingChan5 = e1CcsBearerChan6 = t1CasChan7 = e1CasChan · Integer32
The object indicates the function this DSO is configured to provide. This object provides more detail than cpmConfiguredType. unknown - Unknown configuration t1SignallingChan - DS0 is configured as a T1 common channel signalling (CCS) such as ISDN PRI D-channel t1CcsBearerChan - DS0 is configured as a T1 common channel signalling (CCS) bearer channel e1SignallingChan - DS0 is configured as a E1 common channel signalling (CCS) such as ISDN PRI D-channel e1CcsBearerChan - DS0 is configured as a E1 common channel signalling (CCS) bearer channel t1CasChan - DS0 is configured as a T1 channel associated signalling channel e1CasChan - DS0 is configured as a E1 channel associated signalling channel
1.3.6.1.4.1.9.10.19.1.5.2.1.8
InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d
This is the value of ifIndex in the ifTable for this DS0.
1.3.6.1.4.1.9.10.19.2.0.1
This notification is sent when there is a state change in cpmDS0BusyoutStatus object.
1.3.6.1.4.1.9.10.19.1.5.2.1.4
INTEGER1 = noBusyout2 = busyoutPending3 = busiedOut · Integer32
The busyout status of the DSO. noBusyout - The DS0 is not busied out nor has a busyout pending. busyoutPending - The DS0 has a busyout request pending. It will shutdown when it next transitions to idle(2) cpmDS0OperStatus. busiedOut - The DS0 is out of service due to a busyout request. This object is needed to reflect busyouts initiated other than administrativly, as described in cpmDS0BusyoutSource.
1.3.6.1.4.1.9.10.19.1.5.2.1.6
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
Value of sysUpTime when the most recent busyout request was issued for this DS0. The value is zero indicates no busyout request has been issued.
1.3.6.1.4.1.9.10.19.1.5.2.1.5
INTEGER1 = none2 = local3 = internal4 = remote · Integer32
The source of the busyout request either pending or active for the DSO. none - The DS0 is not busied out nor has a busyout request pending local - The DS0 is busied out or has a pending request due to an adminstrative command issued locally. internal - The DS0 is busied out or has a pending request due to internal system processing. remote - The DS0 is busied out or has a pending request due to a request from the peer switch.
1.3.6.1.4.1.9.10.19.1.5.2.1.8
InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d
This is the value of ifIndex in the ifTable for this DS0.
1.3.6.1.4.1.9.10.19.2.0.2
This notification is sent when there is a state change in dsx1LineStatus object of RFC1406-MIB.
1.3.6.1.2.1.10.18.6.1.10
INTEGER (1..131071) · Integer32
This variable indicates the Line Status of the interface. It contains loopback, failure, received 'alarm' and transmitted 'alarms information. The dsx1LineStatus is a bit map represented as a sum, therefore, it can represent multiple failures (alarms) and a LoopbackState simultaneously. dsx1NoAlarm must be set if and only if no other flag is set. If the dsx1loopbackState bit is set, the loopback in effect can be determined from the dsx1loopbackConfig object. The various bit positions are: 1 dsx1NoAlarm No alarm present 2 dsx1RcvFarEndLOF Far end LOF (a.k.a., Yellow Alarm) 4 dsx1XmtFarEndLOF Near end sending LOF Indication 8 dsx1RcvAIS Far end sending AIS 16 dsx1XmtAIS Near end sending AIS 32 dsx1LossOfFrame Near end LOF (a.k.a., Red Alarm) 64 dsx1LossOfSignal Near end Loss Of Signal 128 dsx1LoopbackState Near end is looped 256 dsx1T16AIS E1 TS16 AIS 512 dsx1RcvFarEndLOMF Far End Sending TS16 LOMF 1024 dsx1XmtFarEndLOMF Near End Sending TS16 LOMF 2048 dsx1RcvTestCode Near End detects a test code 4096 dsx1OtherFailure any line status not defined here 8192 dsx1UnavailSigState Near End in Unavailable Signal State 16384 dsx1NetEquipOOS Carrier Equipment Out of Service 32768 dsx1RcvPayloadAIS DS2 Payload AIS 65536 dsx1Ds2PerfThreshold DS2 Performance Threshold Exceeded
1.3.6.1.2.1.10.18.6.1.1
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
This object should be made equal to ifIndex. The next paragraph describes its previous usage. Making the object equal to ifIndex allows proper use of ifStackTable and ds0/ds0bundle mibs. Previously, this object is the identifier of a DS1 Interface on a managed device. If there is an ifEntry that is directly associated with this and only this DS1 interface, it should have the same value as ifIndex. Otherwise, number the dsx1LineIndices with an unique identifier following the rules of choosing a number that is greater than ifNumber and numbering the inside interfaces (e.g., equipment side) with even numbers and outside interfaces (e.g, network side) with odd numbers.