Title page

Nortel Networks Communication Server 1000

Nortel Networks Communication Server 1000 Release 4.0

Communication Server 1000M and

Meridian 1
Large System Overview
Document Number: 553-3021-010
Document Release: Standard 2.00
Date: September 2004

Year Publish FCC TM

Copyright © 2003–2004 Nortel Networks
All Rights Reserved

Produced in Canada

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design
or components as progress in engineering and manufacturing may warrant.

SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

4

Page 3 of 82

Revision history
September 2004
Standard 2.00. This document is up-issued for Communication Server 1000
Release 4.0.

October 2003
Standard 1.00. This document is a new NTP for Succession 3.0. It was created
to support a restructuring of the Documentation Library. This document
contains information previously contained in the following legacy document,
now retired: System Overview (553-3001-100).

Communication Server 1000M and Meridian 1 Large System Overview

Page 4 of 82 Revision history

553-3021-010 Standard 2.00 September 2004

6

Page 5 of 82

Contents
About this document . . . . . . . . . . . . . . . . . . . . . . . 7
Subject .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Applicable systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Conventions .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Related information .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Product description . . . . . . . . . . . . . . . . . . . . . . . . 11
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
System options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
CS 1000M HG and Meridian 1 Option 51C .. . . . . . . . . . . . . . . . . . 13
CS 1000M SG and Meridian 1 PBX 61C CP PII .. . . . . . . . . . . . . . 16
CS 1000M MG and Meridian 1 PBX 81C CP PII . . . . . . . . . . . . . . 20
System modules .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
NT4N41 Core/Network module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
NT5D21 Core/Network module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
NT8D35 Network module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Fiber Network Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
NT8D37 Intelligent Peripheral Equipment module . . . . . . . . . . . . . 31
Fiber Remote IPE module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Carrier Remote IPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

System architecture . . . . . . . . . . . . . . . . . . . . . . . . 35
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Communication Server 1000M and Meridian 1 Large System Overview

Page 6 of 82 Contents

Hardware architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Common control complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Network interface .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Intelligent Peripheral Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Terminal equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Power equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Signaling Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Office data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Resident programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Nonresident programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Fiber Remote IPE .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Carrier Remote IPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Branch Office .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Geographic Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

List of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

553-3021-010 Standard 2.00 September 2004

10

Page 7 of 82

About this document

This document is a global document. Contact your system supplier or your
Nortel Networks representative to verify that the hardware and software
described are supported in your area.

Subject
This document provides an overview of the general design and features of
CS 1000M and Meridian 1 Large Systems.

Note on legacy products and releases

This NTP contains information about systems, components, and features that
are compatible with Nortel Networks Communication Server 1000
Release 4.0 software. For more information on legacy products and releases,
click the Technical Documentation link under Support on the Nortel
Networks home page:
http://www.nortelnetworks.com/

Applicable systems
This document applies to the following systems:
• Communication Server 1000M Half Group (CS 1000M HG)
• Communication Server 1000M Single Group (CS 1000M SG)
• Communication Server 1000M Multi Group (CS 1000M MG)
• Meridian 1 PBX 51C
• Meridian 1 PBX 61C

Communication Server 1000M and Meridian 1 Large System Overview

Page 8 of 82 About this document

• Meridian 1 PBX 61C CP PII

• Meridian 1 PBX 81
• Meridian 1 PBX 81C
• Meridian 1 PBX 81C CP PII

Note: When upgrading software, memory upgrades may be required on

the Signaling Server, the Call Server, or both.

System migration
When particular Meridian 1 systems are upgraded to run CS 1000 Release 4.0
software and configured to include a Signaling Server, they become
CS 1000M systems. Table 1 lists each Meridian 1 system that supports an
upgrade path to a CS 1000M system.

Table 1
Meridian 1 systems to CS 1000M systems

This Meridian 1 system... Maps to this CS 1000M system

Meridian 1 PBX 51C CS 1000M Half Group

Meridian 1 PBX 61C CS 1000M Single Group

Meridian 1 PBX 61C CP PII CS 1000M Single Group

Meridian 1 PBX 81 CS 1000M Multi Group

Meridian 1 PBX 81C CS 1000M Multi Group

Meridian 1 PBX 81C CP PII CS 1000M Multi Group

For more information, see Communication Server 1000M and Meridian 1:

Large System Upgrade Procedures (553-3021-258).

Intended audience
This document is intended to be an introductory overview for individuals
responsible for the sale, acquisition, planning, or installation of CS 1000M
and Meridian 1 Large Systems.

553-3021-010 Standard 2.00 September 2004

 About this document Page 9 of 82

Conventions
Terminology
In this document, the following systems are referred to generically as
“system”:
• CS 1000M
• Meridian 1

The following systems are referred to generically as “Large System”:

• Communication Server 1000M Half Group (CS 1000M HG)
• Communication Server 1000M Single Group (CS 1000M SG)
• Communication Server 1000M Multi Group (CS 1000M MG)
• Meridian 1 PBX 51C
• Meridian 1 PBX 61C
• Meridian 1 PBX 61C CP PII
• Meridian 1 PBX 81
• Meridian 1 PBX 81C
• Meridian 1 PBX 81C CP PII

Communication Server 1000M and Meridian 1 Large System Overview

Page 10 of 82 About this document

Related information
This section lists information sources that relate to this document.

NTPs
The following NTPs are referenced in this document:
• IP Peer Networking: Installation and Configuration (553-3001-213)
• Branch Office: Installation and Configuration (553-3001-214)
• Communication Server 1000: System Redundancy (553-3001-307)
• Fiber Remote Multi-IPE Interface: Description, Installation, and
Maintenance (553-3001-356)
• Telephones and Consoles: Description, Installation, and Operation
(553-3001-367)
• IP Phones: Description, Installation, and Operation (553-3001-368)
• Communication Server 1000M and Meridian 1: Large System Planning
and Engineering (553-3021-120)
• Fiber Remote IPE: Description, Installation, and Maintenance (553-
3021-354)
• Carrier Remote IPE: Description, Installation, and Maintenance (553-
3021-355)

Online
To access Nortel Networks documentation online, click the
Technical Documentation link under Support on the Nortel Networks
home page:
http://www.nortelnetworks.com/

CD-ROM
To obtain Nortel Networks documentation on CD-ROM, contact your
Nortel Networks customer representative.

553-3021-010 Standard 2.00 September 2004

34

Page 11 of 82

Product description

Contents
This section contains information on the following topics:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
System options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
CS 1000M HG and Meridian 1 Option 51C. . . . . . . . . . . . . . . . . . . 13
CS 1000M SG and Meridian 1 PBX 61C CP PII. . . . . . . . . . . . . . . 16
CS 1000M MG and Meridian 1 PBX 81C CP PII . . . . . . . . . . . . . . 20
System modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
NT4N41 Core/Network module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
NT5D21 Core/Network module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
NT8D35 Network module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Fiber Network Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
NT8D37 Intelligent Peripheral Equipment module . . . . . . . . . . . . . 31
Fiber Remote IPE module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Carrier Remote IPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Introduction
All Large Systems consist of Universal Equipment Modules (UEM) stacked
one on top of another to form a column. Each column contains a pedestal, a
top cap, and up to four modules. A system can have one column or multiple
columns. The CS 1000M Large System includes a rack-mounted Signaling
Server.

Each UEM is a self-contained unit that houses a card cage and backplane,
power and ground cabling, power units, input/output (I/O) panels, circuit

Communication Server 1000M and Meridian 1 Large System Overview

Page 12 of 82 Product description

cards, and cables. When the card cage is installed, the function of the UEM is
established and the module is no longer “universal.” The system modules are
as follows:
• NT4N41 Core/Network module for CS 1000M MG, CS 1000M SG,
Meridian 1 PBX 81C CP PII, and Meridian 1 PBX 61C CP PII
• NT5D21 Core/Network module for CS 1000M HG, CS 1000M SG,
CS 1000M MG, Option 51C, 61C and 81C
• NT8D35 Network module required for CS 1000M MG and Meridian 1
PBX 81C CP PII, Option 81C
• NT8D37 Intelligent Peripheral Equipment (IPE) module (required for
Large Systems)
• Fiber Remote IPE module (optional for Large Systems Multi Group)
• Carrier Remote IPE module (optional for Large Systems)
Note: In addition, modules that house equipment for specific
applications, such as Meridian Mail and Meridian Link, can be included
in a column.

The pedestal generally houses a blower unit, air filter, Power Distribution
Unit (PDU), and System Monitor.

The top cap provides airflow exits, I/O cable entry and exit, and overhead
cable-rack mounting. Thermal sensor assemblies for the column are attached
to a perforated panel on top of the highest module in the column, under the
top cap.

A system can have one column or multiple columns. To comply with FCC
and CSA standards for containing electromagnetic interference and radio
frequency interference (EMI/RFI), spacer kits connect the columns in a
multiple-column system. If a Signaling Server is added to a previously CISPR
Class B system (previously used in some specific countries), the system is
now Compliant to Class A.

553-3021-010 Standard 2.00 September 2004

 Product description Page 13 of 82

System options
This document includes information on the following Large Systems:
• CS 1000M HG and Meridian 1 Option 51C: enhanced common control
complex, single CPU, and one half network group
• CS 1000M SG, Meridian 1 PBX 61C CP PII, and Meridian 1 Option
61C: enhanced common control complex, dual CPU, and one full-
network group
• CS 1000M MG, Meridian 1 PBX 81C CP PII, Meridian 1 Option 81,
and Meridian 1 Option 81C: enhanced common control complex, dual
CPU, and multiple-network groups

These systems are available in AC- and DC-powered versions.

CS 1000M HG and Meridian 1 Option 51C

The CS 1000M HG and the Meridian 1 Option 51C are single-CPU systems
with a half-network group. One Core/Network module and one IPE module
are required. Additional IPE modules, Remote IPE modules, and application
modules can be used.

Table 2 on page 15 lists the specifications for these systems. Figure 1

illustrates an Option 51C system.

With the addition of a Signaling Server, Meridian 1 Option 51C becomes a

CS 1000M HG. Figure 2 on page 14 illustrates a CS 1000M HG.

Communication Server 1000M and Meridian 1 Large System Overview

Page 14 of 82 Product description

Figure 1
Meridian 1 Option 51C

UEM

UEM

UEM

Core/Network
Module

Meridian 1
Option 51C 553-AAA0911

Figure 2
CS 1000M HG

Business Policy
Switch
UEM

UEM

Signaling
UEM Server

Core/Network
Module

553-AAA1613.EPS

553-3021-010 Standard 2.00 September 2004

 Product description Page 15 of 82

Table 2
Specifications for CS 1000M HG and Meridian 1 Option 51C (Part 1 of 2)

System characteristics:

Maximum number of ports — 1000

Input voltage — 208 V AC or –48 V DC

Number of CPUs — 1

Number of network loops — 16

Memory options:

Release 25 — NT5D10 CP or NT5D03 CP card

Succession 3.0 — CP3 NT5D10 CP or CP4 NT5D03 card

CS 1000 Release 4.0 — CP3 NT5D10 CP or CP4 NT5D03 card

Software generic — 2811

Base hardware:

Core/Network module Required per system:

— SDI-type card

Required per module:

— CE power supply (CEPS)

— Call Processor (CP) card

— Input/Output Disk Unit with CD-ROM (IODU/C)

— Core to Network Interface (cCNI) card

— 3-Port Extender (3PE) card

— Clock Controller Card (MCLK)

IPE module — IPE power supply

— IPE cards

Communication Server 1000M and Meridian 1 Large System Overview

Page 16 of 82 Product description

Table 2
Specifications for CS 1000M HG and Meridian 1 Option 51C (Part 2 of 2)

Pedestal (one per column) — System Monitor

— PDU

— Blower unit

Top cap (one per column) — Thermostat harness

— Air probe harness

CS 1000M SG and Meridian 1 PBX 61C CP PII

The CS 1000M SG and the Meridian 1 PBX 61C CP PII are dual-CPU
systems with standby processing capability, fully redundant memory, and a
full-network group. Two cPCI Core/Network modules and one IPE module
are required. Additional IPE modules and application modules can be used.

Figure 3 on page 17 illustrates an Option 61C or Meridian 1 PBX 61C

CP PII.

With the addition of a Signaling Server, Option 61C or Meridian 1 PBX 61C
CP PII becomes CS 1000M SG. Figure 4 on page 17 illustrates a
CS 1000M SG.

553-3021-010 Standard 2.00 September 2004

 Product description Page 17 of 82

Figure 3
Meridian 1 PBX 61C CP PII or Meridian 1 Option 61C

IPE
Module

Core/Network
Module

Core/Network
Module

553-AAA0559

Figure 4
CS 1000M SG

Business Policy
Switch
IPE
Module

Core/Network
Module Signaling
Server

Core/Network
Module

553-AAA1614.EPS

Communication Server 1000M and Meridian 1 Large System Overview

Page 18 of 82 Product description

Table 3 lists the specifications for CS 1000M SG and Meridian 1 PBX 61C
CP PII.

Table 3
Specifications for CS 1000M SG and Meridian 1 PBX 61C CP PII (Part 1 of 3)

System characteristics:

Maximum number of ports — 2000

Input voltage — 208 V AC or –48 V DC

Number of CPUs — 2 (redundant)

Number of network loops — 32

Memory options:

Release 25 — NT5D10 CP or NT5D03 CP card

Succession 3.0 — CP3 NT5D10 or CP4 NT5D03 card

CS 1000 Release 4.0 — CP3 NT5D10 or CP4 NT5D03 card

Software generic — 2911

553-3021-010 Standard 2.00 September 2004

 Product description Page 19 of 82

Table 3
Specifications for CS 1000M SG and Meridian 1 PBX 61C CP PII (Part 2 of 3)

Base hardware:

Core/Network module (two) Required per system:

— SDI-type card

Required per module:

— Multi-Media Disk Unit (MMDU)

® (CP PII) card
— Call Processor Pentium II

— System Utility (Sys Util) card

— Core to Network Interface (cCNI) card

— 3-Port Extender (3PE) card

— Peripheral Signaling card (PS)

— Network cards

— Superloop Network cards

— Conference/TDS card

— CE power supply

— Hybrid Bus Terminators

Cards in the back of the module:

— System Utility Transition (Sys Util Trans) card

— cCNI Transition (cCNI Trans) card

IPE module — IPE power supply

— IPE cards

— Controller card

Communication Server 1000M and Meridian 1 Large System Overview

Page 20 of 82 Product description

Table 3
Specifications for CS 1000M SG and Meridian 1 PBX 61C CP PII (Part 3 of 3)

Pedestal (one per column) — System Monitor

— PDU

— Blower unit

Top cap (one per column) — Thermostat harness

— Air probe harness

CS 1000M MG and Meridian 1 PBX 81C CP PII

The CS 1000M MG and Meridian 1 PBX 81C are dual-CPU systems with
standby processing capabilities, fully-redundant memory, and up to eight full
network groups. These systems are equipped with two redundant input/output
processor and disk drive unit combination packs.

The following modules are required:

• two Core/Network modules (provides one network group)
• a minimum of two Network modules (provides one network group)
• a minimum of one IPE module

Additional Network and IPE modules are required for additional network
groups. Application modules can also be used.

Figure 5 on page 21 shows a typical configuration for eight full network

groups. Additional columns can be added, and there can be more than one row
of columns.

With the addition of a Signaling Server, Meridian 1 Option 81C or

Meridian 1 PBX 81C CP PII becomes a CS 1000M MG. Figure 6 on page 21
illustrates the CS 1000M MG.

553-3021-010 Standard 2.00 September 2004

 Product description Page 21 of 82

Figure 5
Meridian 1 PBX 81C CP PII or Option 81C

IPE IPE IPE IPE IPE IPE IPE

Group 1, shelf 1 Group 2, shelf 1 Group 3, shelf 1 Group 4, shelf 1 Group 5, shelf 1 Group 6, shelf 1 Group 7, shelf 1
loops 48 to 63 loops 80 to 95 loops 144 to 159 loops 144 to 159 loops 176 to 191 loops 208 to 223 loops 240 to 255

Group 2, shelf 0 Group 3, shelf 0 Group 4, shelf 0 Group 5, shelf 0 Group 6, shelf 0 Group 7, shelf 0
Network shelf loops 64 to 79 loops 96 to 143 loops 160 to 175 loops 192 to 207 loops 224 to 239
loops 128 to 143

Core 1 Core 0 Applications IPE IPE IPE IPE

553-AAA0562

Figure 6
CS 1000M MG

Communication Server 1000M and Meridian 1 Large System Overview

Page 22 of 82 Product description

Table 4 lists specifications for the Meridian 1 PBX 81C CP PII.

Table 4
Specifications for CS 1000M MG and Meridian 1 Option 81C CP PII (Part 1 of 3)

System characteristics:

Maximum number of ports — 10 000

Input voltage — 208 V AC or –48 V DC

Number of CPUs — 2 (redundant)

Number of network loops — 256

Memory — 128 MB

— 256 MB

— CP3 NT5D10, required for CS 1000 Release 4.0

— CP4 NT5D03, required for CS 1000 Release 4.0

553-3021-010 Standard 2.00 September 2004

 Product description Page 23 of 82

Table 4
Specifications for CS 1000M MG and Meridian 1 Option 81C CP PII (Part 2 of 3)

Base hardware:

cCPI Core/Network module Cards in the front of the module:

(two side-by-side)
— Multi-Media Disk Unit (MMDU)
® (CP PII) card
— Call Processor Pentium II

— System Utility (Sys Util) card

— Core to Network Interface (cCNI) cards

— 3-Port Extender (3PE) card

— Peripheral Signaling card (PS)

— Fiber Junctor Interface (FIJI) card

— Network cards

— Superloop Network cards

— Conference/TDS card

— CE power supply

— Hybrid Bus Terminators

Cards in the back of the module:

— System Utility Transition (Sys Util Trans) card

— cCNI Transition (cCNI Trans) cards

— Superloop Network card

— Clock Controller card

— SDI-type card

— DDP2 pack

— MSDL

Communication Server 1000M and Meridian 1 Large System Overview

Page 24 of 82 Product description

Table 4
Specifications for CS 1000M MG and Meridian 1 Option 81C CP PII (Part 3 of 3)

IPE module — IPE power supply

— Controller card

— IPE cards

Pedestal (one per column) — System monitor

— Power Distribution Unit (PDU)

— Blower unit

Top cap (one per column) — Thermostat harness

— Air probe harness

System modules
Each type of module is available in AC-powered and DC-powered versions
(except the NT8D36 InterGroup module that does not require power).
AC-power modules generally require a module power distribution unit
(MPDU) to provide circuit breakers for the power supplies. DC-powered
modules do not require an MPDU because a switch on each power supply
performs the same function as the MPDU circuit breakers.

Note: In the UK, DC-powered modules must be used.

The figures in this chapter show a typical configuration for each module.
DC power is represented in these examples.

NT4N41 Core/Network module

This module provides common control and network interface functions. With
the CS 1000M MG and the Meridian 1 PBX 81C CP PII, two Core/Net
modules are installed side-by-side. With the CS 1000M SG and the
Meridian 1 PBX 61C CP PII, the modules are stacked or mounted side-by-
side.

One section of this module houses the common control complex (CPU,
memory, up to four cCNI cards, and mass storage functions). The other

553-3021-010 Standard 2.00 September 2004

 Product description Page 25 of 82

section supports a Conference card, one Peripheral Signaling card, one 3-Port
Extender card, and optional network cards.

Note: cCNI card slots 13 and 14 remain empty.

Each Core/Network module houses up to four NT8D04 Superloop Network

Cards for a total of 16 network loops. Superloop Network cards are cabled to
the backplane of an IPE module. In a typical configuration, one conference/
TDS card is configured in the module, leaving 14 voice/data loops available.

Figure 7 on page 26 illustrates an NT4N41 Core/Network module.

Core side
The Core side of the module contains the circuit cards that process calls,
manage network resources, store system memory, maintain the user database,
and monitor the system. These circuit cards also provide administration
interfaces through a terminal, modem, or LAN.

The Core side runs in redundant mode: one Core operates the system while
the other runs diagnostic checks and remains ready to take over if the active
Core fails. Both Cores are connected to each Network group depending on
hardware configuration. If one Core fails, the second Core immediately takes
over call processing. The Core shelf backplane is a compact PCI data bus.

Communication Server 1000M and Meridian 1 Large System Overview

Page 26 of 82 Product description

Figure 7
NT4N41 cPCI Core/Network module

Net Core

MMDU

QPC43R Peripheral Signaling Card

NT8D04 Superloop Network Card

NT8D04 Superloop Network Card

NT8D04 Superloop Network Card

SYS CP
cCNI UTIL PII
NT8D17 Conference/TDS Card

QPC441 3-Port Extender Card

A
CCOM 1
B Enb

Enb
PS

Dis
Dis
CCOM 2

LLAN 2

LLAN 1

USB

NTRB33 Fiji

NTRB33 Fiji
INIT

RESET
ALRM SPKR

HDD PWR

c9 c10 c11 c12 c13 c14 c15 CP

PS 0 1 2 3 4 5 6 7 8 9 10 11

553-9123r26revised

Network side
The Network side of this module contains the cards for half of the Network
group 0. The other half of Network group 0 resides in the second core network
module.

The CS 1000M MG and Meridian 1 PBX 81C CP PII support a Fiber

Network Fabric network system with a FIJI card in slots 8 and 9 on the Net
side of the Core/Net module.

NT5D21 Core/Network module

This module provides common control and network interface functions in
CS 1000M SG, CS 1000M MG, CS 1000M HG, Meridian 1 Option 51C,
Meridian 1 Option 61C, and Meridian 1 Option 81C.

Two Core/Network modules are required in the CS 1000M SG,

CS 1000M MG, Meridian 1 Option 81C, and Meridian 1 Option 61C systems
to provide redundant common control operation. If a failure occurs in one

553-3021-010 Standard 2.00 September 2004

 Product description Page 27 of 82

module, the function is transferred to the appropriate circuit cards in the other
module without a loss of service. One Core/Network module is required in the
CS 1000M HG or Option 51C system.

One section of this module houses the common control complex (CPU,
memory, up to three CNI cards, and mass storage functions). The other
section supports a Conference card, one Peripheral Signaling card, one 3-Port
Extender card, and optional network cards.

Note: CNI card slots 13 and 14 remain empty.

Each Core/Network module houses up to four NT8D04 Superloop Network

Cards for a total of 16 network loops. Superloop Network cards are cabled to
the backplane of an IPE module. In a typical configuration, one conference/
TDS card is configured in the module, leaving 14 voice/data loops available.

Communication Server 1000M and Meridian 1 Large System Overview

Page 28 of 82 Product description

Figure 8 shows the cards housed in the NT5D21 Core/Network module as

configured for Meridian 1 Option 61C.

Figure 8
NT5D21 Core/Network module

Core/Net Module Net Core

(No card should be inserted into this slot)

QPC43R Peripheral Signaling Card

NT8D04 Superloop Network Card

NT8D04 Superloop Network Card

NT8D04 Superloop Network Card

LRTN
NT8D17 Conference/TDS

3-Port Extender Card

Call Processor Card

NT5D61 IODU/C
Clock Controller

FGND CNI

CNI

CNI

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
CE Pwr Sup SLP SLP SLP SLP PS 3PE CNI NT5D21

Network Group CPU

Core/Net Module
Shelf
553-6383-1

NT8D35 Network module

This module provides the network switching functions in the Meridian 1
Option 81C, Meridian 1 PBX 81C CP PII, and CS 1000M MG.

Two Network modules are required to make a full network group of 32 loops.
A maximum of 16 Network modules (eight network groups) can be
configured in the Meridian 1 Option 81C, CS 1000M MG, and Meridian 1
PBX 81C CP PII.

The Network module houses up to four NT8D04 Superloop Network Cards,

for a total of 16 network loops. Superloop network cards are cabled to the
backplane of an IPE module. In a typical configuration, one Conference/TDS

553-3021-010 Standard 2.00 September 2004

 Product description Page 29 of 82

card is configured in the module, leaving 14 voice/data loops available. In

CS 1000M MG and Meridian 1 PBX 81C CP PII, the Conference/TDS cards
are located in the Core/Network module. The Clock Controller must be
installed in slot 13.

Figure 9 shows the cards housed in the module.

Figure 9
NT8D35 Network module

DCHI (5-13)
MSDL (5-13)
MISP
Network-type cards:
NT8D04 Superloop Net
NT8D17 Conference/TDS
PRI/DTI (5-11)
SDI
553-AAA0563

The Network module can be used as a PRI/DTI expansion module. The

number of PRI/DTI expansion modules that can be used is determined by
traffic considerations. Figure 10 on page 30 shows the card slot configuration
when the Network module is used for PRI/DTI expansion.

Note: The bus terminating units (BTUs) that are equipped in the
NT8D35AA and NT8D35DC Network module configuration are not
required for, and will interfere with, the PRI/DTI expansion
configuration. The NT8D35BA and NT8D35EA Network modules do
not use or need BTUs for any application.

Communication Server 1000M and Meridian 1 Large System Overview

Page 30 of 82 Product description

Figure 10
NT8D35 Network module configured for PRI/DTI expansion

553-5005
CE Module Net

PRI/DTI

PRI/DTI

PRI/DTI

PRI/DTI

PRI/DTI
1 2 3 4 5 6 7 8 9 10 11 12 13 14
CE Pwr Sup 3PE IGS 1 IGS 0 PS SLP SLP SLP SLP

Common Equipment Network Group

Shelf

Fiber Network Fabric

Fiber Network Fabric extends and enhances the 5-group network architecture
to 8 non-blocking (inter-group) Network groups, with a resulting expansion
in network capacity to 8000 timeslots available for Intergroup traffic. The
Meridian 1 61C CP PII can be upgraded to a Meridian 1 81C CP PII with
Fiber Network Fabric. This upgrade takes a Meridian 1 61C CP PII to a
Meridian 1 81C CP PII with two groups. Figure 11 on page 31 illustrates a
four group configuration of Fiber Network Fabric.

553-3021-010 Standard 2.00 September 2004

 Product description Page 31 of 82

Figure 11
Four group Fiber Network Fabric configuration

553-AAA0548

NT8D37 Intelligent Peripheral Equipment module

The Intelligent Peripheral Equipment (IPE) module provides the interface
between network switching and IPE cards, such as intelligent line and trunk
cards, in all Large Systems.

The IPE module houses one NT8D01 Controller Card, which is the peripheral
equipment controller, and up to 16 IPE cards, supporting up to 512 terminal

Communication Server 1000M and Meridian 1 Large System Overview

Page 32 of 82 Product description

numbers (256 voice and 256 data). The controller card is cabled to the
NT8D04 Superloop Network Card.

Figure 12 shows the card slot assignments in the module.

Figure 12
NT8D37 IPE module

PE Module IPE

NT8D01 Controller Card

Intelligent line cards Intelligent line cards
Intelligent trunk cards Intelligent trunk cards
BRSC BRSC

0 1 2 3 4 5 6 7 Cont 8 9 10 11 12 13 14 15
PE Pwr Sup Rng Gen

Intelligent Superloop
Peripheral Equipment Shelf

553-3092

Fiber Remote IPE module

This module provides fiber-optic links between the network functions in a
Large System and the peripheral controller functions in the Fiber Remote
IPE. A floor-standing column or wall-mounted cabinet is installed at the
remote site and is connected to the Large System using fiber-optic links.

The Fiber Remote IPE provides Large Systems functionality with the
installation of only IPE modules and IPE cards at a distant site. Since the
remote IPE system uses the common equipment and network equipment of
the associated local Large System, it can deliver the same features and
functionality as the local system. See “Fiber Remote IPE” on page 62 for
more information on the Fiber Remote IPE configuration option.

553-3021-010 Standard 2.00 September 2004

 Product description Page 33 of 82

Carrier Remote IPE

The Carrier Remote IPE provides functionality by installing only IPE
modules and IPE cards at a distant site. The Remote IPE shares the system
common and network equipment to provide the same functions and features
to remote subscribers that are available to local system subscribers.

See “Carrier Remote IPE” on page 65 for more information on the Carrier
Remote IPE configuration option.

Communication Server 1000M and Meridian 1 Large System Overview

Page 34 of 82 Product description

553-3021-010 Standard 2.00 September 2004

70

Page 35 of 82

System architecture

Contents
This section contains information on the following topics:
Hardware architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Common control complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Network interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Intelligent Peripheral Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Terminal equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Power equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Signaling Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Software architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Office data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Resident programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Nonresident programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Fiber Remote IPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Carrier Remote IPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Branch Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Geographic Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Communication Server 1000M and Meridian 1 Large System Overview

Page 36 of 82 System architecture

Hardware architecture
CS 1000M and Meridian 1 systems are circuit-switched digital systems that
provide voice and data transmission. The internal hardware is divided into the
following functional areas (see Figure 13 on page 37):
• Common Control Complex (Common Equipment) circuit cards provide
the processor control, software execution, and memory functions of the
system.
• Network Interface (Common Equipment) circuit cards perform
switching functions between the processor and Intelligent Peripheral
Equipment (IPE) cards.
Note: As shown in Figure 13, the network interface function is generally
considered a subset of the Common Equipment functions.

• IPE circuit cards provide the interface between the network and
connected devices, including Terminal Equipment and trunks.
• Terminal Equipment includes telephones and attendant consoles (and
may include equipment such as data terminals, printers, and modems).
• Power Equipment provides the electrical voltages required for system
operation and cooling, and sensor equipment for system protection.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 37 of 82

Figure 13
Large System basic architecture

P COMMON EQUIPMENT
COMMON CONTROL COMPLEX
o
w Processor / memory / mass storage functions
e
r

E COMMON EQUIPMENT
q NETWORK INTERFACE
u Circuit switching functions
i
p
m
e
n INTELLIGENT PERIPHERAL EQUIPMENT
t Line, trunk, and data interfaces

TERMINAL EQUIPMENT
Telephones, attendant consoles, data equipment

553-AAA2257

Communication Server 1000M and Meridian 1 Large System Overview

Page 38 of 82 System architecture

Common control complex

The processor is the common control complex of the system. It provides the
sequences to process voice and data connections, monitor call activity, and
perform system administration and maintenance.

The processor communicates with the network interface over a common

control bus that carries the flow of information.

The common control complex consists of:

• the processor card or cards that provide the computing power for system
operation
• system memory that stores all operating software programs and data
unique to each system
• the disk drive unit that provides mass storage for operating programs and
data
• I/O interfaces that provide an information exchange between the user and
the system

CS 1000M and Meridian 1 “core” processor cards support extensive

networking and provide intensive use of software features and applications,
including call centers of up to 1000 agents.

The core software architecture incorporates a real-time multitasking

operating system, as well as code that delivers features and call processing.
This architecture guarantees feature transparency to the user upgrading the
core CPU. The core architecture also provides significant operation,
administration, and maintenance enhancements for the people who work
closely with the system software and hardware.

All core overlays reside in Dynamic Random Access Memory (DRAM) after
they are loaded from the hard disk during an initial software load (software is
shipped on redundant hard disks). The Resident Overlays featured in core-
based systems ensure subsecond speeds in accessing the overlays.

The capacity enhancement in the core architecture is provided by the core

control complex. In Large Systems with cPCI Core/Network modules, the
core control complex refers to the two Core/Network modules (Core/

553-3021-010 Standard 2.00 September 2004

 System architecture Page 39 of 82

Network 0 and Core/Network 1). The Core and Core/Network modules are
fully redundant, with Core 1 duplicating the contents of Core 0.

The backplane in the CS 1000M MG and Meridian 1 PBX 81C CP PII Core
modules is a compact Peripheral Component Interconnect (PCI) data bus.
PCI provides a high-speed data path between the CPU and peripheral devices.
PCI runs at 33MHz, supports 32- and 64-bit data paths and bus mastering.

The backplane in the system is divided into “core” and “network” sides. The
“network” side allows up to eight network cards to be installed for call
processing capability.

In the CS 1000M HG and Option 51C Core/Network module, the core side
houses the following equipment:
• one Call Processor (CP) card
• one Input/Output Disk Unit with CD-ROM (IODU/C)
• one Core-to-Network Interface (CNI or CNI-3) card

In the CS 1000M SG and Meridian 1 PBX 61C CP PII Core/Network

module, the core side houses the following equipment:
• one Call Processor Pentium II® (CP PII) card
• one Multi-Media Disk Unit (MMDU)
• one System Utility (Sys Util) card
• one Core-to-Network Interface (cCNI) cards
• one System Utility Transition (Sys Util Trans) card
• four cCNI Transition (cCNI Trans) cards

Cabling between the CP cards allows memory shadowing and dual-CPU

operation.

The CNI and CNI-3 cards provide the interface between the IPB and the
network shelf, and between the CP card and three-port extender cards in the
network shelf. Each CNI card provides two ports. Each CNI-3 card supports
three ports. In a typical configuration, three CNI-3 cards support eight
network groups.

Communication Server 1000M and Meridian 1 Large System Overview

Page 40 of 82 System architecture

The NT4N43 Multi Media Disk Unit with CD-ROM (MMDU) uses an
industry-standard 2MB floppy drive and CD-ROM drive to install system
software from a CD-ROM.

The system uses a Security Device and an electronic Keycode to perform

security authentication. The security device is located on the utility card. The
Keycode file contains information about which features the system provides
as well as License limits.

Core/Net modules diagnose faults in field-replaceable units for all core

hardware, including cables. In case of a failure, a message appears on the
system terminal and on the Liquid Crystal Display (LCD) of the CP card. All
messages can be stored in a file for future diagnostics.

Figure 14 on page 41 provides a block diagram of the CS 1000M SG and

Meridian 1 PBX 61C CP PII core architecture.

In the CS 1000M MG and Meridian 1 PBX 81C cPCI Core/Network module,

the core side houses the following equipment:
• one Call Processor Pentium II® (CP PII) card
• one Multi-Media Disk Unit (MMDU)
• one System Utility (Sys Util) card
• up to four Core to Network Interface (cCNI) cards
• one System Utility Transition (Sys Util Trans) card
• four cCNI Transition (cCNI Trans) cards

Core/Net modules diagnose faults in field-replaceable units for all core

hardware, including cables. In case of a failure, a message appears on the
system terminal and on the LCD of the faceplate of the utility card.

Core to Core Ethernet connection (LAN2 to LAN2) between the CP PII cards
allows memory shadowing and dual-CPU operation.

The Multi-Media Disk Unit (MMDU) uses an industry-standard 2MB floppy

drive, with a formatted capacity of 1.44 MB, a CD-ROM drive to install
system software from a CD-ROM, and a hard disk.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 41 of 82

Figure 14
CS 1000M SG and Meridian 1 PBX 61C CP PII core complex

Common control section of Interface section of

Core/Network Module 0 Core/Network Module 0

Inter-processor Bus (IPB) XNETs,

ENETs,
SDIs and
PS cards

Call
3-Port
Processor
IODU/C CNI extender
(3PE)
(CP) Clock
Controller PRI/DTI

Inter-CPU SCSI Bus

cable for (daisy-
redundancy chained
control cables)

Clock
Controller PRI/DTI

CP IODU/C CNI 3PE

Line, trunk, SDI,

peripheral
controller cards
IPB

Common control section of Interface section of

Core/Network Module 1 Core/Network Module 1
553-AAA2052.eps

The cCNI Transition cards connect the Core module cards to the 3PE cards
in the Network modules. Each Core module contains between one and four
cCNI cards. Since each cCNI card can connect up to two Network groups,
each Core is connected to a minimum of two groups and a maximum of eight
groups. The number of cCNI cards in a system depends on the number of
Network groups in that system. The first cCNI card that connects to Network
group 0 and group 1 is installed in slot c9 of each Core/Net module. Each
additional cCNI card is installed in ascending order from slots c10 to c12.

Communication Server 1000M and Meridian 1 Large System Overview

Page 42 of 82 System architecture

The System Utility card supports Card ID. The card provides an interface
between the security device and the computer, and an interface between the
XSM and display panel for each Core/Net card cage. This card also includes
a switch on the faceplate to enable or disable the Core cards.

The System Utility Transition card provides connections for the security
device, the system monitor, and the status panel. This Transition card is
mounted on the rear of the backplane (back side) directly behind the System
Utility card.

The cCNI Transition cards provide the cable connections to the 3PE
Termination Panel at the back of the module. A cCNI Transition card is
mounted directly behind each cCNI card (on the back of the Core backplane).
Four cCNI Transition cards for Core/Net module are installed in the factory
regardless of how many cCNI main cards are configured for the system.

Network interface
Network switching, based on digital multiplexed loops, interconnects
peripheral ports. A loop transmits voice, data, and signaling information over
a bidirectional path between the network and peripheral ports.

Network cards digitally transmit voice and data signals, using space
switching and Time Division Multiplexing (TDM) technology. Network
switching also requires service loops (such as conference and TDS loops),
which provide call progress tones and outpulsing.

The following cards provide basic network switching control:

• The NT8D04 Superloop Network card provides switching for four loops
grouped together in an entity called a superloop.
• The NT5D12 Digital Trunk card provides switching for two DTI/PRI
loops and takes one network slot.
• The NT5D97 Digital Trunk card provides switching for two DTI2/PRI2
loops and takes one network slot.

The NT5D12 and NT5D97 Digital Trunk cards replace the functionality of
the QPC720 DTI/PRI and QPC414 Network card, which provided switching
for two loops.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 43 of 82

Network organization
Network loops are organized into groups. A system is generally configured
as one of the following:
• a half group system (CS 1000M HG) that provides up to 16 loops
• a single group system (CS 1000M SG) that provides up to 32 loops
• a multi-group system (CS 1000M MG) that provides up to 256 loops

The Fiber Junctor Interface (FIJI) cards in the Network modules are
connected with fiber-optic cables to form a Dual Ring Fiber Network. This
network consists of two separate rings: one ring connects all the Network
shelf 0’s while the second ring connects all the Network shelf 1’s. This
network communicates on a subset of the Sonet OC12c protocol (622 MB
bandwidth on each ring).

The Dual Ring fiber-optic cable configuration provides complete non-

blocking communication between the Network groups; this eliminates the
incidence of busy signals for calls switched between groups. Each FIJI card
can handle 32 PCM links. A system of eight Network groups provides 8000
timeslots for 4000 simultaneous conversations.

This Dual Ring network is fully redundant: each of the fiber-optic cable rings
is capable of handling the traffic for an entire eight group network. If a fault
in one ring is detected, the other ring automatically takes over call processing.
No calls are lost during the switchover.

The Dual Ring Fiber network operated under four states:

• Normal
— Traffic is shared between the two rings.
— Each FIJI card drives 480 timeslots.
• Full
— Traffic is handled by a single ring.
— Each FIJI card drives 960 timeslots
• Survival
— FIJI cards in both rings are used to maintain intergroup traffic.

Communication Server 1000M and Meridian 1 Large System Overview

Page 44 of 82 System architecture

• Disabled
— The ring is inactive and does not support call processing.

Superloop network configurations

By combining four network loops, the superloop network card makes 120
timeslots available to IPE cards. Compared to regular network loops, the
increased bandwidth and a larger pool of timeslots increases network traffic
capacity for each 120-timeslot bundle by 25 percent (at a P0.1 grade of
service).

The NT8D37 IPE module is divided into segments numbered 0–3 of four card
slots each (see Figure 15). Segment 0 consists of slots 0–3, segment 1 consists
of slots 4–7, segment 2 consists of slots 8–11, and segment 3 consists of slots
12–15.

Figure 15
Superloop segments in the IPE module

Segment 0 Segment 1 Segment 2 Segment 3

NT8D01 Controller Card

Intelligent Intelligent
line and trunk line and trunk
cards cards

0 1 2 3 4 5 6 7 Cont. 8 9 10 11 12 13 14 15

553-3141

553-3021-010 Standard 2.00 September 2004

 System architecture Page 45 of 82

A superloop is made up of NT8D04 Superloop Network cards, NT8D01AC

or NT8D01BC Controller-4 or NT8D01AD Controller-2 cards, and from one
to eight IPE segments. The NT8D01BC Controller-4 replaces the
NT8D01AC and NT8D01AD Controller cards for replacements and new
installations.

A number of superloop-to-segment configurations are possible:

• one segment per superloop requires four superloop network cards and
one controller-4 card
• two segments per superloop requires two superloop network cards and
one controller-2 card
• four segments per superloop requires one superloop network card and
one controller-2 card
• eight segments per superloop requires one superloop network card and
two controller-2 cards
• one segment per superloop/three segments on a second superloop
requires two superloop network cards and one controller-2 card
• two segments per superloop/six segments on a second superloop requires
two superloop network cards and two controller-2 cards

As an example of a superloop configuration, Figure 16 on page 46 shows

eight segments per superloop. If a segment in this configuration is equipped
with analog line cards and trunk cards, a high concentration environment of
120 timeslots to 128–512 Terminal Numbers (TNs) is provided. If half of the
data TNs on digital line cards are enabled, this configuration provides a
concentration of 120 timeslots to 768 TNs.

For a detailed description of superloop-to-segment configurations, see

Communication Server 1000M and Meridian 1: Large System Planning and
Engineering (553-3021-120).

Communication Server 1000M and Meridian 1 Large System Overview

Page 46 of 82 System architecture

Figure 16
Eight segments per superloop

Segment 0 Segment 1 Segment 2 Segment 3

NT8D01 Controller-2 Card

Intelligent Intelligent
line and trunk line and trunk
cards cards

0 1 2 3 4 5 6 7 Cont. 8 9 10 11 12 13 14 15

NT8D04
Superloop
Network Card

Segment 0 Segment 1 Segment 2 Segment 3

NT8D01AD
Controller-2
Card

553-3145

553-3021-010 Standard 2.00 September 2004

 System architecture Page 47 of 82

Intelligent Peripheral Equipment

Using pulse code modulation (PCM), Intelligent Peripheral Equipment (IPE)
converts analog signals to digital signals before switching is performed by the
network. This conversion method samples the amplitude of the analog signal
at a rate of twice the highest signal frequency, then converts the amplitude
into a series of coded pulses. For telecommunications, the PCM-sampling
frequency standard is 8 kHz.

Compressing-expanding (companding) PCM is a standard technique for

using 8-bit words to efficiently represent the range of voice and data signals.
Two standards for companding, A-Law and µ-Law, are recognized
worldwide. IPE conforms to both standards; the standard required is selected
through software.

IPE is associated with network loops. IPE cards are supported by NT8D04
Superloop Network Card loops. The traffic requirements of all IPE cards
provisioned on a particular network loop must match the traffic capacity of
that loop.

IPE includes:
• controller cards that provide timing and control sequences and
monitoring capabilities
• analog and digital line and trunk cards that provide interfaces to
equipment outside the modules (such as telephones, data terminals, and
trunks)

Communication Server 1000M and Meridian 1 Large System Overview

Page 48 of 82 System architecture

Table 5 lists the IPE cards and the number of terminations each supports.

Table 5
Intelligent Peripheral Equipment cards (Part 1 of 2)

Number of
Intelligent Peripheral Equipment cards terminations

Controller cards:

NT8D01 Controller Card-4 N/A

NT8D01 Controller Card-2 N/A

Line cards:

NT1R20 OPS Analog Line card 8

NT5K02 Analog Line card 16

NT5K96 Analog Line card 16

NT8D02 Digital Line card 16 to 32

NT8D09 Analog Message Waiting Line card 16

Trunk cards:

NT5K07 Universal Trunk card 8

NT5K17 Direct Dial Inward Trunk card 8

NT5K18 Extended CO Trunk card 8

NT5K19 E&M/2280 Hz Trunk card 4

NT5K36 Direct Inward/Direct Outward Dial card 4

NT5K70 Extended CO Trunk card 8

NT5K71 Extended CO Trunk card 4

Note: Terminal number (TN) density per segment is 16 to 128 TNs, with
64 to 512 TNs per IPE module. The maximum TN density assumes all
slots are equipped with NT8D02 Digital Line cards with 16 voice and 16
data TNs provisioned. A typical mix of line and trunk cards yields a
nominal density of 64 TNs per segment, 256 TNs per IPE module.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 49 of 82

Table 5
Intelligent Peripheral Equipment cards (Part 2 of 2)

Number of
Intelligent Peripheral Equipment cards terminations

NT5K72 E&M Trunk card 4

NT5K82 Extended CO Trunk card 8

NT5K83 E&M Trunk card 4

NT5K84 Direct Inward Dial Trunk card 8

NT5K90 Extended CO Trunk card 8

NT5K93 Extended CO Trunk card 8

NT5K99 Extended CO Trunk card 8

NT8D14 Universal Trunk card 8

NT8D15 E&M Trunk card 4

NTAG03 Extended CO Trunk card 8

NTAG04 Extended CO/Direct Inward Dial card 8

NTAG36 Meridian Integrated Recorded 8

Announcement card

NTCK16 Generic Extended Flexible CO card 8

Special:

NT5K20 Extended Tone Detector card 8

NT5K48 Global Extended Tone Detector card 8

NT5K92 Direct Inward Dial Tester card 1

Note: Terminal number (TN) density per segment is 16 to 128 TNs, with
64 to 512 TNs per IPE module. The maximum TN density assumes all
slots are equipped with NT8D02 Digital Line cards with 16 voice and 16
data TNs provisioned. A typical mix of line and trunk cards yields a
nominal density of 64 TNs per segment, 256 TNs per IPE module.

Communication Server 1000M and Meridian 1 Large System Overview

Page 50 of 82 System architecture

Intelligent Peripheral Equipment remote location

In a local operating environment, IPE can be housed up to 15.2 m (50 ft) from
the Common Equipment. IPE installed in a remote location extends this
range, allowing approximately 112.6 km (70 miles) between local and remote
facilities.

This extension is achieved by converting multiplexed loop signals to a form

compatible with the commonly used T-1 type digital transmission system.
Refer to Table 5 on page 48 for a list of IPE cards that can be used at the
remote site.

Any medium that conforms to the DS-1 format (1.544 Mbps) can be used to
link local and remote sites, including digital microwave radio and fiber-optic
transmission systems.

Terminal equipment
Large Systems support a wide range of telephones, including multiple-line
and single-line telephones, as well as digital telephones with key and display
functions and data transmission capabilities. A range of options for attendant
call processing and message center applications is also available. In addition,
a number of add-on devices are available to extend and enhance the features
of telephones and consoles. Add-on devices include key/lamp modules, lamp
field arrays, handsets, and handsfree units. Refer to Telephones and
Consoles: Description, Installation, and Operation (553-3001-367) and
IP Phones: Description, Installation, and Operation (553-3001-368) for
more information.

Digital telephones
Analog-to-digital conversion takes place in the digital telephone itself, rather
than in the associated Peripheral Line card. This eliminates attenuation,
distortion, and noise generated over telephone lines. Signaling and control
functions are also handled digitally. Time Compression Multiplexing (TCM)
is used to integrate the voice, data, and signaling information over a single
pair of telephone wires.

For applications where data communication is required, Meridian 1 digital

telephones offer an integrated data option that provides simultaneous voice
and data communication over single pair wiring to a port on a digital line card.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 51 of 82

CS 1000M and Meridian 1 Large Systems support the following digital

telephones:

• M3901 Entry single-line telephone

• M3902 Basic single-line telephone
• M3903 Enhanced telephone
• M3904 Professional telephone
• M3905 Call Center telephone
• M3820 Digital telephone
• M3310 Digital telephone
• M3110 Digital telephone
• M2016S Secure Set

IP Phones
IP Phones bring voice and data to the desktop environment and connect
directly to the LAN through the Ethernet connection. The IP Phones translate
voice into data packets for transport using Internet Protocol (IP).

CS 1000M and Meridian 1 Large Systems support the following IP Phones:

• Nortel Networks IP Phone 2001
• Nortel Networks IP Phone 2002
• Nortel Networks IP Phone 2004
• Nortel Networks IP Softphone 2050
• Nortel Networks Mobile Voice Client (MVC) 2050
• Nortel Networks WLAN Handset 2210 and WLAN Handset 2211

Attendant consoles
Meridian 1 attendant consoles provide high-volume call processing.
Indicators and a 4 x 40 liquid crystal display (LCD) provide information
required for processing calls and personalizing call answering. Loop keys and
Incoming Call Indicator (ICI) keys allow the attendant to handle calls in

Communication Server 1000M and Meridian 1 Large System Overview

Page 52 of 82 System architecture

sequence or to prioritize answering for specific trunk groups. An optional

busy lamp field provides the attendant with user status.

Meridian attendant consoles support attendant message center options. The

attendant console can be connected to a PC to provide electronic directory,
dial-by-name, and text messaging functions. All call processing features can
be accessed using the computer keyboard.

Power equipment
Large Systems provide a modular power distribution architecture.

Each column includes:

• a system monitor that provides:
— power, cooling, and general system monitoring capabilities
— error and status reporting down to the specific column and module
• circuit breaker protection
• a cooling system with forced air impellers that automatically adjusts
velocity to meet the cooling requirements of the system
• backup capabilities

Each module includes:

• an individual power supply unit with shut-off (switch or breaker)
protection
• a universal quick-connect power wiring harness that distributes input
voltages and monitor signals to the power supply

All options are available in both AC-power and DC-power versions. The
selection of an AC- or DC-powered system is determined primarily by
reserve power requirements and existing power equipment at the installation
site.

Although AC-powered and DC-powered systems have different internal

power components, the internal architecture is virtually identical. AC- and
DC-powered systems differ primarily in the external power components.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 53 of 82

AC power
AC-powered systems require no external power components and can plug
directly into commercial AC (utility) power. AC-powered systems are
especially suitable for applications that do not require reserve power. They
are also recommended systems that require reserve power with backup times
ranging from 15 minutes to 8 hours.

If reserve power is required with an AC-powered system, an Uninterruptible

Power Supply (UPS), along with its associated batteries (either internal or
external to the unit), is installed in series with the AC power source (see
Figure 17). An AC-powered system that does not require long-term backup
can benefit from a UPS with short-term backup because the UPS typically
provides power conditioning during normal operation, as well as reserve
power during short outages or blowouts.

Figure 17
External AC-power architecture with reserve power

Large System
(rear view)
Battery bank
(may be
inside UPS)

– 48 V DC

AC AC voltage
input UPS

Required Optional reserve power

553-3201

Communication Server 1000M and Meridian 1 Large System Overview

Page 54 of 82 System architecture

DC power
DC-powered systems always require external rectifiers to convert
commercial AC power into the standard –48 V DC required within the system
(see Figure 18). Batteries are generally used with DC-powered systems, as
the traditional telecommunications powering method is for the rectifiers to
continuously charge a bank of batteries, while the system power “floats” in
parallel on the battery voltage. However, batteries are only required if reserve
power is needed.

A variety of rectifiers and distribution equipment can be used to supply

external DC power. Existing customer equipment can be used or a system that
Nortel Networks either supplies or recommends, such as the Small or Large
Candeo, can be used. The Small Candeo is appropriate for Single Group or
Multi Group systems that do not require more than 300 A, while the Large
Candeo is suitable for larger systems. In all cases, equipment for rectification
and distribution is required, while reserve batteries are optional.

Figure 18
External DC-power architecture with reserve power

Large System
(rear view)

– 48 V DC

AC – 48 V DC
input Rectifier

Required Optional reserve power

553-3202

553-3021-010 Standard 2.00 September 2004

 System architecture Page 55 of 82

Candeo DC power system

The Candeo platform provides a simple, quick-to-deploy, and easy-to-operate
power solution. Based upon modular building blocks (rectifiers, System
Manager, DC distribution, and battery connection modules), the system is
designed to power -48 V DC applications. The Large Candeo power system
uses 50 A rectifiers and has a capacity of 1000 A; the Small Candeo
(SP48300) uses 30 A rectifiers and has a capacity of 300 A. Both Large and
Small Candeo systems provide “plug and walk-away” installation and setup.
The platform can be reconfigured or expanded while it remains online.

Signaling Server
CS 1000M systems use a Signaling Server. The Signaling Server is an
industry-standard, PC-based server that provides a central processor to drive
H.323 and Session Initiation Protocol (SIP) signaling for IP Phones and
IP Peer Networking. It provides signaling interfaces to the IP network using
software components that operate on the VxWorks™ real-time operating
system.

The Signaling Server has both an ELAN and TLAN Ethernet interface. The
Signaling Server communicates with the Call Server through ELAN subnet.

The Signaling Server is mounted in a 19-inch rack. The Signaling Server can
be installed in a load-sharing redundant configuration for higher scalability
and reliability.

The following software components operate on the Signaling Server:

• Terminal Proxy Server (TPS)
• SIP/H.323 Signaling Gateways
• Network Routing Service (NRS)
• Element Manager

All the software elements can coexist on one Signaling Server or reside
individually on separate Signaling Servers, depending on traffic and
redundancy requirements for each element.

Communication Server 1000M and Meridian 1 Large System Overview

Page 56 of 82 System architecture

For more information about H.323 and SIP Trunking, refer to IP Peer
Networking: Installation and Configuration (553-3001-213).

Terminal Proxy Server

The Terminal Proxy Server (TPS) acts as a signaling gateway between the IP
Phones and the Call Server using the UNIStim protocol. It performs the
following functions:
• converts the IP Phone UNIStim messages into messages the Call Server
can interpret
• allows IP Phones to access telephony features provided by the Call
Server

The TPS also controls IP Phone registration.

SIP/H.323 Signaling Gateways

SIP/H.323 Signaling Gateways are software components configured on
virtual loops, similar to IP Phones. They bridge existing call processing
features and the IP network. They also enable access to the routing and
features in the MCDN feature set.

Note 1: The SIP/H.323 Signaling Gateway must register with the

Network Routing Service (NRS).

Note 2: Virtual TNs enable you to configure service data without

hardwiring IP Phones to the CS 1000M system. Virtual TNs are
configured in LD 97.

To support IP Peer Networking, dual Call Servers in a CS 1000M must be

associated with Signaling Servers that run SIP/H.323 Signaling Gateway
software. The number of Signaling Servers required depends on the capacity
and level of redundancy required.

Network Routing Service

The Network Routing Service (NRS) application provides network-based
routing, combining the following into a single application:
• H.323 Gatekeeper — The H.323 Gatekeeper provides central dialing
plan management and routing for H.323-based endpoints and gateways.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 57 of 82

• SIP Redirect Server — The SIP Redirect Server provides central

dialing plan management and routing for SIP-based endpoints and
gateways.
• NRS Database — The NRS database stores the central dialing plan in
XML format for both the SIP Redirect Server and the H.323 Gatekeeper.
The SIP Redirect Server and H.323 Gatekeeper both access this common
endpoint and gateway database.
• Network Connect Server (NCS) — The NCS is used only for Media
Gateway 1000B (MG 1000B) and Virtual Office solutions.
• NRS Manager web interface — The NRS provides its own web
interface to configure the SIP Redirect Server, the H.323 Gatekeeper,
and the NCS.

The NRS application provides routing services to both H.323- and SIP-
compliant devices. The H.323 Gatekeeper can be configured to support
H.323 routing services, while the SIP Redirect Server can be configured to
support SIP routing services. The H.323 Gatekeeper and the SIP Redirect
Server can reside on the same Signaling Server.

Each system in an IP Peer network must register to the NRS. The NRS
software identifies the IP addresses of systems based on the network-wide
numbering plan. NRS registration eliminates the need for manual
configuration of IP addresses and numbering plan information at every site.

Element Manager
Element Manager is a simple and user-friendly web-based interface that
supports a broad range of system management tasks, including:
• configuration and maintenance of IP Peer and IP telephony features
• configuration and maintenance of traditional routes and trunks
• configuration and maintenance of numbering plans
• configuration of Call Server data blocks (such as configuration data,
customer data, Common Equipment data, D-channels)
• maintenance commands, system status inquiries, backup and restore
functions
• software download, patch download, patch activation

Communication Server 1000M and Meridian 1 Large System Overview

Page 58 of 82 System architecture

Element Manager has many features to help administrators manage systems

with greater efficiency. Examples are as follows:
• Web pages provide a single point-of-access to parameters that were
traditionally available through multiple overlays.
• Parameters are presented in logical groups to increase ease-of-use and
speed-of-access.
• The "hide or show information" option enables administrators to see
information that relates directly to the task at hand.
• Full-text descriptions of parameters and acronyms help administrators
reduce configuration errors.
• Configuration screens offer pre-selected defaults, drop-down lists,
checkboxes, and range values to simplify response selection.

The Element Manager web server resides on the Signaling Server and can be
accessed directly through a web browser or Optivity Telephony Manager
(OTM). The OTM navigator includes integrated links to each network system
and their respective instances of Element Manager.

Software architecture
The superloop network card and IPE cards contain microprocessors that
allow software changes and upgrades from the disk drive unit to be
downloaded. These downloads can occur automatically, after a system
reload, or manually through software program commands.

Call processing, maintenance, and administration are controlled by software

programs stored either as firmware programs, as software programs resident
in system memory, or as nonresident programs on disk. The information that
describes system configuration and associated IPE is called office data. This
data resides in the system memory and on disk.

Firmware
Firmware provides fundamental programs consisting of hard-wired logic
instructions stored in programmable read-only memory (PROM). Firmware
programs manipulate data in the central processor and control input/output
operations, error diagnostics, and recovery routines.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 59 of 82

Software
Software programs consist of instruction sequences that control call
processing, IPE, administration, and maintenance functions. Several generic
software programs with optional feature packages are available.

Office data
Office data describes the characteristics of the system in terms of
configuration and call-dependent information, such as features and services.
Office data is arranged in blocks defining IPE, system configuration, and
transient data.

Resident programs
Resident programs are always available in memory during system operation.
Some resident programs are permanently programmed into the ROM portion
of system memory. Other resident programs are automatically loaded into
system memory at system power-up.

Resident programs include:

• Error Monitor, which continuously monitors call processing
• Initialize Program, which locates faults, rebuilds data, and releases
reserve memory areas
• Overlay Loader, which locates, checks, and loads programs into the
overlay area
• Overload Monitor, which monitors the volume of system messages and
determines where overloads occur
• Resident Trunk Diagnostic, which monitors all trunk calls
• System Loader, which loads resident programs from the disk drive unit
into system memory at power-up
• Traffic Monitor, which examines the system schedule, transfers traffic
data from accumulating to holding registers, and produces reports

Communication Server 1000M and Meridian 1 Large System Overview

Page 60 of 82 System architecture

All software programs, including the nonresident programs listed in the

following section are resident in, and accessible from, the memory on the
cards listed above.

Nonresident programs
Nonresident programs are stored on data disks and loaded into the overlay
area of system memory to perform specific tasks. They are removed from the
overlay area when no longer required. Nonresident programs can be loaded
automatically, under program control, or manually, through software
commands.

Nonresident programs are manually loaded into memory through the system
terminal (or maintenance telephone). A terminal can be configured as an
input-only, output-only, or input and output device.

Software programs provide the system interface for maintenance, service

change, and traffic measurement. Each program is independent and has its
own specific set of commands and formats. These programs run concurrently
with normal call processing without interfering with system traffic.

There are five main categories of nonresident programs:

• service change and print routines
• maintenance diagnostics
• traffic
• equipment data dump
• software audit

Service change and print routines

Service changes do not usually require hardware changes. Instead, the service
administration programs are used to create or modify all aspects of the system
from individual feature key assignments to complete system configurations.
There are also programs and print routines for retrieving data from the system
to check the status of office data assignments.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 61 of 82

Maintenance diagnostics
These programs are the primary instrument for clearing system faults.
Individual programs are used for automatically or manually testing the
Common Equipment and IPE. The programs can be loaded into the overlay
area at the request of maintenance personnel, or as part of a daily maintenance
routine automatically initiated by the system at a specified time. In addition,
background and signaling diagnostic routines can occupy the overlay area
when it is not in use.

Traffic
All systems are equipped with traffic data accumulation programs. There is
also a resident traffic print program that examines the schedules, transfers
data from accumulating to holding registers in accordance with schedules,
and prints the traffic data. In addition, there is a traffic program used to query
and modify schedules, options, and thresholds.

Equipment data dump

After making service changes, the changes must be saved to disk in order to
save them. When the equipment data dump program is run, all the office data
in the read/write memory is written to the system disk. The program can be
run automatically during the midnight routine or on a conditional basis (for
example, a data dump would only occur if a software service change has been
made). It can also be run manually through the system terminal.

The data dump program is also used to install a new generic version or issue
and capture protected data store information (such as speed call lists) that may
be changed by a user.

Software audit
This program monitors system operation and gives an indication of the
general state of the system operation. The program is concerned mainly with
the system software. When a software problem is encountered, the program
attempts to clear the problem automatically.

Communication Server 1000M and Meridian 1 Large System Overview

Page 62 of 82 System architecture

Configuration options
Large Systems offer the following configuration options to support increased
system redundancy:
• Fiber Remote IPE
• Carrier Remote IPE
• Branch Office
• Geographic Redundancy

Fiber Remote IPE

Large Systems can be configured in a distributed system to support remote
subscribers, using Remote IPE modules or small cabinets. Fiber-optic links
are used to connect the Remote IPE modules and small cabinets to the PBXs.

In a distributed system, subscriber connections are the same at local IPE

modules as they are at Remote IPE modules or small cabinets. Furthermore,
because Remote IPE equipment uses common and network equipment from
the local system, subscriber functions and features are the same at local and
remote sites.

Figure 19 on page 63 illustrates the fiber-optic connection between a local

system and remote system.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 63 of 82

Figure 19
Large System to Remote IPE site

Local Site Remote Sites

Fiber management
frame Wall-mounted
Large System Fiber Remote IPE

IPE
IPE
Fiber Peripheral
Controller card
IPE
Fiber-optic span

Core/Net

I/O panel at the Floor-standing

rear of the module Fiber Remote IPE

Core/Net
IPE
Optical
connectors

Fiber-optic span

Fiber Superloop Network cards Fiber Peripheral Controller card

553-AAA0558

Fiber Remote Multi-IPE Interface

The Fiber Remote Multi-IPE Interface links a Large System with one or more
Remote IPE sites to provide Meridian 1 Large System functionality. Since the
remote IPE system uses the Common Equipment and Network Equipment of
the associated local Large System, it can deliver the same features and
functionality as the local system. Figure 20 on page 65 illustrates the fiber-
optic connection between the local system and remote system.

Communication Server 1000M and Meridian 1 Large System Overview

Page 64 of 82 System architecture

The Fiber Remote Multi-IPE Interface links the local and remote systems
using a fiber-optic link over a single-mode optical fiber.

The Fiber Remote Multi-IPE Interface is available in four options which

allow the same configuration of the superloop connections at the remote site
as the configuration of the IPE modules at the local site:
• Single-mode fiber supporting four superloops
• Single-mode fiber supporting two superloops
• Muli-mode fiber supporting four superloops
• Multi-mode fiber supporting two superloops

553-3021-010 Standard 2.00 September 2004

 System architecture Page 65 of 82

Figure 20
Meridian 1 Large System to Remote IPE connection over fiber-optic link

Meridian 1 Large System

Local site

Meridian 1

Fiber Remote Multi-IPE Interface units

1-4 Superloops
1-4 Superloops
Fiber-optic Remote IPE
Link Remote site

Meridian 1

SDI Cable

System Monitor Terminal Terminal System Monitor

Cable (J5 toJ6) Cable (J5 to J5)

553-7119
Modem Modem

Refer to Fiber Remote IPE: Description, Installation, and Maintenance (553-

3021-354) for more information on Fiber Remote IPE. For more on the Fiber
Remote Multi-IPE Interface, refer to Fiber Remote Multi-IPE Interface:
Description, Installation, and Maintenance (553-3001-356).

Carrier Remote IPE

The Carrier Remote IPE provides functionality by installing only IPE
modules and IPE cards at a distant site. The Remote IPE shares the system’s

Communication Server 1000M and Meridian 1 Large System Overview

Page 66 of 82 System architecture

Common and Network Equipment to provide the same functions and features
to remote subscribers that are available to local system subscribers.

A floor-standing column or a wall-mounted cabinet Carrier Remote IPE is

installed at the remote site and is connected to the Meridian 1 Large System
using T1 or E1 connection. Figure 21 on page 67 illustrates the connection
between the local system and remote system.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 67 of 82

Figure 21
Meridian 1 Large System to Carrier Remote IPE links

Local Site Remote Sites

Wall-mounted
Large System Carrier Remote IPE

Remote Carrier
IPE Interface Card
IPE
I/O Panel
IPE
Private carrier span
Telco Demarc
Core/Net

Public network
CO
Direct cable
655 feet Floor-standing
Core/Net Carrier Remote IPE

IPE IPE

Local Carrier
Interface Cards
Colocated Carrier IPE Remote Carrier
Interface Card
553-AAA0556

For more information on Carrier Remote IPE, refer to Carrier Remote IPE:
Description, Installation, and Maintenance (553-3021-355).

Communication Server 1000M and Meridian 1 Large System Overview

Page 68 of 82 System architecture

Branch Office
The Branch Office feature extends system features from a main office to one
or more branch offices.

A branch office is an MG 1000B Core connected to an IP PBX at the main

office over a LAN or a WAN. This configuration enables a secondary
location to centralize the call processing of its IP-based communications
network. The Call Server at the main office provides the call processing for
the IP Phones in both the main office and branch offices. The MG 1000B
Core provides call processing functionality to local digital telephones and
analog devices. The MG 1000B Core also provides digital and analog trunk
access to the local Public Switched Telephone Network (PSTN).

The branch office connects to the main office over Virtual Trunks on a LAN/
WAN. The main office transmits and controls IP Phone calls and IP network
connections. If the main office fails to function, or if there is a network
outage, the MG 1000B Small System Controller (SSC) provides service to the
telephones located in the branch office. This enables the IP Phones to survive
the outage between the branch office and the main office.

A branch office can be created as a new hardware configuration, or by

converting an existing Small System to a branch office. The functionality is
the same in both configurations, with one additional feature (Meridian Mail)
supported in the converted system.

For more information on the Branch Office feature, refer to Branch Office:
Installation and Configuration (553-3001-214).

Geographic Redundancy
Geographic Redundancy enables a customer to duplicate the entire redundant
processing core of a CS 1000M SG or CS 1000M MG system at a remote
location, at any distance, over the customer WAN. The duplicate core can
then take over processing if the primary system fails for any reason.
Geographic Redundancy also offers automatic database replication between
main and standby systems to promote a smooth transition. When this
configuration is implemented, the customer enhances the disaster recovery
capability of the network and further secures ultra-high reliability.

553-3021-010 Standard 2.00 September 2004

 System architecture Page 69 of 82

Note: Geographic Redundancy capabilities only apply to IP elements,

for example, to IP Phones and Media Gateways. Geographic
Redundancy does not apply to TDM elements.

For more information on the Geographic Redundancy feature, refer to

Communication Server 1000: System Redundancy (553-3001-307).

Communication Server 1000M and Meridian 1 Large System Overview

Page 70 of 82 System architecture

553-3021-010 Standard 2.00 September 2004

78

Page 71 of 82

List of terms
AC
Alternating Current

analog
A process that models information in the form of a continuously varying
parameter such as current, voltage, or phase.

analog signal
A signal that varies in a continuous manner such as voice or music. An analog
signal can be contrasted with a digital signal, which represents only discrete
states. The signal emitted by a data set has both analog and discrete
characteristics.

architecture
The interrelationship between the parts of a system; the framework of a
system.

backplane
A printed circuit board that extends across the width of the card cage and
connects to the circuit card connectors.

battery backup
System power furnished by standby batteries that are charged by a charger. If
commercial power fails, the batteries maintain service for a limited period of
time, determined by the size of the batteries and the traffic on the system.

capacity
The information-carrying ability of a telecommunications facility, group,
network, or system measured in bits per second (bps).

Communication Server 1000M and Meridian 1 Large System Overview

Page 72 of 82 List of terms

card cage
A frame for holding circuit cards in a module; also called a card chassis.

CBT
Core Bus Terminator

CE
Common Equipment

Central Office (CO)

The site where a telephone company terminates customer lines and houses the
switching equipment that interconnects those lines.

central processing unit (CPU)

The main portion of a computer that contains the primary storage, arithmetic
and logic units, and the control unit (may also mean a mainframe computer).

circuit cards
Cards which carry the electronics for particular functions (such as memory
and switching functions). Most cards are housed in the card cage in a module
and connect to the backplane. Some cards must be installed in dedicated slots
in a card cage. (Also called circuit packs or boards.)

CNI
Core-to-Network Interface

CO
See Central Office.

Common Equipment (CE)

A hardware subsystem that houses one or more central processing units
(CPUs), memory cards, disk drive units, and service cards.

configuration
A group of machines (hardware) that are interconnected and are programmed
to operate as a system.

553-3021-010 Standard 2.00 September 2004

 List of terms Page 73 of 82

CP
Call Processor

cPCI®
Peripheral Component Interconnect. PCI provides a high-speed data path
between the CPU and peripheral devices (video, disk, network, etc.).

cPCI Transition card

Peripheral Component Interconnect Transition Card. Connects the Core
module cards to the 3PE cards in the Network modules.

CP PII®
The successor to the Pentium Pro from Intel. Pentium II refers to the Pentium
II CPU chip.

CPU
Central Processing Unit

DC
Direct Current

diagnostic programs
Software routines used to test equipment and identify faulty components

digital signal
A signal made up of discrete, noncontinuous pulses whose information is
contained in the duration, periods, and/or amplitude

DTR
Digitone Receiver

electromagnetic interference (EMI)

Unwanted electromagnetic static coupling, such as a ham radio signal being
heard on a television, or causing static noise interference.

firmware
A set of instruction sequences stored permanently in hardware (ROM).

Communication Server 1000M and Meridian 1 Large System Overview

Page 74 of 82 List of terms

input/output (I/O)
Exchange between a machine and end-user equipment.

IODU/C
Input/Output Disk Unit with CD-ROM

IPB
Inter-Processor Bus

IPE
Intelligent Peripheral Equipment

ISDN
Integrated Services Digital Network

line
A communication channel or circuit; an electrical path.

loop
A bidirectional path between network equipment and peripheral equipment.

module power supplies

Individual power units that generate the different DC voltages required by the
cards installed in each module.

cPCI Multi-Media Disk Unit (MMDU)

Peripheral Component Interconnect Multi-media Disk Unit. A unit
containing an industry-standard 2MB floppy drive (the floppy is a flexible
circle of magnetic material similar to magnetic tape, except that both surfaces
are used for recording. The drive grabs the floppy's center and spins it inside
its housing. The read/write head contacts the surface through an opening in
the plastic shell or envelope.)

Network Equipment
A hardware subsystem that provides digital multiplexed switching for voice,
data, and signaling paths.

553-3021-010 Standard 2.00 September 2004

 List of terms Page 75 of 82

office data
Office data represents system configuration data, peripheral equipment data,
and transient data (temporary) used for call processing.

PCM
Pulse Code Modulation.

pedestal
The bottom element in a column. Each pedestal houses a blower unit, an air
filter, the PDU (which contains the column circuit breakers), and the system
monitor.

power distribution unit (PDU)

Input power for CS 1000M Large System and Meridian 1 Large System are
brought into the pedestal to the PDU. The PDU distributes input power to the
column.

Pulse Code Modulation (PCM)

A modulation technique where the signal is converted from an analog to a
digital format by sampling the signal at periodic intervals and digitizing the
amplitude into a finite number of discrete levels

random-access memory (RAM)

A storage system or computer memory accessible by the user for either
storing or retrieving information. RAM is volatile memory.

read-only memory (ROM)

Storage system or computer memory that is “burned into” the microprocessor
chip and can be read, but not written to or modified. ROM is nonvolatile
memory.

redundancy
The duplication of software, or hardware, or both (such as redundant CPUs)
used as a standby in case one fails.

SDI
Serial Data Interface. A family of cards equipped with SDI ports provide the
I/O interface for the CS 1000M Large System and Meridian 1 Large System.

Communication Server 1000M and Meridian 1 Large System Overview

Page 76 of 82 List of terms

software
A set of programmed instruction sequences stored either as resident programs
in system memory or as nonresident programs stored on disk and loaded into
memory when needed.

software generic
A term used to identify the system software. Each software generic has a
series of releases, such as Release 25.

system monitor
A microprocessor-based circuit card that controls and monitors the status of
cooling equipment and power-related hardware and functions.

system utility card

Provides an interface between the security device and the computer.

TDS
Tone and Digit Switch

Time Compression Multiplexing (TCM)

The combination of two or more information channels into a single
transmission channel by assigning each information channel an exclusive
periodic transmission time interval.

TN
Terminal Number

top cap
A top cap is mounted on the top module of each column. It provides airflow
exits, EMI/RFI shielding, I/O cable entry and exit, and overhead cable-rack
mounting. The top cap covers thermal sensor assemblies for the column.

trunk
A single circuit between two points, both of which are switching centers or
individual distribution points.

553-3021-010 Standard 2.00 September 2004

 List of terms Page 77 of 82

universal equipment module (UEM)

A modular, self-contained hardware cabinet that houses a card cage, power
supply, backplane, circuit cards, and other basic equipment. When equipped,
the UEM becomes a specific type of module, such as a CPU module or
Network module.

UPS
Universal Power Supply

V AC
Voltage Alternating Current

V DC
Voltage Direct Current

Communication Server 1000M and Meridian 1 Large System Overview

Page 78 of 82 List of terms

553-3021-010 Standard 2.00 September 2004

 Page 79 of 82

Index
Numerics columns, 11
3PE Termination Panel, 42 common control complex, 38
common equipment circuit cards, 36
A companding (compressing-expanding) PCM, 47
AC-power, 13, 24, 53 Controller Cards, 48
air filters, 12 cooling systems, 52
airflow exits, 12 Core/Network Modules, 26
cPCI Core/Net module, 40
B
cPCI Multi-Media Disk Unit, 40
backup capabilities, 52
CPUs (central processing units)
batteries, 54
See also system characteristics under selected
blower units, 12 option
CS 1000M and Meridian 1
C hardware architecture, 36–55
cable-rack mountings, 12 product description, 11–12, 35
Call Processor cards, 39, 40 software architecture, 58
Call Processor Pentium II, 39, 40 CS 1000M HG and Meridian 1 Option 51C
base hardware, 15
Candeo DC power, 55
system characteristics, 15
cardcages, 12
CS 1000M MG and Meridian 1 Option 81C CP PII
cards base hardware, 23
in common control complex, 38 system characteristics, 22
common equipment circuit, 36
CS 1000M SG and Meridian 1 Option 61C CP PII
controller, 48
base hardware, 19
line, 48
system characteristics, 18
network interface circuit, 36
trunk, 48
D
cCNI Transition cards, 41, 42
DC-power, 13, 24, 54
CNI card, 39

Communication Server 1000M and Meridian 1 Large System Overview

Page 80 of 82 Index

Digital telephones, 50 memory, 38

disk drives, 38 See also system characteristics under selected
option
Dual Ring Fiber Network, 43
MPDUs (module power distribution units), 24
E
N
equipment data dump programs, 61
Network cards
Error Monitor program, 59
superloop, 44–46, 47, 58
error reporting, 52
network interface circuit cards, 36
F network loops, 44–46
See also system characteristics under selected
Fiber Junctor Interface (FIJI) card, 43 option
firmware, 58 Network Modules, 12
forced air impellers, 52 network switching, 42–46

H nonresident programs, 60
NT4N41 Core/Network module, 24
heat (thermal) sensor assemblies, 12
NT4N41- cPCI Core/Network Module, 26
I NT8D01 Controller Card-2, 48
Initialize program, 59 NT8D01 Controller Card-4, 48
input/output. See I/O (input/output) interfaces NT8D02 Digital Line Cards, 48
input voltage. See system characteristics under NT8D04 Superloop Network Cards, 45–46, 47, 58
selected option NT8D09 Analog Message Waiting Line Cards, 48
Intelligent Peripheral Equipment (IPE) Modules, NT8D14 Universal Trunk Cards, 49
12, 31, 44–46, ??–48, 58
NT8D15 E&M Trunk Cards, 49
InterGroup Modules, 24
NT8D35 Network Modules, 12, 28
I/O (input/output) interfaces, 12, 38
NT8D36 InterGroup Modules, 24
IPE Modules, 12, 31, 44–46, ??–48, 58
NT8D37 Intelligent Peripheral Equipment (IPE)
Modules, 12, 31, 44–46, 58
L
NT9D11 Core/Network Modules, 26
Line Cards, 48
loading, nonresident programs, 60 O
loops. See network loops office data, 59
Overlay Loader program, 59
M
Overload Monitor program, 59
maintenance diagnostics programs, 61
P
PCI, 39

553-3021-010 Standard 2.00 September 2004

 Index Page 81 of 82

PCM (pulse code modulation), 47 T

PCM (pulse code modulation) companding Terminal Equipment, 36, 50
(compressing-expanding), 47
thermal sensor assemblies, 12
PCM-sampling frequency standard, 47
TN (Terminal Number) density per segment, 48
PDU (Power Distribution Units), 12
top caps, 11, 12
pedestals, 11, 12 See also base hardware under selected option
See also base hardware under selected option
traffic measurement programs, 61
ports
Traffic Monitor program, 59
for I/O (input/output) interfaces, 12, 38
See also system characteristics under selected Trunk Cards, 48
option
U
Power Distribution Units (PDUs), 12
UEMs (Universal Equipment Modules), 11
power equipment, 36, 52–54
See also modules by name or number
R UPS (Uninterruptible Power Supply), 53
release compatibility. See system characteristics
V
under selected option
voltage. See system characteristics under selected
Remote Peripheral Equipment (RPE) Modules, 50
option
resident programs, 59
Resident Trunk Diagnostic program, 59
RPE Modules, 50

S
service change programs, 60
software audit programs, 61
software generic and release compatibility. See
system characteristics under selected
option
status reporting, 52
Superloop Network Cards, 44–46, 47, 58
System Loader program, 59
system memory. See memory
System Monitors, 12
System Utility card, 42
System Utility Transition card, 42

Communication Server 1000M and Meridian 1 Large System Overview

Page 82 of 82 Index

553-3021-010 Standard 2.00 September 2004

Family Product Manual Contacts Copyright FCC notice Trademarks Document
number Product release Document release Date Publish

Nortel Networks Communication Server 1000

Communication Server 1000M
and Meridian 1
Large System Overview

Copyright © 2003–2004 Nortel Networks

All Rights Reserved

Information is subject to change without notice.

Nortel Networks reserves the right to make changes in design
or components as progress in engineering and manufacturing
may warrant.

SL-1, Meridian 1, and Succession are trademarks of

Nortel Networks.

Publication number: 553-3021-010

Document release: Standard 2.00
Date: September 2004
Produced in Canada