PSTN

CCNA-VOICE
2
3
4
5
6
7
8
9
 Loop Start
When the FXO is idle, the two-wire local loop is
open. The tip and ring leads are not connected
to each other. The ring lead connects to a - 48
VDC battery at the FXS side. The tip lead
connects to ground at the FXS side. No current
is flowing in the idle state.
To seize the circuit, the FXO simply connects
the ring wire to the tip wire by going off-hook.
The FXS side detects current flowing from
battery on the ring lead to ground on the tip
lead. The FXS returns dial tone to the FXO. The
FXO then sends the dialed digits.

If the FXS wants to seize the circuit to deliver

an inbound call, it applies a 90 VAC ring
voltage on top of the DC voltage on the ring
lead. After seeing this ring voltage, the FXO
may then connect the ring lead to the tip lead
to accept the inbound call.
The FXS detects that the FXO has closed the
circuit because current flows from battery to
ground. In response, the FXS removes the ring
voltage and completes the call.

10
11
12
 Glare
In the US for example, ring voltage is sent for
two seconds and not sent for the next four
seconds. When the FXS signals an inbound call,
the cadence does not always start with the
two-second 'on' phase.
Consequently, the FXS may think it has seized
the circuit, but the FXO may not detect the
signal for up to four seconds. During this four-
second window, the FXO may attempt to seize
the circuit for an outbound call. If both sides
seize the circuit at the same time, the resulting
condition is called 'glare.'

When the FXO is a telephone, glare is not a big

problem. Often a residential phone user will
take the phone off-hook to place an outbound
call only to find someone already on the
phone. Glare is a problem on a residential
phone only if the end user is trying to avoid the
inbound caller.
When the FXO is a PBX or router trunk link, it
may be shared by many end users at different
times. Glare in this type situation may make a
business seem unprofessional. Inbound callers
will connect to unsuspecting outbound callers
who are not the intended called party.
13
14
15
 Ground Start
When idle, the FXS attaches the ring lead to
battery, but does not attach the tip lead to
ground. The FXO connects the tip lead to a tip
ground detector circuit. During the idle state, the
ring lead in the FXO is not attached to anything.

If the FXS side wants to seize a ground-start

trunk for inbound call, it connects the tip lead
to ground. The FXO detects this occurrence
through its tip ground detection circuitry. In
response, it connects the tip lead to the ring
lead, which completes the call. Now, the
circuit looks exactly like a loop start circuit in
the active call state.
The ground-start process is essentially a
physical layer acknowledgment protocol. The
circuit is not seized until both sides say so.

If the FXO wants to seize the circuit for an outbound call, it

connects the ring lead to ground. The FXS detects current
flow on the ring lead from battery at the FXS to ground at the
FXO. It acknowledges the FXO's request for service by
connecting the tip lead to ground.
The FXO detects this connection through its tip ground-
detection circuitry. In response, it connects the tip lead to the
ring lead, which completes the call. Now the circuit looks
exactly like a loop-start circuit in the active call state.

16
When Sending A DialTone
LoopStart GroundStart

17
 When Ringing
Loop Start Ground Start

18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
 T1 CAS SF Format
Time slot
8 bits
24 * 8 bits + 1 bit = 1 frame (193 bits)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

1 bit
12 frames = Super Frame sync.

1 2 3 4 5 6 7 8 9 10 11 12

24 * (7 bits + 1 robbed bit) + 1 bit = 1 frame (193 bits)

Time slot
7 bits +
1 robbed bit
37
38
 E1 R2 CAS (Cont.)
Time Slot 1 Time slot 17
Frame synchronization Frame 1 Indicates start of multiframe
Frames 216 Carry signaling (ABCD bits) for two
voice channels

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
1. Frame: Start of Multiframe
2. Frame: Signaling for Voice Slots 2 and 18
3. Frame: Signaling for Voice Slots 3 and 19
4. Frame: Signaling for Voice Slots 4 and 20
5. Frame: Signaling for Voice Slots 5 and 21
16 frames 6. Frame: Signaling for Voice Slots 6 and 22
= 7. Frame: Signaling for Voice Slots 7 and 23
Multiframe 8. Frame: Signaling for Voice Slots 8 and 24
2.048 Mb/s 9. Frame: Signaling for Voice Slots 9 and 25
10. Frame: Signaling for Voice Slots 10 and 26
11. Frame: Signaling for Voice Slots 11 and 27
12. Frame: Signaling for Voice Slots 12 and 28
13. Frame: Signaling for Voice Slots 13 and 29
14. Frame: Signaling for Voice Slots 14 and 30
15. Frame: Signaling for Voice Slots 15 and 31
16. Frame: Signaling for Voice Slots 16 and 32
39
40