cCallHistorySetupTime
CISCO-DIAL-CONTROL-MIB ·
.1.3.6.1.4.1.9.10.25.1.4.3.1.2
Object
The value of sysUpTime when the call setup was started. This will be useful for an NMS to sort the call history entry with call setup time. Also, this object can be useful in finding large delays between the time the call was started and the time the call was connected. For ISDN media, this will be the time when the setup message was received from or sent to the network. The value of this object is the same as callActiveSetupTime in the callActiveTable
Context
- MIB
- CISCO-DIAL-CONTROL-MIB
- OID
.1.3.6.1.4.1.9.10.25.1.4.3.1.2- Type
- column
- Access
- readonly
- Status
- current
- Parent
- cCallHistoryEntry
- Groups
- 3
Net-SNMP examples
How SNMP and these commands workWalk the column to discover its indexed instances, or supply every index to read one instance.
Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-DIAL-CONTROL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-DIAL-CONTROL-MIB::cCallHistorySetupTime'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'CISCO-DIAL-CONTROL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-DIAL-CONTROL-MIB::cCallHistorySetupTime.<cCallHistoryIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-DIAL-CONTROL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-DIAL-CONTROL-MIB::cCallHistorySetupTime'
Syntax
- Source
- SNMPv2-TCTimeStamp
- Base type
Unsigned32- Based on
- SNMPv2-SMITimeTicks
Type Description
The 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.
Values & Constraints
No enumerated values or constraints recorded.