CISCO-CALL-TRACKER-MIB

CctCallIdRepresents a Call Identifier. The call identifier is a monotonically assigned, positive integer which uniquely identifies the call within the system. (1..4294967295) · Unsigned32

Represents a Call Identifier. The call identifier is a monotonically increasing unsigned integer which uniquely identifies the call within the system. The Call ID is represented as an unsigned 32-bit integer. After 4,294,967,295 calls, the ID will wrap and the 4,294,967,296th call will receive the next smallest available id starting from 1. Zero is not a valid value.

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 call is first made known to the system.

INTEGER1 = originate2 = answer · Integer32

This object indicates how the call was created. originate(1) - The call was initiated locally with the system sending the setup request. Dialout answer(2) - The call was initiated remotely and the system received the setup request. Dialin

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 system connected the call.

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 physical layer for the call achieved a steady state and the call is ready for higher protocol layers to begin. In the case of modem calls, the physical layer for the call achieves a steady state when the data rates, modulations, and error correcting protocols have been negotiated between the originating and answering modems. This is primarily intended for calls which connect to a processing resource identified by cctActiveResourceSlot and cctActiveResourcePort. It also applies to digital calls using adaptive rate technologies such as V.110 and V.120.

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 call service type identified in cctActiveServiceType was established.

CctServiceType1 = none2 = other3 = slip4 = ppp5 = mp6 = tcpClear7 = telnet8 = exec9 = l2f10 = l2tpRepresents possible service types. none - No service associated with call. other - Service active, but none of the following. slip - Serial Line IP ppp - PPP mp - Multilink PPP (RFC 1990) tcpClear - Byte stream over TCP telnet - TELNET exec - terminal server l2f - Virtual Private Data Network service (VPDN) using Layer 2 Forwarding protocol l2tp - Virtual Private Data Network service (VPDN) using Layer 2 Tunneling Protocol · Integer32

Service associated with the call. This is the highest level of service known to the system for the call. The service represents the encapsulation protocol layer active for the call. In the case of multiple services on a given call, the last service activated will be reported.

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 user identification associated with this call was validated. See cctActiveUserId for description of user identification.

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.

IpAddress SIZE (4)

The IP address assigned to the cctActiveUserId for this call or 0.0.0.0 if not applicable or unavailable.

IpAddress SIZE (4)

The IP subnet mask assigned to the cctActiveUserId for this call or 0.0.0.0 if not applicable or unavailable.

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

Accounting session identification assigned to this call by AAA. The session ID is sent by AAA to RADIUS as the Acct-Session-Id attribute or TACACS+ as the task_id. If no accounting session ID is assigned, the value is a null string. ⓘ

CctCallCategory1 = none2 = other3 = modem4 = isdnSync5 = v1106 = v1207 = casDigital8 = mgcpData9 = syncData10 = lapb-taRepresents possible call categories or types. none - No call category associated with call other - None of the following modem - Modem call isdn-sync - ISDN sync digital call Now mapped to syncData v110 - V110 Call v120 - V120 Call cas-digital - Channel Associated Signaling (CAS) 56k data call mgcpData - MGCP data call Now mapped to syncData syncData - Sync digital data call for any call control lapb-ta - LAPB or LAPB-TA call · Integer32

The call category or type

Unsigned32 · bits per second

Initial receive data rate for this call. If call is a synchronous digital call such as ISDN sync, this value is the data rate of the B-channel. If call is asynchronous, even if using a synchronous transmission medium such as ISDN, the value is determined by the resource providing the asynchronous processing. For modem calls, this value corresponds to the value of cmRXRate from CISCO-MODEM-MGMT-MIB, immediately after the modem has completed initial negotiations. This value does not change, even if the data rate varies during the call. This value will be zero until an initial data rate has been determined.

Unsigned32 · bits per second

Initial transmit data rate for this call. If call is a synchronous digital call such as ISDN sync, this value is the data rate of the B-channel. If call is asynchronous, even if using a synchronous transmission medium such as ISDN, the value is determined by the resource providing the asynchronous processing. For modem calls, this value corresponds to the value of cmTXRate from CISCO-MODEM-MGMT-MIB, immediately after the modem has completed initial negotiations. This value does not change, even if the data rate varies during the call. This value will be zero until an initial data rate has been determined.

Integer32 (-1..214783647)

Identification of the processing resource allocated to the call. In the case of a call requiring a modem resource, this is the value of cmSlotIndex from CISCO-MODEM-MGMT-MIB. This value along with cctActiveResourcePort uniquely identifies a resource port. Value is -1 if call does not utilize such a resource.

Integer32 (-1..214783647)

Identification of the processing resource allocated to the call. In the case of a call requiring a modem resource, this is the value of cmPortIndex from CISCO-MODEM-MGMT-MIB. This value along with cctActiveResourceSlot uniquely identifies a resource port. Value is -1 if call does not utilize such a resource.

Integer32 (0..214783647)

The device slot containing the port on which the call exists.

Integer32 (0..214783647)

The physical port within the device slot on which the call exists.

Integer32 (0..214783647)

The DS1 link containing the call. This may be a DS1 contained within a larger grouping of multiple DS1s within a single physical port. If the physical port is of type DS1, this value is identical to cctActiveEntryPort. If the DS1 is a logical subinterface within the physical port, this value is the number of the DS1 within this slot. Examples: 8 port DS1 card - cctActiveEntryPort and cctActiveEntryDs1 will have identical values. 3 port T3 card - cctActiveEntryPort represents T3 ports. cctActiveEntryEntryDs1 represents logical T1 interfaces. Each T3 contains 28 T1 interfaces. The T1 interfaces are numbered sequentially across the entire T3 card.

Integer32 (0..214783647)

The channel or timeslot within the cctActiveEntryDs1 allocated to the call.

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..64) · OCTET STRING · hint 255a

The called telephone number for this call. For calls answered by the system, this corresponds to the Dialed Number Identification (DNIS). For calls originated by the system, this is the destination number. If not available this is a zero-length string.

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..64) · OCTET STRING · hint 255a

The calling telephone number for this call. For calls answered by the system, this corresponds to the calling identification (CLID). For calls originated by the system, this is the number associated with the device. For the interworking call, this object contains the translated calling party number if there is a translation rule is associated with dial plan for making this outgoing call. If not available this is a zero-length string.

Unsigned32

Multilink PPP bundle identification for call if cctActiveServiceType has the value 'mp'. If the value of cctActiveServiceType for this call is not 'mp', then the value of this object is not meaningful.

AbsoluteCounter32Represents a Counter32-like value that starts at zero, does not decrease, and does not wrap. This may be used only in situations where wrapping is not possible or extremely unlikely. Should such a counter overflow, it locks at the maxium value of 4,294,967,295. The primary use of this type of counter is situations where a counter value is to be recorded as history and is thus no longer subject to reading for changing values. · Unsigned32

The number of charged units for this connection. For incoming calls or if charging information is not supplied by the switch, the value of this object will be zero. ⓘ

AbsoluteCounter32Represents a Counter32-like value that starts at zero, does not decrease, and does not wrap. This may be used only in situations where wrapping is not possible or extremely unlikely. Should such a counter overflow, it locks at the maxium value of 4,294,967,295. The primary use of this type of counter is situations where a counter value is to be recorded as history and is thus no longer subject to reading for changing values. · Unsigned32 · bytes

The number of bytes received on the call. All the 'raw' bytes are counted including any protocol headers which may or may not be present depending on the value of cctActiveServiceType.

AbsoluteCounter32Represents a Counter32-like value that starts at zero, does not decrease, and does not wrap. This may be used only in situations where wrapping is not possible or extremely unlikely. Should such a counter overflow, it locks at the maxium value of 4,294,967,295. The primary use of this type of counter is situations where a counter value is to be recorded as history and is thus no longer subject to reading for changing values. · Unsigned32 · bytes

The number of bytes transmitted on the call. All the 'raw' bytes are counted including any protocol headers which may or may not be present depending on the value of cctActiveServiceType.

CctCallSigType1 = unknown2 = external3 = q9314 = autoDetectRepresents supported signaling types for a call. Unknown - Signaling origin of call type unknown. External - Signaling origin of call type by external agent e.g. MGCP, H.248 Q931 - Signaling origin of call type by Q.931/ISDN Autodetect - Signaling of call type by automatic detection · Integer32

Signaling type used to setup the call.

Unsigned32 (1..4294967295)

A monotonically increasing integer for the sole purpose of indexing terminated calls. When it reaches the maximum value the agent wraps the value back to 1 and will flush existing entries.

CctCallIdRepresents a Call Identifier. The call identifier is a monotonically assigned, positive integer which uniquely identifies the call within the system. (1..4294967295) · Unsigned32

The call identifier for the call. This is the same value assigned to the call in cctActiveCallId when it was in the cctActiveTable. It is possible for two cctHistoryEntry entries to have the same cctHistoryCallId if one very long running call terminates after the cctActiveCallId has wrapped around and is reassigned to a new short lived call.

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 call was first made known to the system.

INTEGER1 = originate2 = answer · Integer32

This object indicates how the call was created. originate(1) - The call was initiated locally with the system sending the setup request. Dialout answer(2) - The call was initiated remotely and the system received the setup request. Dialin

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 system connected the call.

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 physical layer for the call achieved a steady state and the call is ready for higher protocol layers to begin. In the case of modem calls, the physical layer for the call achieves a steady state when the data rates, modulations, and error correcting protocols have been negotiated between the originating and answering modems. This is primarily intended for calls which connect to a processing resource identified by cctHistoryResourceSlot and cctHistoryResourcePort. It also applies to digital calls using adaptive rate technologies such as V.110 and V.120.

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 call service type identified in cctHistoryServiceType was established.

CctServiceType1 = none2 = other3 = slip4 = ppp5 = mp6 = tcpClear7 = telnet8 = exec9 = l2f10 = l2tpRepresents possible service types. none - No service associated with call. other - Service active, but none of the following. slip - Serial Line IP ppp - PPP mp - Multilink PPP (RFC 1990) tcpClear - Byte stream over TCP telnet - TELNET exec - terminal server l2f - Virtual Private Data Network service (VPDN) using Layer 2 Forwarding protocol l2tp - Virtual Private Data Network service (VPDN) using Layer 2 Tunneling Protocol · Integer32

Service associated with the call. This is the highest level of service known to the system for the call. The service represents the encapsulation protocol layer active for the call. In the case of multiple services on a given call, the last service activated will be reported.

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 user identification associated with this call was validated. See cctHistoryUserId for description of user identification.

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. If this contains a non-zero length string, and cctHistoryUserValidationTime is zero, then the user failed validation.

IpAddress SIZE (4)

The IP address assigned to the cctHistoryUserId for this call or 0.0.0.0 if not applicable or unavailable.

IpAddress SIZE (4)

The IP subnet mask assigned to the cctHistoryUserId for this call or 0.0.0.0 if not applicable or unavailable.

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

Accounting session identification assigned to this call by AAA. The session ID is sent by AAA to RADIUS as the Acct-Session-Id attribute or TACACS+ as the task_id. If no accounting session ID is assigned, the value is a null string. ⓘ

CctCallCategory1 = none2 = other3 = modem4 = isdnSync5 = v1106 = v1207 = casDigital8 = mgcpData9 = syncData10 = lapb-taRepresents possible call categories or types. none - No call category associated with call other - None of the following modem - Modem call isdn-sync - ISDN sync digital call Now mapped to syncData v110 - V110 Call v120 - V120 Call cas-digital - Channel Associated Signaling (CAS) 56k data call mgcpData - MGCP data call Now mapped to syncData syncData - Sync digital data call for any call control lapb-ta - LAPB or LAPB-TA call · Integer32

The call category or type

Unsigned32 · bits per second

Initial receive data rate for this call. If call is a synchronous digital call such as ISDN sync, this value is the data rate of the B-channel. If call is asynchronous, even if using a synchronous transmission medium such as ISDN, the value is determined by the resource providing the asynchronous processing. For modem calls, this value corresponds to the value of cmRXRate from CISCO-MODEM-MGMT-MIB, immediately after the modem has completed initial negotiations. This value does not change, even if the data rate varies during the call. This value will be zero if the call terminated prior to an initial data rate determination.

Unsigned32 · bits per second

Initial transmit data rate for this call. If call is a synchronous digital call such as ISDN sync, this value is the data rate of the B-channel. If call is asynchronous, even if using a synchronous transmission medium such as ISDN, the value is determined by the resource providing the asynchronous processing. For modem calls, this value corresponds to the value of cmTXRate from CISCO-MODEM-MGMT-MIB, immediately after the modem has completed initial negotiations. This value does not change, even if the data rate varies during the call. This value will be zero if the call terminated prior to an initial data rate determination.

Integer32 (-1..214783647)

Identification of processing resource allocated to call. In the case of a call requiring a modem resource, this is the value of cmSlotIndex from CISCO-MODEM-MGMT-MIB. This value along with cctHistoryResourcePort uniquely identifies a resource port. Value is -1 if call does not utilize such a resource.

Integer32 (-1..214783647)

Identification of processing resource allocated to call. In the case of a call requiring a modem resource, this is the value of cmPortIndex from CISCO-MODEM-MGMT-MIB. This value along with cctHistoryResourceSlot uniquely identifies a resource port. Value is -1 if call does not utilize such a resource.

Integer32 (0..214783647)

The device slot containing the port on which the call existed.

Integer32 (0..214783647)

The physical port within the device slot on which the call existed.

Integer32 (0..214783647)

The DS1 link containing the call. This may be a DS1 contained within a larger grouping of multiple DS1s within a single physical port. If the physical port is of type DS1, this value is identical to cctActiveEntryPort. If the DS1 is a logical subinterface within the physical port, this value is the number of the DS1 within this slot. Examples: 8 port DS1 card - cctActiveEntryPort and cctActiveEntryDs1 will have identical values. 3 port T3 card - cctActiveEntryPort represents T3 ports. cctActiveEntryEntryDs1 represents logical T1 interfaces. Each T3 contains 28 T1 interfaces. The T1 interfaces are numbered sequentially across the entire T3 card.

Integer32 (0..214783647)

The channel or timeslot within the cctHistoryEntryDs1 which was allocated to the call.

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..64) · OCTET STRING · hint 255a

The called telephone number for this call. For calls answered by the system, this corresponds to the Dialed Number Identification (DNIS). For calls originated by the system, this is the destination number. If not available the string length is zero.

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..64) · OCTET STRING · hint 255a

The calling telephone number for this call. For calls answered by the system, this corresponds to the calling identification (CLID). For calls originated by the system, this is the number associated with the device. For the interworking call, this object contains the translated calling party number if there is a translation rule is associated with dial plan for making this outgoing call. If not available this is a zero-length string.

Unsigned32

Multilink PPP bundle identification for call if cctHistoryServiceType has the value 'mp'. If the value of cctHistoryServiceType for this call is not 'mp', then the value of this object is not meaningful.

Gauge32

The number of charged units for this connection. For incoming calls or if charging information is not supplied by the switch, the value of this object will be zero. ⓘ

Gauge32 · bytes

The number of bytes received on the call. All the 'raw' bytes are counted including any protocol headers which may or may not be present depending on the value of cctHistoryServiceType.

Gauge32 · bytes

The number of bytes transmitted on the call. All the 'raw' bytes are counted including any protocol headers which may or may not be present depending on the value of cctHistoryServiceType.

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 call was disconnected. This is when the system initiates, detects, or is notified of call termination. This is the call duration from initial setup request.

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

Text description of the disconnect reason provided. Value is zero-length string if no text is available.

CctCallSigType1 = unknown2 = external3 = q9314 = autoDetectRepresents supported signaling types for a call. Unknown - Signaling origin of call type unknown. External - Signaling origin of call type by external agent e.g. MGCP, H.248 Q931 - Signaling origin of call type by Q.931/ISDN Autodetect - Signaling of call type by automatic detection · Integer32

Signaling type used to setup the call.