Timestamp generation MAY be used in one of the following
modes:
1. Absolute mode: the PSN-bound IWF sets timestamps
using the clock recovered from the incoming TDM attachment
circuit. As a consequence, the timestamps are closely
correlated with the sequence numbers. All TDM
implementations that support usage of the RTP header MUST
support this mode.
2. Differential mode: Both IWFs have access to a common
high-quality timing source, and this source is used for
timestamp generation. Support of this mode is OPTIONAL.
Parsed from file CISCO-IETF-PW-TDM-MIB.mib
Module: CISCO-IETF-PW-TDM-MIB
Timestamp generation MAY be used in one of the following
modes:
1. Absolute mode: the PSN-bound IWF sets timestamps
using the clock recovered from the incoming TDM attachment
circuit. As a consequence, the timestamps are closely
correlated with the sequence numbers. All TDM
implementations that support usage of the RTP header MUST
support this mode.
2. Differential mode: Both IWFs have access to a common
high-quality timing source, and this source is used for
timestamp generation. Support of this mode is OPTIONAL.
Timestamp generation MAY be used in one of the following
modes:
1. Absolute mode: the PSN-bound IWF sets timestamps
using the clock recovered from the incoming TDM attachment
circuit. As a consequence, the timestamps are closely
correlated with the sequence numbers. All TDM
implementations that support usage of the RTP header MUST
support this mode.
2. Differential mode: Both IWFs have access to a common
high-quality timing source, and this source is used for
timestamp generation. Support of this mode is OPTIONAL.
Parsed from file CISCO-IETF-PW-TDM-MIB.my.txt
Company: None
Module: CISCO-IETF-PW-TDM-MIB
Timestamp generation MAY be used in one of the following
modes:
1. Absolute mode: the PSN-bound IWF sets timestamps
using the clock recovered from the incoming TDM attachment
circuit. As a consequence, the timestamps are closely
correlated with the sequence numbers. All TDM
implementations that support usage of the RTP header MUST
support this mode.
2. Differential mode: Both IWFs have access to a common
high-quality timing source, and this source is used for
timestamp generation. Support of this mode is OPTIONAL.
cpwCTDMCfgTimestampMode OBJECT-TYPE SYNTAX INTEGER { notApplicable(1), absolute(2), differential(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "Timestamp generation MAY be used in one of the following modes: 1. Absolute mode: the PSN-bound IWF sets timestamps using the clock recovered from the incoming TDM attachment circuit. As a consequence, the timestamps are closely correlated with the sequence numbers. All TDM implementations that support usage of the RTP header MUST support this mode. 2. Differential mode: Both IWFs have access to a common high-quality timing source, and this source is used for timestamp generation. Support of this mode is OPTIONAL." DEFVAL { absolute } ::= { cpwCTDMCfgEntry 17 }
cpwCTDMCfgTimestampMode OBJECT-TYPE SYNTAX INTEGER { notApplicable(1), absolute(2), differential(3) } ACCESS read-write STATUS mandatory DESCRIPTION "Timestamp generation MAY be used in one of the following modes: 1. Absolute mode: the PSN-bound IWF sets timestamps using the clock recovered from the incoming TDM attachment circuit. As a consequence, the timestamps are closely correlated with the sequence numbers. All TDM implementations that support usage of the RTP header MUST support this mode. 2. Differential mode: Both IWFs have access to a common high-quality timing source, and this source is used for timestamp generation. Support of this mode is OPTIONAL." DEFVAL { absolute } ::= { cpwCTDMCfgEntry 17 }
Vendor: Cisco
Module: CISCO-IETF-PW-TDM-MIB
[Automatically extracted from oidview.com]
cpwCTDMCfgTimestampMode OBJECT-TYPE SYNTAX INTEGER { notApplicable(1), absolute(2), differential(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "Timestamp generation MAY be used in one of the following modes: 1. Absolute mode: the PSN-bound IWF sets timestamps using the clock recovered from the incoming TDM attachment circuit. As a consequence, the timestamps are closely correlated with the sequence numbers. All TDM implementations that support usage of the RTP header MUST support this mode. 2. Differential mode: Both IWFs have access to a common high-quality timing source, and this source is used for timestamp generation. Support of this mode is OPTIONAL." DEFVAL { absolute } ::= { cpwCTDMCfgEntry 17 }
cpwCTDMCfgTimestampMode OBJECT-TYPE SYNTAX INTEGER { notApplicable(1), absolute(2), differential(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "Timestamp generation MAY be used in one of the following modes: 1. Absolute mode: the PSN-bound IWF sets timestamps using the clock recovered from the incoming TDM attachment circuit. As a consequence, the timestamps are closely correlated with the sequence numbers. All TDM implementations that support usage of the RTP header MUST support this mode. 2. Differential mode: Both IWFs have access to a common high-quality timing source, and this source is used for timestamp generation. Support of this mode is OPTIONAL." DEFVAL { absolute } ::= { cpwCTDMCfgEntry 17 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.10.131.1.3.1.1 | cpwCTDMCfgIndex | 0 | 0 | Index to an entry in this table. The value is a copy of the assigned cpwCTDMCfgIndexNext. |
| 1.3.6.1.4.1.9.10.131.1.3.1.2 | cpwCTDMCfgConfErr | 0 | 0 | This object indicates the various configuration errors, illegal settings within the cpwCTDMCfg table. The errors can be due to se… |
| 1.3.6.1.4.1.9.10.131.1.3.1.3 | cpwCTDMCfgPayloadSize | 0 | 0 | The value of this object indicates the PayLoad Size (in bytes) to be defined during the PW setUp. Upon TX, implementation must be… |
| 1.3.6.1.4.1.9.10.131.1.3.1.4 | cpwCTDMCfgPktReorder | 0 | 0 | If set to true, CE bound packets are queued in the jitter buffer, out of order packets are re-ordered. The maximum sequence numbe… |
| 1.3.6.1.4.1.9.10.131.1.3.1.5 | cpwCTDMCfgRtpHdrUsed | 0 | 0 | If the value of this object is set to false, then a RTP header is not pre-pended to the TDM packet. |
| 1.3.6.1.4.1.9.10.131.1.3.1.6 | cpwCTDMCfgJtrBfrDepth | 0 | 0 | The size of this buffer SHOULD be locally configured to allow accommodation to the PSN-specific packet delay variation. If configu… |
| 1.3.6.1.4.1.9.10.131.1.3.1.7 | cpwCTDMCfgPayloadSuppression | 0 | 0 | This object indicates whether the Payload suppression is eanbled or disabled. Payload MAY be omitted in order to conserve bandwid… |
| 1.3.6.1.4.1.9.10.131.1.3.1.8 | cpwCTDMCfgConsecPktsInSynch | 0 | 0 | The number of consecutive packets with sequential sequence numbers that are required to exit the Loss of Packets (LOPS) state. |
| 1.3.6.1.4.1.9.10.131.1.3.1.9 | cpwCTDMCfgConsecMissPktsOutSynch | 0 | 0 | The number of consecutive missing packets that are required to enter the LOPS state. |
| 1.3.6.1.4.1.9.10.131.1.3.1.10 | cpwCTDMCfgSetUp2SynchTimeOut | 0 | 0 | cpwCTDMCfgSetUp2SynchtimeOut |
| 1.3.6.1.4.1.9.10.131.1.3.1.11 | cpwCTDMCfgPktReplacePolicy | 0 | 0 | This parameter determines the value to be played when CE bound packets have over/underflow the jitter buffer, or are missing for … |
| 1.3.6.1.4.1.9.10.131.1.3.1.12 | cpwCTDMCfgAvePktLossTimeWindow | 0 | 0 | The length of time over which the average packet loss rate should be computed to detect Excessive packet loss rate |
| 1.3.6.1.4.1.9.10.131.1.3.1.13 | cpwCTDMCfgExcessivePktLossThreshold | 0 | 0 | Excessive packet loss rate is detected by computing the average packetloss rate over a cpwCTDMCfgAvePktLossTimeWindow amount of t… |
| 1.3.6.1.4.1.9.10.131.1.3.1.14 | cpwCTDMCfgAlarmThreshold | 0 | 0 | Alarms are only reported when the defect state persists for the length of time specified by this object. The object's unit is mil… |
| 1.3.6.1.4.1.9.10.131.1.3.1.15 | cpwCTDMCfgClearAlarmThreshold | 0 | 0 | Alarm MUST be cleared after the corresponding defect is undetected for the amount of time specified by this object. The object's … |
| 1.3.6.1.4.1.9.10.131.1.3.1.16 | cpwCTDMCfgMissingPktsToSes | 0 | 0 | Number of missing packets detected (consecutive or not) within a 1 second window to cause a Severely Error Second (SES) to be cou… |
| 1.3.6.1.4.1.9.10.131.1.3.1.18 | cpwCTDMCfgStorageType | 0 | 0 | This variable indicates the storage type for this row. The following are the read-write objects in permanent(4) rows, that an age… |
| 1.3.6.1.4.1.9.10.131.1.3.1.19 | cpwCTDMCfgRowStatus | 0 | 0 | The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or creat… |