Communications System Owner Manual
Table Of Contents
- Table of Contents
- ABOUT THIS DOCUMENT
- 1. INTRODUCTION TO CONNECTIVITY
- 2. COMMUNICATION SYSTEM NETWORKING (em AN OVERVIEW
- 3. TANDEM TIE TRUNK NETWORKS
- 4. MAIN-SATELLITE/TRIBUTARY (MS/T) NETWORKS THROUGH THE UDP OR MULTIPREMISES PACKAGES
- 5. ELECTRONIC TANDEM NETWORK (ETN) THROUGH THE ETN AND PNA PACKAGES
- 6. DISTRIBUTED COMMUNICATIONS SYSTEM (DCS)
- 7. DATA CONNECTIVITY - AN OVERVIEW
- 8. DATA COMMUNICATIONS CAPABILITIES
- 9. DATA COMMUNICATIONS CONFIGURATIONS
- A. RELATED DOCUMENTS
- B. SYNCHRONIZATION OF DIGITAL FACILITIES
- THE NEED FOR SYNCHRONIZATION
- SYNCHRONIZATION HIERARCHY
- CHANGES TO THE SCS SOFTWARE MADE AVAILABLE VIA SOFTWARE PATCHES
- NETWORK SYNCHRONIZATION AND ENGIINEERING
- AVAILABILITY OF SYNCHRONIZATION SOURCES
- CONCLUSIONS ON SYNCHRONIZATION
- USE OF GENERIC 2 AS A SYSTEM CLOCK REFERENCE
- USE OF GENERIC 1 AS A SYSTEM CLOCK REFERENCE
- C. TRUNKING TERMS AND CAPABILITIES
- D. COMMUNICATIONS PROTOCOLS
- E. LEAD DEFINITIONS
- F. NETWORKING FEATURES - AVAILABILITY MATRIX
- ABBREVIATIONS
- GLOSSARY
- INDEX

MAIN-SATELLITE/TRIBUTARY (MS/T) NETWORKS THROUGH THE UDP OR MULTIPREMISES PACKAGES 4-3
_ ______________________________________________________________________________________
_ ______________________________________________________________________________________
_ ______________________________________________________________________________________
CENTRAL
OFFICE
LDN
TRIBUTARY
EXTENSIONS
3600-3699
TRUNK
TIE
NETWORK INWARD
DIALING (NID)
RNX (542-XXXX)
MAIN PBX
EXTENSIONS
2800-2899
3200-3299
SATELLITE
PBX (B)
EXTENSIONS
3400-3499
SATELLITE
PBX (A)
EXTENSIONS
3300-3399
3500-3599
ETN NETWORK
REMOTE ACCESS
TRUNK
TIE
CENTRAL
OFFICE
(725-XXXX)
(727-XXXX)
LDN/DID
Figure 4-2. MS/T Coordinated Numbering
Main-Tributary Configuration
A main-tributary configuration is one in which the subtending location is the tributary. This configuration
is very similar to a main-satellite configuration with the following exceptions:
1. The main has its own LDN and the tributary usually has its own LDN. (See figure 4-2.)
2. A tributary can have one or more attendant positions.
3. A tributary usually has public network trunks.