
DS34S132 DATA SHEET
19-4750; Rev 1; 07/11
40 of 194
(B.BCDR1.SCRXBCSS; Xmt SW CAS will only be sent when the Jitter Buffer is empty). These two functions are
programmed on a per-Bundle basis. The Xmt SW CAS codes are programmed using RXSCn.CR1 - RXSCn.CR4
(programmed on a per-Timeslot basis).
In the TXP direction, when CAS Signaling is enabled on a Bundle (B.BCDR3.TXBTS = 2), the S132 can be
programmed to “pass through” the incoming receive TDM Port CAS Signaling or to insert a programmed TXP SW
CAS code (B.BCDR1.SCTXBCSS). The forced TXP SW CAS codes can be used during fault conditions (e.g. “Loss
of Signal”) or to force a known CAS code for idle timeslots. These two functions are programmed on a per-Bundle
basis. The TXP SW CAS codes (transmitted at the Ethernet Port) are programmed using TXSCn.CR1 -
TXSCn.CR4 (programmed on a per-Timeslot basis).
The S132 provides the ability to force Xmt Conditioning Data in the outgoing data stream at the transmit TDM Port
(programmed on a per Bundle basis). For SAT/CES Bundles, RXP Payload that is received from the Ethernet Port
is stored in a Jitter Buffer and later transmitted at the TDM Port as data is needed. For CES Payload Connections,
if the Jitter Buffer runs out of data the S132 continues transmitting data at the TDM Port using either the “Last
Value” or using one of eight programmed Xmt Conditioning Data values (B.BCDR4.SCLVI). For SAT Payload
Bundles, the Unstructured format does not identify byte boundaries and the TDM Port should be programmed to
immediately transmit Data Conditioning (SCLVI = 0). For HDLC Bundles, when the S132 runs out of HDLC data,
the TDM Port transmits the selected Xmt Conditioning Data (e.g. HDLC Idle Flags). The eight Xmt Conditioning
Data values are programmed using G.TCCR1 and G.TCCR2. The Conditioning Data is independently selected for
each Bundle using the B.BCDR4.RXCOS register.
For SAT/CES Bundles, the S132 can force TXP Conditioning Data in the outgoing TXP Packets. This may used
during incoming T1/E1 fault conditions or to send a forced PCM value like “Idle”. TXP Conditioning Data can be
enabled on a per Bundle basis using one of eight programmed TXP Conditioning Data values. Eight TXP
Conditioning Data values can be programmed using G.ECCR1 and G.ECCR2. The Conditioning Data value is
independently selected for each Bundle using BCDR1.SCTXCOS and independently enabled using
BCDR1.SCTXCE. For HDLC Bundles, when the S132 runs out of received/stored HDLC packets the S132 stops
transmitting TXP packets (TXP Conditioning Data is not used for HDLC Bundles).
Special considerations:
For systems that require the legacy CAS “Freeze Signaling” function (TXP and RXP directions), the Framer that
interfaces to the S132 TDM Port should implement the “Freeze Signaling” function so that proper CAS codes are
forwarded during fault conditions. The legacy “Freeze Signaling” function includes a CAS code de-bounce function
that is not implemented in the S132 (new CAS codes are not forwarded until the CAS code is received 3 times).
For systems that need to dynamically insert the transmit TDM Port CAS codes (e.g. to continuously translate
incoming RXP CAS codes into different outgoing CAS codes) the “dynamic insertion” should be implemented in the
external T1/E1 Framer. The S132 CAS functions do not allow the CPU to both monitor the incoming CAS codes
from RXP packets and replace the received CAS codes with Xmt SW CAS codes (the S132 function monitors the
CAS output, not the input).
In the transmit TDM Port (RXP) direction, when a Timeslot and/or its CAS code is “unspecified” (e.g. for unassigned
Timeslots), the data that is transmitted toward the T1/E1 Framer uses default values. The G.TCCR1.TCOA register
value is transmitted for “Unspecified” Timeslot data. “Unspecified” Timeslot CAS positions are filled with the
RXSCn.CTSx register value (“x” is equal to the Timeslot number).
In the transmit TDM Port (RXP) direction, when CAS is enabled on a TDM Port, CAS data is inserted in all
Timeslots (24 for T1, 30 for E1) regardless of whether all Timeslots are intended to include CAS. For T1
applications that use CAS in some Timeslots and “no CAS” in other Timeslots, TSIG should be used to transmit the
CAS codes to the external Framer, the S132 “Overwrite TDAT with CAS” function should be disabled
(Pn.PTCR2.DOSOT) and the external Framer should be programmed to insert the CAS codes (from TSIG) in the
appropriate Timeslots (the “Overwrite TDAT with CAS” function overwrites “with CAS” and “no CAS” Timeslots).
When the “CAS Change Interrupt” function for a TDM Port is enabled (G.GSR2 and G.GSR3), even non-CAS
Timeslots can generate an interrupt since all Timeslots are monitored. If the T1/E1 includes non-CAS Timeslots,
frequent interrupts may occur (once per multi-frame) because the data in the 8th bit position (CAS position) may be
constantly changing.
9.2.4.1 TDM CAS to Packet CAS Translation
When “pass through” CAS Signaling is enabled, the S132 translates the T1/E1 CAS timing at the TDM Port into PW
CAS Sub-channel signaling used by the Bundles. In the TXP and RXP directions the S132 stores and forwards 16
frames of received CAS Signaling for the E1 format and 24 frames of received CAS Signaling for the T1 SF and T1