Nortel Networks 9150 User Manual

NTDR84AC

555-8421-215

Remote Gateway 9150

Installation and Administration Guide

Product release 1.5 Standard 3.1 January 2005

Remote Gateway 9150

Installation and Administration Guide

Product release: 1.5
Publication number: 555-8421-215
Document release: Standard 3.1
Date: January 2005

Copyright © 2005 Nortel. All Rights Reserved

Printed in Canada

All information contained in this document is subject to change without notice. Nortel reserves the
right to make changes to equipment design or program components, as progress in engineering,
manufacturing methods, or other circumstances may warrant.

*Nortel, the Nortel logo, the Globemark, Unified Networks, Meridian 1 PBX, Communication Server
1000 (CS 1000), and Communication Server 2100 (CS 2100) are trademarks of Nortel.

TelStrat is a registered trademark of TelStrat International, Ltd. Microsoft, MS-DOS, and Windows
are trademarks of Microsoft Corporation.

FCC: Customer instructions

The Remote Gateway 9150 unit complies with Part 68 of the FCC rules. On the bottom
side of the equipment is a label that contains, among other information, the FCC
registration number and ringer equivalence number (REN) for this equipment. If
requested, this information must be provided to the telephone company.

The Remote Gateway 9150 unit uses the following standard connections and codes:
USOC Code: RJ21X, Facility Interface Code: 02DU5-64, and Service Order Code: 6.0F.

The REN number shown on the label is used to determine the number of devices that can
be connected to the telephone line. Excessive RENs on the telephone line can result in
the devices not ringing in response to an incoming call. The sum of the RENs should not
exceed five (5.0). To be certain of the number of devices that can be connected to a line,
as determined by the total RENs, contact the local telephone company.

If the equipment causes harm to the telephone network, the telephone company will
notify you in advance that temporary discontinuance of service might be required.
However, if advance notice is not practical, the telephone company will notify you as
soon as possible. Also, you will be advised of your right to file a complaint with the FCC
if you believe it is necessary.

The telephone company may make changes in its facilities, equipment, operations, or
procedures that could affect the operation of the equipment. If this happens, the
telephone company will provide advance notice in order for you to make necessary
modifications to maintain uninterrupted service.

No repairs can be performed by you. If you experience trouble with this equipment,
please contact the following for repair and warranty information:

Nortel
Product Service Center
640 Massman Drive. Nashville, TN 31210
Phone: [phone]

If the equipment is causing harm to the telephone network, the telephone company
might request that you disconnect the equipment until the problem is resolved.

This equipment cannot be used on public coin phone service provided by the telephone
company. Connection to party line service is subject to state tariffs. Contact the state
public utility commission, public service commission, or corporation commission for
information.

Industry Canada: Equipment attachment limitation

NOTICE: The Industry Canada Label identifies certified equipment. This certification
means that the equipment meets telecommunications network protective, operational,
and safety requirements as prescribed in the appropriate Terminal Equipment Technical
Requirements document(s). The Department does not guarantee that the equipment will
operate to the user’s satisfaction.

Before installing this equipment, you should ensure that it is permissible to be connected
to the facilities of the local telecommunications company. The equipment must also be
installed using an acceptable method of connection. You should be aware that
compliance with the above conditions might not prevent degradation in service in some
situations.

Repairs to certified equipment should be coordinated by a representative designated by
the supplier. Any repairs or alterations made by the user to this equipment, or equipment
malfunctions, can give the telecommunications company cause to request you to
disconnect the equipment.

You should ensure, for your own protection, that the electrical ground connections of the
power utility, telephone lines, and internal metallic water pipe system, if present, are
connected together. This precaution can be particularly important in rural areas.

Caution: You should not attempt to make such connections yourself, but should contact
the appropriate electric inspection authority, or electrician, as appropriate.

NOTICE: The Ringer Equivalence Number (REN) assigned to each terminal device
provides an indication of the maximum number of terminals allowed to be connected to
a telephone interface. The termination on an interface can consist of any combination of
devices subject only to the requirements that the sum of the Ringer Equivalence
Numbers of all the devices does not exceed 5.

Publication history

January 2005

July 2004

September 2001

March 2000

This is the Standard 3.1 issue of the Remote Gateway 9150
Installation and Administration Guide for Remote Gateway

9100 Series product release 1.5.

This is the Standard 3.0 issue of the Remote Gateway 9150
Installation and Administration Guide for Remote Gateway
9100 Series product release 1.5.

This is the Standard 2.0 issue of the Remote Gateway 9150
Installation and Administration Guide for Remote Gateway
9100 Series product release 1.3.0. Support for
Communication Server 2100 (CS 2100) has been added
along with new and enhanced feature information that was
formerly published in the Remote Gateway 9100 Series and
RLC Release Notes.

This is the Standard 1.0 issue of the Remote Gateway 9150
Installation and Administration Guide for Remote Gateway
9100 Series product release 1.0.

Remote Gateway 9150 Installation and Administration Guide v

Publication history Standard 3.1

vi Remote Gateway 9150 Installation and Administration Guide

Contents

About this document xvii

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Product overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Skills you need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Conventions used in this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

Related information products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

1 Remote Gateway 9150 description 1

Product introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Operational characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

How to use this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Nortel product knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Telecommunications experience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Data networking knowledge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Precautionary messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

Instructions for selecting menu options . . . . . . . . . . . . . . . . . . . . . . . xxiii

Instructions for displaying property sheets . . . . . . . . . . . . . . . . . . . . xxiii

PBX terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Printed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

Remote Gateway 9150 hardware description . . . . . . . . . . . . . . . . . . . . 3

Add-on modules description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Connection options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

System security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Trunk connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

64K (56K) dynamic adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Bandwidth allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Connection types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Minimum call duration timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Idle timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

How the timers work to control ISDN costs. . . . . . . . . . . . . . . . . . . . . 15

Remote Gateway 9150 Installation and Administration Guide vii

Contents Standard 3.1

How the Remote Gateway 9150 unit works. . . . . . . . . . . . . . . . . . . . . . . . . . 16

Outgoing call process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Incoming call process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Bridge Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Host controlled call mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Locally controlled call mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

QoS Transitioning Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Call scenario 1: host-controlled—internal corporate call . . . . . . . . . 20

Call scenario 2: host-controlled—external corporate call . . . . . . . . . 22

Call scenario 3: locally controlled mode—local call . . . . . . . . . . . . . 24

Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Supported digital telephone sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

M2000 series (M3310, and M3820 European models) and
M39xx series digital telephone set model and

accessory compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

M39xx series digital telephone set accessory compatibility . . . . . . . . 30

Supported telephone modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Computer telephony integration (CTI) applications . . . . . . . . . . . . . . 31

Automatic Call Distribution (ACD) applications . . . . . . . . . . . . . . . . 32

Voice over IP features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

QoS Transitioning Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Port management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Station priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Connection bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Local calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Online/offline table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Other supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Communications system and software requirements . . . . . . . . . . . . . . 42

Supported Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Administration software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Administration PC connection options . . . . . . . . . . . . . . . . . . . . . . . . 43

Remote Gateway 9100 Series Configuration Manager . . . . . . . . . . . . 43

Command line interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

viii Remote Gateway 9150 Installation and Administration Guide

January 2005 Contents

2 Planning for Remote Gateway 9150 unit

installation 45

Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Physical environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Temperature and humidity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Mounting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Cables included with the Remote Gateway 9150 unit . . . . . . . . . . . . . 53

Cables you must supply yourself . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Network considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

IP addressing and routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

QoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Numbering plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Call blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Administration PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Connection options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Windows PC requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Optivity Telephony Manager and Configuration Manager . . . . . . . . . 63

Trunk connection management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

QoS Transitioning Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Online/offline schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Changing the online/offline mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Trunk bandwidth allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Station configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

RLC settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Remote Gateway 9150 unit settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Toll fraud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Data network security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Planning for future growth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Adding DSP modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Adding trunk interface modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Maximum configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Deployment options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Port and station assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Implementing PSTN mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Implementing Voice over IP mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Implementing Remote Gateway 9150 units behind Network Address

Translation (NAT) routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Implementing QoS Transitioning Technology . . . . . . . . . . . . . . . . . . . 79

Remote Gateway 9150 Installation and Administration Guide ix

Contents Standard 3.1

Planning the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Data entry form completion sequence . . . . . . . . . . . . . . . . . . . . . . . . . 81

Station assignments and configuration . . . . . . . . . . . . . . . . . . . . . . . . 81

ISDN BRI information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Connection link between the RLC and

the Remote Gateway 9150 unit information. . . . . . . . . . . . . . . . . . . . . 83

Online/offline schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Trunk configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Numbering plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

3 Installing the Remote Gateway 9150 unit 85

General safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Precautionary messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Required installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Required tools for hardware installation . . . . . . . . . . . . . . . . . . . . . . . 88

Required tools for software installation or upgrade . . . . . . . . . . . . . . 88

Unpacking and inspecting the equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Removing and replacing the Remote Gateway 9150 unit cover . . . . . . . . . . 90

Installing trunk interface or DSP application modules. . . . . . . . . . . . . . . . . . 93

Determining when to install trunk interface or

DSP application modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Determining where to install the modules . . . . . . . . . . . . . . . . . . . . . . 94

Installing trunk interface or DSP application modules . . . . . . . . . . . . 96

Removing trunk interface or DSP application modules. . . . . . . . . . . . 96

Installing the Remote Gateway 9150 unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Choosing a suitable location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Installing the Remote Gateway 9150 unit on a desk . . . . . . . . . . . . . . 99

Installing the Remote Gateway 9150 unit on the wall . . . . . . . . . . . . 100

Installing the Remote Gateway 9150 unit in a rack. . . . . . . . . . . . . . 103

Connecting the Remote Gateway 9150 unit. . . . . . . . . . . . . . . . . . . . . . . . . 105

Cables you must provide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Connector and pin-out reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

More information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Remote Gateway 9150 unit connection panel . . . . . . . . . . . . . . . . . . 107

Attaching the cables to Remote Gateway 9150 unit . . . . . . . . . . . . . 108

Connecting the Remote Gateway 9150 unit to the network. . . . . . . . 109

Powering up the Remote Gateway 9150 unit . . . . . . . . . . . . . . . . . . . . . . . . 111

Power-up self-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

LED indicator test sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Installing the Configuration Manager software . . . . . . . . . . . . . . . . . . . . . . 113

x Remote Gateway 9150 Installation and Administration Guide

January 2005 Contents

Using the Configuration Wizard to perform initial configuration . . . . . . . . 115

What you can configure with the Configuration Wizard . . . . . . . . . . 115

Starting Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Establishing a serial connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Performing configuration with the Configuration Wizard. . . . . . . . . 119

Testing the network connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Verifying telephone network connectivity . . . . . . . . . . . . . . . . . . . . . 129

4 Using Configuration Manager 133

What is Configuration Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Starting and viewing Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . 135

Configuration Manager description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Parts of the Configuration Manager screen . . . . . . . . . . . . . . . . . . . 137

Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

System tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Property sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Drop down boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Check boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Option buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Scroll boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Scroll bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Command buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Using online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Configuration files description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Configuration Manager: File operations diagram . . . . . . . . . . . . . . 145

Types of files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Configuration Manager: File operations description . . . . . . . . . . . . 148

Working with configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

When to use the Configuration Manager file operations. . . . . . . . . . 153

Creating a configuration file on the PC. . . . . . . . . . . . . . . . . . . . . . . 154

Opening a configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Uploading a configuration to a unit . . . . . . . . . . . . . . . . . . . . . . . . . 155

Downloading a configuration from a unit . . . . . . . . . . . . . . . . . . . . . 155

Selecting the device type for offline configuration . . . . . . . . . . . . . . . . . . . 156

Logging on to a unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Connection types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Default logon ID and password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Connection history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Auto logoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Logging on to a unit using the connection history. . . . . . . . . . . . . . . 158

Logging on to a unit using Telnet. . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Logging on to a unit using the serial port . . . . . . . . . . . . . . . . . . . . . 164

Remote Gateway 9150 Installation and Administration Guide xi

Contents Standard 3.1

Logging off of the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Using the Remote Connection command . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Performing a system restart or shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

When to perform a restart or shutdown . . . . . . . . . . . . . . . . . . . . . . . 169

Closing Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Uninstalling the Configuration Manager software . . . . . . . . . . . . . . . . . . . . 172

5 Configuring the Remote Gateway 9150 unit 173

9150 System configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

NLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Emergency service programmability . . . . . . . . . . . . . . . . . . . . . . . . . 176

Configuring the Remote Gateway 9150 system settings . . . . . . . . . . 176

International tones support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Configuring International Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Configuring the IP addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

IP Configuration field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Prioritizing voice traffic over shared networks . . . . . . . . . . . . . . . . . 197

RLC connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Configuring the RLC connection information . . . . . . . . . . . . . . . . . . 199

PSTN connection configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Security level configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

9150 port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Configuring stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Bridge Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Analog port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Configuring a fax station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Configuring the fax port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

BRI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Remote Gateway 9150 ISDN BRI Interface information—

for Norway and Sweden only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

ISDN Line Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Automatic TEIs (Terminal Endpoint Identifiers) . . . . . . . . . . . . . . . . 227

Entering the BRI settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

xii Remote Gateway 9150 Installation and Administration Guide

January 2005 Contents

Trunk group configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Primary trunk on the Remote Gateway 9150 unit . . . . . . . . . . . . . . . 233

Trunk groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Trunk access codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

ISDN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

European ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

National ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Configuring trunk groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

DSP configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Module identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Device configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Configuring DSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Auto upgrade configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Configuring automatic upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Syslog configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Configuring syslog functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Station configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Bridge Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Call processing capabilities and station settings. . . . . . . . . . . . . . . . 251

Call appearance keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

MCR keys increase DSP requirements. . . . . . . . . . . . . . . . . . . . . . . . 254

Private lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Calling permissions and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . 255

ATA- and MCA-equipped stations and

bandwidth requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

6 Using Remote Gateway 9150 stations 259

Modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Host-controlled mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Locally controlled mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Relationship between host-controlled and

locally controlled modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Online mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Offline mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Why offline mode is important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

What controls the online and offline modes. . . . . . . . . . . . . . . . . . . . 263

Remote Gateway 9150 Installation and Administration Guide xiii

Contents Standard 3.1

Placing and receiving calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Receiving incoming calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Methods for placing outgoing calls . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Placing host-controlled calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Placing outgoing locally controlled calls . . . . . . . . . . . . . . . . . . . . . 266

Calling another station at your site . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Indicator updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Host-controlled indicator updates . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Locally controlled indicator updates . . . . . . . . . . . . . . . . . . . . . . . . . 269

Display messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Message descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Telephone features operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Emergency service calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Call Forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Going online and offline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Using the SPRE code to put all stations into online mode. . . . . . . . . 277

Using the SPRE code to put all stations into offline mode . . . . . . . . 277

Overriding an automatic offline event from the host PBX. . . . . . . . . 278

7 Administration 279

Changing the administration password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Changing the Configuration Manager password . . . . . . . . . . . . . . . 280

Changing the Remote Gateway 9150 unit password . . . . . . . . . . . . . 281

Creating a backup configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Storing backup configuration files. . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Creating the backup file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Restoring the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Uploading a configuration file over the IP network . . . . . . . . . . . . . 286

Display logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Viewing display logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Printing the display logs to a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Changing the size of Remote Gateway 9150 unit logs. . . . . . . . . . . . 292

Clearing logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

xiv Remote Gateway 9150 Installation and Administration Guide

January 2005 Contents

Statistics screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Trunk Connection Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Bandwidth Connection Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Caller Info Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Hardware Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

DSP Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Ethernet Interface Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

BRI Information Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Local Call Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Remote Call Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Device Information Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

ISDN Module Information Statistics . . . . . . . . . . . . . . . . . . . . . . . . . 325

Network Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

PSTN Error Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Verifying the firmware and software version. . . . . . . . . . . . . . . . . . . . . . . . 335

Verifying the software version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Verifying the firmware version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Determining the current firmware and software versions . . . . . . . . . 336

Obtaining the latest upgrade file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Types of upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Downloading the upgrade file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Performing a firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Manual firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

When to perform a firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . 339

About firmware upgrades and configuration files . . . . . . . . . . . . . . . 339

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Upgrading the Remote Gateway 9150 unit firmware . . . . . . . . . . . . 340

Automatic or scheduled firmware upgrade . . . . . . . . . . . . . . . . . . . . 342

Self-contained firmware upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Performing a software upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Upgrading the Configuration Manager software . . . . . . . . . . . . . . . 346

8 Troubleshooting 347

Before you begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Identifying why a problem occurred . . . . . . . . . . . . . . . . . . . . . . . . . 348

Remote Gateway 9150 unit LED indicators. . . . . . . . . . . . . . . . . . . . . . . . . 349

What to do if the LEDs do not display correctly . . . . . . . . . . . . . . . . 349

Digital telephone set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Symptoms descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Device connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Symptom descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Remote Gateway 9150 Installation and Administration Guide xv

Contents Standard 3.1

Software problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Symptom descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Using Configuration Manager PING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Performing a Configuration Manager PING. . . . . . . . . . . . . . . . . . . 362

Unsuccessful PING options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Syslog testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Performing Syslog testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Alarms and alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Responding to a catastrophic failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Inoperative hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Repair and warranty information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Canada. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

United States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Europe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Asia/Pacific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

CALA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

A Planning forms 371

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

Network planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

Remote Gateway 9150 forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

Data entry form completion sequence . . . . . . . . . . . . . . . . . . . . . . . . 372

Completing the Remote Gateway 9150 forms . . . . . . . . . . . . . . . . . . . . . . . 374

B Sample configuration files 389

Example of a network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Sample configuration printouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Configuration recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Network diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

Voice port configuration on the Meridian 1 PBX. . . . . . . . . . . . . . . . . . . . . 392

Data port configuration on the Meridian 1 PBX. . . . . . . . . . . . . . . . . . . . . . 394

RLC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Remote Gateway 9150 unit configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 400

C Pin-out tables for connections 403

TELCO 1 connector pin-out table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

TELCO 2 connector pin-out table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

Ethernet connector pin-out table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

Admin (serial) connector pin-out table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Power connector pin-out table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

xvi Remote Gateway 9150 Installation and Administration Guide

January 2005 Contents

D Display log definitions 411

Display logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

Glossary 485

Fields index 507

Index 515

Remote Gateway 9150 Installation and Administration Guide xvii

Contents Standard 3.1

xviii Remote Gateway 9150 Installation and Administration Guide

Preface

About this document

In this preface

About this guide xviii

Product overview xix

Skills you need xx

Conventions used in this guide xxii

Related information products xxv

Remote Gateway 9150 Installation and Administration Guide xvii

About this document Standard 3.1

About this guide

The Remote Gateway 9150 Installation and Administration Guide (NTP 555-
8421-215) is for telecom and data network managers and administrators who
plan, install, and manage corporate telecommunications and data networks. This
guide contains the following information:

! a detailed description of the Remote Gateway 9150 unit

! procedures necessary to properly install, configure, and manage the Remote

Gateway 9150 unit at a location remote from the host PBX

! troubleshooting procedures for addressing possible problems

This guide assumes that you are familiar with the following:

! basic telecommunications terminology

! basic networking terminology

! PC terminology and operation (specifically, Windows 95, 98, NT

Workstation 4.0, Millennium Edition (ME), 2000 Professional, XP
[Professional and Home Edition])

! Nortel PBX terminology, functionality, and administration

How to use this guide

This guide provides step by step procedures for installing, configuring, and
managing the Remote Gateway 9150 unit as a part of your Nortel remote
services network. Review this guide before beginning Remote Gateway 9150
unit installation and configuration.

When you are ready to begin, follow the steps for planning, installing, and
configuring your hardware in the order that they are presented in this guide. This
helps you to achieve a successful, trouble-free installation.

xviii Remote Gateway 9150 Installation and Administration Guide

January 2005 About this document

Product overview

The Remote Gateway 9150 unit provides full-featured host PBX services to as
many as 32 users located in your office.

The Remote Gateway 9150 solution consists of the following components:

! Reach Line Card (RLC)

The RLC is installed in the PBX at the host location and relays voice and
signaling information from the digital telephones connected at the Remote
Gateway 9150 site to the PBX at the host site.

! Remote Gateway 9150 unit

The Remote Gateway 9150 unit is installed in your office. It relays voice
and signaling information between the digital telephones in your office to
the PBX at the host location.

! 10BaseT Ethernet and ISDN Basic Rate Interface (BRI) connections

These connections provide the voice and data connections between the
Remote Gateway 9150 unit and the host PBX.

! ISDN BRI trunk interface modules are supported for the following:

— U interface

— S/T interface

! optional Digital Signal Processor (DSP) application modules

You can add these modules to increase the system’s voice processing
capacity.

The Remote Gateway 9150 unit uses the Voice over IP technology to route voice
conversation and telephone set control signals between your office and the host
PBX over your existing IP data network.

The Remote Gateway 9150 unit can also use the PSTN to route calls if:

! the voice Quality of Service (QoS) degrades below predefined thresholds

In this case, Nortel’s patented QoS Transitioning Technology automatically
transitions calls to the PSTN when the voice QoS degrades. Calls transition
back to the IP network when the QoS returns to normal.

! you are not yet ready to use the IP network to route voice calls

You can configure the Remote Gateway 9150 unit to use only the PSTN,
and implement the IP network functionality when you are ready.

Remote Gateway 9150 Installation and Administration Guide xix

About this document Standard 3.1

Skills you need

Knowledge of, or experience with, the following concepts as appropriate to your
network is helpful when administering the Remote Gateway 9150 unit:

! Microsoft Windows

! software installation

! network configuration

Nortel product knowledge

Knowledge of, or experience with, the following Nortel products and concepts:

! basic administration of a Meridian 1, Communication Server 1000

(CS 1000), or Communication Server 2100 (CS 2100) PBX (telephone set
and XDLC configuration)

! characteristics and principles of XDLC operation

! PBX data calls

! Meridian digital telephones

Telecommunications experience

Knowledge of, or experience with, the following aspects of telecommunications:

! Extended Digital Line Cards (XDLCs) and how they work

! configuring voice and data ports

! configuring ISDN BRI, PRI (or other types of trunks)

! establishing telephone connections

xx Remote Gateway 9150 Installation and Administration Guide

January 2005 About this document

Data networking knowledge

Knowledge of, or experience with, the following aspects of data networking:

! data link (Layer 2 of the OSI model)

— IP protocol

— routing

! network (Layer 3 of the OSI model)

— addressing

— traffic analysis and provisioning

— configuration

! Voice over IP concepts

Remote Gateway 9150 Installation and Administration Guide xxi

About this document Standard 3.1

Conventions used in this guide

This section describes the conventions used in this guide.

Precautionary messages

Note: A “Note” describes the secondary results of procedures or commands, or
special conditions that require you to use a procedure or command.

ATTENTION!

.

.

.

Provides information essential to the completion of a task.

CAUTION

Risk of data loss or equipment damage

Cautions you against unsafe practices or potential hazards, such as
equipment damage, service interruption, or loss of data.

WARNING

Risk of minor personal injury

Warns you of a potentially hazardous situation that can result in
minor or moderate injury.

DANGER

Risk of electric shock

Alerts you to an immediate hazard that can result in death or
serious injury through high voltage or electric shock.

xxii Remote Gateway 9150 Installation and Administration Guide

January 2005 About this document

Instructions for selecting menu options

To simplify the instructions for selecting menu options, this guide abbreviates
the selection path. For example, if you must choose Over IP from the PSTN
Connectivity menu, under the Tests menu, this guide uses the following style:

From the menu, choose Tests

→ PSTN Connectivity → Over IP.

Instructions for displaying property sheets

To simplify the procedures for accessing property sheets throughout this guide,
the instructions for displaying a particular property sheet are summarized in a
“Getting there” statement.

The procedure for displaying the screen that you need depends on if you are:

! performing an online configuration (connected to a node by serial port or

Telne t)

! performing an offline configuration (not connected to a node)

Example

Getting there 9150 → Configuration Manager → IP Configuration

The long instruction for this example is as follows:

1 Do the following:

IF THEN

you are performing an offline
configuration,

select the device type as described in
“Selecting the device type for offline
configuration” on page 156.

you are performing an online
configuration,

2 In the left pane, click on the plus sign (+) beside Configuration Manager to

expand the node list.

3 Click on IP Configuration.

Result: The IP Configuration property sheet for the Remote Gateway 9150

unit displays in the right pane.

Remote Gateway 9150 Installation and Administration Guide xxiii

connect to, and then log on to the node
as described in “Logging on to a unit” on
page 157.

About this document Standard 3.1

PBX terminology

Throughout this guide, the term “host PBX” refers to any of the following
Nortel PBX platforms:

! Meridian 1 PBX

! CS 1000

! CS 2100

xxiv Remote Gateway 9150 Installation and Administration Guide

January 2005 About this document

Related information products

This section lists sources for additional information related to the Remote
Gateway 9150 unit. You can order printed documentation and the CD-ROM
from your Nortel distributor.

You can also download the documentation in Portable Document Format (PDF)
from the Nortel website. To locate these documents, click on the Technical

Documentation link at the following website:

www.nortel.com

Note: The information available on the website may supersede the information

provided on the CD-ROM.

For further details, refer to Remote Gateway 9100 Series and RLC Release Notes
(NTP 555-8421-102).

Printed documents

The following documents provide additional information on the RLC and other
elements of a Remote Gateway 9100 Series system:

Remote Gateway 9100 Series Network Engineering Guidelines
(NTP 555-8421-103)

The Remote Gateway 9100 Series Network Engineering Guidelines, written for
the installer/administrator, describe how a Remote Gateway 9100 Series system
integrates with existing telecommunications and data networks. This document
helps you to ensure that your networks are prepared for 9150.

Remote Gateway 9100 Series and RLC Release Notes
(NTP 555-8421-102)

The Remote Gateway 9100 Series and RLC Release Notes, written for the
installer/administrator, describe the features and known problems for the
different elements of a 9150 system. This document contains information
pertaining to the Reach Line Card (RLC), the Remote Gateway 9150 unit,
Remote Gateway 911x series units, and Digital Telephone IP Adapter units.

Remote Gateway 9150 Installation and Administration Guide xxv

About this document Standard 3.1

Reach Line Card Installation and Administration Guide

(NTP 555-8421-210)

The Reach Line Card Installation and Administration Guide, written for the
installer/administrator, describes how to install, configure, and manage the
Reach Line Card on the host PBX.

Remote Gateway 911x Series Installation and Administration Guide
(NTP 555-8421-220)

The Remote Gateway 911x Series Installation and Administration Guide, written
for the installer/administrator, describes how to install, configure, and manage
Remote Gateway 911x series units.

Digital Telephone IP Adapter Installation and Administration Guide
(NTP 555-8421-211)

The Digital Telephone IP Adapter Installation and Administration Guide,
written for the installer/administrator, describes how to install, configure, and
manage Digital Telephone IP Adapter units.

Installer’s Notes

The following Installer’s Notes are quick reference documents that are provided
with the component discussed in the document:

! Reach Line Card Installer’s Notes

! Remote Gateway 9150 and RLC DSP Application Module Installer’s Notes

! Remote Gateway 9150 Trunk Interface Module Installer’s Notes

CD-ROM

A Remote Gateway 9100 Series Product CD-ROM is available containing the
documentation in Portable Document Format (PDF), firmware, and Remote
Gateway 9100 Series Configuration Manager software.

xxvi Remote Gateway 9150 Installation and Administration Guide

Chapter 1

Remote Gateway 9150 description

In this chapter

Product introduction 2

Operational characteristics 12

How the Remote Gateway 9150 unit works 16

Telephones 26

Administration software 43

Remote Gateway 9150 Installation and Administration Guide 1

Remote Gateway 9150 description Standard 3.1

Product introduction

The Remote Gateway 9150 unit installed in your office provides PBX
functionality for up to 32 digital telephones. Voice and signaling information
between the digital telephones connected at your office and the RLC installed on
the PBX at the host location is relayed over one or both of the following:

! IP network

! PSTN

The illustration below shows the connection between a Remote Gateway 9150
unit and an RLC.

Remote site 1: Branch office

Up to 32 digital telephones Fax machine

Remote Gateway 9150

P
O

W

E
R

E

T
H

E
R

N
E

T

T
X

R
X

C
O

L
L

1
L
1

M

L

O

2

D
U

2

L
E

L
1

L
2

3
L
1

L
2

4
L
1

V
.

3

L
2

5

T

S

X

T

A
T

U

R

S

X

Ethernet

Central
office

Corporate office

Host PBX
trunks
(ISDN BRI)

ISDN PRI

Public

Corporate

WAN

Telephone

Network

Ethernet

Reach Line Card

G101391

Note: Nortel does not support a Remote Gateway 9100 Series system as a free­standing key system.

2 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Remote Gateway 9150 hardware description

The Remote Gateway 9150 unit is installed in your office and can be mounted
on a desk, in a rack, or on the wall. This section describes the LED indicator
displays, power supply, cables, and connectors for the unit.

LED indicators on the Remote Gateway 9150 unit

The following diagram shows the LED indicators on the front panel of the
Remote Gateway 9150 unit.

P

O

W

E

R

E

T

H

E

R

N

E

T

T

X

R

X

C

O

L

L

1

1

M

L

O

2L

D

U

2

L

E

L

1

L

2

3

L

1

L

2

4

L

1

L

2

V

.3

5

X

R

XT

Remote Gate

S

T

A

T

U

S

way 9150

Power

Ethernet Modules V.35 Status

Note: The V.35 LED indicators are present but are not functional.

G101402

Remote Gateway 9150 Installation and Administration Guide 3

Remote Gateway 9150 description Standard 3.1

The operational status of the Remote Gateway 9150 unit is indicated by these
LEDs as described in the following table.

LED indicator
type

LED indicator
name Description

Power On When lit, this LED indicator signifies that

power is present.

Ethernet TX When flashing, this LED indicator signifies

that data is being transmitted by the Remote
Gateway 9150 unit over the Ethernet network.

RX When flashing, this LED indicator signifies

that data is being presented to the Remote
Gateway 9150 unit over the Ethernet network.

COLL When flashing, this LED indicator signifies

that a collision has occurred on the Ethernet
network.

Module L1 and L2 L1 LED indicator:

! not lit: there is no D-channel activity

! flashing: the D-channel is active but the

B-channel is not active

! lit solid: both the D- and B-channels are

active

L2 LED indicator:

! not lit: the B-channel is not active

! lit: the B-channel is active

V.35 TX For future use.

RX For future use.

Boot status Status Indicates the condition of the Remote

Gateway 9150 unit. This LED indicator stays
lit when the power on self-test is successful. If
it goes out, there is a problem.

4 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Collisions

Half-duplex Ethernet connections only allow their nodes to either send or
receive packets at any given time. Collisions occur when two nodes on a half­duplex Ethernet connection attempt to transmit information simultaneously.
Before transmitting, the Network Interface Card (commonly referred to as the
NIC card) monitors the line, or listens, for transmissions. A NIC card listens to
the line for the amount of time that it takes to transfer a minimum-sized packet
the maximum length of the cable. If the NIC card senses no transmission from
the destination node, it proceeds with its own transmission.

If a NIC card detects a collision, it waits for a period of time determined by the
back-off algorithm, then re-transmits the packet. Ethernet nodes keep track of
how many times they must re-transmit a packet with a maximum collision re-try
counter. In previous versions of Remote Gateway 9100 Series software, the
maximum collision re-try counter had a limit of 15. After 16 unsuccessful
attempts to transmit a packet (the original attempt plus 15 re-tries) the Remote
Gateway 9100 Series unit dropped the packet. In an effort to decrease delay and
improve QoS, the limit of the maximum collision re-try counter is now eight.
After nine unsuccessful attempts to transmit a packet (the original attempt plus
eight re-tries) the Remote Gateway 9100 Series unit drops the packet and begins
attempting to transmit the next packet.

Note: Since Ethernet traffic has a nominal speed of 10 Mbps, the flashing
Ethernet COLL, TX, RX LED indicators are cosmetic. They do not reflect real­time traffic patterns or packets.

Connectors

The following connections are made from the rear panel of the Remote Gateway
9150 unit to the telephone and data networks:

! Two 25-pair connectors (labeled TELCO 1 and TELCO 2) provide tip and

ring connections to user stations (telephones) and central office trunks
(ISDN BRI).

These connections provide the interface to the telephone network and the
Public Switched Telephone Network (PSTN).

! An RJ-45 connector (labeled ETHERNET) provides a 10BaseT Ethernet

connection.

This connection provides the ability to pass both voice and data traffic over
the existing Ethernet network.

Remote Gateway 9150 Installation and Administration Guide 5

Remote Gateway 9150 description Standard 3.1

! A DB-9 connector (labeled ADMIN) provides an RS-232 serial port

connection.

You can use this serial port connection to configure a Remote Gateway
9150 unit that is directly connected to a PC.

Refer to Chapter 2, “Planning for Remote Gateway 9150 unit installation,” for a
detailed description of cables and connectors.

Mounting options

The Remote Gateway 9150 unit can be mounted on a desk, in a rack, or on the
wall.

Universal power supply

The Remote Gateway 9150 unit includes an auto-sensing 110/220 V power
supply that is compatible with commercially available UPS systems.Refer to the
diagram on page 7.

Note: If you want to connect the Remote Gateway 9150 unit to a UPS, ensure
that the UPS has a minimum rating of 100 Watts.

6 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Remote Gateway 9150 power supply

TELCO

1

To wall
outlet

ETHERNET

Remote Gateway
9150 cable

Remote Gateway 9150

TELCO 2 POWER ADMIN

Power supply

Power cable

G101536

Remote Gateway 9150 Installation and Administration Guide 7

Remote Gateway 9150 description Standard 3.1

Add-on modules description

The Remote Gateway 9150 unit can support trunk interface modules, such as
ISDN BRI U or S/T interfaces, and up to three DSP application modules.

Optional trunk interface modules

Trunk interface modules route calls over the PSTN. The number of modules you
must install depends on the number of simultaneous calls you want to process in
host-controlled or locally controlled mode.

Note: To determine how many trunk interface modules you need for your
calling requirements, use the “Remote Gateway 9150 System expansion
worksheet” on page 385.

The Remote Gateway 9150 unit can support up to four U or S/T ISDN BRI
interfaces. Each module supports one ISDN BRI line (with two B-channels)
from the local telephone service provider. Refer to the following illustration for
an example of an ISDN BRI module:

ISDN BRI module

U interface (NTDR74xx)
S/T interface (NTDR75xx)

G101420

8 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Note: Initially, the Remote Gateway 9150 unit ships with no ISDN BRI modules
installed.

Optional DSP application modules

DSPs convert voice and fax into digital data for transport over the IP network
and PSTN. Initially, the Remote Gateway 9150 unit ships with the ability to
support up to eight simultaneous calls through a DSP that is built into the
Remote Gateway 9150 unit’s motherboard. To add support for up to 32
simultaneous calls, you must install DSP application modules. Up to three DSP
application modules are supported. Each module provides up to eight more
simultaneous calls.

Note: To determine how many DSP application modules you need for your
calling requirements, use the “Remote Gateway 9150 System expansion
worksheet” on page 385.

In addition, you can configure the Remote Gateway 9150 unit for blocking with
only enough modules to support the maximum number of simultaneous calls.
For example, a Remote Gateway 9150 unit that is equipped with a single DSP
application module supports 16 simultaneous calls, for a ratio of 2 to 1 blocking.
Refer to the following illustration for an example of a DSP application module:

DSP application module (NTDR73xx)

G101388

Note: For more details, refer to “Planning for future growth” on page 72.

Remote Gateway 9150 Installation and Administration Guide 9

Remote Gateway 9150 description Standard 3.1

Connection options

Communications between the Remote Gateway 9150 unit in your office and the
host PBX take place using 10BaseT Ethernet or ISDN BRI connections, or both.
This section provides a description of each of these connections.

10BaseT Ethernet interface

Voice over IP technology is used to carry voice conversation and telephone set
control signals over your IP network to the host PBX. The voice data is
forwarded as UDP/IP packets, and the signaling data is forwarded as TCP/IP
packets.

Note: The Remote Gateway 9150 unit, vintages AC, BC, CC, and earlier use a
half-duplex 10BaseT Ethernet connection. Vintages AD, BD, CD and later
default to a half-duplex 10BaseT Ethernet connection. You can configure a full­duplex 10BaseT Ethernet connection on units of these vintages through
Configuration Manager. When you configure a full-duplex 10BaseT Ethernet
connection, the Remote Gateway 9150 unit's Ethernet collision LED remains on
solid (constantly lit). In addition, when you enable full-duplex Ethernet, you
must also set the corresponding port on the connected switch to 10 FULL
Duplex. Remote Gateway 9100 Series products do not support Auto negotiation
of the Ethernet interface.

ISDN BRI lines to PSTN

The PSTN provides a cost-effective alternative to leased lines. You can use
ISDN BRI lines at the Remote Gateway 9150 site to place local calls without
involving the host PBX. You can also choose to use the ISDN BRI lines instead
of the IP network to route calls through the host PBX.

To use ISDN BRI lines, you must install trunk interface modules. The Remote
Gateway 9150 unit can support up to four U or S/T ISDN BRI trunk interface
modules. (Refer to “Add-on modules description” on page 8.)

Quality of Service (QoS) Transitioning Technology

If both the IP network and ISDN BRI lines are used, you can use the QoS
Transitioning Technology to re-route calls from the IP network to the PSTN
when the QoS on the IP network degrades. When the QoS returns to normal, the
QoS Transitioning Technology automatically moves the calls back to the IP
network.

10 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

The Remote Gateway 9150 unit monitors the QoS on the IP network. If the QoS
falls below pre-programmed acceptable thresholds, calls are dynamically and
transparently switched to the ISDN BRI lines. Refer to “QoS Transitioning
Technology” on page 34 for additional details.

Analog port for fax machines

The Remote Gateway 9150 unit has one analog port that you can use as a fax
connection. Refer to “Fax support” on page 41 for more detailed information.

ATTENTION!

You cannot transfer a call on a telephone set connected to
the analog port of a Remote Gateway 9150 unit. Remote
Gateway 9100 Series does not support Switch Hook flash.

Remote Gateway 9150 Installation and Administration Guide 11

Remote Gateway 9150 description Standard 3.1

Operational characteristics

This section provides details on how the Remote Gateway 9150 unit functions.

System security

This section describes the security levels that are supported for controlling
access from the Remote Gateway 9150 unit to the RLC on the host PBX.

! No security

When no security measures are used, the RLC accepts all incoming calls
from the Remote Gateway 9150 site.

Use this level with caution as it can be prone to unauthorized use. For
example, a user in your site could accidentally, or intentionally, enter a
trunk number for another site and place long distance phone calls through
this connection.

! Caller Identification (ID)

When Caller ID is used, and the PSTN routes the call, the RLC identifies
the Remote Gateway 9150 unit’s calling line identification (CLID). If the
CLID matches the remote number configured on the port assigned to the
Remote Gateway 9150 unit, access is granted. If the incoming call’s CLID
does not match, access is denied.

Note: Caller ID authentication cannot be performed over the IP network.

! Provision ID

You can use Provision Identification (ID) authentication over the IP
network or PSTN. When you choose Provision ID, the Remote Gateway
9150 unit sends its 10-digit security identifier (password) for each
connection request. The RLC compares the security identifier with the one
configured on the RLC port where the Remote Gateway 9150 unit is
assigned. If the security identifiers match, access is granted.

If the security identifiers do not match, then an event is recorded in the
Remote Gateway 9150 unit system log (you can view the system log in
Configuration Manager). The telephone that was used to place the call
displays a message indicating that communications with the host PBX are
down.

12 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

You must configure two security identifier passwords on the Remote
Gateway 9150 unit:

— inbound security identifier: This is the RLC’s security identifier. It is

presented on incoming calls.

— outbound security identifier: This is the Remote Gateway 9150 unit’s

security identifier. It is presented to the RLC on outgoing calls.

You must configure the same security identifiers in reverse on this Remote
Gateway 9150 unit’s RLC port.

Trunk connections

The Remote Gateway 9150 unit supports the following digital trunk
connections:

! ISDN BRI from the Remote Gateway 9150 unit to the PSTN

! ISDN PRI from the PSTN to the RLC at the host site

Multiple Subscriber Numbering (MSN)

Remote Gateway 9100 Series supports MSN. If the Central Office provides each
B-channel with a unique DN, then the first B-channel that you configure defines
the number for both B-channels.

Remote Gateway 9100 Series requires the ISDN numbers to be unique per
module for PSTN connections between the RLC and Remote Gateway 9150
unit.

Do not configure B-channels as Local and Remote if MSN is disabled.

For Remote Gateway 9150 units with multiple BRI modules:

! Configure a maximum of one BRI module as Remote Only if PSTN

connections are required.

! Configure all other BRI modules as Local only.

For Remote Gateway 9150 units with just one BRI module the BRI module can
be configured as Local only or Remote only. If local ISDN calls and remote
calls over PSTN are required, then MSN must be enabled.

Remote Gateway 9150 Installation and Administration Guide 13

Remote Gateway 9150 description Standard 3.1

64K (56K) dynamic adaptation

With some carriers, 64K calls routed over a 56K PSTN infrastructure may cause
errors. The dynamic adaptation feature allows the Remote Gateway 9150 unit
and the RLC to dynamically detect the limitation of the bandwidth. The call is
then downgraded from 64K to 56K.

Bandwidth allocation

The RLC automatically allocates trunk bandwidth to the Remote Gateway 9150
connection as needed. For example, as calls are initiated and bandwidth
requirements increase, additional trunk connections are established. Likewise, as
calls terminate and bandwidth requirements drop, connections to idle trunks are
terminated.

Connection types

The Remote Gateway 9150 connection to the RLC can be defined on the RLC as
permanent or on demand. A permanent connection means that the ISDN
connection to the host PBX always remains open. An on demand connection
means that the ISDN connection is established only when a connection with the
host PBX is required.

If the connection is defined as demand, then you can configure minimum call
duration and idle timers on the RLC to help reduce call charges.

Minimum call duration timer

Most ISDN tariffs specify minimum charges incurred when you open the line,
regardless of the call duration. This charge is the minimum call charge listed on
long distance telephone bills.

The minimum call duration timer is used in PSTN mode only and specifies the
minimum length of time that each PSTN call to the host PBX remains active,
regardless of telephone activity or inactivity. Configure the timer on the RLC to
drop inactive connections just before an additional charge period is incurred. For
example, if the timer is set to 59 seconds and your call lasts only 20 seconds, the
ISDN connection drops when the timer reaches 59 seconds.

14 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

If another call is made to the host PBX before the timer expires, the timer is
reset. The timer tracks the current call.

Idle timer

The idle timer identifies the maximum length of time that an ISDN connection
remains idle before Remote Gateway 9100 Series closes it. Idle means that a
voice connection exists but is not active, and buttons are not being pressed on
digital telephones.

For example, if the idle timer is set on the RLC to 60 seconds, the ISDN call
remains open for 60 seconds after you hang up. If you or someone else dials
another number before 60 seconds have passed, another ISDN connection is not
opened.

How the timers work to control ISDN costs

The minimum call duration and idle timers work together to control ISDN
charges. The following examples describe what happens when the minimum call
duration timer is set to 59 seconds and the idle timer is set to 60 seconds.

Example 1

If the call lasts for 20 seconds and no other calls are made, the ISDN connection
drops when the minimum call duration timer reaches 59 seconds. The minimum
call duration timer expires before the idle timer.

Example 2

If the call lasts for 65 seconds and no other calls are made, the ISDN connection
drops after another 60 seconds has passed without activity. Since the ISDN call
exceeded 59 seconds, the minimum call duration timer no longer applies. The
idle timer is used, in this case, to prevent further ISDN charges.

Remote Gateway 9150 Installation and Administration Guide 15

Remote Gateway 9150 description Standard 3.1

How the Remote Gateway 9150 unit works

There are two major components to the Remote Gateway 9150 product:

! the Remote Gateway 9150 unit located in your office

! the RLC located on the PBX at the host site

These two components, along with the connection options described on page 10,
extend the host PBX services to users in your office.

The following diagram shows a RLC and Remote Gateway 9150 network:

Remote site 1: Branch office

Up to 32 digital telephones Fax machine

Remote Gateway 9150

P

O
W

E

R

E
T

H
E
R

N

E
T

T
X

R
X

C
O

LL

1
L
1

M

2

O

D
U

2

L

E

L
1L

L2

3

L

1

L

2

4

L1

V

.3

L

2

5

T

S

X

T
A

T
U

RX

S

Ethernet

Central
office
trunks
(ISDN BRI)

ISDN PRI

Public

Corporate

WAN

Telephone

Network

Ethernet

16 Remote Gateway 9150 Installation and Administration Guide

Corporate office

Host PBX

Reach Line Card

G101391

January 2005 Remote Gateway 9150 description

Outgoing call process

To place outgoing calls, users can either pick up the handset on the telephone or
press a line appearance key. There are two types of line appearance keys:

! host call appearance key

Use this key to place a call through the host PBX.

! local call appearance keys

Use these keys to place calls to other stations in your office, or to place and
receive calls through the local PSTN. You can define up to two local call
appearance keys on each digital telephone.

For a detailed description of the outgoing call process, refer to the sample
illustrations beginning on page 20.

Incoming call process

When a user places a call through the host PBX to a user at the Remote Gateway
9150 site, a connection is made from the RLC to the Remote Gateway 9150 unit
and the host PBX completes the call. If a connection cannot be established, then
the call rings until it is forwarded to voice mail by the host PBX. Refer to
Chapter 6, “Using Remote Gateway 9150 stations,” for a more detailed
description of the incoming call process.

When someone places a call through the PSTN to a user at the Remote Gateway
9150 site, a connection is made from the central office to the Remote Gateway
9150 unit. The number that outside callers dial is the number assigned by the
ISDN service provider to the ISDN BRI B-channel carrying the incoming call.

You can configure an unanswered incoming local call to Call Forward to a DN
on the host PBX. The Bridge Port connects the call to the host PBX and it can
then transfer to voicemail.

Remote Gateway 9150 Installation and Administration Guide 17

Remote Gateway 9150 description Standard 3.1

Bridge Port

A Bridge Port is a proxy port that represents a local or inbound PSTN call to the
host PBX. When a local incoming call on a Remote Gateway 9150 unit needs
PBX services, the Bridge Port obtains a PBX presence on behalf of the local
call.

Bridge Ports can represent the following types of local calls:

! Call Forward: A Local and Remote call made to another Local and Remote

telephone uses Call Forward to connect to a third telephone on the PBX.

! Call Transfer: A Local call to a Local and Remote telephone uses Call

Transfer to connect to a local trunk or a host-based set.

! Conference: A Remote call to a host telephone can connect to trunk call(s),

or if you are on a call to a local trunk, you can connect to host telephone(s)
to create three-or-more-party telephone calls.

To configure Remote Gateway 9150 Bridge Ports refer to page 250.

Host controlled call mode

When a user places a call to someone at the host site, or when someone from the
host site calls the Remote Gateway 9150 site, the call is in host-controlled call
mode. Calls in host-controlled mode are routed through the host PBX. Refer to
the sample illustrations on pages 20 and 22.

Locally controlled call mode

When a user places a call from a local call appearance key, or the call is to
another telephone at the Remote Gateway 9150 site, the call is in locally
controlled mode. Calls that are initiated from the local call appearance key are
routed through the local PSTN. Calls to other extensions in the Remote Gateway
9150 site are routed only through the Remote Gateway 9150 unit.

The host PBX is not involved in locally controlled mode calls. Refer to the
sample illustration on page 24.

18 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

QoS Transitioning Technology

If the QoS on the IP network falls below a predefined threshold, you can
configure the Remote Gateway 9150 unit to automatically route voice traffic
away from the IP network connection to the PSTN connection. Refer to “QoS
Transitioning Technology” on page 34 for a detailed description.

Remote Gateway 9150 Installation and Administration Guide 19

Remote Gateway 9150 description Standard 3.1

Call scenario 1: host-controlled—internal corporate call

The following diagram shows how a call is routed when making a
host-controlled call to the corporate office.

Host-controlled call (corporate internal call)

Branch office
(Chicago)

Ethernet network

Host location
(Los
Angeles)

Host
PBX

C

Up to 32 digital telephones

User 1 User 2 User 3

A

Remote Gateway 9150

P
O

W

E
R

E
T

H
E

R

N

E
T

T
X

R
X

C
O

L
L

1
L
1

M

L

O

2

D
U

2

L
E

L
1

L
2

3

1

L
2L

4

1

V

.
3

L
2L

5

T

S

X

T
A

T
U

R

S

X

B

RLC

4

1

Central office trunks
(ISDN BRI)

2

PSTN

ISDN PRI

3

Host
stations

1

2

3

Voice over IP call
PSTN call

G101392

The network that is used to route the host-controlled call is transparent to the
user, and the dialing requirement is the same for both. Calls work the same way
in reverse, from host PBX site to the Remote Gateway 9150 site.

20 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Voice over IP network call

1 User 1 presses the host call appearance key.

Result: User 1 hears a dial tone. This indicates that the connection to the

RLC over the IP network was successful.

2 User 1 dials a telephone number (such as the extension number of host

station 1).

Result: The dialed digits are sent by the Remote Gateway 9150 unit as
packets across the Ethernet network. The RLC converts the packets to the
format required by the PBX. The PBX then converts the data to voice and
routes the call to host station 1.

PSTN call

1 User 3 presses the host call appearance key.

Result: User 3 hears a dial tone. This indicates that the connection to the

RLC over the PSTN was successful.

2 User 3 dials the telephone number (such as the extension number of host

station 3).

Result: Dialed digits are sent across the PSTN then sent through the host
PBX to host station 3.

Remote Gateway 9150 Installation and Administration Guide 21

Remote Gateway 9150 description Standard 3.1

Call scenario 2: host-controlled—external corporate call

The following diagram shows how a call is routed when making a
host-controlled call to a party outside the organization.

Host-controlled call (corporate external call)

Branch office
(Chicago)

Ethernet network

Host location
(Los
Angeles)

Host
PBX

1 3

2

Up to 32 digital telephones

User 1 User 2 User 3

A

Remote Gateway 9150

P

O

W

E
R

E
T

H

E
R

N
E

T

TX

RX

COLL

1

L1

M

O
D

U

2

L
E

L1L2

L2

3

L1

4

L1L2

V

.3

L2

5

TX

S
T

A
T

U

RX

S

B

RLC

Voice over IP call
PSTN call

1

Central office trunks
(ISDN BRI)

2

ISDN PRI

PSTN

3

C

D

4

Called party
is local
pizza parlor
(Chicago)

5

G101393

The network used to route the call is transparent to the user, and the dialing
requirement is the same for both. Calls work the same way in reverse, through
the host PBX site to the Remote Gateway 9150 site.

22 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Voice over IP network call

1 User 1 presses the host call appearance key.

Result: User 1 hears a dial tone. This indicates that the connection to the

RLC over the IP network was successful.

2 User 1 dials the external telephone number.

Result: The dialed digits are sent by the Remote Gateway 9150 unit as

packets across the Ethernet network. The RLC converts the packets to the
format required by the PBX. The PBX then converts the data to voice and
routes the call through the PSTN to the called party.

PSTN call

1 User 3 presses the host call appearance key.

Result: User 3 hears a dial tone. This indicates that the connection to the

RLC over the PSTN was successful.

2 User 3 dials the external telephone number.

Result: Dialed digits are sent across ISDN BRI through the PSTN, through

the host PBX to the called party.

Remote Gateway 9150 Installation and Administration Guide 23

Remote Gateway 9150 description Standard 3.1

Call scenario 3: locally controlled mode—local call

The following diagram shows how a call is routed when making a call within
your local area.

Locally controlled call

Branch office
(Chicago)

Ethernet network

Host location
(Los
Angeles)

Host
PBX

1 3

2

Up to 32 digital telephones

User 1 User 2 User 3

1

Remote Gateway 9150

POWER

ETHERNET

T
X

R
X

C
O

L
L

1
L
1

MODULE

L
2

2
L
1

L
2

3

L

1

L
2

4
L
1

V.35

L
2

T

STATUS

X

R
X

RLC

PSTN call

Central office trunks
(ISDN BRI)

2

PSTN

ISDN PRI

3

Called party
is local
pizza parlor
(Chicago)

G101394

24 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Local call

1 User 1 presses the local call appearance key and hears a dial tone from the

Remote Gateway 9150 unit.

2 User 1 then dials a trunk access code (such as #61) and hears a dial tone

from the Central Office (PSTN).

Note: If all trunks are busy and unavailable, then User 1 hears a fast busy
signal.

3 User 1 dials the telephone number (the pizza parlor in this example). The

dialed digits are sent across the ISDN BRI connection through the PSTN to
the called party.

Remote Gateway 9150 Installation and Administration Guide 25

Remote Gateway 9150 description Standard 3.1

Telephones

This section lists the telephones, modules, and related applications supported by
the Remote Gateway 9150 unit. This section also describes some of the basic
characteristics of these elements of a Remote Gateway 9100 Series system.

Supported digital telephone sets

The Remote Gateway 9150 unit supports following Meridian digital telephone
sets:

! M2008D

! M2008HFD

! M2216D

! M2616D

! M3110

! M3310

! M3820

! M3901

! M3902

! M3903

! M3904

! M3905

Notes:

1. Because it is a discontinued model, the M2616CT cordless digital
telephone set is no longer supported.

2. When you update the message on the host PBX that displays when the
digital telephone set is idle, you must unplug the digital telephone set and
plug it back in for the change to take effect.

Notes for M2xxx series digital telephone sets:

1. The M2006 digital telephone set is also supported, but can be used only for
locally controlled calls.

2. Auto Answer Back (AAB) activation on M26xx series digital telephone
sets on Remote Gateway 9100 Series units connected to CS 2100 PBXs
does not produce a dial tone. The digital telephone sets operate properly,
but no dial tone is present. To produce dial tone in this situation, configure
the port on the RLC as a TAPI port.

26 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Notes for M39xx series digital telephone sets:

1. If you want to use an M3901 digital telephone set for remote (host­controlled) calls, you must configure the digital telephone set as an M3901
at the remote unit and as an M3902 at the host PBX. For local calls, you
must configure the M3901 digital telephone set as an M3901 at both the
remote unit and the host PBX.

2. To label the Local Keys on M3902 digital telephone sets, use the options
key on the digital telephone set itself.

3. The M3904 digital telephone set Key Map fails using Virtual Office on
Remote Gateway 9100 Series. Upgrade the digital telephone set’s firmware
to version 7.9 to resolve this problem.

4. Uploading and downloading M3904 and M3905 firmware requires the
most recent digital telephone set hardware. To resolve problems following
firmware uploads and downloads, including missing functionality, refer to
the User Guide and Release Notes for your particular digital telephone set.

5. When logging on to an ACD queue using an M3905 digital telephone set
connected to a Remote Gateway 9150 unit, the logon process takes longer
than expected if a headset is not plugged into the digital telephone set.
Initialization of the digital telephone set under these conditions can take up
to one minute.

6. Phase I M3905 digital telephone sets receive false messages during a re­boot of the Remote Gateway 9150 unit and can lock up. Unplug and re-plug
the telephone cord at the wall jack or perform a system shutdown and re­power up the Remote Gateway 9150 unit to recover. This is not a problem
with Phase III M3905 digital telephone sets.

7. When you answer an incoming local call on an M39xx digital telephone
set, the call log records the calling DN. However, you cannot dial directly
from the Call Log, as the trunk access code and country code do not always
appear. To resolve this, navigate through the call log to the number that you
want to dial. Press the Edit key and the digit(s) of the missing code(s).
Press the Done key. To dial the revised number, press the Dial key.

Remote Gateway 9150 Installation and Administration Guide 27

Remote Gateway 9150 description Standard 3.1

For example, the call log for an ISDN number displays the digits

4445551212. The missing trunk access code (9) and country code (0) are
required to dial the number. Use the Edit key to enter the missing digits, 9
followed by 0. The number now appears in the M39xx’s LCD display as

904445551212. The end-user can now press the Dial key to place the call
from the call log.

8. If you downgrade the host PBX to a release prior to X11 release 25.40, you
must also downgrade any new or upgraded M39xx digital telephone sets so
that the Meridian 1 PBX can support them. This applies to digital telephone
sets attached to Remote Gateway 9100 Series units and Extended Digital
Line Cards.

9. Flash upgrade download times to remote M39xx digital telephone sets over
an IP network with low delay and packet loss are comparable to PBX wired
downloads. Using PSTN bandwidth on a Remote Gateway 9150 unit or a
Remote Gateway 911x series unit, download times increase.

28 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

M2000 series (M3310, and M3820 European models) and M39xx series
digital telephone set model and accessory compatibility

Compatibility with

Remote Gateway 9150

Digital Telephone Set Models

M2006 ✓

M2008D, M2008HFD ✓

M2616D ✓

M2216D-ACD ✓

M2616CT Cordless Discontinued

M3310, M3820 (Europe only) ✓

ii

M3901

M3902, M3903 ✓

M3904 ✓

M3905 (ACD) ✓

M2000 series (M3310 & M3820 European models) Add-on Modules

Headsets ✓

External alert ✓

Key-based expansion module ✓

ATA (Analog Terminal Adapter)

MCA (Meridian Communications Adapter) ✓

i.The host PBX must be running software capable of supporting each digital telephone

set model used.

ii.Refer to the Meridian digital telephone hardware compatibility section of the Reach

Line Card Installation and Administration Guide (NTP 555-8421-210) for required
configuration details.

iii.ATA modules support analog telephone sets and facsimile (FAX) machines. ATA

modules do not support modems.

i

iii

units

✓

✓

Remote Gateway 9150 Installation and Administration Guide 29

Remote Gateway 9150 description Standard 3.1

M39xx series digital telephone set accessory compatibility

The following table shows Remote Gateway 9150 unit compatibility with
M39xx series digital telephone set accessories.

Compatibility with
M39xx series Digital Telephone Set Accessories
and Add-on Modules

Headsets ✓

External alert & recording interface ✓

Key-based expansion module (22-button, up to two per
3904/05)

Display-based expansion module ✓

ATA (Analog Terminal Adapter)

Personal Directory PC utility ✓

Full-duplex Speakerphone ✓

CTI (Computer Telephony Integration) Adapter ✓

i.The Remote Gateway 9150 unit supports ATA modules. These modules support analog

telephone sets and facsimile (FAX) machines. They do not support modems.

i

Remote Gateway 9150

units

✓

(Refer to Note i)

Supported telephone modules

The following telephone modules are supported:

! add-on modules (to add more keys)

! application modules that provide more functionality

! Meridian Communication Adapters (MCA)

! Analog Telephone Adapters (ATA)

Notes:

1. You cannot dial host PBX calls from the Call Log of M39xx series digital
telephone sets because the Trunk Access code and country code can be not
displayed. You cannot dial local calls from the Call Log of the M39xx
series digital telephone sets because the information contained in the Call
Log does not contain trunk group information.

2. After re-boot of a Remote Gateway 9150 unit, re-boot each ATA as well.

30 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Computer telephony integration (CTI) applications

There are two types of CTI applications:

! first-party CTI applications that use the Symposium Desktop TAPI Service

Provider

! third-party CTI applications that use Symposium TAPI Service Provider for

the Meridian 1 PBX

Both types can be used with the Remote Gateway 9150 unit.

TAPI Type Supported CTI Application

Symposium Desktop TAPI Service
Provider 1.6

Symposium TAPI Server Provider
for Meridian 1 PBX release 2.1

! Symposium FastView 1.6

! Symposium FastCall 1.6

! Symposium Call Manager 5.0

! other TAPI-compliant applications

! Symposium Agent 1.1

! Symposium Call Manager 5.0

! other Symposium Partner products

You can use first-party CTI applications with the Remote Gateway 9150 unit if

! your PC is equipped with a Symposium Communicator card version 1.2

with software version 2.0

! your digital telephone is equipped with a Meridian Communications

Adaptor (MCA)

Note: The Symposium Communicator card is not available in all countries.
Check with your Nortel distributor for availability.

Remote Gateway 9150 Installation and Administration Guide 31

Remote Gateway 9150 description Standard 3.1

Automatic Call Distribution (ACD) applications

The Remote Gateway 9150 unit supports all Nortel ACD applications.

If an ACD agent loses communication to the Remote Gateway 9150 unit, or the
unit goes offline, the agent is placed in Make Set Busy (MSB) mode. This mode
logs the agent out of the ACD queue so that calls can be routed to other ACD
agents. Once you re-establish communication between the agent and the Remote
Gateway 9150 unit, the digital telephone set display shows “Set Busy
Activated”.

In addition, when an ACD agent is on a call using a Local Calling key, the
Remote Gateway 9150 unit sends a transparent Not Ready key press to the host
PBX and places the ACD agent’s digital telephone set in Not Ready mode. This
feature prevents the ACD agent from receiving ACD calls when active on a
local call. The Remote Gateway 9150 unit removes the digital telephone set
from the Not Ready mode when the agent terminates the local call.

If you are having trouble with ACD agents being logged off unexpectedly or
calls that terminate prematurely, try the following:

! Set the User On Demand Idle Timer to 90 seconds and the User On

Demand Minimum Call Timer to 1 second.

Note: You can configure these settings on the RLC’s Remote Connection
Configuration property sheet in Configuration Manager.

! Allocate a permanent connection for the ACD agents.

— On the RLC Port Configuration property sheet, click on the Configure

button for the Network Port in question.

— In the Network Port Configuration dialog box, select Permanent

Allocation.

Voice over IP features

You can configure the Remote Gateway 9150 unit to use the following Voice
over IP (VoIP) features:

! Convert analog voice into digital data for transmission as voice packets

over the network for calls to or from the fax machine or other analog device
that is connected to the analog port on Telco 1.

32 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

! Automatically switch from the IP network to the PSTN when the voice QoS

on the IP network falls below a predetermined threshold, and back to the IP
network when the QoS returns to normal.

Packetized voice

DSPs located in the Remote Gateway 9150 unit convert voice into digital data
packets and, if compression is used, compresses them. The data is constructed as
UDP/IP voice packets for transmission over the IP network.

When voice packets are compressed, they consume less bandwidth, leaving
more bandwidth for data or other voice or fax communications. The following
algorithms are supported:

! G.711: Packets are transmitted at 64 Kbps (that is, they are not

compressed).

! G.726: Packets are compressed and transmitted at 32 Kbps.

! G.729A: Packets are compressed and transmitted at 8 Kbps.

G.729A is the default algorithm on both the RLC and the Remote Gateway 9150
unit.

In addition to voice compression, the Remote Gateway 9150 unit supports the
following additional packetized voice features:

! A voice jitter attenuation buffer removes the variable delays from the voice

packets sent across the IP network, thus avoiding awkward-sounding
speech.

! Packet loss handling techniques accommodate missing packets or packets

received too late to be processed.

! Silence suppression prevents packet transmission during periods when

there is no voice data present. Comfort noise is inserted to assure the user
that the line is still active.

Silence is determined when the difference between the adaptable noise
floor and the detected signal is less than 9 dB. To prevent clipping, silence
must be present for a minimum of 250 milliseconds.

Remote Gateway 9150 Installation and Administration Guide 33

Remote Gateway 9150 description Standard 3.1

QoS Transitioning Technology

Communications between the Remote Gateway 9150 unit in your office and the
host PBX take place across the IP network using a 10BaseT Ethernet interface.
You can configure the Remote Gateway 9150 unit to switch automatically from
the IP network to the PSTN when the voice QoS falls below a predetermined
threshold. Within the QoS settings, you can also enable Differentiated Services
(DiffServ) and 802.1Q Mapping to give priority to voice over IP traffic on your
network.

Both the RLC and the Remote Gateway 9150 unit monitor the IP network’s QoS
constantly. If the IP network QoS degrades, causing poor voice quality, the
Remote Gateway 9150 unit moves, or transitions, the call to the PSTN. When
the QoS returns to normal, the Remote Gateway 9150 unit transitions the call
back to the IP network.

QoS transition recovery

Due to the requirement for on-demand router support, the IP network is not
continually tested during QoS transition situations. It is tested only when there
are active voice calls over the PSTN. As a result, to switch back to the IP
network, QoS Transitioning Technology needs active calls for the user­configured recovery period.

If you test QoS transition by disconnecting the Ethernet cable from the Remote
Gateway 9100 Series unit, or RLC, expect up to a 20-second delay before the
Remote Gateway 9100 Series unit can place or receive a call. You do not
encounter this delay when the network degrades and calls switch to BRI as
designed.

For detailed instructions on configuring the thresholds, refer to the Reach Line
Card Installation and Administration Guide (NTP 555-8421-210). For
guidelines on evaluating and adjusting the QoS on your IP network, refer to the

Remote Gateway 9100 Series Network Engineering Guidelines

(NTP 555-8421-103).

Voicemail messages and Quality of Service transitions

It can take several seconds of sustained errors to cause a Quality of Service
(QoS) transition to the PSTN. During this time, voice quality may suffer due to
errors. If a message to a voice mailbox is being recorded during these errors,
portions of the message can be unintelligible.

34 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Log reports and statistics

Configuration Manager provides a statistics log that identifies the number of
QoS transitions (refer to “Caller Info Statistics” on page 300).

Refer to Chapter 7, “Administration” for a detailed description of log and
statistic reports.

Port management

You can assign Remote Gateway 9150 stations to one of the following types of
RLC ports:

! single-user ports

! multi-user voice ports

! dynamic port pool

Port types are assigned on the RLC. Refer to the Reach Line Card Installation
and Administration Guide (NTP 555-8421-210) for detailed instructions.

Single-user ports

Each port that is defined as a single-user (dedicated) port on the RLC supports
one Remote Gateway 9150 station.

Multi-user ports

Ports that are defined on the RLC as multi-user ports allow multiple stations on
different Remote Gateway 9150 units to time-share a single port on the host
PBX.

Up to eight persons can share the same RLC port, but not at the same time. All
stations that use this type of port must respond to the same DN and have
identical telephone set configurations. This port type is especially useful for
employees who work mutually exclusive shifts.

Dynamic port pool

Dynamic port pooling is similar to a multi-user port except that the persons who
share ports in a dynamic pool are assigned to the next available port in the RLC
port pool. There is no correlation between the station and the port on the RLC.

This feature is especially useful in free-seated ACD environments where agents
log on to the host PBX using their agent IDs.

Remote Gateway 9150 Installation and Administration Guide 35

Remote Gateway 9150 description Standard 3.1

Station priority

You can define the priority of a station’s assigned RLC port as normal, high, IP
only, or circuit only.

Normal priority

When both the IP and PSTN networks are used to route calls, calls to and from
the station are routed primarily over the IP network. Calls transition between the
IP and PSTN networks whenever voice QoS levels change. (The voice QoS
levels are defined on the Quality of Service screen on the RLC for your Remote
Gateway 9150 unit.)

High priority

When you define an RLC port as high priority, the associated station has the
following benefits:

! If allowed to use the IP network to process calls (this is transparent to the

user), an active call on that station is always one of the first to transition to
PSTN trunks when Voice over IP QoS degrades. (This transition is
accomplished using the QoS Transitioning Technology.)

! Call blocking is reduced because bandwidth is always available to these

stations.

Note: If the reserved bandwidth is being used by other high priority
stations, then new calls are processed using unreserved bandwidth.

The number of stations that you can configure as high priority depends on the
amount of available bandwidth. Ensure that enough bandwidth is available to
process calls on normal priority stations.

IP only

Calls to and from the station are routed over the IP network only. QoS
transitioning is not available for stations that are defined as IP only.

Circuit only

Calls to and from the station are routed over the PSTN network only. Circuit
only stations never experience voice QoS degradation.

36 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Connection bandwidth

On the connection between the RLC and the Remote Gateway 9150 unit, you
can configure the following:

! when to open additional B-channels (referred to as extra bandwidth)

! how much bandwidth to reserve for high priority stations (referred to as

priority reserved bandwidth)

For instructions, refer to “Configuring ports” in the Reach Line Card
Installation and Administration Guide (NTP 555-8421-210).

Extra bandwidth

When available bandwidth is no longer sufficient to process active calls,
additional B-channels are opened according to the extra bandwidth setting. For
example, if you configure the extra bandwidth setting as 16 Kbps, another
B-channel opens when existing bandwidth is reduced to 16 Kbps or less.

Priority reserved bandwidth

The priority reserved bandwidth setting defines how much bandwidth to reserve
for high priority stations. The reserved bandwidth cannot be used by stations
configured as normal, IP only, or circuit-only priority. High priority stations
consume priority reserved bandwidth before consuming unreserved bandwidth.

For example, if you configure the priority reserved setting as 16 Kbps, then only
high priority stations can use this reserved bandwidth. When the reserved
bandwidth is being used for active high priority calls, additional calls from high
priority stations are processed using unreserved bandwidth. If no bandwidth is
available, calls to or from high priority stations are blocked until bandwidth
becomes available.

Local calling

The Remote Gateway 9150 unit allows you to place calls to other extensions
within your office or to telephones in your local community. This is
accomplished through the use of up to two local call appearance keys. Refer to
Chapter 6, “Using Remote Gateway 9150 stations,” for a detailed description of
the local call appearance keys.

Remote Gateway 9150 Installation and Administration Guide 37

Remote Gateway 9150 description Standard 3.1

The Remote Gateway 9150 unit discovers the DN numbers of the local digital
telephones either through DN Discovery or configuration. The Bridge Ports,
Local Calling, and Local SwitchOver features depend on this knowledge as
follows:

! If a call has an appearance on a Local Calling key, the Remote Gateway

9150 unit first attempts to complete the operation (for example, call,
transfer, forward) using the local dialing plan.

! If a call is placed from a Local Calling key to a number not found in the

Remote Gateway 9150 unit’s local list, then a Bridge Port is used to place
the intended call to the host PBX.

Local extension calling

When you place a call to another telephone in your office using the local call
appearance key, it is handled by the Remote Gateway 9150 unit, not the host
PBX.

Note: If the call is initiated from the host call appearance key, then the
station-to-station call requires transmission of signaling data through the host
PBX.

Local SwitchOver

Local SwitchOver is a mechanism that the Remote Gateway 9150 unit uses to
determine if a PBX-controlled call that originated on the Remote Gateway 9150
unit is destined for a DN on the same Remote Gateway 9100 Series unit.

Note: The DN Discovery feature is necessary for the Local SwitchOver feature
to work properly. Refer to the Reach Line Card Installation and Administration
Guide (NTP 555-8421-210) for more information.

In this situation, the Remote Gateway 9150 unit switches to a local 64K channel
and cross-connect the voice-paths of the phone without using wide area
bandwidth.

There are times, however, when the Remote Gateway 9150 unit does not know
that an incoming and outgoing call are part of the same call (for example, you
transfer/forward a call within the same PBX, or re-dial the last number).
Although the call still functions, it consumes Wide Area bandwidth.

Local SwitchOver is not available if the call is answered with the Handsfree
button on M39xx telephones.

38 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Local calls through PSTN

The Remote Gateway 9150 unit allows you to place outgoing and answer
incoming PSTN calls over the ISDN BRI connection.

Refer to Chapter 6, “Using Remote Gateway 9150 stations,” for a more detailed
description of local calling.

Bridge Port

Bridge Ports are proxy ports that represent local calls or inbound PSTN calls to
the PBX. When a local call on a Remote Gateway 9150 unit needs PBX
services, the Bridge Port obtains a PBX presence on behalf of the local call.

Call restrictions

To prevent outgoing calls to certain types of numbers (for example, 1-976), you
can disable outgoing calls to specific digit sequences.

Supported digital telephone features

Remote Gateway 9100 Series supports the following Meridian digital telephone
features for locally controlled calls:

! Paging

! Call Waiting

! Hold for calls that appear on local call appearance keys

! Call Transfer (blind and announced) for station-to-station calls only

! Release

! Handsfree

! calling line identification (CLID) and calling party name display (CPND)

Unsupported telephone features

Remote Gateway 9100 Series does not support Distinctive ring functionality of
any kind.

Digital telephone features requiring Bridge Ports

You must configure Bridge Ports for Remote Gateway 9100 Series to support
the following Meridian digital telephone features for locally controlled calls:

! Conference

! Call Forward

Remote Gateway 9150 Installation and Administration Guide 39

Remote Gateway 9150 description Standard 3.1

Online/offline table

The online/offline table is configured on the RLC and allows you to schedule
times

! when the ISDN BRI connection to the host PBX is made available to the

Remote Gateway 9150 site

Note: When the Remote Gateway 9150 unit is in offline mode, users
cannot place or receive calls through the host PBX over the IP or PSTN.

! when all telephones at the Remote Gateway 9150 site revert to normal

telephone service

This allows you to ensure that unwanted ISDN BRI telephone calls through the
host PBX are disabled after business hours.

How the table works

You can define up to eight entries per day, every day of the week, for each
remote site. You can define each entry as online, offline, or undefined for each
time period entered.

Users at the Remote Gateway 9150 site can override the settings of the online/
offline table, if the table attempts to suspend access to the host PBX in the
middle of a business call. Each user station at the remote site is alerted by a buzz
and a display message at 30, 20, and 10 seconds before the connection is
terminated. To override connection termination, the user must enter the online
SPRE (Special Prefix) code on the telephone.

Configuration

The online/offline table is configured for each remote site on the RLC. Refer to
the Reach Line Card Installation and Administration Guide
(NTP 555-8421-210) for configuration information.

For a description of how to go online or offline at the Remote Gateway 9150
site, refer to Chapter 6, “Using Remote Gateway 9150 stations.”

40 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Other supported features

In addition to the features described in the previous sections, the Remote
Gateway 9150 unit also supports the following features:

Fax support

The Remote Gateway 9150 unit contains one analog port that can be used to
send and receive faxes. You can send and receive faxes in both host- and locally
controlled call modes over the IP or PSTN.

To support faxing through the host PBX, the fax port on the Remote Gateway
9150 unit must be associated with a port on the RLC that is configured on the
host PBX with voice capability.

Emergency activation code

If your community has implemented an emergency service number (such as 911)
to call the police, fire department, or ambulance, you can configure that number
on the Remote Gateway 9150 unit. This allows users in your office to dial the
emergency number and be connected directly to the local emergency dispatch
center through the PSTN. The call is automatically routed through the local
PSTN without having to dial a local trunk access code.

When you configure an emergency activation code on the Remote Gateway
9150 unit, you also prevent the call from being automatically routed through the
host PBX. This is because the PBX can be in a different city. An emergency call
that is routed through the host PBX can result in emergency support being
dispatched to the wrong location.

ATTENTION!

If you are using only the IP network to route calls, place
emergency service calls on a telephone that is directly
connected to a PSTN line. If you place an emergency
service call from a station that is connected to the Remote
Gateway 9150 unit, the call is routed through the host PBX.
If the PBX is in a different city, the call contacts the wrong
emergency services.

Remote Gateway 9150 Installation and Administration Guide 41

Remote Gateway 9150 description Standard 3.1

Communications system and software requirements

The following table shows the software versions necessary to run Remote
Gateway 9150 units on compatible Nortel’s communications systems.

Remote Gateway 9150, Remote Gateway 911x series, and Digital
Telephone IP Adapter units

Communications system

Meridian 1 PBX X11 release 23 or higher

CS 1000 Release 2 or higher

CS 2100 Release MSL12 or higher

i. Requires Remote Gateway 9100 Series software version 1.5 or higher.

Supported Codecs

The following tables show the Codecs supported by the Remote Gateway 9100
Series and Digital Telephone IP Adapter units, as well as the data stream, and
approximate peak bandwidth required by each.

Remote Gateway 9150 units

CODEC Data stream only

G.711 64 Kbps 78 Kbps

G.726 32 Kbps 44 Kbps

G.729A 8 Kbps 22 Kbps

i

System software version

Approximate total bandwidth, including IP
overhead (30 ms voice packets)

42 Remote Gateway 9150 Installation and Administration Guide

January 2005 Remote Gateway 9150 description

Administration software

Configuration and administration of the Remote Gateway 9150 unit is
performed with Configuration Manager software, a Windows-based application
that is installed on your PC.

The software is provided on the Remote Gateway 9100 Series Product CD­ROM. You can obtain the CD from your Nortel distributor or click on the
Support link at the following website:

www.nortel.com

Administration PC connection options

You can connect the administration PC to the Remote Gateway 9150 unit
through the following:

! an RS-232 connection to the administration PC’s serial port

! a 10BaseT Ethernet interface connection

Remote Gateway 9100 Series Configuration Manager

Remote Gateway 9100 Series Configuration Manager allows you to configure
the Remote Gateway 9150 unit. It also provides the Configuration Wizard for
first-time configuration. The Configuration Wizard prompts you for the
minimum information that is needed to get the Remote Gateway 9150 unit
communicating with the RLC on the host PBX. After the initial configuration is
completed, use Configuration Manager to administer the Remote Gateway 9150
unit. Administration tasks include the following:

! viewing the system status

! performing upgrades, backups, or restores

! making configuration changes

! changing the administration password

Note: Configuration Manager alerts you when you must restart after you have
made a configuration change.

Remote Gateway 9150 Installation and Administration Guide 43

Remote Gateway 9150 description Standard 3.1

Command line interface

When the administration PC is connected to the Remote Gateway 9150 unit
through the serial port, you can view the command line interface using an
application such as Telnet or HyperTerminal. However, the command line
interface is not documented in this guide. Configuration Manager is the
supported tool for administering the Remote Gateway 9150 unit over both the
serial port and Ethernet connections.

44 Remote Gateway 9150 Installation and Administration Guide

Chapter 2

Planning for Remote Gateway 9150 unit installation

In this chapter

Remote Gateway 9150 Installation Checklist 46

Physical environment 50

Network considerations 55

Administration PC 59

Trunk connection management 64

Station configuration 66

Security 70

Planning for future growth 72

Deployment options 75

Planning the configuration 81

Remote Gateway 9150 Installation and Administration Guide 45

Planning for Remote Gateway 9150 unit installation Standard 3.1

Installation checklist

When you are preparing to install your Remote Gateway 9150 unit, use the
following checklist to ensure that you complete all the required processes
properly.

Remote Gateway 9150 Installation Checklist

Page 1 of 4

✓

Task For details, refer to

Review the Release Notes for last-

❒

minute product updates.

Ensure you have the latest firmware

❒

and software.

You can route calls over the IP

❒

network, the PSTN, or both.
Determine, at a high level, what you
must do to implement these call routing
methods.

If you want to use the IP network to

❒

route calls, evaluate the IP network to
determine if the network infrastructure
can support voice traffic.

If you want to use the PSTN to route

❒

calls, order trunks from the central
office to the Remote Gateway 9150
unit site.

Remote Gateway 9100 Series
and RLC Release Notes

(NTP 555-8421-102).

Remote Gateway 9100 Series
and RLC Release Notes

(NTP 555-8421-102)

“Deployment options” on
page 75.

! your data network

administrator

! Remote Gateway 9100

Series Network
Engineering Guidelines

(555-8421-103)

“ISDN BRI information” on
page 82.

Note: The Remote Gateway 9150 unit
supports ISDN BRI trunks (S/T or U
interface).

46 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

Remote Gateway 9150 Installation Checklist

Page 2 of 4

✓

Task For details, refer to

Obtain the cables that you need to

❒

establish the network connections.

Decide on the administration PC setup. “Administration PC” on page

❒

Gather the configuration information

❒

(network addresses, connection
numbers, online/offline schedule, QoS
thresholds, and so on).

Install DSP application and trunk

❒

interface modules into the Remote
Gateway 9150 unit.

Choose a suitable location for the

❒

Remote Gateway 9150 unit.

Install the Remote Gateway 9150 unit

❒

in the chosen location.

Connect the Remote Gateway 9150

❒

unit to the power source, administration
PC, and network.

“Cables you must supply
yourself” on page 53.

59.

! “Deployment options” on

page 75

! Appendix A, “Planning

forms”

“Installing trunk interface or
DSP application modules” on
page 93.

“Choosing a suitable
location” on page 98.

“Installing the Remote
Gateway 9150 unit” on page

98.

“Connecting the Remote
Gateway 9150 unit” on page

105.

Power up the Remote Gateway 9150

❒

unit and observe LED indicator
behavior.

The Status LED indicator remains lit
when the power-up cycle completes
successfully.

Remote Gateway 9150 Installation and Administration Guide 47

“Powering up the Remote
Gateway 9150 unit” on page

111.

Planning for Remote Gateway 9150 unit installation Standard 3.1

Remote Gateway 9150 Installation Checklist

Page 3 of 4

✓

Task For details, refer to

Install the software from the product

❒

CD-ROM or the Nortel web site.

Configure the IP address, subnet mask,

❒

and default gateway on the Remote
Gateway 9150 unit.

Configure the following items, as

❒

required, to create the communication
paths between the Remote Gateway
9150 unit and the RLC:

! IP network: RLC’s IP address

! PSTN:

— RLC’s telephone number

—primary trunk

! security level and, if required,

security identifier

PING the Remote Gateway 9150 unit

❒

and ensure that it is recognized as a
device on the network.

“Installing the Configuration
Manager software” on page

113.

“Using the Configuration
Wizard to perform initial
configuration” on page 115.

! “Using the Configuration

Wizard to perform initial
configuration” on page
115

! “Security level

configuration” on page
200

“Testing the network
connections” on page 129.

Ensure that the Remote Gateway 9150

❒

unit’s connection information is
completed on the RLC.

the Reach Line Card

Installation and
Administration Guide

(NTP 555-8421-210).

Configure user stations with

❒

appropriate calling permissions and

“9150 port configuration” on
page 207.

features.

48 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

Remote Gateway 9150 Installation Checklist

Page 4 of 4

✓

Task For details, refer to

Configure ports on the RLC. the Reach Line Card

❒

Installation and
Administration Guide

(NTP 555-8421-210).

Configure network devices

❒

! so that voice traffic is not

constrained or congested

! to maximize network efficiency for

Voice over IP service

Ensure that voice calls can be sent or
received over the following:

! IP network

❒

! PSTN

❒

Ensure that processing of voice and

❒

data traffic over the IP network
performs as expected.

Adjust QoS Transitioning Technology

❒

settings, if required.

Ensure that calls can be made and

❒

received on each station.

! your data network

administrator.

! Remote Gateway 9100

Series Network
Engineering Guidelines

(555-8421-103)

your data network
administrator.

! your data network

administrator

! your telecom network

administrator

! Remote Gateway 9100

Series Network
Engineering Guidelines

(555-8421-103)

“Testing the network
connections” on page 129.

Plan for administration training and

❒

technical support.

! Chapter 7,

“Administration”

! Chapter 8,

“Troubleshooting”

Remote Gateway 9150 Installation and Administration Guide 49

Planning for Remote Gateway 9150 unit installation Standard 3.1

Physical environment

This section provides the space, temperature, cabling, and mounting information
you need to know before you install the Remote Gateway 9150 unit.

Space

Ensure that the Remote Gateway 9150 unit is installed in a location that is dry
and provides plenty of air circulation.

The chosen location must be no more than cable-length distance from the
following:

! the administration PC (if the serial connection is used)

! the Ethernet hub

! trunk and telephone connection interfaces

The Remote Gateway 9150 unit can be installed up to

! 1230.7 meters (4000 feet) from the digital telephones

! 307.7 meters (1000 feet) from the analog device

It is recommended that you install the Remote Gateway 9150 unit in the same
room where your communications equipment is installed.

50 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

Temperature and humidity

The following table describes the temperature and humidity conditions that the
Remote Gateway 9150 unit can withstand without any performance degradation
or damage.

Specification Minimum Maximum

Normal operation

Recommended:

! Temperature (Ambient)

! Relative humidity

! 0°C (32°F)

! 5%

! 40°C (104°F)

! 95% (non-

condensing)

Storage

Recommended temperature -40°C (-40°F) 70°C (158°F)

Relative humidity 5% 95% (non-condensing)

Remote Gateway 9150 Installation and Administration Guide 51

Planning for Remote Gateway 9150 unit installation Standard 3.1

Mounting options

You can place the Remote Gateway 9150 unit on a desk or in a rack, or you can
mount it on the wall.

The Remote Gateway 9150 unit dimensions are

! 42.5 cm (17 in.) wide (without rack-mounting brackets)

! 29.4 cm (11.75 in.) deep

! 4.4 cm (1.75 in.) high

Mounting the Remote Gateway 9150 unit in a rack

If you want to install the Remote Gateway 9150 unit in a rack, the rack slot must

! be large enough to provide air circulation to keep the Remote Gateway

9150 unit cool

! allow you to securely fasten the Remote Gateway 9150 unit to the rack

using the rack-mount brackets

Mounting the Remote Gateway 9150 unit on the wall

If you want to install the Remote Gateway 9150 unit on the wall, you can mount
it so the cables from the rear panel are directed either right or left. Ensure that
the chosen location allows you to easily view the LED indicators on the front
panel.

ATTENTION!

You must complete wall installation using standard
telephony installation practices.

Connections

The following connections are made from the rear panel of the Remote Gateway
9150 unit to the telephone and data networks:

! Two 25-pair connectors (labeled TELCO 1 and TELCO 2) provide tip and

ring connections to stations (telephones) and central office trunks (ISDN
BRI). These connections provide the interface to the telephone network and
the PSTN.

52 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

! An RJ-45 connector (labeled ETHERNET) provides a 10BaseT Ethernet

connection. This connection provides the ability to pass both voice and data
administration traffic over the existing Ethernet network.

! A DB-9 connector (labeled ADMIN) provides an RS-232 serial port

connection. You can use this serial port connection to configure a Remote
Gateway 9150 unit that is directly connected to a PC.

Cables included with the Remote Gateway 9150 unit

The Remote Gateway 9150 unit package includes the following cables:

! power cord and power supply

Notes:

— In North America, the power cord and power supply are included inside

the Remote Gateway 9150 box. In all other regions, the power supply is
provided inside the box. However, the power cord for your region is
provided outside the box.

— When the North American power cord and power supply are connected

together, they are 3.2 meters (10.4 feet) in length.

— If you connect the Remote Gateway 9150 unit to an uninterruptible

power supply then the UPS must have a minimum of 100 Watts
available.

! RS-232 serial cable

If the RS-232 cable is not long enough, you can supply your own cable, up
to 15.38 meters (50 feet) in length.

Cables you must supply yourself

The cables used to establish the telephone and Ethernet network connections are
industry-standard cables. They are not provided in the Remote Gateway 9150
package. You must obtain them from your local cable supplier.

Telephone network cables

The telephone network cables establish the telephone and trunk connections.

One end of the cable must provide a male 50-pin connector. (This end connects
to the Remote Gateway 9150 unit.)

Remote Gateway 9150 Installation and Administration Guide 53

Planning for Remote Gateway 9150 unit installation Standard 3.1

Ensure that the other end of the cable matches the connectors needed to connect
to the telephones or trunks. (For example, if you are using a BIX block to
establish the telephone connections, you might need to cut off the connector to
expose the wires inside.)

Notes:

! Two telephone cables may be required, based on how many telephones and

ISDN BRI lines you plan to connect. (Each telephone cable provides
support for up to 16 digital telephones, and two ISDN BRI lines providing
two B-channels each. The Telco 1 cable also provides support for one
analog station such as a fax machine.)

! The Telco 1 and 2 connections are the opposite gender of the connections

for a Meridian 1 PBX IPE or Meridian 1 PBX 11 cabinet line card slot.
Therefore, you must use different cables when connecting to the Remote
Gateway 9150 unit than those used to connect to Meridian 1 PBX line
cards.

! Digital telephones must be located no farther than 1230.7 meters (4000

feet) from the Remote Gateway 9150 unit.

! The analog device must be located no farther than 307.7 meters (1000 feet)

from the Remote Gateway 9150 unit.

Ethernet cable

If you are connecting the Remote Gateway 9150 unit to a hub, you need a
standard CAT5 un-shielded twisted-pair (UTP) straight-through Ethernet cable.
The cable must be no longer than 100 meters (325 feet) in length.

54 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

Network considerations

The Remote Gateway 9150 unit communicates through both the IP and
telecommunications network using a host PBX.

To use the Remote Gateway 9150 unit in these networks, you must consider the
issues described in this section.

IP addressing and routing

To place and receive calls over the IP network, the Remote Gateway 9150 unit
must have:

! a physical connection to the IP network

! a unique IP address, default gateway, and subnet mask

Note: Similarly, you must assign a unique IP address, default gateway, and
subnet mask to the RLC on the host PBX.

In addition, the Remote Gateway 9150 unit must be able to send and receive
traffic to and from the RLC on the host PBX.

Remote Gateway 9150 Installation and Administration Guide 55

Planning for Remote Gateway 9150 unit installation Standard 3.1

Network diagram

The following diagram shows the Remote Gateway 9150 unit’s position in an IP
network.

QoS

Internal
network

10. 3.1.1

Host
PBX

Ethernet
network

Router

Ethernet
network

Remote Gateway 9150

10.1 .1.2

P
O

W
E

R

E
T

H
E
R
N

E
T

T
X

R
X

C
O
L

L

1
L
1

M

L

O

2

D

U

2

L
E

L
1

L

2

L

10.2.1.10 10.4.1.2

10. 3.1.2

RLC

Management
port (optional)

Router

10.2.1.1

10.2.1.310.3.1.3

Network

Router

10.4.1.1

10.1.1.10

Note: For placement of one or more administration PCs, refer to
“Administration PC” on page 59.

3

1

L
2

4
L
1

V

.
3

L

2

5

T

S

X

T
A

T
U

R

S

X

G101418

The routers used on your IP network must be capable of handling voice traffic,
with little or no congestion and few delays. If the network is congested or
subjected to many delays, voice quality is affected.

For more information, refer to the Remote Gateway 9100 Series Network
Engineering Guidelines (555-8421-103).

56 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

Numbering plans

Each trunk group at the Remote Gateway 9150 unit site must be assigned a trunk
access code (that is, the number dialed to obtain an outgoing trunk). In addition,
special prefix (SPRE) codes must be defined for the following features if you
want to use them:

! paging

! local calling on ATA-equipped analog devices

! to go online or offline (for more details, refer to “Online/offline table” on

page 40)

! registration and deregistration for multi-user or dynamic ports

All trunk access and SPRE codes are automatically defined in Configuration
Manager with a pound prefix (# in North America) so that there are no conflicts
with host PBX dialing plans. For a list of the default trunk access and SPRE
codes, refer to the “Remote Gateway 9150 Configuration Information—Dialing
Plans” form on page 384.

Numbering plan for local stations

Consider the numbering plan on the host PBX when setting up the numbering
plan for local stations at the Remote Gateway 9150 unit site. This ensures that
station-to-station calls through the host PBX complete correctly.

Call blocking

Call blocking can occur when there are more users installed and more calls
being processed than can be supported by the Remote Gateway 9150 unit’s DSP
application and trunk interface modules.

The voice processing capacity of the remote system depends on the number of
DSP application and trunk interface modules installed in the Remote Gateway
9150 unit and the amount of bandwidth available to process calls. If bandwidth
is not available, additional calls are blocked. (This setting is configured on the
RLC for each site). This voice processing capacity defines how many calls can
be active at one time.

Remote Gateway 9150 Installation and Administration Guide 57

Planning for Remote Gateway 9150 unit installation Standard 3.1

The Remote Gateway 9150 unit ships with the ability to support up to 32 users,
with up to 8 simultaneous calls (providing a 4:1 call blocking ratio). By adding
additional DSP application or trunk interface modules, you can reduce or
eliminate call blocking.

Reducing call blocking between the Remote Gateway 9150 unit and
the host PBX

Each DSP application module provides the ability to support eight more
simultaneous calls when voice traffic is routed over the IP network. Up to three
more DSP application modules can be installed in the Remote Gateway 9150
unit, allowing 32 active calls at one time.

Note: If you add DSP capacity to the Remote Gateway 9150 unit, you must add
the same DSP capacity to the RLC on the host PBX.

Trunks are required for the Remote Gateway 9150 unit to operate in PSTN mode
(that is, over the PSTN instead of the IP network). Trunks are used to route calls
between the Remote Gateway 9150 unit and the host PBX or the local PSTN.

By default, the Remote Gateway 9150 unit ships with no trunks installed. Trunks
can be provided by installing trunk interface modules.

The number of trunks you can install depends on the type of trunk interface
modules used on the Remote Gateway 9150 unit. For example, if ISDN BRI
trunks are used, each trunk interface module provides one BRI trunk (providing
two B-channels). You can install up to four trunk interface modules in the
Remote Gateway 9150 unit.

Note: The Remote Gateway 9150 unit supports only ISDN BRI S/T or U trunks.

Calculating system requirements

To determine how many DSP application or trunk interface modules are needed
to reduce or eliminate call blocking, use the “Remote Gateway 9150 System
expansion worksheet” on page 385.

58 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

Administration PC

Install the Windows-based Remote Gateway 9150 administration software on a
PC in the Remote Gateway 9100 Series network. This section describes options
for connecting an administration PC to the Remote Gateway 9150 unit. It also
describes the hardware and software requirements of the administration
software.

Connection options

The Remote Gateway 9150 product includes the Configuration Manager
software that enables you to configure, administer, and upgrade the Remote
Gateway 9150 unit. Perform these tasks over one of the following connections:

! RS-232 serial connection (required for first-time configuration only)

! 10BaseT Ethernet connection (for ongoing administration and upgrades)

Serial connection

Use the serial connection when you first install and configure the Remote
Gateway 9150 unit. You must establish a serial connection to the Remote
Gateway 9150 unit to enter the IP interface information. Refer to the following
illustration:

Remote
Gateway 9150

P
O

W

E
R

E

T
H

E
R

N

E
T

T
X

R
X

C

O
LL

1

M

L

O

2L1

D
U

2

L
E

1

L

2L

3
L
1

L

2

4
L
1

V

.
3

L
2

5

T

S

X

T
A

T
U

R

S

X

RS-232 serial connection
(using Configuration
Manager software)

Administration
PC

G101417

You can continue using the serial connection for ongoing administration of the
Remote Gateway 9150 unit, if you prefer. However, if this is the only connection
option you use, you cannot administer the Remote Gateway 9150 unit remotely
or perform upgrades.

Remote Gateway 9150 Installation and Administration Guide 59

Planning for Remote Gateway 9150 unit installation Standard 3.1

Note: When the administration PC is connected to the Remote Gateway 9150
unit through the serial port, you can view the command line interface using an
application such as Telnet or HyperTerminal. However, the command line
interface is not documented in this guide. Configuration Manager is the
supported tool for administering the Remote Gateway 9150 unit over the serial
port.

Ethernet connection

Once you configure the Remote Gateway 9150 unit with its IP interface
information, the following can happen:

! Communication can be established between the Remote Gateway 9150 unit

and the RLC (that is, calls can be routed over the IP network).

! You can administer and upgrade the Remote Gateway 9150 unit over the IP

network.

This means you do not have to install an administration PC in the same
location as the Remote Gateway 9150 unit. Refer to the following
illustration:

Remote Gateway 9150

Ethernet
network

Router

POW

ER

E

THERN

ET

T
X

R
X

C
O

L
L

1
L
1

MO

L
2

DU

2

LE

L
1

L

2

3
L
1

2

4
L
1L

V

.35

L

2

T

STA

X

TUS

R

X

10.4.1.110. 1.1.1010.1.1. 2

Network

Administration
PC

10.1.1.3

G101415

60 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

Administering multiple nodes in the network

If you are responsible for administering one or more Remote Gateway 9150
units and the RLC on the host PBX, you can access the Remote Gateway 9150
unit and the RLC from anywhere on the network. The following diagram shows
an example of an assembled network with administration PCs.

Note: You do not have to install separate administration PCs for the RLC and
the Remote Gateway 9150 unit. You can use one administration PC to
administer all units in the Remote Gateway 9100 Series network.

Host
administration
PC

Internal
network

10. 3.1.1

10. 3.1.2

Management
port (optional)

Router

RLC
Administration

PC

Host
PBX

RLC

10. 2.1. 1

10. 2.1. 2

10 .2.1. 310 .3.1. 3

Ethernet
network

10. 2.1. 10

Router

Router

10.4.1.2

Network

10.4.1.1

10 .1.1.1 0

Ethernet
network

P
O
W
E

10.1.1.2

10.1.1.3

Remote
Gateway
9150

R

E
T

H
E
R
N

E
T

T

X

R
X

C
O
L
L

1
L
1

M

L

2

O
D

U

2

L
E

L
1

L

2

L
1

L
2

43
L
1

V
.

3

L

2

5

T

S

X

T
A

T
U

R

S

X

Remote
Gateway 9150
Administration
PC

G101400

Remote Gateway 9150 Installation and Administration Guide 61

Planning for Remote Gateway 9150 unit installation Standard 3.1

Windows PC requirements

To use Configuration Manager, the administration PC must:

! be an IBM-compatible PC

! use a Windows 95, 98, NT Workstation 4.0, Millennium Edition (ME),

2000 Professional, or XP (Professional and Home Edition) operating
system with the Microsoft TCP/IP networking component installed

! be equipped with a CD-ROM drive

! be equipped with a 10BaseT Ethernet interface card (this provides access to

the Ethernet network)

! have an available COM port if you wish to use the RS-232 serial port to

establish a direct serial connection

! be equipped with a pointing device, such as a mouse

! have 32 Mbytes of RAM for Windows 95, 98, and ME, or 64 Mbytes of

RAM for Windows NT Workstation 4.0, 2000 Professional, and XP
(Professional and Home Edition

! have 48 Mbytes of available storage for Windows 95, 98 and ME, or 64

Mbytes of available storage for Windows NT Workstation 4.0, 2000
Professional, and XP (Professional and Home Edition)

Note: Configuration Manager does not support any of the Win32 Server
versions of Microsoft Windows.

Trivial File Transfer Protocol (TFTP) server

Firmware upgrades and configuration uploads require that the administration PC
have a TFTP server application installed. The administrator must know the
TFTP server’s IP address in the network. In other words, the IP address of the
administration PC.

You can use any TFTP server application. These applications are available free
of charge on the Internet.

62 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

Year 2000 compliance

The Remote Gateway 9150 unit and Configuration Manager software are Year
2000 compliant. However, ensure that the administration PC is Year 2000
compliant by verifying that the Windows operating system meets the
compliance requirement listed in the following table:

Operating system Year 2000 compliance requirement

Windows 95 Version 95b

Windows 98 OK as is

Windows NT Workstation 4.0 Service Pack 5 or higher

Windows 2000 Ok as is

Windows ME Ok as is

Windows XP OK as is

Optivity Telephony Manager and Configuration Manager

Nortel does not guarantee that Optivity Telephony Manager (OTM) and the
Configuration Manager can operate simultaneously on the same administration
PC. Simultaneous running of these to applications has not been tested and is,
therefore, not supported.

Remote Gateway 9150 Installation and Administration Guide 63

Planning for Remote Gateway 9150 unit installation Standard 3.1

Trunk connection management

You can manage trunk connections to the host PBX in several ways:

! Put the Remote Gateway 9150 unit into offline mode, so that it cannot place

or receive calls through the host PBX when operating in PSTN mode.

! Define call duration and idle timers, if the trunk connection is defined as

on-demand.

! Define minimum and maximum bandwidth allocation settings.

! Use QoS Transitioning Technology.

QoS Transitioning Technology

On IP networks, traffic congestion or delays can occur that result in poor voice
quality or lost connections. The RLC can be configured to transition call
processing from the IP network to the PSTN when the QoS degrades. When
QoS on the IP network returns to normal, call processing can be transitioned
back to the IP network.

The QoS thresholds (level and duration) defined on each RLC port determine
when the transitions occur. To determine appropriate thresholds for each site in
your network, consult your data network administrator. For more information,
refer to the Remote Gateway 9100 Series Network Engineering Guidelines (555-
8421-103).

Online/offline schedule

You can configure an online/offline schedule on the RLC to control when the
Remote Gateway 9150 unit can place and receive calls through the host PBX.
When the Remote Gateway 9150 unit is in offline mode, calls cannot be made or
received through the host PBX over the IP or PSTN.

Configure offline entries:

! for times when the connection to the host PBX is not normally active, such

as during evenings and weekends

64 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

! to prevent the Remote Gateway 9150 unit from staying online permanently,

thereby eliminating unwanted ISDN BRI charges

When the RLC processes an offline entry, it instructs the Remote Gateway 9150
unit to go offline for a specified number of hours and minutes. The number of
hours and minutes the Remote Gateway 9150 unit stays offline is the difference
between the offline entry being processed and the next online entry.

For example, an offline entry is configured at 6:00 p.m. The next online entry is
configured at 9:00 a.m. the following day. When the RLC processes the 6:00
p.m. entry, it instructs the Remote Gateway 9150 unit to go offline for 15 hours.

When going offline, a timer is activated within the Remote Gateway 9150 unit.
When the timer expires (in the example above, at 9:00 a.m.), the Remote
Gateway 9150 unit automatically initiates a “going online” request to the host
PBX. If the RLC successfully receives the request, the Remote Gateway 9150
unit and its connected telephones go online.

Changing the online/offline mode

Whether an online/offline schedule is used or not, you can put the Remote
Gateway 9150 unit into online or offline mode at any time by dialing the online
or offline SPRE code at any telephone set connected to the Remote Gateway
9150 unit. The SPRE codes are configured on the Remote Gateway 9150 unit.

Trunk bandwidth allocation

The Remote Gateway 9150 unit can dynamically allocate available trunk
bandwidth to active calls in PSTN mode. As calls are initiated and bandwidth
requirements increase, additional trunk connections are established. Similarly,
as calls terminate and bandwidth requirements drop, calls are aggregated and
idle trunks are shut down.

Remote Gateway 9150 Installation and Administration Guide 65

Planning for Remote Gateway 9150 unit installation Standard 3.1

Station configuration

When planning the stations at the Remote Gateway 9150 site, you must think
about the call capabilities required by each station.

Each station at the Remote Gateway 9150 site inherits settings such as voice
compression and priority from its associated RLC port. Configurations at the
Remote Gateway 9150 site determine each station’s ability to place locally
controlled calls, host-controlled calls, or both. For stations defined with local
control or local and host control, you can enable or disable specific features.

RLC settings

You must define the following on each RLC port:

! port allocation as dedicated, multi-user, or dynamic

! whether voice compression is used

! priority level

Port allocation

Assign each user at the Remote Gateway 9150 site to one port on the RLC on the
host PBX. You can configure an RLC port in one of the following ways:

! as a dedicated port (one port per remote user)

! as a multi-user port (one port shared by multiple users)

Up to eight persons can share the same RLC port, but not at the same time.
All stations that use this type of port must respond to the same DN and have
identical telephone set configurations. This port type is especially useful for
employees who are working in mutually exclusive shifts.

! as part of a dynamic pool

Dynamic port pooling is similar to a multi-user port except that the persons
who share ports in a dynamic pool are assigned to the next available port in
the RLC port pool. There is no correlation between the station and the port
on the RLC.

This feature is especially useful in free-seated ACD environments where
agents log on to the host PBX using their agent IDs.

66 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

Voice compression

If calls are to be routed over the IP network, you must select one of the
following voice compression algorithms on each RLC port:

! G.711: Voice is transmitted at 64 Kbps (no compression).

! G.726: Voice is compressed and transmitted at 32 Kbps.

! G.729A: Voice is compressed and transmitted at 8 Kbps.

G.729A is the default voice compression algorithm used by the RLC. This
allows

— up to six simultaneous voice calls to be processed over the first ISDN

BRI B-channel (16 Kbps are reserved for signaling data)

— up to eight simultaneous voice calls to be processed over the remaining

ISDN BRI B-channels

Each Remote Gateway 9150 station inherits its compression algorithm from its
assigned RLC port.

Station priority

You can configure each RLC port that is assigned to each station as normal
priority, high priority, PSTN only, or IP only.

When the port is configured as high priority and the priority reserved setting is
configured on the connection between the RLC and Remote Gateway 9150 unit,
you can ensure voice QoS for calls to and from those stations.

For more details, refer to “Station priority” on page 36 and “Connection
bandwidth” on page 37.

Notes:

1. Each Remote Gateway 9150 station inherits its priority setting from its
assigned RLC port.

2. The number of RLC ports that you can configure as high priority depends
on the amount of available bandwidth. The RLC administrator must ensure
that enough bandwidth is available to process calls on normal priority ports.

Remote Gateway 9150 Installation and Administration Guide 67

Planning for Remote Gateway 9150 unit installation Standard 3.1

Remote Gateway 9150 unit settings

You can define the following settings for each Remote Gateway 9150 station:

! port type as local, remote, or both

! extension (directory) number (on local stations only)

! key placement (on local stations only)

Port types

On the Remote Gateway 9150 unit, you can define each station with one of the
following capabilities:

! local control only (local)

You can use stations defined as local to place and receive calls through the
local PSTN. You can also place station-to-station calls at the Remote
Gateway 9150 site. Calls through the host PBX are not allowed.

! host control only (remote)

If a particular station is not allowed to place or receive calls through the
local PSTN, that station is configured as remote only. All calls are routed
through the host PBX, except for emergency calls (such as 911). If the
emergency service number is configured on the Remote Gateway 9150
unit, calls made to the emergency number are routed through the local
PSTN so the emergency service receives the correct location information.

! both local and remote control

You can use stations defined as local and remote to place and receive calls
through both the host PBX and the local PSTN. You can also place station­to-station calls at the Remote Gateway 9150 site.

Outgoing calls are routed according to the call appearance key used to
initiate the call. Calls initiated on the key defined as the primary or host call
appearance key are routed through the host PBX. Calls initiated on the key
defined as the local call appearance key are routed through the local PSTN,
if a trunk access code was dialed before the telephone number.

68 Remote Gateway 9150 Installation and Administration Guide

January 2005 Planning for Remote Gateway 9150 unit installation

When a station is configured with local control capability, further configuration
of the station is required to:

! enable or disable certain features

! disable outgoing calls or single-digit dialing, if required

! define key placement on the telephone

User extension configuration

Each station is assigned a local directory number (DN). The Remote Gateway
9150 unit uses the DN to route the incoming call to the correct station.

Stations that are configured with host-controlled call capability are associated
with a port number on the RLC. The RLC and the Remote Gateway 9150 unit
use this port number to establish the communication path between the host PBX
and the station.

Placement of local call appearance and feature keys

When determining the placement of the local call appearance key on a station,
ensure that the key position is not already configured for a specific feature on the
host PBX. If you configure a PBX-configured feature key as a local call
appearance key, the user cannot use that feature.

If the station is configured with local control capability, you can also configure
the placement of other keys, such as Transfer, Call Waiting, and Make Set Busy.

Remote Gateway 9150 Installation and Administration Guide 69

Planning for Remote Gateway 9150 unit installation Standard 3.1

Security

The RLC and Remote Gateway 9150 unit offer the following types of security:

! security level and, if required, security identifier to prevent toll fraud on the

host PBX

! two levels of administration passwords to secure node configurations

Toll fr aud

You can minimize toll fraud on the PBX by implementing one of the following
levels of security:

! Caller ID

When Caller ID is selected, the Remote Gateway 9150 unit’s calling line
identification (CLID) is compared with its PSTN number configured on the
RLC port when a connection to the host PBX is attempted. If they match,
the connection is established. If they do not match, the host PBX drops the
call.

Caller ID authentication cannot be performed over the IP network.

! security identifier

You can use security identifier authentication over the IP or PSTN. If you
choose this level, you must configure a security identifier on both the
Remote Gateway 9150 unit and its assigned RLC port. When an incoming
call attempts to initiate a connection between the host PBX and Remote
Gateway 9150 unit, Remote Gateway 9100 Series compares the security
identifiers. If they match, the attempted connection succeeds. If they do not
match, the host PBX drops the call and the connection fails.

Data network security

The Remote Gateway 9150 solution does not provide for data network security.
If security on the data network is an issue, security must be implemented on the
data network devices.

70 Remote Gateway 9150 Installation and Administration Guide