KuberEva Book a call

Home/Documentation/T1 & fractional T1

T1, DS1 & fractional T1

The circuit sitting under a great many contact centers, explained at the level you need to migrate off it — including the details that determine whether your replacement actually carries the same traffic.

T1 versus DS1

The two terms are used interchangeably in practice, and that is mostly fine, but they describe different layers. T1 is the physical carrier system — the pair of copper pairs and the electrical specification. DS1 is the digital signal that rides on it. You will hear both used to mean "the 1.544 Mbps circuit," and in a migration conversation that is what matters.

Where 1.544 Mbps comes from

A DS1 carries 24 channels, each called a DS0, each running at 64 kbps. That is 1.536 Mbps of payload. The gap up to 1.544 Mbps is the framing overhead: one framing bit added after each round of 24 channel bytes.

Fig. 1 — the DS1 frame 193 bits · 8,000 per second
One frame = 1 framing bit + 24 timeslots F 1 4 8 12 16 20 24 24 timeslots × 64 kbps = 1.536 Mbps payload 1 bit × 8,000/s = 8 kbps One DS0 = 8 bits = 64 kbps ← LSB robbed in frames 6 & 12 → 56 kbps data Payload 1.536 Mbps Framing 0.008 Mbps Line rate 1.544 Mbps
The eight kilobits everyone forgets. One bit per frame, eight thousand times a second — that is the entire difference between 1.536 and 1.544 Mbps. The clay bit is the one robbed-bit signaling steals, which is why a CAS T1 gives you 56 kbps of data rather than 64.
ElementValueDerivation
DS0 channel64 kbps8 bits × 8,000 samples per second
Channels per DS124
Payload1.536 Mbps24 × 64 kbps
Frame size193 bits(24 × 8) + 1 framing bit
Frame rate8,000 / secMatches the voice sampling rate
Framing overhead8 kbps1 bit × 8,000 per second
Line rate1.544 Mbps193 bits × 8,000

The 8,000 samples per second is not arbitrary. It is the Nyquist rate for the 4 kHz channel the analog telephone network was built around, and it is the reason a DS0 is 64 kbps rather than any other number. Every later design inherited it.

Framing: D4/SF versus ESF

Those framing bits carry information, and how they are organized determines what you can see about the circuit.

Why this matters during migration If your circuits are ESF, you have historical performance data — errored seconds, severely errored seconds, unavailable seconds — that tells you whether the circuit has been degrading. That is genuinely useful evidence when you are building a case for the migration budget. On D4 circuits you have nothing but trouble tickets.

Line coding: AMI versus B8ZS

T1 receivers recover their clock from the data stream, which requires a minimum density of pulses. A long run of zeros starves the clock and the circuit loses framing.

This is the origin of the 56k-versus-64k distinction that still appears in older documentation. If you inherit a circuit inventory listing 56 kbps channels, you are looking at AMI with bit stuffing, and the circuit is old.

Robbed-bit signaling

On channel-associated signaling (CAS) T1s, supervision — on-hook, off-hook, ringing — is carried in-band by "robbing" the least significant bit of each channel's sample in designated frames. In D4 that is frames 6 and 12; in ESF, frames 6, 12, 18 and 24.

The signaling states this produces are the familiar ones: loop start, ground start, E&M wink start, and immediate start. The important consequence for migration is that robbed-bit signaling is why a CAS T1 cannot carry clean 64 kbps data, and why the industry moved to ISDN PRI, which puts signaling on its own channel. See ISDN PRI & BRI.

Fractional T1

A fractional T1 is a subscription to a subset of the 24 channels rather than the whole 1.544 Mbps. A 256 kbps fractional service is four DS0s; 512 kbps is eight.

The detail that matters operationally: the service provider assigns specific timeslots. You are not given "any four channels" — you are given, for example, timeslots 1 through 4, and your CSU/DSU must be configured to use exactly those. A mismatch between the timeslots the carrier provisioned and the timeslots your equipment is configured for produces a circuit that comes up cleanly and passes no traffic, which is one of the more frustrating faults to chase.

The full T1 is physically delivered either way. Fractional service is a billing and provisioning arrangement, not a different circuit. That has a practical implication during migration: growing from fractional to full is a provisioning change, not an installation.

Inventory reality check Billed capacity and provisioned capacity diverge more often than anyone expects. We regularly find fractional circuits billed at one rate and provisioned at another, in both directions. Read the actual DS0 assignments from the CSR before you size a replacement — not the invoice.

Channelized, unchannelized, and the wider hierarchy

LevelRateCapacity
DS064 kbpsOne voice channel
DS1 / T11.544 Mbps24 DS0
DS3 / T344.736 Mbps28 DS1 (672 DS0)
E1 (outside North America)2.048 Mbps32 timeslots — 30 bearer, TS0 framing, TS16 signaling

Reading the alarms

When a T1 fails, the alarm tells you which direction the problem is in — which is the fastest way to work out whose fault it is.

AlarmAlso calledMeans
LOSLoss of signalNo pulses arriving at all. Usually physical — cable, connector, or the far-end device is off.
LOFRed alarm / loss of frameSignal present but the framing pattern can't be found. Often a framing mismatch (D4 versus ESF) rather than a fault.
AISBlue alarmAn unframed all-ones signal, sent upstream to indicate an upstream failure. Someone else's problem, being reported to you.
RAIYellow alarmThe far end is telling you it cannot see your transmit. Your outbound direction is broken.

A yellow alarm at your end and a red alarm at theirs is the classic one-direction failure. Both ends red is usually a framing or line-coding configuration mismatch.

What carries over to SIP, and what doesn't

T1 conceptSIP equivalentNote
24 DS0 channelsConcurrent session limitEnforced by call admission control on the SBC rather than by physics.
Fixed 64 kbps per channelCodec-dependent bandwidthG.711 is comparable; G.729 is far lower but with a quality cost. Budget for overhead.
Robbed-bit supervisionSIP methods and responsesThe states map, but timing and edge-case behavior differ.
Circuit is up or downQuality is a spectrumThe single biggest mental shift. A SIP trunk can be "up" and unusable. See voice quality.
Deterministic latencyVariable latency and jitterNeeds an explicit budget, not an assumption.

That last row is the one that catches teams out. On a T1, the circuit either works or it does not, and quality is not really a variable. On SIP, everything can be nominally operational while customers report that calls sound terrible. Migration plans need a measurable quality target from the start.

Related reading

Circuit inventories are almost always wrong. Reading the actual provisioning is where we start.

Book a call