Sourced in Canada.
The information in this document is subject to change without notice. The statements, configurations, technical
data, and recommendations in this document are believed to be accurate and reliable, but are presented without
express or implied warranty. Users must take full responsibility for their applications of any products specified in this
document. The information in this document is proprietary to Nortel Networks.
Nortel, the Nortel Logo, the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.
All other trademarks are the property of their respective owners.
Revision history
June 2007
This document has been up-issued to reflect changes in technical content
for CR Q01514742.
May 2007
Standard 01.01. This document is issued to support Communication Server
1000 Release 5.0. This document contains information previously contained
in the following legacy document, now retired: (553-3001-314).
September 2006
Standard 5.00. This document is up-issued for CR Q0143871, with an
update to Procedure 23, which resulted in no remote access over IP
Network to CS. See Page 297.
January 2006
Standard 4.00. This document is up-issued for CR Q01202736, with
information on reconfiguring Call Server alarm notification levels if
necessary when configuring Adaptive Network Bandwidth Management.
See pages 74 and 82
3
August 2005
Standard 3.00. This document is up-issued to support CS 1000 Release 4.5.
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: Branch Office (553-3023-221).
MG 1000B hardware platform17
Media Card MC32S18
Main and Branch Office running different releases18
Main Office and Branch Office Migration 18
How to get help19
Getting help from the Nortel web site19
Getting help over the telephone from a Nortel Solutions Center19
Getting help from a specialist by using an Express Routing Code19
Getting help through a Nortel distributor or re-seller20
Overview21
Contents21
What is Branch Office?22
Main Office and Branch Office Migration 24
MG 1000B (MGC) compared to the MG 1000B (SSC)24
MGC Serial Ports26
Main office hardware description28
MG 1000B platform hardware description29
5
Single CPU Implications 26
Dual CPU Implications 26
Terminal Server Support26
MGC serial port default configuration27
MGC serial ports configuration change in Overly 1727
CEMux Support27
Clock References28
MG 1000B Core31
MG 1000B Expander 33
Signaling Server34
Network Routing Service (NRS)35
Telephones 36
Voice Gateway Media Card37
Analog or digital trunk cards38
Analog or digital line cards38
Every Branch Office HLOC is shared with the main office96
No Branch Office HLOC is shared with the main office, but can be shared with
another Branch Office97
No Branch Office HLOC is shared with the main office or another Branch
Office98
Call between branch offices associated with different main office99
Every Branch Office HLOC is shared with the main office99
No Branch Office HLOC is shared with the main office or another Branch
Office102
Summary of provisioning procedures for Tandem Bandwidth Management104
Provisioning Example of Tandem Bandwidth Management105
Network using mixed Coordinated Dialing Plan and Uniform Dialing Plan111
Call between two local branch offices112
Call between branch offices associated with different main offices113
Network using CDP only115
Call between two local branch offices117
Call between branch offices associated with different main offices118
Bandwidth Management Support for Network Wide Virtual
Network Class of Service144
Network Routing Service (NRS)145
Trunk Route Optimization (TRO) 145
Virtual Office145
Feature packaging145
Feature implementation using Command Line Interface 145
Task summary list145
Sample printout146
Feature implementation using Element Manager 147
Zone configuration147
Diagnostics149
Maintenance155
Command Line Interface maintenance155
Element Manager maintenance155
Feature operation158
How the Branch Office feature works159
Contents159
Introduction160
Normal Mode and Local Mode operation160
Normal Mode 160
Local Mode160
Virtual Trunks 164
IP Phone calls165
Zones165
Vacant Number Routing165
Time of Day 166
MG 1000B IP Phone to local PSTN calls166
IP Phone to analog (500/2500-type) or digital telephone calls167
Conference calls167
Group Call168
Configuring non-zero S2 IP Addresses169
Points to remember170
Configuring the S2 IP Address parameter171
Multiple Appearance DN (MADN) 172
IP Phones with the same DN at the Branch Office172
IP Phones with the same DN at the main office 172
Emergency services172
Configuring ESA for emergency services173
Configuring SPN for emergency services174
Abbreviated Dialing174
MG 1000B Core interoperability176
Network Wide Redundancy Phase II and Network Music176
Emergency Services182
Zones182
Music on Hold182
ESN Access Codes182
Provisioning the IP Phones182
Configuration example for PSTN resources at the Branch Office183
Management185
Remote Access185
Element Manager185
Telephony Manger 3.1186
Set-Based Installation for IP Phones 186
Traffic measurement186
Call Detail Recording (CDR)187
Proactive Voice Quality management188
System security189
Adding a Branch Office191
Contents191
Introduction191
Main office requirements 192
Optional features193
Branch Office requirements193
Implementation summary194
Adding a CS 1000 Release 5.0 Branch Office to a Branch Office with a previous
software release196
Upgrade the entire network to CS 1000 Release 5.0197
Upgrade only the main office to CS 1000 Release 5.0198
IP Phone passwords and parameters215
MG 1000B IP Phone configuration218
MG 1000B IP Phone configuration using TM 3.01218
MG 1000B IP Phone configuration using LD 11 218
MG 1000B platform hardware installation221
Contents221
Installing an MG 1000B Core221
Readiness checklist222
Rack-mounting an MG 1000B Core or MG 1000B Expander 223
Installing cards227
Installing a Signaling Server228
Materials required228
Preparing for rack-mounting230
Rack-mounting232
Connecting and powering up the Signaling Server235
MG 1000B software installation239
Contents239
Signaling Server software installation 239
Materials required240
Creating the Signaling Server CD240
Installing the Signaling Server software241
Upgrading the SIgnaling Server software241
Signaling Server tools241
Signaling Server port speed243
Verifying a successful configuration244
Connecting the MG 1000B Core to the network244
Connecting the MG 1000B Core to the network244
Using Element Manager to configure the node247
Installing MG 1000B Hardware249
Installing the cards250
Installing a DSP Daughterboard250
Installing the MGC card251
Installing the CP PM card252
Summary of steps255
Configuring the Media Cards256
Configuring the trunks and lines256
Zone parameters256
Element Manager Branch Office zone configuration260
Adding the Branch Office endpoints to the NRS database260
MG 1000B telephones263
Contents263
Overview263
Installing and configuring IP Phones264
Password requirements265
Installing an IP Phone using the keypad265
Branch User Config 270
Transferring IP Phone data using TM 3.01274
Survivability test276
Installing IP Phones through LD 11279
Using the IP Phones281
Telephone Options282
Virtual Office Login on the Branch Office284
Test Local Mode286
Personal Directory, Callers List, Redial List 287
Set-Based Removal287
Analog and digital devices in the Branch Office288
Analog devices288
Digital devices288
Activating analog (500/2500-type) and digital telephones289
Routing ESA calls316
Configuring ESA for the Branch Office317
Element Manager ESA configuration 326
Emergency Service using Special Numbers (SPN) 327
CLID verification (CLIDVER)328
Networked M911328
Basic Emergency Services When VO Logged Out329
Contents329
Overview329
Configure ESA Data Block333
Warm Start333
Emergency Services For Client Mobility333
Active Call Fail Over334
Context Sensitive Soft Keys334
Element Manager335
Abbreviated Dialing configuration337
Contents337
Overview337
Recommended configuration337
Configuring Abbreviated Dialing338
Maintenance and diagnostics345
Contents345
Firmware downloads345
Enhanced UNIStim Firmware Download for IP Phones345
Troubleshooting 349
Signaling Server CLI commands354
isetShow354
clearLockout TN or IP 354
Call Server commands355
Verify CLID355
Print Branch Office zone information356
Enable/disable Branch Office zone features357
View status of Branch Office zone at main office Call Server357
Change/print PVQ notification levels 357
Print PVQ statistics358
Print inventory358
Procedure 1Printing intrazone and interzone statistics for a zone67
Procedure 2Displaying CAC parameters for one or more zones85
Procedure 3Provisioning Tandem Bandwidth Management106
Procedure 4Accessing the Zones web page147
Procedure 5Printing zone ALTPrefix 150
Procedure 6Show Status153
Procedure 7Enabling a zones Branch Office behavior156
Procedure 8Suppress Alternative Call Routing for NBWM alarms157
Procedure 9Configuring ESN and MG 1000B zones210
Procedure 10Setting the IP Phone Installers Password215
Procedure 11Setting and changing the Station Control Password
Configuration216
Procedure 12Configuring MG 1000B IP Phones at the main office using LD
11218
Procedure 13Mounting the MG 1000B Core or MG 1000B Expander in a
19-inch rack223
Procedure 14Preparing the Signaling Server for rack-mounting230
Procedure 15Rack-mounting the Signaling Server233
Procedure 16Connecting and powering up the Signaling Server235
Procedure 17Creating a Signaling Server software CD-ROM240
Procedure 18Viewing the Tools Menu241
Procedure 19Changing the Signaling Server port speed243
Procedure 20Verifying successful configuration244
Procedure 21Configuring the ELAN network interface IP address246
Procedure 22Connecting the Ethernet ports247
ProcedureRemoving the SSC card 250
ProcedureInstalling a DSP Daughterboard251
ProcedureInstalling the MGC card252
ProcedureInstalling the CP PM card252
Procedure 23Configuring the MG 1000B zone257
Procedure 24Using Set-Based Installation267
Procedure 25Configuring a Branch User271
ProcedureUsing the Reports and Import Facility in TM274
Procedure 26Testing the telephone for survivability278
Procedure 27Installing IP Phones through overlays279
Procedure 28Changing the SCPW282
Procedure 29Using the Telephone Options feature282
Procedure 30Using the Virtual Office Login feature 284
Procedure 31Using the Test Local Mode feature286
Procedure 32Using the Set-Based Removal feature288
Procedure 33Configuring the main office299
Procedure 34Configuring the NRS database306
Procedure 35Configuring the Branch Office308
Procedure 36Testing PSTN access using an MG 1000B IP Phone312
Procedure 37Configuring the main office319
Procedure 38Configuring the Branch Office324
Procedure 39Configuring the Branch Office zone 325
Procedure 40Testing ESDN using an MG 1000B Telephone326
Procedure 41Configuring Speed Call List (SCL)339
Procedure 42Configuring Pretranslation Groups340
Procedure 43Assigning Pretranslation Groups to the telephones341
Procedure 44Configuring Incoming DID Digit Conversion (IDC)342
Procedure 45Upgrading firmware for CS 1000 Release 5.0347
Procedure 46Upgrading firmware for CS 1000 Release 4.0 and earlier348
Procedure 47Calculating traffic373
Procedure 48Calculating Call Server Loading375
Procedure 49Calculating TLAN subnet bandwidth for IP Phone traffic377
Procedure 50Calculating MG 1000B with Virtual Trunk
LAN/WAN 378
Procedure 51Calculating unspecified conference traffic379
Procedure 52Calculating known conference traffic380
Procedure 53Calculating Branch Office traffic, and LAN/WAN
This document is a global document. Contact your system supplier or your
Nortel representative to verify that the hardware and software described
are supported in your area.
This document describes the Branch Office feature and contains information
on planning, installation, configuration, and maintenance. Information
in this document complements information found in documents in the
Communication Server 1000 documentation suite, as listed in Related
information.
This NTP contains information about systems, components, and features
that are compatible with Nortel Communication Server 1000 Release 5.0
software. For more information on legacy products and releases, click the
Technical Documentation link under Support on the Nortel home page:
Table 1
Contents
17
"MG 1000B hardware platform" (page 17)
"Media Card MC32S" (page 18)
"Main and Branch Office running different releases" (page 18)
"Main Office and Branch Office Migration" (page 18)
MG 1000B hardware platform
The MG 1000B system has been enhanced for CS 1000 Release 5.0
Branch Office. The CP-PM Call Server and MGC replace the Small System
Controller (SSC) used in the Release 4.0 and 4.5 MG 1000B.
Two new DSP Daughterboards are included in the CS 1000 portfolio of
products. The daughterboards are available in two different sizes, a 32-port
daughterboard and a 96-port daughterboard. These daughterboards are
located on the Media Gateway Controller card to provide DSP resources
for connecting IP and TDM devices, and eliminate the need to install the
Voice Gateway Media Cards within the CS 1000E Media Gateways (MG
1000B) chassis.
For CS 1000 Release 5.0, the new Media Card 32S (MC32S) fully replaces
the functionality of the current VGMV pack NTVQ01BB. You can use the
new pack in both large and small systems, and anywhere you can use the
current NTVQ01BB pack. The MC32S also adds SRTP security. For an
MGC-based MG 1000B, the sets are configured in four-field format.
As there are new conference capabilities on the MGC, the Group Call
feature available in CS 1000 Release 5.0 on the CS 1000B is enhanced.
The number of group members increases from 6 to 20.
Main and Branch Office running different releases
If the main office Call Server is running CS 1000 Release 5.0, the Branch
Office can run on CS 1000 Release 5.0, CS 1000 Release 4.5, or CS 1000
Release 4.0.
Customers will no longer be permitted to order a Branch Office running on
Succession 3.0.
Main Office and Branch Office Migration
All Main Office call servers in CS 1000 Release 5.0 are large system based.
A CS 1000 Small System Main Office is no longer supported. Since all CS
1000 Release 5.0 Small System Controller (SSC) based Main Offices have
been migrated to Call Processor Pentium Mobile (CP-PM) Call Servers, the
Main Office TN (MOTN) Type in a Branch Office will always be set to the
large system MOTN Type.
In a system where the Main Office has been migrated from a SSC to CP-PM
call server, the LD 20 PRT on the branch will not correctly display the MOTN
using the small system TN format until the branch has been migrated or
upgraded to CS 1000 Release 5.0. In the case where the branch is SSC
based, the LD 20 PRT will remain incorrect until the Branch Office Call
Server has been migrated to a CP-PM call server. In the case where the
branch is already linked to a Large System Format Call Server, the LD 20
PRT report on the branch will remain incorrect until the branch has been
upgraded to CS 1000 Release 5.0.
This chapter explains how to get help for Nortel products and services.
Getting help from the Nortel web site
The best way to get technical support for Nortel products is from the Nortel
Technical Support web site:
ttp://www.nortel.com/support
h
This site provides quick access to software, documentation, bulletins, and
tools to address issues with Nortel products. From this site, you can:
•
download software, documentation, and product bulletins
•
search the Technical Support Web site and the Nortel Knowledge Base
for answers to technical issues
•
sign up for automatic notification of new software and documentation
for Nortel equipment
•
open and manage technical support cases
19
Getting help over the telephone from a Nortel Solutions Center
If you do not find the information you require on the Nortel Technical Support
web site, and you have a Nortel support contract, you can also get help over
the telephone from a Nortel Solutions Center.
In North America, call 1-800-4NORTEL (1-800-466-7835).
Outside North America, go to the following web site to obtain the telephone
number for your region:
h
ttp://www.nortel.com/callus
Getting help from a specialist by using an Express Routing Code
To access some Nortel Technical Solutions Centers, you can use an Express
Routing Code (ERC) to quickly route your call to a specialist in your Nortel
product or service. To locate the ERC for your product or service, go to:
Getting help through a Nortel distributor or re-seller
If you purchased a service contract for your Nortel product from a distributor
or authorized re-seller, contact the technical support staff for that distributor
or re-seller.
This section contains information on the following topics:
"What is Branch Office?" (page 22)
"MG 1000B (MGC) compared to the MG 1000B (SSC)" (page 24)
"MGC Serial Ports" (page 26)
21
"Main Office and Branch Office Migration" (page 24)
"Single CPU Implications" (page 26)
"Dual CPU Implications" (page 26)
"Terminal Server Support" (page 26)
"MGC serial port default configuration" (page 27)
"MGC serial ports configuration change in Overly 17" (page 27)
Table 2 "CEMux Packs and daughter boards supported in MG 1000B with
"Main and Branch Office running the same release" (page 47)
"Main and Branch Office running different releases" (page 48)
"Package Combinations" (page 50)
"Supported applications" (page 50)
"Survivability" (page 50)
"Active Call Failover" (page 52)
"Configuring S2 IP Address to point to the main office TPS" (page 53)
What is Branch Office?
The Branch Office feature extends CS 1000 features from a main office to
one or more remote offices.
The Branch Office feature is implemented on a Media Gateway 1000B
(MG 1000B) platform. The MG 1000B platform includes 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 communication network. The Call Server at the main office
provides the call processing for the IP Phones in both the main office and
Branch Office locations. 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 MG 1000B platform 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 Media Gateway Controller (MGC) card in the MG
1000B Core provides service to the telephones located at the Branch Office
location. This enables the IP Phones to survive the outage between the
Branch Office and the main office.
Currently, MG 1000B Branch Office is small system based; which is still
supported in CS 1000 Release 5.0. In addition, changes are made to
allow large system based branch offices. Branch Office configurations
supported in CS 1000 Release 5.0, and are not changed with the CP PM
(Call Processor Pentium Mobile). Additionally, the CP PM adds the ability
for large systems to be supported as a Branch Office. A mixture of pre
CS 1000 Release 5.0 branches are supported with CS 1000 Release 5.0
branches as long as the main office is running the latest software.
The Branch Office feature does not change with the addition of large system
based branches. The Branch Office feature is ported to a large system.
Both small and large systems are supported as either main or branch
offices with only one restriction; the main must be running the highest
release of software.
Support is available for CS 1000 Release 5.0 Branch Office features, as
long as the main office is running the highest release of software. For
example, Branch offices can be either the SSC based MG 1000B (CS 1000
Release 4.5), or the new MGC based MG 1000B (CS 1000 Release 5.0).
With CS 1000 Release 5.0 and the introduction of the new hardware
platforms, the following configurations are supported:
•
Main Office: MGCbased system. Branch Office: MGC based MG
1000B.
•
Main Office: MGC based system. Branch Office: MGC based MG
1000B (large system software stream).
•
Main Office: Large system (1000M or 1000E). Branch Office: MGC
based MG 1000B.
•
Main Office: Large system (1000M or 1000E). Branch Office: MGC
based MG 1000B (large system software stream).
For small Branch Office configurations, the Survivable Remote Gateway
feature can provide the same functionality and benefits as the Branch Office
feature.
You can implement the Branch Office feature as a new hardware
configuration. It can also be created by converting an existing Small System
to an MG 1000B platform (see "Converting a Small System to a Branch
Office" (page 201)). The functionality is the same in both configurations.
The main office can be any one of the CS 1000 systems (see ""Main office
hardware description" (page 28)" More than one Branch Office location
can be associated with a single main office. In addition, one Branch Office
location can be associated with more than one main office.
A Branch Office is designed to work with a main office only if the two offices
use a common dialing plan. Any other configuration is not guaranteed to
work properly.
Figure 1 "Branch Office associated with a CS 1000E main office" (page
Figure 1
Branch Office associated with a CS 1000E main office
Main Office and Branch Office Migration
All Main Office call servers in CS 1000 Release 5.0 are large system based.
A CS 1000 Small System Main Office is no longer supported. Since all CS
1000 Release 5.0 Small System Controller (SSC) based Main Offices have
been migrated to Call Processor Pentium Mobile (CP-PM) Call Servers, the
Main Office TN (MOTN) Type in a Branch Office will always be set to the
large system MOTN Type.
In a system where the Main Office has been migrated from a SSC to CP-PM
call server, the LD 20 PRT on the branch will not correctly display the MOTN
using the small system TN format until the branch has been migrated or
upgraded. In the case where the branch is SSC based, the LD20 PRT will
remain incorrect until the Branch Office Call Server has been migrated to a
CP-PM call server. In the case where the branch is already a large system
(CP-PII or CP-PIV), then the LD 20 PRT on the branch will remain incorrect
until the branch has been upgraded to CS 1000 Release 5.0.
MG 1000B (MGC) compared to the MG 1000B (SSC)
The MG 1000B with MGC has a number of differences in hardware
capability when compared with Release 4.5 gateways.
The MGC has six Ethernet interfaces for connecting to external networking
equipment. Three are reserved for ELAN connections and three are
reserved for TLAN1 connections. The six external Ethernet interfaces on
the MGC are set to Auto Negotiate mode by default. You can change the
settings for ports 1E, 2T, E and T to 100 Mbps full duplex by using the
mgcsetup command. With a properly designed data network, the multiple
ELAN and TLAN interfaces can be used to implement a dual homed
configuration for the MG 1000B with MGC.
Four of these interfaces are accessed by using RJ45 connectors on the
faceplate. Two are reserved for ELAN and two are reserved for TLAN.
Two additional Ethernet connections are available if an Option 11C cabinet
is used. One is reserved for ELAN and one is reserved for TLAN.
For the Option 11C cabinets, to break out the two new 100BaseT Ethernet
connections, you need a new backplane adapter. This adapter replaces
the MDF-to-AUI cable used for the 10BaseT Ethernet connection on the
existing system.
One use for the additional LAN connections is to allow for network
redundancy, also known as dual-homing on the Release 4.5 MG 1000B.
The MGC Ethernet interface failover is accomplished with the embedded
Ethernet switch. The Ethernet interface failover feature requires no special
network configuration to function. The end customer decides if two separate
Layer 2 switches are used to implement the feature to minimize the service
outage. For more information see the Communication Server 1000E:
Installation and Configuration (NN43041-310) NTP.
Also, you can use the broadcast and multi cast rate limiting features of the
embedded Ethernet switch on the MGC to reduce the susceptibility of the
Call Server to broadcast storms and similar network issues, if you directly
cable the Call Server to the MGC.
In addition, certain debug features use the LAN connections (for example,
port mirroring.)
The MGC has two conference loops with thirty units each. The maximum
number of participants in a conference is thirty. On the MG 1000B, the
maximum number of conference loops was four with sixteen units in each
loop. The maximum number of participants in a conference was six.
The MGC has a four-character alphanumeric LED display on the faceplate.
the boot and application software use the display to show diagnostic
information to the technician.
The MGC has a clock reference input/output to support the requirements
of the Digital Enhanced Cordless Telecommunications (DECT) standard.
The DECT product requires a tight clock tolerance between cabinets with
interconnected radio equipment of ±5ppm. To accommodate the tight clock
tolerance, the MGC is equipped with a clock reference input/output. The
clock reference input and output connections and cable detect are provided
through a 15-pin DSUB connector.
MGC Serial Ports
Each MGC installed in a CS 1000B provides the opportunity for 3 remote
SDIs. The maximum number of TTYs does not change. Therefore, after you
configure the maximum TTYs , no additional TTYs are supported.
The MGC has three serial ports SDI0, SDI1, and SDI2.
You can use serial ports for local debugging; or, you can configure the ports
in the MG 1000B Call Server as system terminals in LD 17.
During the initial configuration of the MGC, you must connect to either
SDI0 or SDI1 to access the installation menu. Only SDI0 has full modem
support, as SDI1 and SDI2 have no hardware flow control (limitation of
the three-port cable used).
SDI2 is not available during the MGC bootup; therefore, you cannot use
it to access the installation menus.
Unlike the NTDK20xx SSC card, all SDI ports on the MGC are configured
by using shipped software. No DIP switches are on the MGC for configuring
the baud rate of SDI0.
Single CPU Implications
Single CPU installations do not require dynamic binding of TTY ports to
the active CPU because only one CPU exists. Therefore, single-CPU
installations can use the Call Server TTY ports or the MGC remote TTY
ports.
Dual CPU Implications
MG 1000B uses a terminal server to ensure that serial ports are always
bound to the active CPU. The remote SDIs on the MGC provide similar
functionality. Each MGC provides three SDI ports that you can provision
in the softswitch as TTYs.
Remote TTY provisioning is enhanced over the terminal server model. SDI
port provisioning is performed on the softswitch and does not require local
provisioning at the IPMG.
Terminal Server Support
The remote SDI feature on the MGC eliminates the need for a terminal
server.
If you configure the serial ports on an MG 1000B with MGC as SL1 terminals
on the Call Server, then the baud rate, number of data bits, number of stop
bits, parity, and flow control are configured in LD 17.
Any values configured in LD 17 are downloaded to the MGC and override
the default values. The downloaded values are stored on the MGC and
persist over restarts and power outages. When the serial port baud rate is
changed, a system message indicates the change.
MGC Serial Ports27
CEMux Support
Support of the Option 11C CS 1000M cabinet and chassis CEMux type
cards are additions to the MG 1000B with an MGC with the CP PM. The
list of supported cards is as follows:
Table 2
CEMux Packs and daughter boards supported in MG 1000B with MGC
PackDaughterboard
1.5MB DTI/PRI
(NTAK09)
1.5MB TMDI
(NTRB21)
2.0MB DTI (NTAK
10)
2.0MB PRI (NTAK79)n/aclock controller (stratum 3/4), non-downloadable
Standard Option 11C minimum vintages apply to all packs and daughter
boards.
Attempts to install unsupported CEMux packs or to configure an
unsupported application are blocked.
Support of CEMux requires CS 1000 Release 5.0 Softswitch software and
a Media Gateway Controller Card (MGC). It is supported by all MG 1000B
systems.
Features supported by Option 11C SIPE related to CEMux are supported in
MG 1000B, which includes support for nB+D by having single D-Channel
support trunk packs in separate MG1000Bs.
The TMDI D-Channel ISM used on small systems IS NOT included for the
CS 1000B. D-Channels configured or removed for TMDI cards increment
the existing large system software based DCH ISM. The maximum number
of D-Channels, which is 255, supported with CS 1000B in CS 1000 Release
5.0, matches that of the CS 1000M large systems.
n/an/a
n/an/a
For BRI, you must provision the MISP and the SILC/UILC in the same
IPMG. This is the only supported configuration.
Clock References
With CEMux support, you can configure digital trunks and clock controller
configuration in the IPMG. Each IPMG that contains a digital trunk card
requires a clock controller on that shelf. You cannot use Clock references
across IPMGs, and you can configure only one clock controller per shelf..
Main office hardware description
The main office must be one of the following systems:
The diagrams throughout this document show a CS 1000E main office. All
of the systems appearing in the list perform identical main office functions
as far as the Branch Office feature is concerned.
MG 1000B platform hardware description
The MG 1000B system has been enhanced for CS 1000 Release 5.0 Branch
Office. The CP-PM Call Server and MGC replace the SSC (Motorola) used
in the Release 4.0/4.5 MG 1000B. The Voice Gateway Media Card is still
supported however, the DSPs are also available on the MGC.
Two new DSP Daughterboards are included in the CS 1000 portfolio of
products. The daughterboards are available in two different sizes, a 32-port
daughterboard and a 96-port daughterboard. These daughterboards are
located on the Media Gateway Controller (MGC) card to provide DSP
resources for connecting IP and TDM devices. These daughterboards
eliminate the need to instal the Voice Gateway Media Cards within the CS
1000E Media Gateways (MG 1000B) chassis, to save slots and reduce cost
over the current Voice Gateway Media Card solution. The addition of the
DSP Daughterboards into a MG 1000B system does not limit the use of
Voice Gateway Media Cards (either Pentium or Strong-Arm versions), either
for DSP-only functionality or for the full IP Line application within the same
system. The MGC is used only in the Media Gateway chassis or Option
11C-style cabinets. Froma functional perspective, the DSP Daughterboards
behave in a similar manner as the current Voice Gateway (VGW) application
on the Voice Gateway Media Card.
Support exists for four configurations:
•
a system with no DSP DBs or Voice Gateway Media Card (A pure TDM
system, single media gateway).
•
a system with only Voice Gateway Media Cards
•a system with only DSP DBs
— a 32-port daughterboard in daughterboard position 1
— a 32-port daughterboard in daughterboard position 2
— A 32-port daughterboard in daughterboard position 1 and a 32-port
daughterboard in daughterboard position 2
— a 96-port daughterboard in daughterboard position 1
— a 96-port daughterboard in daughterboard position 1 and a 32-port
daughterboard in daughterboard position 2
•
a system with DSP DBs (all of the position combinations described in c)
and Voice Gateway Media Cards.
The basic hardware of an MG 1000B platform includes the MG 1000B Core
and the Signaling Server.
CS 1000 Release 5.0 continues to support the existing Branch Office
configuration that uses the SSC processor, but Nortel no longer offers sales
of the SSC based Branch Office.
CS 1000 Release 5.0 provides various hardware versions of the Signaling
Server, the existing ISP1100 signaling servers, or the new CP-PM Signaling
Server.
With CS 1000 Release 5.0 Branch Office, the hardware configuration
includes a CP-PM call processor card with the MGC, as well as a CP-PM
Signalling Server. If the CP-PM Signalling Server configuration cannot be
used, the option exists to use the Signaling Server on COTS.
The MG 1000B Core and MG 1000B Expander can connect to either a
LAN or a WAN.
An MG 1000B platform can be a new hardware configuration. It can also
be a Small System platform converted to an MG 1000B platform. In the
latter case, the cabinet or chassis performs the same functionality as the