This table is indexed by the same index that was
created for the associated entry in the VC Table
(in the CISCO-IETF-PW-MIB).
- The CpwVcIndex.
An entry is created in this table by the agent for every
entry in the cpwVcTable with a cpwVcType equal to one of the
following:
e1Satop(12), t1Satop(13), e3Satop(14), t3Satop(15),
basicCesPsn(16), basicTdmIp(17), tdmCasCesPsn(18),
tdmCasTdmIp(19).

The parameter represents the bit-rate of the TDM service
in multiples of the 'basic' 64 Kbit/s rate. It complements
the definition of cpwVcType used in CISCO-IETF-PW-MIB.
For structure-agnostic the following should be used:
a) Satop E1 - 32
b) Satop T1 emulation:
i) MUST be set to 24 in the basic emulation mode
ii) MUST be set to 25 for the 'Octet-aligned T1'
emulation mode
c) Satop E3 - 535
d) Satop T3 - 699
For all kinds of structure-aware emulation, this parameter
MUST be set to N where N is the number of DS0 channels
in the corresponding attachment circuit.

This is a unique index within the ifTable. It represents
the interface index of the full link or the interface
index for the bundle holding the group of
time slots to be transmitted via this PW connection.
A value of zero indicates an interface index that has yet
to be determined.
Once set, if the TDM ifIndex is (for some reason) later
removed, the agent SHOULD delete the associated PW rows
(e.g., this cpwCTDMTable entry). If the agent does not
delete the rows, the agent MUST set this object to
zero.

Index to the relevant TDM configuration table entry
that appears in one of the related MIB modules
such as TDMoIP or CESoPSN. It is likely that
multiple TDM PWs of the same characteristic will share
a single configuration entry of the relevant type.
The value 0 implies no entry in other related MIB

Any of the bits are set if the local configuration is
not compatible with the peer configuration as available
from the various parameters options.
-tdmTypeIncompatible bit is set if the local configuration
is not carrying the same TDM type as the peer configuration.
-peerRtpIncompatible bit is set if the local configuration
is configured to send RTP packets for this PW, and the
remote is not capable of accepting RTP packets.
-peerPayloadSizeIncompatible bit is set if the local
configuration is not carrying the same Payload Size as the
peer configuration.

The number of seconds, including partial seconds,
that have elapsed since the beginning of the current
measurement period. If, for some reason, such as an
adjustment in the system's time-of-day clock, the
current interval exceeds the maximum value, the
agent will return the maximum value.

The number of previous 15-minute intervals for which data
was collected.
An agent with TDM capability must be capable of supporting
at least n intervals. The minimum value of n is 4, The
default of n is 32 and the maximum value of n is 96.
The value will be unless the measurement was (re-)
started within the last (*15) minutes, in which case
the value will be the number of complete 15 minute
intervals for which the agent has at least some data.
In certain cases(e.g., in the case where the agent is
a proxy) it is possible that some intervals are unavailable.
In this case, this interval is the maximum interval number
for which data is available.

The number of previous days for which data
was collected.
An agent with TDM capability must be capable of supporting
at least n intervals. The minimum value of n is 1, The
default of n is 1 and the maximum value of n is 30.

The following defects should be detected and reported
upon request:
-Stray packets MAY be detected by the PSN and multiplexing
layers. Stray packets MUST be discarded by the CE-bound IWF
and their detection MUST NOT affect mechanisms for
detection of packet loss.
-Malformed packets are detected by mismatch between the
expected packet size (taking the value of the L bit into
account) and the actual packet size inferred from the PSN
and multiplexing layers. Malformed in-order packets MUST be
discarded by the CE-bound IWF and replacement data
generated as for lost packets.
-Excessive packet loss rate is detected by computing the
average packet loss rate over the value of
cpwCTDMAvePktLossTimeWindow and comparing it with a
preconfigured threshold [SATOP].
-Buffer overrun is detected in the normal operation state
when the CE bound IWF's jitter buffer cannot accommodate
newly arrived packets.
-Remote packet loss is indicated by reception of packets
with their R bit set.
-Packet misorder is detected by looking at the Sequence
number provided by the control word.
-TDM Fault, if L bit in the control word is set, it
indicates that TDM data carried in the payload is invalid
due an attachment circuit fault. When the L bit is set the
payload MAY be omitted in order to conserve bandwidth.
Note: the algorithm used to capture these indications
is implementation specific.

The state of TDM indicators when the TDM PW last declared
an error second (either as ES, SES or a second with
errors inside a UAS) condition. At this time, only LOPS
can create a failure. Since indicators other than LOPS are
useful, all are latched here. For bit definitions, see
cpwCTDMCurrentIndications above.
Note: the algorithm used to latch these indications when
entering a defect state is implementation specific.

This object contains the value to be used for
cpwCTDMCfgIndex when creating entries in the
cpwCTDMCfgTable. The value 0 indicates that no
unassigned entries are available. To obtain the
value of cpwCTDMCfgIndexNext for a new entry in the
cpwCTDMCfgTable, the manager issues a management
protocol retrieval operation. The agent will
determine through its local policy when this
index value will be made available for reuse.

This object indicates the various configuration errors,
illegal settings within the cpwCTDMCfg table. The errors
can be due to several reasons, like Payload size mismatch
or Jitter Buffer depth value mistmatch.
payloadSize - This bit is set if there is Payload size
mismatch between the local and peer
configurations.
jtrBfrDepth - This bit is set if there is Jitter Buffer
depth value mistmatch.
other - This bit is set if the error is not due to
payloadSize and jtrBfrDepth mismatch.

The value of this object indicates the PayLoad Size (in
bytes) to be defined during the PW setUp. Upon TX,
implementation must be capable of carrying that amount of
bytes. Upon RX, when the LEN field is set to 0, the
payload of packet MUST assume this size, and if the actual
packet size is inconsistent with this length,
the packet MUST be considered to be malformed.

If set to true, CE bound packets are queued in the
jitter buffer, out of order packets are re-ordered. The
maximum sequence number differential (i.e., the range in
which re-sequencing can occur) is dependant on the depth
of the jitter buffer. See cpwCTDMCfgJtrBfrDepth.

The size of this buffer SHOULD be locally
configured to allow accommodation to the PSN-specific
packet delay variation.
If configured to a value not supported by the
implementation, the agent MUST return an error code
'jtrBfrDepth' in 'cpwCTDMConfigError '.
Jitter buffers are a limited resource to be managed.
The actual size should be at least twice as big as the
value of cpwCTDMCfgJtrBfrDepth

This object indicates whether the Payload suppression
is eanbled or disabled.
Payload MAY be omitted in order to conserve bandwidth.
enable - Payload suppression is allowed.
disable - No Payload suppresion under any condition.

The amount of time the host should wait before declaring
the pseudo wire in down state, if the number of consecutive
TDM packets that have been received after changing the
administrative status to up and after finalization of
signaling (if supported) between the two PEs is smaller
than cpwCTDMCfgConsecPktsInSynch. Once the the PW has
OperStatus of 'up' this parameter is no longer valid. This
parameter is defined to ensure that the host does not
prematurely inform failure of the PW. In particular PW
'down' notifications should not be sent before expiration of
this timer. This parameter is valid only after adminisrative
changes of the status of the PW. If the PW fails due to
network impairments a 'down' notification should be sent.

This parameter determines the value to be played when CE
bound packets have over/underflow the jitter buffer, or are
missing for any reason. This AIS (Alarm Indication Signal)
pattern is sent (played) on the TDM line.
ais - AIS (Alarm Indication Signal)
pattern is sent (played) on
the TDM line.
implementationSpecific - Implementation specific pattern is
sent on the TDM line.

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.

This variable indicates the storage type for this row.
The following are the read-write objects in permanent(4)
rows, that an agent must allow to be writable:
cpwCTDMCfgPayloadSize, cpwCTDMCfgPktReorder,
cpwCTDMCfgRtpHdrUsed, cpwCTDMCfgJtrBfrDepth,
cpwCTDMCfgPayloadSuppression, cpwCTDMCfgConfErr.

The status of this conceptual row.
To create a row in this table, a manager must
set this object to either createAndGo(4) or
createAndWait(5).
All of the columnar objects have to be set to
valid values before the row can be activated.
Default value will be automatically provisioned
if for those objects not specified during row
creation.
No objects in cascading tables have to be populated with
related data before the row can be activated.
The following objects cannot be modified if the
RowStatus is active:
cpwCTDMCfgPayloadSize, cpwCTDMCfgRtpHdrUsed,
cpwCTDMCfgJtrBfrDepth, and cpwCTDMCfgPayloadSuppression.
If the RowStatus is active, the following parameters can be
modified:
cpwCTDMCfgConfErr, cpwCTDMCfgPktReorder,
cpwCTDMCfgConsecPktsInSynch,
cpwCTDMCfgConsecMissPktsOutSynch,
cpwCTDMCfgSetUp2SynchTimeOut, cpwCTDMCfgPktReplacePolicy,
cpwCTDMCfgAvePktLossTimeWindow,
cpwCTDMCfgExcessivePktLossThreshold,
cpwCTDMCfgAlarmThreshold, cpwCTDMCfgClearAlarmThreshold,
cpwCTDMCfgMissingPktsToSes, cpwCTDMCfgTimestampMode,
cpwCTDMCfgStorageType.
A row may be deleted by setting the RowStatus to 'destroy'.

This table provides TDM PW performance information.
This includes current 15 minute interval counts.
The table includes counters that work together to
integrate errors and the lack of errors on the TDM PW.
An error is caused by a missing packet. Missing packet
can be a result of, packet loss in the network,
(uncorrectable) packet out of sequence, packet length error,
jitter buffer overflow, and jitter buffer underflow.
The result is declaring whether or not the TDM PW is in
Loss of Packet (LOPS) state.

An entry in this table is created by the agent for every
cpwCTDMTable entry. After 15 minutes, the contents of this
table entry are copied to a new entry in the
cpwCTDMPerfInterval table and the counts in this entry
are reset to zero.

This object represents the number of TDM failure
events. A failure event begins when the LOPS failure
is declared, and ends when the failure is cleared. A
failure event that begins in one period and ends in
another period is counted only in the period in which
it begins.

This table provides performance information per TDM PW
similar to the cpwCTDMPerfCurrentTable above. However,
these counts represent historical 15 minute intervals.
Typically, this table will have a maximum of 96 entries
for a 24 hour period, but is not limited to this.

An entry in this table is created by the agent for
every cpwCTDMPerfCurrentEntry that is 15 minutes old.
The contents of the Current entry are copied to the new
entry here. The Current entry, then resets its counts
to zero for the next current 15 minute interval.

This object indicates a number (normally between 1 and
96 to cover a 24 hour period) which identifies the interval
for which the set of statistics is available. The interval
identified by 1 is the most recently completed 15 minute
interval, and the interval identified by N is the interval
immediately preceding the one identified by N-1.
The minimum range of N is 1 through 4.The default range
is 1 through 32. The maximum value of N is 1 through 96.

The duration of a particular interval in seconds.
Adjustments in the system's time-of-day clock, may
cause the interval to be greater or less than, the
normal value. Therefore this actual interval value
is provided.

This object represents the number of TDM failure
events. A failure event begins when the LOPS failure
is declared, and ends when the failure is cleared. A
failure event that begins in one period and ends in
another period is counted only in the period in which
it begins.

This table provides performance information per TDM PW
similar to the cpwCTDMPerfIntervalTable above. However,
these counters represent historical 1 day intervals up to
one full month. The table consists of real time data, as
such it is not persistence across re-boot.

The duration of a particular interval in seconds,
Adjustments in the system's time-of-day clock, may
cause the interval to be greater or less than, the
normal value. Therefore this actual interval value
is provided.

The counter associated with the number of
UnAvailable Seconds.
When first entering the UAS state, the number
of SES To UAS is added to this object, then as each
additional UAS occurs, this object increments by one.