Nortel Networks 311 用户手册
Operation
757
E and M Type II signaling
shows E and M Type II signaling patterns for incoming and
outgoing calls.
shows Type II signaling
patterns for a tandem connection where the originating end is senderized
and the route is over a CO trunk (CCSA not applicable).
and the route is over a CO trunk (CCSA not applicable).
Type II signaling uses four leads: M, SB, E, and SG. Instead of changes
of state between battery and ground (M signals) or open and ground (E
signals), the trunk signals by closing the contacts between the lead pairs
M and SB. Signals are received by detecting current flow between lead
pairs E and SG.
of state between battery and ground (M signals) or open and ground (E
signals), the trunk signals by closing the contacts between the lead pairs
M and SB. Signals are received by detecting current flow between lead
pairs E and SG.
On incoming calls, the far end seizes the trunk by shorting the E and SG
leads together. This transmits the ground from the SG lead to the E lead (in
Type I signaling the ground to the E lead comes from the far-end). Dialing
is done by opening and closing the E/SG contacts. Since the SB and M
leads are also used as the ESCG and ESC leads, respectively, for echo
suppression, echo suppressor control cannot be used with Type II signaling.
leads together. This transmits the ground from the SG lead to the E lead (in
Type I signaling the ground to the E lead comes from the far-end). Dialing
is done by opening and closing the E/SG contacts. Since the SB and M
leads are also used as the ESCG and ESC leads, respectively, for echo
suppression, echo suppressor control cannot be used with Type II signaling.
Note: M, SB, E, and SG designations are Electronic Industries
Association and Telecommunications Industries Association (EIA/TIA)
conventions. These leads are also known as MB, MA, EA, and EB,
respectively.
Association and Telecommunications Industries Association (EIA/TIA)
conventions. These leads are also known as MB, MA, EA, and EB,
respectively.
Release control
Release control of a call made over a trunk is specified in LD 16. Disconnect
supervision is specified for each trunk group independently. The two options
available are EITHER or ORIGINATING party control. These can be
specified for the end (near-end), or for the central office or other PBX end
(far-end). Joint party control can also be specified for the far-end.
supervision is specified for each trunk group independently. The two options
available are EITHER or ORIGINATING party control. These can be
specified for the end (near-end), or for the central office or other PBX end
(far-end). Joint party control can also be specified for the far-end.
Release control of a call made over a trunk is specified in LD 16. Disconnect
supervision is specified for each trunk group independently. The two options
available are EITHER or ORIGINATING party control. These can be
specified for the Meridian 1 end (near-end), or for the CO or other PBX end
(far-end). Joint party control can also be specified for the far-end.
supervision is specified for each trunk group independently. The two options
available are EITHER or ORIGINATING party control. These can be
specified for the Meridian 1 end (near-end), or for the CO or other PBX end
(far-end). Joint party control can also be specified for the far-end.
Release control of a call made over a trunk is specified in LD 16. Disconnect
supervision is specified for each trunk group independently. The two options
available are EITHER or ORIGINATING party control. These can be
specified for the CS 1000 end (near-end), or for the CO or other PBX end
(far-end). Joint party control can also be specified for the far-end.
supervision is specified for each trunk group independently. The two options
available are EITHER or ORIGINATING party control. These can be
specified for the CS 1000 end (near-end), or for the CO or other PBX end
(far-end). Joint party control can also be specified for the far-end.
Nortel Communication Server 1000
Circuit Card Reference
NN43001-311
01.04
Standard
Release 5.0
23 May 2008
Copyright © 2003-2008, Nortel Networks
.