Avaya Programming Operations Guide Operation.bk

2015-06-01

: Avaya Avaya-Programming-Operations-Guide-735637 avaya-programming-operations-guide-735637 avaya pdf

Open the PDF directly: View PDF PDF.
Page Count: 1010

DownloadAvaya Avaya-Programming-Operations-Guide- Operation.bk Avaya-programming-operations-guide
Open PDF In BrowserView PDF
Part No. P0609326 1.1
May, 2006

Business Communications
Manager 3.6
Programming Operations
Guide

2

Copyright © Nortel Networks 2003–2006
All rights reserved.
The information in this document is subject to change without notice. The statements, configurations, technical data, and
recommendations in this document are believed to be accurate and reliable, but are presented without express or implied
warranty. Users must take full responsibility for their applications of any products specified in this document. The
information in this document is proprietary to Nortel Networks NA Inc.

Trademarks
NORTEL NETWORKS is a trademark of Nortel Networks.
Microsoft, MS, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation.
Symbol, Spectrum24, and NetVision are registered trademarks of Symbol Technologies, Inc.
All other trademarks and registered trademarks are the property of their respective owners.

P0609326 1.1

Software licensing

3

Software licensing
The Apache Software License, Version 1.1
Copyright (c) 2000-2002 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
1

Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer.

2

Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials provided
with the distribution.

3

The end-user documentation included with the redistribution, if any, must include the
following acknowledgment: “This product includes software developed by the Apache
Software Foundation (http://www.apache.org/).”
Alternately, this acknowledgment may appear in the software itself, if and wherever such
third-party acknowledgments normally appear.

4

The names “Apache” and “Apache Software Foundation” must not be used to endorse or
promote products derived from this software without prior written permission. For written
permission, please contact apache@apache.org.

5

Products derived from this software may not be called “Apache”, nor may “Apache” appear in
their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
====================================================================
This software consists of voluntary contributions made by many individuals on behalf of the
Apache Software Foundation. For more information on the Apache Software Foundation, please
see .
Portions of this software are based upon public domain software originally written at the National
Center for Supercomputing Applications, University of Illinois, Urbana-Champaign.

Business Communications Manager 3.6 Programming Operations Guide

4

Software licensing

P0609326 1.1

5

Contents
Software licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
The Apache Software License, Version 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Symbols used in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
About the buttons on your telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Model 7100 and 7000 telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Portable handsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Acronyms used in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
System documentation map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Installation documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Operations documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Call Management documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Unified Manager and hardware maintenance documentation . . . . . . . . . . . . . . . . 61
Multi-site Administration: Network Configuration Manager . . . . . . . . . . . . . . . . . . 61
How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
System configuration process maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Initial system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Configuring telephony components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Optional keycoded features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Data and IP telephony configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Post-system setup features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Finding your way around . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Security and User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Telephony programming quick access list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Configuration overviews and planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lines and network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Telephony configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reference material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

72
72
73
73
73

Data programming sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Business Communications Manager hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
BCM1000 (legacy equipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
BCM200/BCM400 base units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
What do media bay modules do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Business Communications Manager 3.6 Programming Operations Guide

6

Contents
How does the system connect to the network? . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Additional Business Communications Manager applications . . . . . . . . . . . . . . . . . . . 76

Chapter 2
Getting started with Unified Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Understanding BCM SSL certificate properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Uploading a certificate and a private security key . . . . . . . . . . . . . . . . . . . . . . . . . 78
Troubleshooting: Restoring the default certificate . . . . . . . . . . . . . . . . . . . . . . 79
Suppressing the security alert message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Using the non-secure http:6800 port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Using the Unified Manager main page buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Locating Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Navigating the wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Locating optional features from the main page . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Finding documentation from the main page . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Using BRU from the main page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Accessing maintenance information from the main page . . . . . . . . . . . . . . . . 82
Using the Unified Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Business Communications Manager system access . . . . . . . . . . . . . . . . . . . . . . 82
Unified Manager screen display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Understanding the dynamic menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Understanding the navigation tree headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Understanding tabbed pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Using Unified Manager Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Viewing help for navigation tree headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Viewing help for tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Logging off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Using the SSH client to access the text-based interface . . . . . . . . . . . . . . . . . . . . . . . 89
Installing PuTTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Using PuTTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Manually activating Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Chapter 3
Configuring system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Accessing the Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Wizard Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
What you need to know before you use the wizard . . . . . . . . . . . . . . . . . . . . . . . . 93
Using the Quick Start Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Entering information into the Quick Start Wizard . . . . . . . . . . . . . . . . . . . . . . . . . 97
Changing system identification parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Identifying your system and software version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Changing the system name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Viewing the system software version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Changing the Business Communications Manager time and date . . . . . . . . . . . . 99
P0609326 1.1

Contents

7

Changing the system domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Assigning a workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Assigning a domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Assigning a Windows 2000 domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Changing the CallPilot region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Delayed system restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 4
Managing system and user security access levels . . . . . . . . . . . . . . . . . 105
Setting the interface timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Setting system security compatibility levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Managing access passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Viewing the User Manager tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Adding or modifying a user profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Deleting a user profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Setting up callback for a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Adding or modifying a group profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Deleting a Group profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Adding a Domain User Group profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Deleting a Domain User Group profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Setting password lockout policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Setting password policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Chapter 5
Configuring resources — media bay modules . . . . . . . . . . . . . . . . . . . . . 123
Explaining the Media Bay Modules headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Media bay module Bus numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Identifying the module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Module types and capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
GATM (Global Analog Trunk module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Ports on Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Defining trunk module types and settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Configuring the trunk module to line type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Determining Clock Sources for DTMs or BRIs . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Timing within networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
T1 interface parameters (region-specific) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Interface levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Internal CSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
E1 parameters (region-specific) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
PRI Call-by-Call service selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Provisioning lines (PRI, T1, DASS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Provisioning a line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Provisioning BRI loops/lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Deprovisioning a line/loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Business Communications Manager 3.6 Programming Operations Guide

8

Contents
PRI B-channel provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Trunk module ports programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
PRI version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Viewing station module information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Determining station port state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Viewing port device information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Station module line deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Internally-driven channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Working with the modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Viewing Media Bay Module status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Disabling/enabling a DS30 bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Disabling/enabling a single module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Disabling or enabling a port channel setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Configuring DECT resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Chapter 6
Data and split-line configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Configuring the DDI Mux module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
DDI Mux features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Configuring DDI Mux connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Assigning the DDI mux modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Assigning lines for voice traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Assigning lines to the data module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Changing the line type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Assigning the line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Removing a line assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Removing the line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Configuring the line for telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Configuring the DDI Mux to work with the DTE . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Universal T1 WAN (UTWAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
UTWAN connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Point-to-Point-Protocol (PPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
RTP Header compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Configuring the Business Communications Manager to use the UTWAN . . . . . 161
Assigning lines for voice traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Assigning lines for data traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Determining which lines are available to the UTWAN . . . . . . . . . . . . . . . . . 162
Changing the line type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Assigning lines to the Data Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Removing a line assigned for data traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
P0609326 1.1

Contents

9

Configuring the UTWAN Network Interface parameters . . . . . . . . . . . . . . . . . . . 164
Configuring the UTWAN Summary parameters . . . . . . . . . . . . . . . . . . . . . . . . . 164
Configuring the UTWAN to use a Frame Relay link . . . . . . . . . . . . . . . . . . . . . . 166
Configuring the Frame Relay parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Configuring the PVC Configuration parameters . . . . . . . . . . . . . . . . . . . . . . 167
Configuring the UTWAN to use a PPP link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Configuring the PPP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Configuring the LCP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Configuring the IPCP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Configuring the PPP User List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Configuring additional IP addresses for the UTWAN . . . . . . . . . . . . . . . . . . . . . 176
Examples of uses of multiple IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . 176
Restrictions when using multiple IP addresses . . . . . . . . . . . . . . . . . . . . . . 176
Adding an additional IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Modifying an additional IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Deleting an additional IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Viewing the UTWAN performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Viewing UTWAN resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Configuring a data module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Viewing the data module settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Programming the BayStack settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Fixed access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Adding line assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Deleting line assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Switched access (PRI & BRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Line assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Adding line assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Deleting line assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Line pool access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Adding line pool access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Deleting line pool access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter 7
Telephony Services overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Process map: Creating telephony services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Telephony Services headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Typical DN record headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Planning your telephony services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Three basic system telephony configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Square system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
PBX system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
DID system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Telephony metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Business Communications Manager 3.6 Programming Operations Guide

10

Contents

Chapter 8
Telephony feature planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Creating numbering plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Outgoing calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Incoming calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Name a telephone, a line or a Hunt group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Incoming and outgoing call display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Programming line access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Making lines available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Incoming calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Outgoing calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Answering calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Distinctive ring patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Centralized and group answering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Pick up features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Make a call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Emergency 911 Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Select how you dial your calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Receive a busy signal on an internal call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Create a conference call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Time-saving features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Handling calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Holding calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Parking or transferring calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Sharing calls by parking on SWCA buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Forwarding calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Prevent calls from ringing at your telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Communicating in the office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Using handsfree and mute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Track your incoming calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Use alternate or scheduled services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Special telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Auxiliary devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Call out to external systems using host system dialing . . . . . . . . . . . . . . . . . . . . . . . 222
Call in from outside the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Controlling telephone programming access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Special features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Information matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Chapter 9
Configuring lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Understanding the process of line configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Understanding how the system identifies lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
P0609326 1.1

Contents

11

Copying line programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Determining which lines you need to program . . . . . . . . . . . . . . . . . . . . . . . . . . 230
VoIP lines (require keycode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Target lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

230
231
231
234

Using the General record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Assigning Trunk/line data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Loop start analog/digital fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Ground start fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
DID fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
E&M fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Target lines and DASS2 fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
PRI fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
BRI fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
DPNSS fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
VoIP fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Lines field cross-reference chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Turn Privacy on or off for a call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Received # . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Line pool tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Using loss packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Assigning Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Setting line restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Setting remote restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Setting line telco features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Line matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Chapter 10
Configuring BRI Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
BRI configuration process map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Using an NT-1 for BRI U2/BRI U4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Identifying BRI T-loops (T1 profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Adding SPIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Identifying the SPID B-channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Adding SPID network DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Identifying BRI T-loops (ETSI, QSIG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Configuring D-packet service for T loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Provisioning the loop variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Provisioning the Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Provisioning the lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Programming BRI lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning the lines to telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

274
275
276
277

Setting BRI for ISDN device connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Business Communications Manager 3.6 Programming Operations Guide

12

Contents
Wiring internal connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Configuring S-loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Assigning DNs to the S- loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Configure the ISDN terminal records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Loop matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Chapter 11
Controlling access into the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Defining DN length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Changing the DN length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Using the Received # length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Changing the received # length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Assigning target lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Assigning a target line to a telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Configuring the target line received number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Notes about the Public and Private Received Numbers . . . . . . . . . . . . . . . . 290
Target lines matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Configuring for remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Creating Direct Inward System Access (DISA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Remote access line settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote access on loop start trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote access on T1 DID trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote access on PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote access on DPNSS lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote access on a private network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

292
292
292
293
293
293

Defining remote access packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Defining line pool access for remote packages . . . . . . . . . . . . . . . . . . . . . . . 294
Defining remote Page for remote packages . . . . . . . . . . . . . . . . . . . . . . . . . 295
Using COS passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Creating COS parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Notes about COS passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
COS examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
External access tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Remote access matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Chapter 12
Configuring outgoing calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Configuring the public and private dialing plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Setting Dialing timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Using private network dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Setting up the dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Outgoing private calls routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Setting up public network dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
About the Public DN lengths table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Adding or modifying dialing plan Public DN lengths . . . . . . . . . . . . . . . . . . . 306
P0609326 1.1

Contents

13

Outgoing public calls routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Dialing Plans matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Determining line access dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Understanding access codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Programming access codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Call Park codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Creating Direct Dial sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Direct dial matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Tips about access codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Using the MCDN access codes (tandem calls) . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Setting up line pool access codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Using Carrier codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
About Carrier access codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Identifying Carrier access codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Access code matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Configuring call routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Defining routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Call by Call service routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Programming the PRI routing table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Enbloc dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Using destination codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Why use destination codes? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Deciding on a code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Grouping destination codes using a wild card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Configuring destination codes with wild cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Create the destination code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Set up the destination code schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Enable/disable wild card digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Setting up a destination for local calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Setting up a route through a dedicated trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Notes about the Absorbed length: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Adding Carrier access codes to destination codes . . . . . . . . . . . . . . . . . . . . . . . 334
Programming for least-cost routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Using multiple routes and overflow routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Using dialing restrictions with routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Routing matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Configuring Call by Call services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Supporting protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Call by Call services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Switches supporting Call by Call limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Provisioning for Call by Call limits with PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Other required programming in the Unified Manager . . . . . . . . . . . . . . . . . . 341
Business Communications Manager 3.6 Programming Operations Guide

14

Contents
Setting CbC limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
PRI line pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
CbC matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Viewing CbC limit metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Defining restriction filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Adding a restriction filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Removing restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Notes about restriction filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Default filters (North America) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Default filters (other) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Adding overrides to restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Restriction filter examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Restriction filters matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Enhanced 911 (E911) configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Chapter 13
Configuring DN records, an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Understanding the configuration process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
DN mapping for digital telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Double Density and DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
DN chart for upgraded 2.5 systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
DN chart for new 3.0 or newer systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
DN mapping for Companion, DECT and ISDN devices . . . . . . . . . . . . . . . . . . . 358
Defining the System DN headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
The two sides of a DN record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
The System DN headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
DN Registration headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Moving between the Inactive and Active lists . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
From Active list to the Inactive list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
From Inactive list to Active list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Deregistering IP and wireless IP devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Feature DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Renumbering DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Using a wizard to renumber telephone DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Change telephone DNs using the Unified Manager . . . . . . . . . . . . . . . . . . . . . . 367

Chapter 14
Configuring DNs using the Wizards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Editing DN Record Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
What you need to know to fill out a template . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Creating telephone records with the Add Users Wizard . . . . . . . . . . . . . . . . . . . . . . 375
What you need to know about the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Notes about Add Users target lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

P0609326 1.1

Contents

15

Changing button programming in the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Notes about programming telephone buttons . . . . . . . . . . . . . . . . . . . . . . . . 383
Using remote templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Saving wizard pages on your computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Chapter 15
Configuring DNs for system devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Copying settings to other DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Identifying the telephone (General heading) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Configuring line access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Assigning line access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Rules about assigning prime lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Assigning intercom (I/C) buttons (keys). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Private OLI notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Determining line assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Applying target lines (incoming calls only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Assigning lines to telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Notes about assigning lines to telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Assigning line pool access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
About PRI line pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Using Answer DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Assigning Answer DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Answer DN notes: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Defining device capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Configuring the Capabilities features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Line redirection notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Assigning Call Forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
DPNSS notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Assigning a Hotline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Determining analog settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
MWI tone/lamp matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Setting intrusion controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Defining user preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Configuring user preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Call log notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Programming telephone buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Configuring buttons from the DN record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Notes about button programming: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Replacing digital telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Button labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Default button assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Rules of default button assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
T7316E Business Series Terminal button defaults . . . . . . . . . . . . . . . . . . . . 422

Business Communications Manager 3.6 Programming Operations Guide

16

Contents
T7316 Business Series Terminal button defaults . . . . . . . . . . . . . . . . . . . . .
Model 7208 button defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Model 7100 telephone button defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Model 7000 telephone button defaults* . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T7406 Business Series Terminal button defaults . . . . . . . . . . . . . . . . . . . . .
IP telephone button defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Model 2004 IP telephone and 2050 Software Phone button defaults . . . . . .
Model 2002 IP telephone button defaults . . . . . . . . . . . . . . . . . . . . . . . . . . .
2001 IP telephone button defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetVision telephones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M7324(N) button defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

424
425
425
426
426
427
427
428
428
430
431

Configuring user speed dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Entering user speed dials at the telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Setting up CAP stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Configuring CAP/KIM assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
CAP/KIM notes: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Monitoring telephones with the CAP or KIM module . . . . . . . . . . . . . . . . . . . . . . 437
Configuring a CAP or KIM module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Programming CAP/KIM buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Cold starting the KIM to erase programming . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Programming restrictions for DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Defining telephone dialing restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Setting restriction schedules for telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Defining line/set restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Configuring telco features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Voice Mail settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Deleting a mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Digital telephones DN record matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Chapter 16
Configuring system settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Network name display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Receiving and sending calling party name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Network name display interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Enabling/disabling outgoing name display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Programming Business name display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Using alpha tagging for name display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Programming Feature settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Background and on-hold music sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Answer key levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Phantom DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Configuring system-wide call appearance groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Finding SWCA calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Programming SWCA controls for your system . . . . . . . . . . . . . . . . . . . . . . . . . . 463
NetVision telephone interactions with SWCA keys . . . . . . . . . . . . . . . . . . . . . . . 466
P0609326 1.1

Contents

17

How SWCA works in a call group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Transferring calls between SWCA groups . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Parking and retrieving calls on SWCA keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Manually associating a call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Parking a call to a SWCA key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Retrieving a parked call from a SWCA key . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Call interactions with SWCA controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Resetting call log space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
System features matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Setting system timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Timers matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Define release reason levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Configuring system speed dial numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Assigning numbers to system speed dial codes . . . . . . . . . . . . . . . . . . . . . . . . . 476
System speed dial matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Setting system telco features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Defining Voice Message Center numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Setting outgoing name and number blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Configuring ONN blocking service codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Telco features matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

Chapter 17
Configuring schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Turn services on and off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Overriding services with a Control telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Direct-dial telephone ringing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Defining common schedule settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Defining the service control password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Changing schedule names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Changing schedule times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
About start and stop times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Defining service schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Configuring ringing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Defining ring groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Defining ringing service schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Assigning ringing groups to lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Configuring restriction service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Notes about restriction service filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Configuring routing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Services matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

Chapter 18
Configuring public networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Simple networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Business Communications Manager 3.6 Programming Operations Guide

18

Contents
Callers using Business Communications Manager . . . . . . . . . . . . . . . . . . . . . . . 500
Callers in the public network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Callers in the private network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Dialing plans for T1 lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Dialing plan using public lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Destination code numbering in a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Other programming that affects public networking . . . . . . . . . . . . . . . . . . . . . . . . . . 503

Chapter 19
Configuring private networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Private network programming parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Private networking protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Keycode requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Remote access to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Lines used for networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Other programming that affects private networking . . . . . . . . . . . . . . . . . . . . . . 507
Using routing to create networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Using shared line pools to create a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
PRI networking using Call-by-Call services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

Chapter 20
Configuring private networks with SL-1 MCDN. . . . . . . . . . . . . . . . . . . . . 519
System numbering plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Creating tandem private networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Calls originating from the public network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Calls originating in the private network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Routing for tandem networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Understanding MCDN network features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Network Call Redirection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
ISDN Call Connection Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Trunk Route Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Trunk Anti-tromboning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Using SL-1 with MCDN to network with a Meridian system . . . . . . . . . . . . . . . . . . . 533
Meridian system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
MCDN networking checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
UDP-specific programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
CDP-specific programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
An example of a private network with Meridian 1 . . . . . . . . . . . . . . . . . . . . . . . . 537
VoIP networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Configuring special IP trunking interoperability . . . . . . . . . . . . . . . . . . . . . . . 541

P0609326 1.1

Contents

19

Chapter 21
Configuring ETSI QSIG and DPNSS network services. . . . . . . . . . . . . . . 543
Networking with ETSI QSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
ETSI Euro network services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
DPNSS 1 services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
DPNSS 1 capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
DPNSS to Embark connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
DPNSS 1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Three party service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Making a conference call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Using the diversion feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Restrictions by telephone type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Setting Diversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Using the Redirection feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Restrictions by telephone type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Setting redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Executive intrusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Restrictions by telephone type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Intrusion levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Programming IPL on a telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Call offer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Call Offer Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Restrictions by telephone type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
User actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Route optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Setting Route Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Loop avoidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Programming loop avoidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Private networking with DPNSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Guidelines for creating a private numbering plan with DPNSS . . . . . . . . . . . . . . 558
Customizing the DPNSS routing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

Chapter 22
Configuring centralized voice mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Business Communications Manager as host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Meridian system as host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
CallPilot compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Meridian Mail compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
System set up for host Business Communications Manager . . . . . . . . . . . . . . . . . . 561
System set up for satellite systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Configuring the system for centralized voice mail . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Meridian MCDN call features over PRI SL-1 lines . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Message Waiting Indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Camp-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Business Communications Manager 3.6 Programming Operations Guide

20

Contents
Break-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Configuring MWI on DPNSS 1 networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Assigning message centers to a line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Programming MWI and MWC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Selecting a message center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Setting Message Waiting Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

Chapter 23
Configuring Hunt groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
How to use Hunt groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Identifying a Hunt group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
Hunt group modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Hunt group members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Adding a Hunt group member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Removing a Hunt group member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Removing all members from a Hunt group . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Moving members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Programming Hunt group lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Assigning a line to a hunt group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Unassigning a line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Unassigning all lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Feature operation within Hunt groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Hunt group matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Monitoring Hunt groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Setting up Silent Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Using Silent Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Using Hunt group metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

Chapter 24
Configuring Hospitality Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
About the Hospitality feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Hospitality telephone definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Alarm Time (AL) feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Power failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Setting up Hospitality services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Identifying room telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Identifying Call Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Setting room restriction filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Programming Alarm data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Setting alarm parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Configuring for expired alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Hospitality matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Using the Hospitality Services Admin telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Hospitality Services admin alarm feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
P0609326 1.1

Contents

21

Setting the state of a room at a telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Setting room condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Using the Hospitality services room telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Setting the alarm on a room telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Change or cancel an alarm time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Turn off an alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Setting the Room condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600

Chapter 25
Configuring the music source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Selecting the music source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Configuring BcmAmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Opening the BcmAmp Administration application . . . . . . . . . . . . . . . . . . . . . . . . 603
Loading music onto the Business Communications Manager . . . . . . . . . . . . . . 603
Restrictions on uploading files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Deleting music from Business Communications Manager . . . . . . . . . . . . . . . . . 604
Adding music to the Play List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Removing music from the Play List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Using the BcmAmp Player . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Configuring a Network Device to be the IP Music Source . . . . . . . . . . . . . . . . . . . . . 607

Chapter 26
Configuring the MSC resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Types of MSC resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Signaling channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Media channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
DSP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Voice bus paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Media gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Rules for managing the MSC resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Signaling channel rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Media channel rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Example of how to estimate peak media channel usage . . . . . . . . . . . . . . . 612
DSP resources rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Voice bus path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Media gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Determining the MSC resources you require . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
ISDN WAN (Dial-up/Nailed-up) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
DECT mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Voice Mail and ACD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
IVR and IVR Fax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
IP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
IP Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Business Communications Manager 3.6 Programming Operations Guide

22

Contents
Record of required MSC resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Example of a Business Communications Manager configuration . . . . . . . . . 621
Configuring the MSC resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Viewing the MSC information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Viewing the MS-PEC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Understanding the MSC Minimum and Maximum values . . . . . . . . . . . . . . . . . . 624
Minimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Maximum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Viewing the MSC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Changing the MSC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Creating a custom MSC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
DTMF Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Changing the DS30 Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Configuring Double Density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630

Chapter 27
Using a wizard to change data parameters . . . . . . . . . . . . . . . . . . . . . . . . 633
Viewing Business Communications Manager resources . . . . . . . . . . . . . . . . . . . . . . 633
Using the Network Update Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
What you need to know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

Chapter 28
Configuring DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
DHCP configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Configuring the DHCP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
Configuring a DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
LAN settings for DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Configuring Address ranges for a Local Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Adding an address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Modifying an address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Deleting an address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Configuring Excluded addresses for a Local Scope . . . . . . . . . . . . . . . . . . . . . . 645
Adding an excluded address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Modifying excluded address ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Deleting an excluded address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Configuring Reserved addresses for a Local Scope . . . . . . . . . . . . . . . . . . . . . . 647
Adding a reserved address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Modifying a reserved address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Deleting a reserved address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Viewing the Lease Information for a Reserved address . . . . . . . . . . . . . . . . 648
Remote Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Adding a Remote Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Modifying Remote Scope settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
P0609326 1.1

Contents

23

Configuring Remote Scope Address ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Adding an address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Modifying address ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Deleting an address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Configuring Remote Scope excluded addresses . . . . . . . . . . . . . . . . . . . . . . . . 653
Adding a excluded address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Modifying excluded address ranges: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Deleting an excluded address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Configuring Remote Scope Reserved Addresses . . . . . . . . . . . . . . . . . . . . . . . . 655
Adding a reserved address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Deleting a reserved address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Remote Scope Lease Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Deleting a Remote Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Configuring a DHCP Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Deleting a server from the Server List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
LAN settings for DHCP Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Importing and Exporting DHCP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Exporting DHCP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Importing DHCP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Reconciling the DHCP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661

Chapter 29
Configuring the LAN resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Viewing the LAN resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Configuring LAN resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Setting LAN global parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Configuring a LAN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Configuring multiple IP addresses for the LAN interface . . . . . . . . . . . . . . . . . . . 667
Adding an additional IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
Modifying an Additional IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Deleting an Additional IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Viewing LAN performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668

Chapter 30
Configuring the WAN resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Permanent WAN connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Point-to-Point-Protocol (PPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Multi-link Point-to-Point Protocol (MLPPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
WAN data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Viewing WAN resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Setting global WAN parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Configuring the PPP password list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Modifying an existing item on the PPP Password List: . . . . . . . . . . . . . . . . . 672
Business Communications Manager 3.6 Programming Operations Guide

24

Contents
Deleting an item from the PPP Password List . . . . . . . . . . . . . . . . . . . . . . . . 672
Configuring the WAN interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Configuring WAN summary parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Setting WAN Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Setting WAN Sync Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Setting WAN Frame Relay Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
PVC Congestion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Adding PVC congestion control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Modifying PVC congestion controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Deleting a PVC congestion control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
WAN PPP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Configuring multiple IP addresses for a WAN interface . . . . . . . . . . . . . . . . . . . 681
Examples of uses of multiple IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . 681
Restrictions when using multiple IP addresses . . . . . . . . . . . . . . . . . . . . . . 681
Adding an additional IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Modifying an Additional IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Deleting an Additional IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Configuring the DLCI to IP Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Adding DLCI to IP Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Modifying DLCI to IP Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Deleting DLCI to IP Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
WAN performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684

Chapter 31
Configuring the Dial Up resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Configuring the dial up global parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
V.90 modem (North America) dial up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Enabling and disabling the V.90 modem interface . . . . . . . . . . . . . . . . . . . . . . . 686
Configuring the V.90 modem interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
ISDN dial up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Creating an ISDN dial up interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Configuring an ISDN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Configuring the ISDN channel characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
Assigning an ISDN dial number and IP address . . . . . . . . . . . . . . . . . . . . . . 694
Modifying the characteristics of an existing ISDN channel . . . . . . . . . . . . . . 694
Deleting an ISDN channel from the ISDN Channel Characteristics list . . . . 694
Deleting an ISDN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
Point to Point Protocol on Ethernet (PPPoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Settings required for PPPoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Installing PPPoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Creating a PPPoE dial up interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
Configuring a PPPoE interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
Connecting to the Internet Service Provider (ISP) . . . . . . . . . . . . . . . . . . . . . . . 700

P0609326 1.1

Contents

25

Deleting a PPPoE interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Guidelines for using Remote Dial-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701

Chapter 32
Configuring DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Using the Business Communications Manager DNS service . . . . . . . . . . . . . . . 704

Chapter 33
Configuring IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Routing Information Protocol (RIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Open Shortest Path First (OSPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
IP routing protocol precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Configuring IP Routing global settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Setting the RIP Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Setting the OSPF Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Configuring IP routing on an interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Configuring RIP parameters on a network interface . . . . . . . . . . . . . . . . . . . . . . 709
Enabling the RIP Subnet summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Disabling the RIP Subnet summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
Configuring OSPF Parameters on a network interface . . . . . . . . . . . . . . . . . . . . 712
OSPF NBMA Neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Adding OSPF NBMA Neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Modifying OSPF NBMA Neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Deleting OSPF NBMA Neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Adding a static route to the routing table . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Modifying the static route configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
Deleting a static route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
Restarting the router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717

Chapter 34
Configuring IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Enabling IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
Configuring IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Configuring IPX routing on an interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Configuring Packet Filters for IPX routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Adding Packet Input filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Modifying Packet Input filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Deleting Packet Input filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Adding Packet Output filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Modifying Packet Output filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Deleting Packet Output filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
RIP filters for IPX routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Configuring RIP for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Adding RIP Input Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Business Communications Manager 3.6 Programming Operations Guide

26

Contents
Modifying RIP Input filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Deleting RIP Input filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Adding RIP Output filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Modifying RIP Output filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
Deleting RIP Output filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
SAP filters for IPX routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Configuring the SAP for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Adding SAP Input Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Modifying SAP Input Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Deleting SAP Input Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Adding SAP Output Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Modifying SAP Output Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Deleting SAP Output Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Static Routes for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Adding Static Routes for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Modifying Static Routes for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Deleting Static Routes for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Static Service for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
Adding a Static Service for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
Modifying a Static Service for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . 739
Deleting a Static Service for IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 739

Chapter 35
Configuring Web Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Guidelines for using Web caching/Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

Chapter 36
Configuring QoS monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
How QoS monitoring works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
Setting the QoS monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Viewing the QoS Monitor Mean Opinion Score . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Configuring the logging options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Viewing the Mean Opinion Score log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747

Chapter 37
Configuring Net Link Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
Enabling or Disabling Net Link Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Selecting a permanent WAN link as the primary WAN connection . . . . . . . . . . . . . . 750
Selecting a dial-up link as the primary WAN connection . . . . . . . . . . . . . . . . . . . . . . 752

Chapter 38
Configuring NAT (Network Address Translation) . . . . . . . . . . . . . . . . . . . 753
Static NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
Dynamic NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
NAT and IP Firewall filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754

P0609326 1.1

Contents

27

Managing Business Communications Manager . . . . . . . . . . . . . . . . . . . . . . . . . 754
Enabling and disabling NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Configuring an Interface with NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
Adding Default rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
Adding a Rule to an interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
Modifying a Rule to an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
Deleting a Rule to an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
Configuring the Rule order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
Examples of common NAT configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758

Chapter 39
Configuring NTP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Configuring the NTP Client settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
Starting the NTP Client Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Manually updating the Business Communications Manager time . . . . . . . . . . . . . . . 764

Chapter 40
Virtual Private Networks (VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
PPTP tunnel notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
IPSec tunnel modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
PPTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Settings required for PPTP tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
NAT (Network Address Translation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
IP Routing and IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
IP Addresses and DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
DNS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Changing the PPTP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Adding a PPTP client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
Deleting a PPTP client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
Adding a PPTP tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
Configuring a PPTP tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
Add a Destination Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
Modifying a Destination Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Deleting a Destination Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
Deleting a PPTP tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
IPSec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Encryption method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Authentication method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
IPSec capacity restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780

Business Communications Manager 3.6 Programming Operations Guide

28

Contents
Settings required for IPSec tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
NAT (Network Address Translation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
Dialup ISDN connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
Compatibility with Contivity Extranet Switch and Shasta 5000 . . . . . . . . . . . 781
IPSec and PPTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
Multiple IP Address restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
Firewall rules for IPSec Branch Office and Remote User Tunnels . . . . . . . . 781
Changing the IPSec global settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
IPSec Branch Office configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Adding a Branch Office IPSec Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Adding Local Accessible Networks to the Branch Office IPSec tunnel . . . . . 789
Adding Remote Accessible Networks to the Branch Office IPSec tunnel . . . 789
Sending all traffic from Local Accessible Networks through the IPSec tunnel 790
Modifying a Branch Office IPSec Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
Modifying Local Accessible Networks to the Branch Office IPSec tunnel . . . 791
Modifying Remote Accessible Networks to the Branch Office IPSec tunnel . 791
Deleting a Branch Office IPSec tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
Deleting Local Accessible Networks to the Branch Office IPSec tunnel . . . . 792
Deleting Remote Accessible Networks to the Branch Office IPSec tunnel . . 792
Creating a tunnel between two Business Communications Managers . . . . . . . . 793
Configuring the first Business Communications Manager . . . . . . . . . . . . . . 793
Configuring the second Business Communications Manager . . . . . . . . . . . 793
Creating a tunnel between a Business Communications Manager
and a Contivity Extranet Switch v02_61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
Configuring the Business Communications Manager . . . . . . . . . . . . . . . . . . 794
Configuring the Contivity Extranet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . 794
Configuring the Business Communications Manager . . . . . . . . . . . . . . . . . . 795
Configuring the Contivity Extranet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . 795
IPSec Remote User configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
IPSec Remote User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
Split Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
Adding a Remote User IPSec Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
Assigning an IP Address to a Remote User Account . . . . . . . . . . . . . . . . . . 798
Adding a Remote IP Address Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Modifying a Remote IP Address Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
Deleting a Remote IP Address Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
Adding Remote User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
Configuring Remote User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Configuring the DNS/WINS setting for the Remote User Account . . . . . . . . 803
Adding a Split Tunnel Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
Modifying a Split Tunnel Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
Deleting a Split Tunnel Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Deleting a Remote User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805

P0609326 1.1

Contents

29

Creating Banner Text for a remote user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805

Chapter 41
Policy-enabled networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Policy configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Differentiated Services (DiffServ) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
DiffServ IP Quality of Service (QoS) architecture . . . . . . . . . . . . . . . . . . . . . 808
DiffServ components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
IP service classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Packet classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
COPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Policy overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Implementing Quality of Service (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Configuring the QoS Summary parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Configuring Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Creating an interface group configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Modifying an interface group configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Deleting an interface group configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Configuring Policy Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
Creating an IP filter configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
Modifying an IP filter configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
Deleting an IP filter configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Creating an IP filter group entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Modifying an IP filter group configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Deleting an IP filter group entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Configuring Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Creating an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Modifying an Action entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Deleting an Action entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Configuring QoS policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Adding a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Modifying a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
Deleting a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
Implementing Common Open Policy Services (COPS) . . . . . . . . . . . . . . . . . . . . . . . 823
Viewing COPS statistics and capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Configuring a COPS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
Adding a COPS Client Server entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
Modifying a COPS Client Server entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
Modifying the COPS Client Server Retry Data . . . . . . . . . . . . . . . . . . . . . . . 827
Configuring the Policy Agent characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Chapter 42
Configuring IP Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Packet filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Business Communications Manager 3.6 Programming Operations Guide

30

Contents
Basic (stateless) Packet Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Stateful Packet Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
IP Firewall filters and NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
Viewing and changing the status of Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . 832
Configuring IP Firewall Filters for an interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
Adding Default Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Adding an Input Filter for a Firewall Filter Interface . . . . . . . . . . . . . . . . . . . . . . . 835
Modifying an Input Filter for a Firewall Filter Interface . . . . . . . . . . . . . . . . . . . . . 837
Deleting an Input Filter for a Firewall Filter Interface . . . . . . . . . . . . . . . . . . . . . . 837
Configuring the order of the Input Filters for an interface . . . . . . . . . . . . . . . . . . 838
Adding an Output Filter for a Firewall Filter Interface . . . . . . . . . . . . . . . . . . . . . 839
Modifying an Output Filter for a Firewall Filter Interface . . . . . . . . . . . . . . . . . . . 839
Deleting an Output Filter for a Firewall Filter Interface . . . . . . . . . . . . . . . . . . . . 839
Configuring the order of the Output Filters for an interface . . . . . . . . . . . . . . . . . 840
Accessing Unified Manager through the Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
Firewall rules for Business Communications Manager with Dialup interfaces . . . . . . 843

Appendix A
Defining region-based defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
Region-based system settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
Core software and regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Caller ID displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
Companding Law by region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
Mobility services by region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
Media bay module availability by region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
FEM-trunk module combinations by region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
PRI line protocol support, by region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Supported ISDN line services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
Defining time zones by country and language . . . . . . . . . . . . . . . . . . . . . . . . . . 853
System feature defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
Dialing plan defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
BRI and PRI line types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
CallPilot regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859

Appendix B
System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Business Communications Manager feature codes . . . . . . . . . . . . . . . . . . . . . . . . . 861
Button programming features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865

Appendix C
ISDN overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Welcome to ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Analog versus ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
P0609326 1.1

Contents

31

Types of ISDN service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
ISDN Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
ISDN bearer capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
Services and features for ISDN BRI and PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
PRI services and features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
BRI services and features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
Network name display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Name and number blocking (ONN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Call by Call Service Selection for PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Emergency 911 dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-way DID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialing plan and PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

873
874
874
875
875
875

ISDN hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
PRI hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
BRI hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
S Reference Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
T Reference Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Clock Source for ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
ISDN BRI NT1 equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
ISDN standards compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
Planning your ISDN network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
Ordering ISDN PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Ordering ISDN PRI Service in Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Ordering ISDN PRI Service in United States . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Ordering ISDN PRI Service Outside of Canada and the United States . . . . . . . 880
Ordering ISDN BRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Ordering ISDN BRI Service in Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Ordering ISDN BRI Service in the United States . . . . . . . . . . . . . . . . . . . . . . . . 881
Ordering ISDN BRI Service Outside Canada or the United States . . . . . . . . . . . 881
Supported ISDN Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
ISDN Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
Program PRI Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
Programming ISDN BRI Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
Program PRI Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
Program ISDN BRI Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
Program Direct Inward System Access (DISA) on PRI Lines . . . . . . . . . . . . . . . 885
Method 1:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
Method 2: (North America only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
Program ISDN Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
Terminal equipment for BRI Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Devices on an S loop (BRI cards only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
S or LT Loop DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D-packet Service (BRI only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

886
886
886
887

Business Communications Manager 3.6 Programming Operations Guide

32

Contents

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
J . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943

P0609326 1.1

33

Figures
Figure 1

Process for initial system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 2

Process for configuring the telephony components

Figure 3

Process for activating optional keycoded features . . . . . . . . . . . . . . . . . . . . . . . 69

Figure 4

Process for configuring the data and IP telephony components . . . . . . . . . . . . 70

Figure 5

Post-setup processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figure 6

Upgradeable BCM1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Figure 7

BCM200 and BCM400 hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Figure 8

Main display of the Unified Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Figure 9

Tabbed page example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Figure 10

Accessing navigation tree heading help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

. . . . . . . . . . . . . . . . . . . . . 68

Figure 11

Accessing navigation tree heading help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Figure 12

Quick Start Wizard application warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Figure 13

Maintenance Tools screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Figure 14

Job scheduling window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 15

Security and user access headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Figure 16

Unified Manager Timeout setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Figure 17

System security level settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Figure 18

User Profile screen to add or modify a user profile . . . . . . . . . . . . . . . . . . . . . 112

Figure 19

User Manager delete confirmation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Figure 20

User profile for dial-up user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Figure 21

Default user groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Figure 22

User Group List add/modify screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Figure 23

User Manager delete confirmation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Figure 24

Domain User Group Profile add/modify screen . . . . . . . . . . . . . . . . . . . . . . . . 119

Figure 25

Lockout Policy screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Figure 26

Password Policy tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Figure 27

Resources, Media Bay Modules menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Figure 28

Confirming the Programmed Bus Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Figure 29

Example of PRI module settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Figure 30

Finding state of port on Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Figure 31

Station media bay module Bus headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Figure 32

Bus assigned to a station module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Figure 33

Finding state of port on Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Figure 34

Ports on Bus, B1 screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Figure 35

DECT media bay module description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Figure 36

DECT maintenance selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Figure 37

Network overview: DDI MUX connected to 2.5 hardware internal router . . . . . 152

Figure 38

Network overview: DDI MUX connected to BCM400 internal router . . . . . . . . 153

Figure 39

Overview of network using DDI Mux module with an external router . . . . . . . . 153

Figure 40

Tasks for installing the telephony components . . . . . . . . . . . . . . . . . . . . . . . . . 185
Business Communications Manager 3.6 Programming Operations Guide

34

Figures

Figure 41

Telephony Services menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Figure 42

Headings found under typical DN heading . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Figure 43

Square system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Figure 44

PBX system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Figure 45

DID system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Figure 46

Incoming public and private call coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Figure 47

Process map: Configuring the lines for your system . . . . . . . . . . . . . . . . . . . . 228

Figure 48

Lines menus and fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Figure 49

Using the Lines General screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Figure 50

Target line Private and Public received numbers . . . . . . . . . . . . . . . . . . . . . . . 259

Figure 51

Entering a line restriction filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Figure 52

Enter remote restriction filters for a line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Figure 53

Choosing a remote voice message center . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Figure 54

Loops headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Figure 55

Process map: Configuring the loops for your BRI module . . . . . . . . . . . . . . . . 266

Figure 56

T-loop screen (T1 profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Figure 57

Adding a SPID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Figure 58

Assign number of B-channels per SPID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Figure 59

Add Network DN to SPID X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Figure 60

Specifying a Network DN call type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Figure 61

T-loop screen (UK profile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Figure 62

Enable/disable D-packet service, and associate a loop . . . . . . . . . . . . . . . . . . 273

Figure 63

Add a D-packet service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Figure 64

Add a TEI to the D-packet service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Figure 65

Provisioning BRI loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Figure 66

Provisioning BRI loop lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Figure 67

Configuring an auto-answer BRI line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Figure 68

Assigning the BRI line to a DN record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Figure 69

BRI RJ45 wiring array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Figure 70

S-loop screen (North American profile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Figure 71

Adding a DN to the Loop DN group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Figure 72

Adding a Loop DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Figure 73

Process map: Access headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Figure 74

DN length screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Figure 75

Received # length, (PBX template default) . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Figure 76

Assigning a target line to a set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Figure 77

Defining a Received number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Figure 78

Setting remote page for a remote access package . . . . . . . . . . . . . . . . . . . . . 295

Figure 79

Assigning COS password and remote access parameters . . . . . . . . . . . . . . . 296

Figure 80

Unified manager telephony services headings . . . . . . . . . . . . . . . . . . . . . . . . 301

Figure 81

Configuring private network types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Figure 82

Adding a Public DN length prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

P0609326 1.1

Figures
Figure 83

Defining the prefix DN length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Figure 84

Line management diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Figure 85

Defining access codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Figure 86

Direct dial menu and screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Figure 87

Local call tandemed through Business Communications Manager nodes . . . . 316

Figure 88

Defining line pool access codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Figure 89

Adding Carrier code prefix records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Figure 90

Configuring a carrier code prefix ID length . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Figure 91

Call Routing headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Figure 92

Add a route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Figure 93

Define route parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Figure 94

Using destination codes to access another system . . . . . . . . . . . . . . . . . . . . . 327

Figure 95

Adding a destination code with a wild card . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Figure 96

Routing Service programming example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Figure 97

Destination codes for call routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Figure 98

Carrier code call numbering sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Figure 99

Multiple routing with destination schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

35

Figure 100 Configuring the Normal schedule for overflow . . . . . . . . . . . . . . . . . . . . . . . . . 337
Figure 101 Setting CbC limits parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Figure 102 Metrics for all CbC options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Figure 103 Restriction Filters headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Figure 104 Adding restriction filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Figure 105 Adding overrides to restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Figure 106 Line restriction example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Figure 107 Remote line restriction example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Figure 108 Process map: Configuring DNs for system devices . . . . . . . . . . . . . . . . . . . . . 354
Figure 109 System DNs main headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Figure 110 Registration DNs, main headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Figure 111 Target line assignments in the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Figure 112 Feature selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Figure 113 Internal autodial selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Figure 114 External autodial selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Figure 115 Add Users first page, choosing remote template . . . . . . . . . . . . . . . . . . . . . . . 384
Figure 116 First and second-level System DNs headings and features . . . . . . . . . . . . . . . 388
Figure 117 Headings found under typical DNXXX heading . . . . . . . . . . . . . . . . . . . . . . . . 389
Figure 118 DN General screen for digital and IP telephones . . . . . . . . . . . . . . . . . . . . . . . 391
Figure 119 Line access fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Figure 120 Assigning characteristics to each line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Figure 121 T7316E display button assignment protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Figure 122 Adding an intercom button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Figure 123 Adding an Answer DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Figure 124 Answer condition for Answer DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Figure 125 Features that define telephone feature capabilities . . . . . . . . . . . . . . . . . . . . . 405
Business Communications Manager 3.6 Programming Operations Guide

36

Figures

Figure 126 Configuring call forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Figure 127 ATA settings for a DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Figure 128 User preference telephone settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Figure 129 Button programming options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Figure 130 T7316E lower button mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Figure 131 T7316 telephone button assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Figure 132 Model 7208 button mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Figure 133 Model 7000 button mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Figure 134 T7406 button defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Figure 135 Models 2004/2050 default button programming . . . . . . . . . . . . . . . . . . . . . . . . 427
Figure 136 Model 2002 default button assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Figure 137 Model 2001 default button formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Figure 138 M7324N defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Figure 139 Add a user speed dial code to a telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Figure 140 Entering call parameters for a user speed dial . . . . . . . . . . . . . . . . . . . . . . . . . 432
Figure 141 T7316E with KIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Figure 142 T7324 with CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Figure 143 CAP/KIM assignment, CAP/KIM 1 screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Figure 144 Programming a CAP/KIM button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Figure 145 Telephone-based dialing restrictions, menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Figure 146 General restrictions for telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Figure 147 Defining set restrictions for the Night schedule . . . . . . . . . . . . . . . . . . . . . . . . 443
Figure 148 Defining Line/set restrictions for line 001, Night schedule . . . . . . . . . . . . . . . . 444
Figure 149 DN Telco Features fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Figure 150 General Settings headings and fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Figure 151 Feature settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Figure 152 Checking for Park prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Figure 153 Setting SWCA controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Figure 154 SWCA indicators, incoming call from a line (auto SWCA association is on) . . 466
Figure 155 SWCA indicators, incoming call from an intercom (auto SWCA association for
intercom is on) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Figure 156 Setting system timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Figure 157 Undefined speed dial screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Figure 158 Expanded speed dial screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Figure 159 Voice message center programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Figure 160 ONN blocking parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Figure 161 Scheduled Services headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Figure 162 Entering the Service control password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Figure 163 Entering schedule names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Figure 164 Entering schedule time parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Figure 165 Adding a telephone to a ring group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Figure 166 Defining ring schedule parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
P0609326 1.1

Figures

37

Figure 167 Defining ring service schedule line settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Figure 168 Defining restriction service setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Figure 169 Defining routing service settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Figure 170 Connection to a private network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Figure 171 Routing service record: use pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Figure 172 Routing service record: Destination code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Figure 173 Dialing plan for T1 E and M routing network . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Figure 174 Network example using shared line pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Figure 175 PRI networking using Call-by Call Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Figure 176 Private tandem network of Business Communications Managers . . . . . . . . . . 520
Figure 177 Network call redirection path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Figure 178 Call loop on system without ICCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Figure 179 Call paths with and without TRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Figure 180 Call paths with and without TAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Figure 181 MCDN networking, with a common public network connection . . . . . . . . . . . . 537
Figure 182 IP trunking interoperability fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Figure 183 ETSI QSIG networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Figure 184 DPNSS networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Figure 185 Message waiting indication message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Figure 186 Camping a call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Figure 187 Breaking into a Business Communications Manager call path . . . . . . . . . . . . 568
Figure 188 Telco features Voice message center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Figure 189 Target line Telco features voice message center . . . . . . . . . . . . . . . . . . . . . . . 571
Figure 190 Setting Target line voice mail settings for the telephone . . . . . . . . . . . . . . . . . 572
Figure 191 Hunt groups menus and fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
Figure 192 Hunt group XX screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
Figure 193 Broadcast call mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Figure 194 Linear call mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Figure 195 Rotary call mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Figure 196 Hunt group XX screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Figure 197 Moving hunt group members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Figure 198 Adding lines to hunt groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Figure 199 Silent Monitoring system settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Figure 200 Hunt Group Metrics screen for Hunt group 01 . . . . . . . . . . . . . . . . . . . . . . . . . 587
Figure 201 Hospitality commands and settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Figure 202 Hospitality service times and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Figure 203 Hospitality room settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Figure 204 Hospitality call permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Figure 205 Alarm data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Figure 206 Expired alarms fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Figure 207 BcmAmp Player . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Figure 208 Double Density Mode choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Figure 209 LAN, WAN and Dialup headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
Business Communications Manager 3.6 Programming Operations Guide

38

Figures

Figure 210 Example Mean Opinion Score Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Figure 211 Example of a Split Tunneling environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
Figure 212 DiffServ bandwidth brokers and nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
Figure 213 S reference point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Figure 214 T reference point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878

P0609326 1.1

39

Tables
Table 1

Telephone buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 2

Menu bar items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Table 3

Navigation tree menu functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Table 4

Security settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Table 5

User Profile settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Table 6

User Group Profile settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Table 7

Domain User Group Profile settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Table 8

Lockout policy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Table 9

Password policy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Table 10

Bus XX record settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Table 11

Programmed Bus Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Table 12

Module record values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Table 13

TI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Table 14

Services available for each PRI protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Table 15

Module record values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Table 16

Configuring DDI Mux connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Table 17

List of all the multiples of 56000 and 64000 bits/s . . . . . . . . . . . . . . . . . . . . . . 155

Table 18

DDI Mux Configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Table 19

Bandwidth available per channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Table 20

Line numbers for the UTWAN based on the DS30 bus of the DTM . . . . . . . . . 162

Table 21

UTWAN Summary parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Table 22

UTWAN frame relay parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Table 23

WAN PVC Configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Table 24

PPP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Table 25

LCP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Table 26

IPCP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Table 27

PPP User parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Table 28

Additional WAN IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Table 29

Telephony Services subheadings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Table 30

DS30 number and offset line-loop default list . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Table 31

General record values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Table 32

Loop start analog and digital fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Table 33

Ground start fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Table 34

DID line fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Table 35

E&M line fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Table 36

Target lines and DASS2 line fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Table 37

PRI line fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Table 38

BRI line fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Table 39

DPNSS line fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Table 40

VoIP line data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Business Communications Manager 3.6 Programming Operations Guide

40

Tables

Table 41

Combined line settings table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Table 42

Loss package settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Table 43

Default restriction filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Table 44

Default remote restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Table 45

Line attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Table 46

Loop settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Table 47

Loop settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Table 48

Loop settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Table 49

Loop attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Table 50

Private and Public received numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Table 51

General record values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Table 52

Target line record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Table 53

COS password values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Table 54

External access tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Table 55

Remote access matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Table 56

Private network values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Table 57

Dialing plan matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Table 58

Default codes table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Table 59

Access codes values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Table 60

Direct dial values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Table 61

Direct dial sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Table 62

Access/dialing codes: avoiding numbering conflicts . . . . . . . . . . . . . . . . . . . . 314

Table 63

Carrier access code values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Table 64

Access code values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Table 65

Route settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Table 66

Call by Call routing table example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Table 67

PRI Service type/DN type values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Table 68

Destination codes: avoiding numbering conflicts . . . . . . . . . . . . . . . . . . . . . . . 326

Table 69

Establishing routes and dialout requirements . . . . . . . . . . . . . . . . . . . . . . . . . 329

Table 70

Destination codes not using a wild card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Table 71

Destination codes using the ANY character . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Table 72

Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Table 73

Call by Call Services available on the system . . . . . . . . . . . . . . . . . . . . . . . . . 339

Table 74

Switches and service types chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Table 75

DN length values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Table 76

CbC matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Table 77

Default restriction filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Table 78

Default filters for program headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Table 79

Restriction filters matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

Table 80

DN mapping for DECT, Companion and ISDN . . . . . . . . . . . . . . . . . . . . . . . . . 358

Table 81

Edit DN Record Template information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Table 82

Add Users wizard information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

P0609326 1.1

Tables

Table 83

Copy values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Table 84

General record values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

Table 85

Telephone line access fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

Table 86

Telephone line assignment fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

Table 87

Capabilities fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

Table 88

Call forward fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

Table 89

Embark validation error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

Table 90

Hotline values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Table 91

ATA settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

Table 92

413

Table 93

User preference choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

Table 94

Button programming choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

Table 95

User speed dial settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

Table 96

CAP/KIM feature button programming choices . . . . . . . . . . . . . . . . . . . . . . . . 439

Table 97

Telephone restriction fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

Table 98

Schedule filter defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443

Table 99

Telco features settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

Table 100

DN voice mail settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

Table 101

DN equipment identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Table 102

General and Line access settings for DNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Table 103

Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Table 104

User preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Table 105

Button programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Table 107

Telephone (set) Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

Table 106

User speed dial settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

Table 108

Telephone restriction schedules and line/set restrictions . . . . . . . . . . . . . . . . . 450

Table 109

DN record, Telco features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

Table 110

Call features/interface list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

Table 111

Set feature values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

Table 112

Answer keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

Table 113

SWCA controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

Table 114

Call log options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470

Table 115

System features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

Table 116

Timer values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472

Table 117

Timer fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

Table 118

Release reason values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474

Table 119

Release reason values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

Table 120

System speed dial matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

Table 121

Voice message center settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

Table 122

ONN blocking settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

Table 123

Telco features matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

Table 124

Turning services on and off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484

41

Business Communications Manager 3.6 Programming Operations Guide

42

Tables

Table 125

Default schedule times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

Table 126

Ringing group schedule values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491

Table 127

Ringing group schedule line values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

Table 128

Restriction schedule values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

Table 129

Routing service schedule values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

Table 130

Ringing and Scheduling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

Table 131

Restriction and Routing Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

Table 132

Common settings: Schedule Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

Table 133

Common settings: Schedule times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

Table 134

Destination code leading digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

Table 135

E and M routing for a Business Communications Manager network . . . . . . . . 509

Table 136

Creating a coordinated dialing plan using line pools . . . . . . . . . . . . . . . . . . . . 514

Table 137

PRI call-by-call services routing information . . . . . . . . . . . . . . . . . . . . . . . . . . 516

Table 138

Call originating from the public network to a tandem network . . . . . . . . . . . . . 521

Table 139

Calls originating from the private network within a tandem network . . . . . . . . 524

Table 140

Node A destination code table, external termination . . . . . . . . . . . . . . . . . . . . 526

Table 141

Node A destination code table, internal termination . . . . . . . . . . . . . . . . . . . . . 527

Table 142

Node C destination code table, external termination . . . . . . . . . . . . . . . . . . . . 527

Table 143

Node C destination code table, internal termination . . . . . . . . . . . . . . . . . . . . 527

Table 144

MCDN network features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

Table 145

Module settings for MCDN network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

Table 146

MCDN dialing plan settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

Table 147

Network routing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

Table 148

IP trunking interoperability fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

Table 149

Hardware programming for branch offices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

Table 150

ETSI network values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

Table 151

Calling numbers required for DPNSS network example . . . . . . . . . . . . . . . . . 556

Table 152

Routing for DPNSS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557

Table 153

MCDN feature enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

Table 154

Parts of the NSI string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

Table 155

Hunt group settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575

Table 156

Hunt group member settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580

Table 157

Hunt group feature operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584

Table 158

Hunt group matrix fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584

Table 159

Silent monitor system settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585

Table 160

Hospitality main settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591

Table 161

Room settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592

Table 162

Call permission settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

Table 163

Alarm data settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

Table 164

Alarm data settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

Table 165

Hospitality settings matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

Table 166

IP Music Summary parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602

P0609326 1.1

Tables

Table 167

Networks Device parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607

Table 168

Advanced Networks parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607

Table 169

DSP resource requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

Table 170

Required MSC resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

Table 171

Evaluation of required Business Communications Manager configuration . . . 620

Table 172

Example of required configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621

Table 173

Evaluation for the example of required configuration . . . . . . . . . . . . . . . . . . . . 621

Table 174

MSC information parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

Table 175

MS-PEC information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

Table 176

Advantages and Disadvantages of Minimum and Maximum values . . . . . . . . 624

Table 177

MSC configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625

Table 178

MSC custom configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626

Table 179

MSC component parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627

Table 180

Business Communications Manager resources . . . . . . . . . . . . . . . . . . . . . . . . 633

Table 181

DHCP Server Summary attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639

Table 182

DHCP Global Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

Table 183

DHCP Summary settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641

Table 184

LAN Scope Specific Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643

Table 185

Address Range attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

Table 186

Excluded Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

Table 187

Reserved Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647

Table 188

Reserved Addresses Lease Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648

Table 189

Remote Scope settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

Table 190

Remote Scope specific settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651

Table 191

Remote Scope Address Range attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652

Table 192

Remote Scope Excluded Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653

Table 193

Remote Scope Reserved Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

Table 194

Lease Information for a Remote Scope Reserved Addresses . . . . . . . . . . . . . 656

Table 195

Relay Agent Interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659

Table 196

LAN global parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664

Table 197

Guidelines to configure LAN to LAN traffic smoothing . . . . . . . . . . . . . . . . . . . 664

Table 198

LAN Summary attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

Table 199

Additional LAN IP address parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667

Table 200

PPP password parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

Table 201

WAN summary parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

Table 202

WAN line parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675

Table 203

WAN sync parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676

Table 204

WAN frame relay parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677

Table 205

WAN PVC congestion control parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678

Table 206

WAN PPP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680

Table 207

Additional WAN IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681

Table 208

DLCI to IP Mapping parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683

43

Business Communications Manager 3.6 Programming Operations Guide

44

Tables

Table 209

RAS server TCP/IP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685

Table 210

V.90 modem summary parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687

Table 211

Modem link parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688

Table 212

V.90 modem access parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689

Table 213

ISDN summary settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691

Table 214

ISDN link parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692

Table 215

ISDN access parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692

Table 216

ISDN dial-out user parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693

Table 217

ISDN channel characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693

Table 218

Features that interact with PPPoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696

Table 219

PPPoE summary settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698

Table 220

PPPoE link parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699

Table 221

PPPoE access parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699

Table 222

PPPoE dial-out user parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

Table 223

PPPoE channel characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

Table 224

DNS Summary attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704

Table 225

IP Routing Summary attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707

Table 226

IP RIP Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707

Table 227

IP OSPF Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708

Table 228

IP RIP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710

Table 229

IP OSPF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713

Table 230

IP OSPF NBMA Neighbor parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714

Table 231

IP Static Route attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715

Table 232

IPX Routing Summary settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

Table 233

IPX Global settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

Table 234

IPX RIP Global settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

Table 235

IPX SAP Global settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722

Table 236

IPX Packet Filter Summary Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

Table 237

IPX Packet Input Filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724

Table 238

IPX Packet Output Filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726

Table 239

IPX RIP Summary settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727

Table 240

IPX RIP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728

Table 241

IPX RIP Input Filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

Table 242

IPX RIP Output Filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730

Table 243

IPX SAP Summary settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732

Table 244

IPX SAP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732

Table 245

IPX SAP Input Filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733

Table 246

IPX SAP Output Filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

Table 247

IPX Static Routing attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

Table 248

IPX Static Service attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738

Table 249

Web Cache attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742

Table 250

QoS Monitor Summary attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

P0609326 1.1

Tables

Table 251

Mean Opinion Score descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

Table 252

QoS Monitor Logging attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747

Table 253

Net Link Manager attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750

Table 254

Permanent WAN Connections settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750

Table 255

NAT Summary attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754

Table 256

NAT Rule Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756

Table 257

NTP Client settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762

Table 258

NTP Client Service settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

Table 259

PPTP Summary settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768

Table 260

PPTP Client attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770

Table 261

PPTP Tunnel attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

Table 262

PPTP Tunnel Summary attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772

Table 263

PPTP Tunnel Link parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772

Table 264

PPTP Tunnel Authentication parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773

Table 265

PPTP Destination Networks attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774

Table 266

Comparing Encryption and Authentication Methods . . . . . . . . . . . . . . . . . . . . 778

Table 267

Firewall rules for IKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782

Table 268

Firewall rules for ESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782

Table 269

Firewall rules for AH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782

Table 270

Firewall rules for the QOTD server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783

Table 271

Firewall filter for the Password server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783

Table 272

Firewall filter for the ICMP that the Client sends to the tunnel endpoint . . . . . . 783

Table 273

Firewall filter for Private Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783

Table 274

IPSec Global settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786

Table 275

IPSec Branch Office Tunnel settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787

Table 276

IPSec Local Accessible Network parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 789

Table 277

IPSec Remote Accessible Network parameters . . . . . . . . . . . . . . . . . . . . . . . . 790

Table 278

Remote Accessible Networks used to route all traffic through
the IPSec tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790

Table 279

IPSec Remote IP Address Pool settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800

Table 280

IPSec Remote User Account settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801

Table 281

DNS/WINS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803

Table 282

Split Tunnel Network settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804

Table 283

Service classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810

Table 284

Default Queue mapping for Business Communications Manager . . . . . . . . . . 811

Table 285

QoS Summary parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813

Table 286

QoS Advanced parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814

Table 287

QoS Interface Group Table parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815

Table 288

QoS IP Filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816

Table 289

QoS IP Filter Group parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818

Table 290

QoS Action parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820

Table 291

QoS Policy parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821

45

Business Communications Manager 3.6 Programming Operations Guide

46

Tables

Table 292

Status page items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823

Table 293

COPS Client Server parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826

Table 294

COPS Client Retry data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

Table 295

Policy Agent settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Table 296

Policy Server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Table 297

Policy Class Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Table 298

Policy Device Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Table 299

IP Firewall Filters Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832

Table 300

Firewall Input Filter Rule settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835

Table 301

Input Rule Configuration for Unified Manager — RPC . . . . . . . . . . . . . . . . . . . 841

Table 302

Input Rule Configuration for Unified Manager — DCOM . . . . . . . . . . . . . . . . . 841

Table 303

Input Rule Configuration for Unified Manager — port 443 . . . . . . . . . . . . . . . . 841

Table 304

Input Rule Configuration for systems with dialup interfaces . . . . . . . . . . . . . . . 843

Table 305

Core software, defined by region and carrier profile . . . . . . . . . . . . . . . . . . . . 846

Table 306

Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846

Table 307

South/Central America language breakout . . . . . . . . . . . . . . . . . . . . . . . . . . . 847

Table 308

Companding law . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847

Table 309

Mobility services, by region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848

Table 310

Module availability, by profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849

Table 311

Trunk availability, by region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850

Table 312

PRI line protocol supported, by region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851

Table 313

ISDN line services

Table 314

ISDN services, by Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852

Table 315

Time/date formats based on language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853

Table 316

Region defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853

Table 317

Default dialing restrictions, by profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856

Table 318

BRI and PRI line types (DTM and BRI modules) . . . . . . . . . . . . . . . . . . . . . . . 857

Table 319

CallPilot region default languages by country . . . . . . . . . . . . . . . . . . . . . . . . . 859

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852

Table 320

CallPilot feature default anomalies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860

Table 321

Features sorted by feature name and by activation code . . . . . . . . . . . . . . . . . 861

Table 322

Button Programming Feature settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865

P0609326 1.1

47

Preface
This guide explains how to program your Business Communications Manager system. For more
information about the Business Communications Manager document suite, refer to “Related
publications” on page 56.
This issue of the document reflects the added functionality built into the Business
Communications Manager 3.6 release. The hardware, and new and updated features described in
this and other documentation from this suite requires that your Business Communications
Manager system is running release 3.6.
This section includes the following general information:
•
•
•
•
•
•
•
•

“Before you begin” on page 48
“Symbols used in this guide” on page 48
“Text conventions” on page 49
“About the buttons on your telephones” on page 49
“Acronyms used in this guide” on page 51
“Related publications” on page 56
“System documentation map” on page 57
“How to get help” on page 62
Warning: Ensure that you make a complete backup of your data before attempting to
upgrade your system. Refer to the upgrade guide that comes with the upgrade package for
instructions about upgrading the Business Communications Manager software from one
version to another.

Note: The section “Software licensing” on page 3 contains software licensing
information.

Note: Hardware: BCM200 and BCM400 hardware is shipped with 3.0 or newer
software, only.
Note: Network: All the Business Communications Managers in your private network
should be running the same level of software to ensure that remote gateways and other
networking protocols are compatible. Meridian 1 systems connected to your network
using Voice Over IP (VoIP) trunks must be running the ITP software. Ask your Meridian
distributor for details.
After you perform an upgrade, always check that your gateways are still correctly
configured for local and remote connections.

Business Communications Manager 3.6 Programming Operations Guide

48

Before you begin

Before you begin
This guide is intended for these audiences:
•
•
•

the installer who performs the initial configuration of the system
the operator who manages the overall telephony operations of the system
the system administrator who manages the data and network operations of the system

This guide assumes the following:
•

There is an existing plan outlining the telephony and data requirements for your Business
Communications Manager system.

•

The Business Communications Manager is installed and initialized, and all hardware appears
to be working. External lines and wiring for terminals and sets are connected to the appropriate
media bay modules on the Business Communications Manager. All required keycodes have
been entered.

•

That all operators have a working knowledge of the Windows operating system and graphical
user interfaces.
That operators managing the data portion of the system are familiar with network management
and applications.

•

Symbols used in this guide
This guide uses symbols to draw your attention to important information. The following symbols
appear in this guide:
Caution: Caution Symbol
Alerts you to conditions where you can damage the equipment.
Danger: Electrical Shock Hazard Symbol
Alerts you to conditions where you can get an electrical shock.
Warning: Warning Symbol
Alerts you to conditions where you can cause the system to fail or work improperly.
Note: Note Symbol
A Note alerts you to important information.
Tip: Tip Symbol
Alerts you to additional information that can help you perform a task.

P0609326 1.1

Text conventions

!

49

Security Note: This symbol indicates a point of system security where a default should
be changed, or where the administrator needs to make a decision about the level of
security required for the system.

Text conventions
This guide uses the following text conventions:
angle brackets (< >)

Indicates that you choose the text to enter based on the description
inside the brackets. Do not type the brackets when entering the
command.
Example: If the command syntax is: ping 
you enter: ping 192.32.10.12

bold Courier text

Indicates command names and options and text that you need to enter.
Example: Use the dinfo command.
Example: Enter show ip {alerts|routes}.

italic text

Indicates book titles

plain Courier
text

Indicates command syntax and system output, for example, prompts
and system messages.
Example: Set Trap Monitor Filters

FEATURE
HOLD
RELEASE

Indicates that you press the button with the coordinating icon on
whichever set you are using. (Refer to About the buttons on your
telephones.)

About the buttons on your telephones
This guide uses text designators to indicate key pad feature buttons, such as Feature, Hold and
Release. The Business Series Terminals (BST) telephones and the IP telephones all use icons to
label these buttons. Table 1 shows the icons that appear for each function on the different types of
Nortel Networks digital telephones. Note that the T7316 and T7208 have a separate button for
mute functions. The IP telephones and the T7316E have separate buttons for both mute and
handsfree.
Table 1 Telephone buttons
Button Name
Feature1

Business Series Terminal T-series: 7XXX
IP telephones: i20XX

, Feature (i20XX)
(i2004, i2002);

Handsfree2
Mute3

Legacy Norstar M-series telephones
European Norion telephones

,
(7316E)

7208/7316 use assigned memory button.
(i20XX),

(7208, 7316, 7316E)

Business Communications Manager 3.6 Programming Operations Guide

50

About the buttons on your telephones

Table 1 Telephone buttons (Continued)
Hold4

,

,

Release5

,

, (2001 has a Goodbye button

Call button

(2001)

,

N/A

This document uses FEATURE to indicate the action of pressing the feature button.
This document uses HANDSFREE to indicate the action of pressing the handsfree or handsfree/mute button for
handsfree functionality.
3 This document uses MUTE to indicate the action of pressing the mute or handsfree/mute button for mute functionality.
4 This document uses HOLD to indicate the action of pressing the hold button.
5 This document uses RELEASE to indicate the action of pressing the release button.
1
2

You press the FEATURE key and then the feature code to use a feature.
For example: Press FEATURE 70 to transfer a call.

Model 7100 and 7000 telephones
The 7100 and 7000 telephones work differently from other telephones on your system because
they do not have line buttons. Where other telephones can require that you select a line or intercom
button to answer a call, with these telephones you just pick up the handset. Where other telephones
require you to select a line button to take a call on that line off hold, on these telephones, you press
HOLD.
You answer a second call by pressing HOLD. Your active call is put on hold and you connect to
the waiting call. You only can have two active calls at one time.
The 7100 and 7000 telephones do not have speakers, therefore, cannot use the handsfree feature.

Portable handsets
Companion, DECT, and the BST T7406 portable handsets all access system features in different
ways. Each of these handsets comes with a user guide that explains the specific feature access for
the handsets.

IP telephones
Nortel Networks IP telephones (i2001, i2002, i2004, i2050) have user cards that explain the
buttons on each device, including the Feature button, which is a softkey located under the
display on these telephones. The Telephone Feature User Guide can be used with these
telephones, as most Business Communications Manager features can be accessed from these
telephones. These telephones also have a display menu that provides quick access to listed
features.
The Symbol NetVision wireless IP handsets have a separate feature card which provides a quick
reference for accessing the system through the handset. The card also explains how to access the
Business Communications Manager features allowed by the system. Features can be accessed
either by entering the code on the dialpad or by using the menu on the handset display.
P0609326 1.1

Acronyms used in this guide

51

Information about configuring IP telephones and NetVision handsets is contained in the
IP Telephony Configuration Guide.

Acronyms used in this guide
This guide uses the following acronyms:
AAL

Analog Access Lines

ACD

Automated Call Distribution

AH

Authentication Header

ANSI

American National Standards Institute

API

Application Program Interface

ARP

Address Resolution Protocol

ASM

Analog station module

ATA (or ATA2)

Analog Terminal Adapter

AUI

Attachment Unit Interface

AWG

American Wire Gauge

BERT

Bit Error Rate Test

BC

committed burst

BE

excess burst

BIOS

Basic Input Output System

BKI

Break-in

BLF

Busy Lamp Field

BootP

Bootstrap Protocol

BRI

Basic Rate Interface

BRU

Backup and Restore Utility

CAA

Centralized Auto Attendant

CAC

Equal Access Identifier Code (carrier code)

CAP

Central Answering Position (T7316E+KIM or M7324+CAP modules)

CDP

Coordinated Dialing Plan

CHAP

Challenge-Handshake Authentication Protocol

CIC

Carrier Identification Code

CIR

Committed Information Rate

CLID

Calling Line Identification

COPS

Common Open Policy Service

Business Communications Manager 3.6 Programming Operations Guide

52

Acronyms used in this guide

COS

Class of Service

CSMA/CD

Carrier Sense Multiple Access/Collision Detection

CSU

Channel Service Unit

CTE

Connected Telecommunications Equipment

CVM

Centralized Voice Mail

DAL

Digital Access Lines

DASS2

Digital Access Signaling System Number 2

DCE

Data Communications Equipment

DCOM

Distributed Component Object Model

DECT

Digital enhanced cordless telecommunications or Digital European
cordless telephone

DES

Data Encryption Standard

DHCP

Dynamic Host Configuration Protocol.

DID

Direct Inward Dial

DiffServ

Differentiated Services

DIMM

Dual In-line Memory Module

DISA

Direct Inward System Access

DLCI

Data Link Connection Indentifier

DLCMI

Data Link Control Management Interface

DN

Directory Number

DNS

Domain Name Service (DNS)

DPNSS

Digital Private Network Signalling System

DRT

Delayed Ring Transfer

DSCP

Diff-Serv Code Point

DSP

Digital Signal Processor

DSS

Direct Station Set (also referred to as an auto dial key)

DTE

Data Terminal Equipment

DTM

Digital Trunk Module

DTMF

Dual Tone Multifrequency.

EBN

Egress Border Node

EDO

Extended Data-Out

EF

Expedited Forwarding

eKIM

enhanced Key Indicator Module

EN

Edge Node

ES

End Station

P0609326 1.1

Acronyms used in this guide

ESP

Encapsulated Security Payload

FDD

Full Double Density

FQDN

Fully Qualified Domain Name

FTP

File Transfer Protocol

GATM

Global Analog Trunk Module

HDLC

High-level Data Link Control

HF

Handsfree

HLC

Home Location Code (UDP dialing)

HS

Hospitality services

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol Secured

IBN

Ingress Border Node

I/C

Intercom feature button

ICCL

ISDN Call Connection Limitation

ICMP

Internet Control Message Protocol

IETF

Internet Engineering Task Force.

IP

Internet Protocol

IF

Input Filter

IPCP

IP Control Protocol

IPSec

Internet Protocol Security

IPX

Internetwork Packet Exchange

IRQ

Interrupt Request

ISDN

Integrated Services Digital Network

ISO

International Organization for Standardization

ISP

Internet Service Provider

ITU-T

International Telecommunication Union-Telecommunication
Standardization Sector (formerly CCITT)

IVR

Interactive Voice Response

KIM

Key Indicator Module

LAN

Local Area Network

LCD

Liquid Crystal Display

LCP

Link Control Protocol

LM

LAN Manager

LQR

Link Quality Rate

MAC

Media Access Control

53

Business Communications Manager 3.6 Programming Operations Guide

54

Acronyms used in this guide

MAU

Media Access Unit

MCDN

Meridian Client Defined Network (PRI SL-1)

MD5

Message Digest algorithm

MLPPP

Multi-Link Point-to-Point Protocol

MPPC

Microsoft Point to Point Compression

MSC

Media Services Card

MS-PEC

Media Services Processor Expansion Card

MWI

Message Waiting Indicator

NAT

Network Address Translation

NBMA

Non Broadcast Multi-Access

NCRI

Network Call Redirection Information

NIC

Network Interface Card

NTLM

NT LAN Manager

NNTP

Network News Transfer Protocol

OPX

Off Premises Extension.

OSI

Open Service Interconnection

OSPF

Open Shortest Path First

PAP

Password Authentication Procedure

PBX

Private Branch Exchange.

PCI

Peripheral Component Interconnect Slot

PDD

Partial Double Density

PDN

Public Data Network

PFS

Perfect Forward Secrecy

PHB

Per Hop Behavior

POF

Packet Output Filter

POP3

Post Office Protocol

PPP

Point-to-Point Protocol

PPPoE

Point-to-Point Protocol over Ethernet

PPTP

Point-to-Point Tunneling Protocol

PRI

Primary Rate Interface

PSTN

Public Switched Telephone Network

PVC

Permanent Virtual Circuit

QoS

Quality of Service

QOTD

Quote of the day server

QSIG

Q reference point signalling

P0609326 1.1

Acronyms used in this guide

RAS

Remote access service

RIP

Routing Information Protocol

RLR

Receive Loudness Rating

RPC

Remote Procedure Call

RTP

Realtime Transport Protocol

SAP

Service Advertising Protocol

SAPS

Station Auxiliary Power Supply

SDRAM

Synchronous Dynamic Random Access Memory

SHA

Secure Hash Algorithm

SLA

Service Level Agreement

SLR

Send Loudness Rating

SMB

Server Message Block

SMDS

Switched Multimegabit Data Service

SMTP

Simple Mail Transfer Protocol

SNMP

Simple Network Management Protocol

SPID

Service Profile Identifier

SR

Static Route

SS

Static Service

SSL

Secure Sockets Layer

STP

Shielded Twisted Pair

SUNNFS

SUN Network File System

TAPI

Telephony Application Program Interface

TCP/IP

Transmission Control Protocol/Internet Protocol

TE

Terminal Equipment

TEI

Terminal Endpoint Identifier

TFTP

Trivial File Transfer Protocol

TOS

Type of Service.

TPE

Twisted Pair Ethernet

TTL

time-to-live

UNISTIM

Unified Networks IP Stimulus

UDP

User Datagram Protocol or Universal Dialing Plan

VLAN

Virtual Local Area Network

VoIP

Voice over IP

VPN

Virtual Private Networks

WAN

Wide Area Network

55

Business Communications Manager 3.6 Programming Operations Guide

56

Related publications

WFQ

Weighted Fair Queuing

WINS

Windows Internet Name Service

Related publications
In addition to the Programming Operations Guide, the Business Communications Manager
documentation suite contains the following documents:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

Management User Guide
Telephony Features Handbook
Installation and Maintenance Guide (BCM1000 and BCM400/200)
IP Telephony Configuration Guide
CallPilot Manager Set Up and Operation Guide
CallPilot Reference Guide
CallPilot Quick Reference Guide
CallPilot Programming Record
CallPilot Message Networking Set Up and Operation Guide
CallPilot Message Networking User Guide
CallPilot Unified Messaging Installation and Maintenance Guide
CallPilot Desktop (Unified) Messaging Quick Reference Guide
Software Keycode Installation Guide
Call Center Set Up and Operation Guide
Call Center Agent Guide
Call Center Supervisor Guide
Call Center Reporting Set Up and Operation Guide
LAN CTE Configuration Guide
Personal Call Manager User Guide
Call Detail Recording System Administrator Guide
Analog Telephone User Guide
CallPilot Fax Set Up and Operation Guide
CallPilot Fax User Guide
Interactive Voice Response Installation and Configuration Guide (IVR)

From the Business Communications Manager 3.6 Documentation CD, you can also access a
number of telephone and accessory quick reference cards.
If you operate a multi-site Business Communications Manager network, you can use the Network
Configuration Manager to provide centralized configuration and management operations. The
documentation for this tool can be found on the Network Configuration Manager CD, which
includes the software and the following documentation.
•
•
•
•

Network Configuration Manager Installation Guide
Network Configuration Manager Administration Guide
Network Configuration Manager Client Software User Guide
Network Configuration Manager Reference Guide

P0609326 1.1

System documentation map

57

System documentation map
The following pages provide a map of the Business Communications Manager documentation CD.
The map shows the overall task process of the system, and indicates which documentation deals
with each section. All the documents describes are included on the documentation CD that came
with your system.
•
•
•
•
•

“Installation documentation” on page 58
“Operations documentation” on page 59
“Call Management documentation” on page 60
“Unified Manager and hardware maintenance documentation” on page 61
“Multi-site Administration: Network Configuration Manager” on page 61

Business Communications Manager 3.6 Programming Operations Guide

58

System documentation map

Installation documentation

Documentation CD

Remove your Business
Communications Manager
components from the box

Business Communications Manager base
and expansion unit hardware installation

Operations

Installation and
Maintenance Guide

Data cards

System planning
and configuration
records

Setting up media bay modules

Analog telephones

Installation
manuals
come with
telephones

Programming Records (CD only)

Analog
Telephone
User Guide

Companion Installation
and Configuration Guide

Companion
Portable handsets
(Region-specific)

Voice Mail and
Call Management
Applications

DECT Deployment Tool
and Provisioning Guide

DECT

DECT Installation and
Maintenance Guide

T7406
T7406 Cordless Telephone
Installation Guide
IP Telephones

Nortel Networks
IP telephones

Three-port Switch Installation Guide
IP Telephony Configuration Guide

Symbol NetVision
wireless IP telephone
Digital telephony

Installing lines

Nortel Networks
digital telephones

P0609326 1.1

NetVision Phone Administrator
Guide
Bix Block Wiring Guide
Installation manuals
come with telephones

System documentation map

59

Operations documentation
System Management and Maintenance
Documentation CD
Voice Mail and Call Management Applications
Operations

Hardware
Installation

Telephony Configuration

Using the telephones
and equipment

T7000 User Card
T7100 User Card
T7208 User Card
T7316 User Card
T7316E User Card
T7406 User Card
M7324 User Card
i2004 User Card
i2002 User Card
i2001 User Card
NetVision Feature Card
Central Answering Position
(CAP) User Card
Telephone Features User
Guide
SWCA User Card
Analog Telephone User Guide

Quick Start Wizard
Setting up Lines,
Routes and
Access Codes

Programming Operations Guide

Controlling calls
Setting up
Telephone records
and features

Software Keycode
Installation Guide

Data Configurations
Land
Telephony Networking
VoIP
Registering Telephones

CallPilot Quick Reference
card, NVM interface
CallPilot Quick Reference
card, CP interface

Using the telephones
and equipment

IP Telephones

IP Telephony
Configuration Guide

Symbol NetVision
Companion
DECT
Using Telephone Features, and
finding prompt descriptions.

Companion Installation
and Configuration Guide
DECT Installation and
Maintenance Guide
Telephony Features Handbook

Business Communications Manager 3.6 Programming Operations Guide

60

System documentation map

Call Management documentation
System Management and Maintenance

Documentation CD

Voice Mail and Call Management Applications
Hunt Groups
Programming
Operations Guide
Hospitality Services
Call Detail Recording
System Administration Guide

CDR

Keycoded Applications

Hospitality
Features Card

CallPilot

Reference
Guide

Call Pilot Manager Set Up
and Operation Guide

Programming
Record
Software Keycode
Installation Guide

CallPilot Message
Networking
CallPilot Fax
CallPilot Desktop
(Unified) Messaging

CallPilot Message Networking
Set Up and Operation Guide

User Guide

CallPilot Fax Set Up and
Operations Guide

User Guide

CallPilot Unified Messaging
Installation and Maintenance

User Guide

Call Center Set Up
and Operation Guide

Call Center

Professional Call
Center
Multimedia Call Center

Reporting Set Up and
Operation Guide

Supervisor and
Agent Guides
Multimedia Call Center
Web Developer Guide

Multimedia Call Center
Set Up and Operation Guide
LAN CTE Configuration Guide

LAN CTE

IVR

P0609326 1.1

Personal Call Manager

Personal Call Manager User Guide

Interactive Voice Response Installation and Configuration Guide

System documentation map

61

Unified Manager and hardware maintenance documentation
Hardware Installation
Documentation CD

Operations

Voice Mail and
Call Management

System Management and Maintenance

System configuration records

Security and User Administration

Backup and Restore

Programming Records (CD only)

Programming Operations Guide

Management User Guide

Maintenance and Troubleshooting

Multi-site Administration: Network Configuration Manager
Network Configuration Manager CD

Installation Guide

Administration Guide
Software
Client Software User Guide
Reference Guide

Business Communications Manager 3.6 Programming Operations Guide

62

How to get help

How to get help
If you do not see an appropriate number in this list, go to www.Nortelnetworks.com/support.

USA and Canada
Authorized Distributors - ITAS Technical Support
Telephone: 1-800-4NORTEL (1-800-466-7835)
If you already have a PIN Code, you can enter Express Routing Code (ERC) 196#.
If you do not yet have a PIN Code, or for general questions and first line support, you can enter
ERC 338#.
Website: http://www.nortelnetworks.com/support

Presales Support (CSAN)
Telephone: 1-800-4NORTEL (1-800-466-7835)
Use Express Routing Code (ERC) 1063#

EMEA (Europe, Middle East, Africa)
Technical Support - CTAS
Telephone:
* European Freephone
European Alternative/
United Kingdom
Africa
Israel

00800 800 89009
+44 (0)870-907-9009
+27-11-808-4000
800-945-9779

* Note: Calls are not free from all countries in Europe, Middle East or Africa
Fax: 44-191-555-7980
email: emeahelp@nortelnetworks.com

CALA (Caribbean & Latin America)
Technical Support - CTAS
Telephone: 1-954-858-7777
email: csrmgmt@nortelnetworks.com

APAC (Asia Pacific)
Technical Support - CTAS
Telephone: +61-2-870-8800
Fax: +61 388664644
email: asia_support@nortelnetworks.com

In-country toll free numbers
Australia 1800NORTEL (1800-667-835)
China 010-6510-7770
P0609326 1.1

How to get help

63

India 011-5154-2210
Indonesia 0018-036-1004
Japan 0120-332-533
Malaysia 1800-805-380
New Zealand 0800-449-716
Philippines 1800-1611-0063
Singapore 800-616-2004
South Korea 0079-8611-2001
Taiwan 0800-810-500
Thailand 001-800-611-3007
Service Business Centre & Pre-Sales Help Desk +61-2-8870-5511

Business Communications Manager 3.6 Programming Operations Guide

64

How to get help

P0609326 1.1

65

Chapter 1
Introduction
The Business Communications Manager includes software and hardware components that provide
telephony, voice messaging, interactive voice response (IVR), data networking, and IP telephony.
The web-based navigation tool, Unified Manager, provides easy access to all operations and
maintenance programming on the Business Communications Manager system at a single site. For
more information about Unified Manager, see “Using the Unified Manager” on page 82.
This section includes the following topics:
•
•
•
•
•
•

“System configuration process maps” on page 66
“Finding your way around” on page 72
“Business Communications Manager hardware” on page 74
“What do media bay modules do?” on page 76
“How does the system connect to the network?” on page 76
“Additional Business Communications Manager applications” on page 76

With the introduction of BCM version 3.5 software, there was an increase in the awareness
of security in regards to access to the Unified Manager, both by administrative users and by
client applications. The icon shown to the left, when used within this document, denotes
points of security that you need to consider when setting up or using your system.
!

•

•

•

This software includes a generic security certificate that provides an increased level of
encryption ability. You can replace this certificate with a site-specific certificate. Since
encryption levels have some dependencies to the version of Windows operating systems, the
defaults are set at a mid-range level to allow for clients using earlier versions that do not
support strict encryption requirements. You can reset these levels higher or lower.
This version also provides more control over password policies, that allow you to determine
the complexity of the passwords you want to assign to the users who do programming in the
Unified Manager. You can also determine if you want the system to lockout users who have
entered an incorrect password after a specified of times.
Finally, a more secure front end application to the text-based interface is being introduced. The
PuTTY application uses SSH to provide a secure connection to the text-based interface. The
application is downloaded to a user’s computer, rather than being resident on the Business
Communications Manager, like Telnet.

The Network Configuration Manager provides multi-site network management. This process is
described in a separate set of user guides.
Figure 2 on page 68, Figure 4 on page 70, Figure 5 on page 71, and Figure 3 on page 69 provide an
overview of the processes for operating the Business Communications Manager system.

Business Communications Manager 3.6 Programming Operations Guide

66

System configuration process maps

System configuration process maps
The following process maps show you the order in which your system is configured. Each section
provides quick reference information about the step, plus a link to the process section.
•
•
•
•
•

Initial system configuration
“Configuring telephony components” on page 68
“Optional keycoded features” on page 69
“Data and IP telephony configuration” on page 70
“Post-system setup features” on page 71
Caution: Programming affects system operation.
Only a qualified system administrator should perform startup, installation and
maintenance programming. Many of the settings affect correct system operation.

P0609326 1.1

System configuration process maps

67

Initial system configuration
Figure 1 Process for initial system configuration

System
hardware is
installed

Set and
install
modules

Run
startup
Wizard

Refer to the Installation and Maintenance Guides for hardware setup.

Refer to the Installation and Maintenance Guides for media bay module
settings and connections. To identify the media bay modules to the system
and set up their line values, refer to “Configuring resources — media bay
modules” on page 123.

Set up your system for correct network connection and basic telephony and
CallPilot properties. Refer to “Using the Quick Start Wizard” on page 96.

Set up
security
levels

There are a number of points at which you can enhance the security of
access to your system:
You can install a site-specific security certificate (“Understanding BCM SSL
certificate properties” on page 77).
You can determine the encryption level required between the system and
clients (“Setting system security compatibility levels” on page 107).

Set up
user
access

To maintain user access security, you can define different levels of
password security and user access. At a minimum, change the default
administration default passwords (ee_admin and supervisor). Refer to
“Managing system and user security access levels” on page 105.

Business Communications Manager 3.6 Programming Operations Guide

68

System configuration process maps

Configuring telephony components
Figure 2 Process for configuring the telephony components

System
setup is
complete

Set up
lines/loops

Refer to the preceding flow chart.

When the trunk media bay modules are configured, the system assigns line
or loop numbers. You may need to change some of the line attributes. You
can also refer to the lines and loops to set up line pools and call routing.
Refer to “Configuring lines” on page 227.
See also “Data and split-line configuration” on page 151

Set up
access

Set up
telephones

Confirm
system
settings

When your lines are configured, you can set up system access
configurations. Refer to “Configuring outgoing calls” on page 301 and
“Controlling access into the system” on page 283.
When the station media bay modules are configured, the system assigns
extension numbers (DNs) for each telephone connection.
DNs define each set or piece of equipment connected to the system. Within
the System DN headings, you can define how individual sets will interact in
the system. Refer to “Configuring DNs for system devices” on page 387.
Cordless/wireless telephones (NetVision, BST T7406, DECT, Companion)
all have their own installation and configuration guides and feature cards.
A number of settings affect all lines or telephones. Most of these settings
are default. Confirm that they suit your purposes.
Refer to “Configuring system settings” on page 451.
After you set the basic telephony information, you can configure the special
features such as:

Set up
special
features

Set up
call
management
features

P0609326 1.1

•
•
•

Hunt groups (“Configuring Hunt groups” on page 573)
Hospitality (“Configuring Hospitality Services” on page 589)
IP music (“Configuring the music source” on page 601)

The Business Communications Manager has built-in call management
applications. Basic CallPilot features can be accessed from the CallPilot
button on the first page of the Unified Manager. CallPilot documentation
describes how to install and use the available features. CallPilot also has
enhanced features, which require a keycode to activate (refer to the CD
contents flowchart: “System documentation map” on page 57).
Remote voice mail: If your system is not the voice mail host, set up remote
access to the network voice mail system. Refer to “Configuring centralized
voice mail” on page 559

System configuration process maps

69

Optional keycoded features
Figure 3 Process for activating optional keycoded features

System is
set up

Purchase
the optional
feature

Get an
Authorization
code

The basic system has been installed and configured.

Keycoded applications:
Call Center/Call Center Reporting
Companion (US UTAM code)
Fax Suite
LAN CTE (TSP) (required for Personal Call Manager)
Message Networking (VPIM/AMIS)
Multimedia Call Center
Networking DPNSS/MCDN (region-specific)
Professional Call Center (upgrade) and Professional Call Center Agents
Unified Messaging and Voice Mailbox Expansion
VoIP Gateway and IP telephony and IP trunks
Interactive Voice Response (IVR)

When you purchase an optional feature, you receive an Authorization
Code for the feature.

Get the
software
keycode

Access the Nortel Networks Keycode web site and use the Authorization
Code to get a software keycode for the feature. For information about
how to get the software keycode, refer to the Software Keycode
Installation Guide.

Enter
software
keycode

Use Unified Manager to enter the software keycode. For information
about how to enter the software keycode, refer to the Software
Keycode Installation Guide.

Program
the feature

For information about how to program the new optional feature, refer
to the documentation for that feature.
Also refer to “Using a wizard to change data parameters” on page 633.

Business Communications Manager 3.6 Programming Operations Guide

70

System configuration process maps

Data and IP telephony configuration
Figure 4 Process for configuring the data and IP telephony components

System
setup is
complete

Set up
data
network

Basic system configuration is complete. Refer to previous flowcharts.

You configure the data network options, so that Business Communications
Manager operates properly on your network. For information about how to
configure the data networking options, refer to:
“Configuring DHCP” on page 637
“Configuring DNS” on page 703
“Configuring IP Routing” on page 705
“Configuring IPX Routing” on page 719
“Configuring QoS monitor” on page 743
“Configuring Web Cache” on page 741
“Configuring Net Link Manager” on page 749
“Configuring NAT (Network Address Translation)” on page 753
“Configuring NTP Client” on page 761

Set up
network
Policies

Policies allow you to control the data traffic on your network so more
bandwidth is available to delay sensitive data such as IP telephony. For
information about how to configure Policies, refer to “Policy-enabled
networking” on page 807.

Set up
firewalls

To control access to your system, you can use firewalls to block or allow
specific ports and IP addresses. Refer to “Configuring IP Firewall Filters”
on page 831.

Set up
VPN
Tunnels

Set up IP
telephony

P0609326 1.1

Virtual Private Networks (VPN) tunnels allow you to create secure
connections over the public data network. You can also use VPN to ensure
a secure connection to the Business Communications Manager. For more
information about VPN Tunnels, refer to “Virtual Private Networks (VPN)”
on page 765.
Set up any voice over IP (VoIP) trunks and/or IP telephones and Netvision
telephones. Refer to the IP Telephony Configuration Guide for details. The
DNs for these telephones are configured within the digital range of DNs.

System configuration process maps

71

Post-system setup features
Figure 5 Post-setup processes

System is
set up

The basic system has been installed and configured.

Set up
alarm
manager

Determine how your Business Communications Manager system will
report alarms. Refer to the Management User Guide

Set up
BRU and
CDR

Set backup schedules and determine call detail reporting (CDR). Refer to
the Management User Guide and the CDR User Guide.

Business Communications Manager 3.6 Programming Operations Guide

72

Finding your way around

Finding your way around
The following sections provides you with quick links to the detailed configuration information:
•
•
•

“Security and User Management” on page 72
“Telephony programming quick access list” on page 72
“Data programming sections” on page 73

Security and User Management
•
•

Unified Manager access: “Getting started with Unified Manager” on page 77
Security and user management: “Managing system and user security access levels” on page
105

Telephony programming quick access list
Configuration overviews and planning
•
•
•
•

System configuration process overview: “System configuration process maps” on page 66
Application overview: Getting started with Unified Manager on page 77
Telephony Services overview: “Planning your telephony services” on page 188
Quick reference section to telephony programming: “Telephony feature planning” on page
193

Lines and network configuration
•
•
•
•
•
•

•
•

P0609326 1.1

Configuring media bay modules: “Configuring resources — media bay modules” on page
123
Configuring the PSTN lines: “Configuring lines” on page 227 and “Configuring BRI
Loops” on page 265
Configuring outgoing call programming: “Configuring outgoing calls” on page 301
Configuring incoming and internal access: “Controlling access into the system” on page
283
Configuring the public network access: “Configuring public networks” on page 499
Configuring private network access: “Configuring private networks” on page 505, and
“Configuring private networks with SL-1 MCDN” on page 519, or “Configuring ETSI
QSIG and DPNSS network services” on page 543.
Centralized Voice Mail (host or remote system and telephony settings): “Configuring
centralized voice mail” on page 559
ISDN general information: “ISDN overview” on page 869

Finding your way around

73

Telephony configuration
•
•
•
•
•

Using Wizards to configure telephones: “Configuring DNs using the Wizards” on page
369
Using DN records to configure telephones: “Configuring DNs for system devices” on
page 387
Setting telephony system features: “Configuring system settings” on page 451
Define telephony schedules: “Configuring schedules” on page 483
Telephony features list: System Features on page 861

Special features
•
•

Hunt groups: “Configuring Hunt groups” on page 573
Hospitality Services: “Configuring Hospitality Services” on page 589

Reference material
•
•

System profile tables: “Defining region-based defaults” on page 845
Features available for programming on the telephone memory buttons: “Button
programming features” on page 865

Data programming sections
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

“Configuring the MSC resources” on page 609
“Using a wizard to change data parameters” on page 633
“Configuring DHCP” on page 637
“Configuring the LAN resources” on page 663
“Configuring the WAN resources” on page 669
“Configuring the Dial Up resources” on page 685
“Configuring DNS” on page 703
“Configuring IP Routing” on page 705
“Configuring IPX Routing” on page 719
“Configuring QoS monitor” on page 743
“Configuring Web Cache” on page 741
“Configuring Net Link Manager” on page 749
“Configuring NAT (Network Address Translation)” on page 753
“Configuring NTP Client” on page 761
“Virtual Private Networks (VPN)” on page 765 (tunnels)
“Policy-enabled networking” on page 807
“Configuring IP Firewall Filters” on page 831

Business Communications Manager 3.6 Programming Operations Guide

74

Business Communications Manager hardware

Business Communications Manager hardware
The main component of the Business Communications Manager system is the Business
Communications Manager base unit. The Business Communications Manager base unit controls
all tasks such as call processing, voice messaging, and data routing.

BCM1000 (legacy equipment)
If you have existing equipment, like the unit shown in the figure below (BCM1000), you can
update the operating system with new Business Communications Manager software.
Figure 6 Upgradeable BCM1000
Media bay module (MBM) slots

Ethernet ports

For a detailed description about maintaining these units, refer to the Business Communications
Manager BCM1000 Installation and Maintenance Guide.
Note: Some of the components described in this section are not available in all areas. Ask your
Nortel Networks Business Communications Manager supplier for information about the
availability of components.

P0609326 1.1

Business Communications Manager hardware

75

BCM200/BCM400 base units
In conjunction with the BCM version 3.0 system release, Nortel released two new base unit
models to provide added flexibility for system planning. These systems come preloaded with the
latest version of software. You cannot run versions previous to BCM 3.0 software on these units.
However, you can reuse modules from previous versions of the system, if you are replacing old
system hardware with the new BCM200 or BCM400 hardware (shown below). For a detailed
description of this hardware, and how it is installed and maintained, refer to the Business
Communications Manager BCM200/BCM400 Installation and Maintenance Guide.
Figure 7 BCM200 and BCM400 hardware
Media bay module (MBM) slots

BCM400

Primary Mirror

Master
Buzzer Off

Modem port

Ethernet ports

Media services
card (MSC)

WAN card

Media bay module (MBM) slots

BCM200

Modem port

Ethernet ports

Media services
card (MSC)

WAN card

Business Communications Manager 3.6 Programming Operations Guide

76

Additional Business Communications Manager applications

What do media bay modules do?
Media bay modules are key components of the system. They provide the link between the external
lines (trunks), the Business Communications Manager applications, and the internal extensions
(DNs), which connect to individual telephones.
The type of modules on your system depends on your set requirements and the type of lines
available from your service provider. You need to determine this information before you order the
system. For a detailed description of this hardware, and how it is installed and maintained, refer to
the Hardware Installation and Maintenance Guide.

How does the system connect to the network?
The Business Communications Manager is designed to connect to your business network on a
LAN and/or a WAN.
For data networking, the Business Communications Manager acts as a policy enabled router that
optimizes data traffic and ensures consistent bandwidth for IP telephony, VoIP trunks, and mission
critical data.
For telephony applications, the Business Communications Manager base unit acts as a switch and
feature controller for the external lines and the internal extensions attached to the sets.
The IP telephone uses both data and telephony features to provide an network-based telephone that
provides the call features of the telephony-based digital telephones.

Additional Business Communications Manager applications
The Business Communications Manager provides a number of software applications. Some
applications work immediately after you install the Business Communications Manager system
and access the Unified Manager. Refer to Chapter 2, “Getting started with Unified Manager,” on
page 77 for a description of the Unified Manager interface.
To use other applications, you enable the application by entering software keycodes.
Keycodes are based on your system identification and an encrypted code that you obtain when you
purchase the rights to an option. Refer to the Software Keycode Installation Guide for information
about how to acquire a keycode and how to enter it. Each of these optional features has separate
documentation which includes information keycodes and how to set up the application.
Refer to “Related publications” on page 56 for a list of the documentation for each of these
applications. Also refer to “System documentation map” on page 57 for an overview of how these
applications fit into the overall system.

P0609326 1.1

77

Chapter 2
Getting started with Unified Manager
This section provides you with information about the Unified Manager, the tool you access on the
Business Communications manager from your desktop and use to configure system information.
This section describes the Unified Manager interface functions.
Warning: If the installer did not change the access password to the Unified Manager,
you should do so at the earliest opportunity. Refer to “Managing access passwords” on
page 109 for procedures for changing passwords and adding new users.
This section includes information about:
•
•
•
•
•
•
•

“Understanding BCM SSL certificate properties” on page 77
“Using the Unified Manager main page buttons” on page 79
“Using the Unified Manager” on page 82
“Using Unified Manager Help” on page 87
“Logging off” on page 88
“Using the SSH client to access the text-based interface” on page 89
“Manually activating Telnet” on page 90

!

Security note: Multiple users logging on to the Business Communications Manager
with the administrator account, from different client stations, can cause inconsistent or
wrong configuration. Therefore, it is advisable to limit the number and distribution of
administrator accounts.
Security note: The configuration section in the Unified Manager is not secured through
SSL encryption. To provide security for this section, establish a VPN client tunnel. Refer
to “IPSec Remote User configuration” on page 796.

Understanding BCM SSL certificate properties
When you first run the BCM version 3.6 software, you will note that the default Web access to the
Business Communications Manager now utilizes SSL encryption for system security (BCM 3.5
and newer software). This includes the appearance of a security alert when you initiate a
connection to the Unified Manager using SSL, which indicates site validation of the default
certificate.
This security alert does not appear if you:
•
•
•

add a site-specific certificate (“Uploading a certificate and a private security key” on page 78)
suppress the message on your client browser (“Suppressing the security alert message” on
page 79)
use the non-SSL port (http:6800) (“Using the non-secure http:6800 port” on page 79)

Business Communications Manager 3.6 Programming Operations Guide

78

Understanding BCM SSL certificate properties

The self-signed certificate that is included in the BCM version 3.6 software enables SSL
encryption functionality, providing the necessary encryption keys. However, it does not address
site authentication. Site authentication requires system-specific information such as an IP address,
company name, and so on.
Note: Client applications do not need to install the certificate. The Business Communications
Manager sends the certificate when it accesses the client application.

Uploading a certificate and a private security key
Obtain a site certificate for your Business Communications Manager from a CA (Certificate
Authority) vendor. Certificate files must use the .PEM format. You will be provided with a
certificate and a private security key. These are what need to be installed on the Unified Manager.

!

Security note: Ensure that you maintain a copy of your certificate and private security
keys in a secure place, preferably offsite. This provides you with a backup if your system
ever requires data re-entry.

1

Log on to the Business Communications Manager main screen.

2

Click on the Maintenance button.

3

You will be prompted to enter a system user name and password.

4

Click on OK.
The main Business Communications Manager Product Maintenance and Support page
appears.

5

On the left menu, click on the Maintenance Tools link.
A web page showing a list of Maintenance Tools appears.

6

Under Maintenance Tools, Security, click the Upload Certificate and Private Key link.
A web page displaying Certificate and Private Key fields appears.

7

Use the Browse button beside each field to locate the certificate and private key files.
Both files must be uploaded at the same time.

8

Click the Upload button.
Upload messages:
•

If the upload is successful:
Certificate and Private Key Upload Was Successful!
You must restart the Apache Service or Restart the BCM before the
Settings will take Effect.

•

If the upload is unsuccessful:
Certificate and Private Key Upload Was NOT Successful!
The Certificate and Private Key do not match.
Please upload a VALID Certificate and Private Key Combination!

9

Click on the BCM link beside Your Location to exit the maintenance pages.

10 To replace the default certificate with the new certificate and private key:
P0609326 1.1

Using the Unified Manager main page buttons

a

Exit the Unified Manager.

b

Log back into the Unified Manager.

79

Troubleshooting: Restoring the default certificate
If something happens to your private security certificate file, you cannot access the Unified
Manager and you need to restore the default certificate. Contact your technical support team for
assistance.

Suppressing the security alert message
If you do not want to add a site-specific security certificate, but you want to suppress the security
alert message, you can use the Internet Explorer Security options to disable the warning.
1

Open Internet Explorer.

2

On the top menu bar, click Tools and select Internet Options.

3

Select the Advanced tab.
Note: Location of the following prompt may vary, depending on the version of Internet
Explorer.

4

Scroll to the item “Warn about invalid site certificates.”

5

If the check box has a check mark, click on the box to remove it. This disables this option.

6

Restart the browser.

Using the non-secure http:6800 port
If you choose not to use SSL on your system, you can disable the system prompt that forces secure
web access. Refer to “Setting system security compatibility levels” on page 107. On the Security
screen described in that section, choose Disabled for the Force Secure Web Access field.

Using the Unified Manager main page buttons
On the Business Communications Manager Unified Manager initial page, a number of buttons
provide access to various parts of the Unified Manager. The purpose of each button is discussed in
this section.
•

“Locating Wizards” on page 80

•

“Locating optional features from the main page” on page 81

!

Security note: Ensure that you change the password after you first log on to Business
Communications Manager. For information about how to change passwords, and how to
define user profiles, refer to “Managing system and user security access levels” on page
105.
Business Communications Manager 3.6 Programming Operations Guide

80

Using the Unified Manager main page buttons

Locating Wizards
The Wizards are self-contained task applications that you can use to speed up some configuration
tasks. The access icons for the Wizards are located on the Setup and Management Wizards page,
which is accessed through the Wizards button on the start page of the Unified Manager.
These are the wizards that are available from this page:
•

•

•

•
•

•
•

Quick Start Wizard: initializes the system and sets up your basic system information. This
wizard is only run once, when your system is first set up. Refer to “Using the Quick Start
Wizard” on page 96.
Add Users Wizard: allows you to change the telephony settings for a set of DNs or for a
single DN. You can define the settings in this Wizard, or you can use a pre-defined template,
from a local site or from a remote site, created with the Edit DN Record Template wizard.
Refer to “Creating telephone records with the Add Users Wizard” on page 375.
Edit DN Record Template Wizard: allows you to select Telephony User Templates and
change and define the user settings for telephones. The Telephony Template is stored in a file
for use with the Add Users Wizard. Refer to “Editing DN Record Templates” on page 369.
DN Renumber Wizard: renumbers a range of DNs. Refer to “Using a wizard to renumber
telephone DNs” on page 367.
Network Update Wizard: allows you to update your system data network settings any time
after the Quick Start Wizard was run, which sets the initial network setup. Refer to “Using the
Network Update Wizard” on page 634.
DECT Mobile Recording Wizard: allows you to enable/disable mobile recording for one of
the base station ports.
DECT Configuration Wizard: allows you to easily configure a DECT module. It also turns
on one of the base station ports to allow mobile recording (handset registration).
Note: The DECT Wizards only appear on the Wizards page if there is a DECT module
installed and identified to the system. These wizards are discussed in the DECT Installation
and Maintenance Guide.

Navigating the wizards
These are some helpful hints about how the wizards work, and how to use them.
•
•
•

To open the online help, from the Programming Wizards screen click the Programming
Wizards Help link.
You can move back and forth between screens in the wizards by clicking the Back and Next
buttons.
You can revise your choices and entries on any of the wizard pages until you click the Apply
button. Once you click the Apply button, the system proceeds to apply the selected
configurations. The user is presented with a confirmation box that provides the approximate
timing of the process. To check the status of the configuration, press the Refresh button. When
the process is complete, the title of the page has the word completed as part of the title.

P0609326 1.1

Using the Unified Manager main page buttons

81

Locating optional features from the main page
After you set up the system and it is operating, you can add the keycodes for any optional features
you want to include.
You access the optional applications, including those which require keycodes, through the Install
Clients button.
The program that manages CallPilot is accessed through the Call Pilot button.

Access optional
applications

Access CallPilot
application

For information about how to set up these optional features, refer to the documentation for each
application.
Note: Basic CallPilot functions are standard on the Business Communications Manager and you
define your region and basic settings when you run the Quick Start Wizard. Refer to “What you
need to know before you use the wizard” on page 93. If you are using this call pilot as the voice
mail host to other systems, you may need to set up areas of the Unified Manager, as well. Refer to
“Configuring centralized voice mail” on page 559.

Business Communications Manager 3.6 Programming Operations Guide

82

Using the Unified Manager

Finding documentation from the main page
Use the Documentation button to find the information you require to help you understand and
configure your system to your specifications. The entire Business Communications Manager
documentation suite, plus a number of training panels, are included on your Business
Communications Manager computer, as well as on the CD that accompanied your system.
The Programming Records are on the CD only.

Using BRU from the main page
The BRU (Backup and Restore Utility) button, allows you to ensure the integrity of your system
data by providing a way to back up your system data and configurations in the way that is most
useful for your purposes. Backed up data can be restored to the Business Communications
Manager should a system failure occur, such as a prolonged power outage. The Management User
Guide describes how to use this feature.

Accessing maintenance information from the main page
The Maintenance button accesses a number of maintenance tools that allow you to determine the
current status of the various aspects of your Business Communications Manager system. The
Management User Guide describes how to use these tools.

Using the Unified Manager
Most changes made with Unified Manager become part of current Business Communications
Manager programming when you select an item from the menu options. However, some changes
take effect after you exit the screen. If a programming error occurs, you must reenter the original
programming.
This section describes the various parts of the configuration main screen:
•
•
•
•
•

Business Communications Manager system access
Unified Manager screen display
“Understanding the dynamic menu” on page 84
“Understanding the navigation tree headings” on page 85
“Understanding tabbed pages” on page 87

Business Communications Manager system access
You must control system access by providing one user id, the administrator, with read-write
privileges. Give all other users selected access privileges to control the possibility of concurrent
configuration of the Business Communications Manager system. For information about defining
user profiles and passwords, see “Managing system and user security access levels” on page 105.
P0609326 1.1

Using the Unified Manager

83

Unified Manager screen display
The Unified Manager screen display, shown in the figure below, consists of:
•
•
•

a menu bar, where users access configuration commands
a navigation frame that displays the navigation tree you use to navigate through Business
Communications Manager programming headings
an information frame that displays the windows related to the headings you select in the
navigation frame

Figure 8 Main display of the Unified Manager

Navigation
key
Navigation frame

Buttons Headings
Navigation tree

Menu bar
Tabbed pages

Information frame

The menu bar contains configuration management options. When you select the different headings
in the navigation tree, these options are enabled. If an option appears dimmed, it is not available
for the heading you have selected.
The navigation tree contains headings that allow you to access specific areas of the Business
Communications Manager system. The key symbol ( ) beside each heading indicates that the
heading can be expanded to show sub-headings. To display sub-headings, double-click the item or
just click on the key itself. As you select various headings in the navigation tree, the heading
changes color and Unified Manager displays the appropriate information frame.
Note: If you receive the error message Telephony programming is currently not
available. Please try again later. when you click on one of the headings, this means
that the part of the system that handles MSC is doing a reset. Wait about one-and-a-half minutes
and try again.

Business Communications Manager 3.6 Programming Operations Guide

84

Using the Unified Manager

The information frame can contain configuration windows or dialog boxes indicating the
appropriate action or showing system messages or warnings.

Understanding the dynamic menu
You access some of the Business Communications Manager functions using the top menu bar.
This menu bar is dynamic. Commands become active or inactive depending on the heading you
select from the navigation tree in the left frame. The following table defines the menu bar top-level
items.
Table 2 Menu bar items

Menu item

Description

Group

View the system, resources, services, and management.

Edit

Edit parameters.

Configuration

Access configuration dialog boxes and screens.

Performance

Access performance graphs and tables.

Fault

Access fault management settings.

Report

Generate a report.

Tools

Use Business Communications Manager tools.

Logoff

Log off, reboot or shutdown the Business Communications Manager base
unit.

View

Refresh the information window to reflect configuration changes.

Help

Access online help.

Refer to the figure in “Unified Manager screen display” on page 83.

P0609326 1.1

Using the Unified Manager

85

Understanding the navigation tree headings
The Unified Manager navigation tree contains five main headings that allow you to access specific
areas of the Business Communications Manager system. These headings are described in the
following table.
Table 3 Navigation tree menu functions

Heading

Programming

System

Provides access to Licensing, Identification and Security subheadings. This
includes a form to enter keycodes, and a list of current supported services.
The Security heading provides screens that allow you to determine the level of
security within and entering the system. Refer to “Managing system and user
security access levels” on page 105.
When you select the System heading, you can view system information such as
your system name and a description about which resources and services are
available.
Selecting the System heading also enables the following menu options:
Configuration, Performance, Fault, Logoff, View and Help. These menu
options provide access for you to:
• enable/disable services
• access CPU and memory status
• access to the alarm banner, which displays totals of alarms
• access or refresh a system inventory list
• perform system reboot or shutdown operations
Also refer to the Management User Guide.

Resources

Provides access for configuring data and telephony resources for Business
Communications Manager hardware setup. This information is included in
“Configuring resources — media bay modules” on page 123, “Data and split-line
configuration” on page 151, “Configuring the LAN resources” on page 663,
“Configuring the WAN resources” on page 669, “Configuring the Dial Up
resources” on page 685, and “Configuring the MSC resources” on page 609, as
well as in the DECT Installation and Maintenance Guide.

Business Communications Manager 3.6 Programming Operations Guide

86

Using the Unified Manager

Table 3 Navigation tree menu functions (Continued)

Heading

Programming

Services

Provides access for configuring telephony and data networking services and
various other related services. Telephony information is discussed from Chapter
7, “Telephony Services overview,” on page 183 to Chapter 31, “Configuring the
Dial Up resources,” on page 685 and in the IP Telephony Configuration Guide. /
Doorphone configuration is located in separate documentation. System data
configuration is discussed from Chapter 32, “Configuring DNS,” on page 703 to
Chapter 42, “Configuring IP Firewall Filters,” on page 831.
This section also supports the information found in the CallPilot documentation,
and the documents for CDR Recording, LAN CTE, IVR, Doorphone, Network
administration, universal power supply, UPS) document, and DECT Installation
and Configuration Guide.
The Management User Guide provides information about SNMP, Alarm
Service, and NetIQ.
To manually enable or disable the Telnet service, refer to “Manually activating
Telnet” on page 90.

Management

Provides access to the User Manager, which you use to manage the users who
have access to the Unified Manage (“Managing system and user security
access levels” on page 105), and to the Alarm Manager, which is used to define
why types of alarms get reported by the system. The latter information is
discussed in the Management User Guide.

Diagnostics

Provides access to items that allow you to generate and access statistics on
different system components. Business Communications Manager provides
statistics, metrics and event logs on resources and services to help you carry
out system maintenance activities. For more information about using
diagnostics tools, refer to the Management User Guide.
System metrics information is contained in the programming section to which
they apply. Refer to “Viewing CbC limit metrics” on page 343, “Using Hunt group
metrics” on page 587, and the IP Telephony Guide.
Split DS30 configuration and double density configuration are located under the
Configuration menu of the MSC heading. These system features are discussed
in the section that discusses MSC configuration. Refer to “Changing the DS30
Split” on page 629 and “Configuring Double Density” on page 630.

P0609326 1.1

Using Unified Manager Help

87

Understanding tabbed pages
Some headings display records that have more than one level. Each level is accessed by clicking
the appropriate tab at the top of the screen.
Figure 9 Tabbed page example

Screen tabs

Using Unified Manager Help
As noted in “Understanding the dynamic menu” on page 84, the dynamic menu has a Help
heading. This heading allows you to access help topics relevant to active navigation tree headings
and screens. Each navigation tree heading and tab also has an alternate-click help link.
The help pages open in a new web-based window. Each help page also have navigation tools that
allow you to move back or forward to find other help topics.

Viewing help for navigation tree headings
1

Highlight the heading for which you want to view help.

2

Alternate-click anywhere in the left pane to get the csHelp button.

3

Then click normally on the csHelp button to open the help web page.

Figure 10 Accessing navigation tree heading help

Select heading, then alternate-click
to get csHelp button.

Business Communications Manager 3.6 Programming Operations Guide

88

Logging off

Viewing help for tabs
1

Click on the tab to make it the active screen.

2

Alternate-click anywhere in the right pane to get the csHelp button.
Note: Some tabs may have other headings as well.

3

Then click normally on the csHelp button to open the help web page.

Figure 11 Accessing navigation tree heading help

Click the tab, then
alternate-click to get
csHelp button

Logging off
When you have finished a session on the Unified Manager, you need to log off correctly to protect
the integrity of the information you entered.
1

Choose BCM () at the top of the navigation tree.
The Logoff menu is enabled.

2

Click Logoff, then select Logoff.
A message appears that asks you to confirm your request to log off.

3

Click Yes to continue.

4

A second message appears reminding you to close your browser window after the system has
logged out. Click Yes to continue.
A Logoff progress bar appears. When it the logoff is complete, the browser display will revert
to the Login screen.

5

Click the Windows exit icon (top, right corner).

6

Click the Windows exit icon on the browser window displaying the Business Communications
Manager main menu.
Note: Exit both Unified Manager browser windows, even if you want to re-log on to the
Configuration area. Once you have exited both windows, you can re-establish a connection
with the Business Communications Manager and log on as usual.
Failure to log out of both browser windows could result in a failed attempt to re-enter the
Unified Manager Configuration section.

P0609326 1.1

Using the SSH client to access the text-based interface

89

Using the SSH client to access the text-based interface
Some operations for the Business Communications Manager, such as initializing a new hard disk,
use a text-based interface. In previous versions, the Telnet application was used to access the
Business Communications Manager text menus. BCM version 3.6 software introduces the ability
to securely access the Business Communications Manager through a network connection using
SSH server software. SSH service software is from SSH Communications Security
(www.ssh.com). The SSH client application, called PuTTY, can be downloaded from a link under
the Install Clients button on the Business Communications Manager first page. Refer to Installing
PuTTY. Refer to “Using PuTTY” on page 89 for detailed information about using the client to
access the Unified Manager text-based menus.
Users require an administrator-level password to use either PuTTY or Telnet.

!

Security note: You can still use Telnet for direct connections through a crossover
cable, since network security is not an issue in this case.
If you want to use Telnet over the network, you need to manually start the service.
Refer to “Manually activating Telnet” on page 90.

Installing PuTTY
The PuTTY application resides on your computer. It provides an access interface that allows you
to connect to the text interface used by the Business Communications Manager.
1

On the Unified Manager front page, click the Install Clients button.

2

On the resulting web page, go to the bottom of the left column.

3

Under Administrative Tools, click SSH client.

4

On the SSH Client page, click the button beside Download SSH Client, at the bottom of the
right pane.
The application downloads to your computer.

5

On your computer desktop, double click Putty.exe.

6

Follow the steps in the install Wizard to install the application.

Using PuTTY
1

Click the shortcut PuTTY icon.
The PuTTY Configuration screen appears.

2

Click on the radio box beside SSH.

3

In the Host Name (or IP address) box enter the IP address or the Fully Qualified Domain
Name for the Business Communications Manager you want to connect with.

4

Click Open.

Business Communications Manager 3.6 Programming Operations Guide

90

Manually activating Telnet

5

The first time you enter the application you may receive a security notice. Click OK.
The PuTTY text screen appears.

6

At the login prompt, enter an administrator-level user name.

7

Press .

8

At the next prompt, enter the corresponding password.

9

Press .

10 The Business Communications Manager Main Menu appears.
11 Refer to the specific tasks that require this menu for details about using this it.

Manually activating Telnet
If you choose to continue operating the text-based menus with Telnet, rather than using the PuTTY
client, you can manually activate the service from the Unified Manager.

!

Security note: Using the Telnet interface poses a security risk since the Telnet protocol
is not encrypted.

Note: If you are using a cross-over cable to make a direct connection, Hyperterminal is still
enabled, regardless of the status of Telnet on the system.
1

Click the key beside Services.

2

Click on Telnet.

3

On the Telnet screen, change Status to Enabled.

P0609326 1.1

91

Chapter 3
Configuring system parameters
This section describes how to configure the basic programming information onto your new
Business Communications Manager system using the Quick Start Wizard. This wizard allows you
to choose the network and default telephony information that you want to use as the basic
parameters for your system. This includes choosing a system software and companding law
protocol.
Refer to the Installation and Maintenance Guides for information about installing Business
Communications Manager hardware.
Warning: If you are installing this Business Communications Manager as a replacement
for an existing system, you must ensure that the system has been re-initialized and the
Region is correct.
This is especially important if you have a DECT system that requires the µ-law
companding law protocol. Refer to the DECT Installation and Maintenance Guide for
information about setting up a DECT system that requires the µ-law protocol.
Once the system is re-initialized using the Quick Start Wizard, you can restore system
programming from the latest backup file taken from your old Business Communications
Manager.
This section also describes how to change some of the system settings after the Quick Start Wizard
has been run.
Information in this section includes:
•
•
•
•

“Accessing the Wizards” on page 92
“Wizard Warnings” on page 93
“Changing system identification parameters” on page 98
“Delayed system restart” on page 102
Wizard Warnings
Read the Warnings in this chapter before you attempt to use any of the wizards.

Business Communications Manager 3.6 Programming Operations Guide

92

Accessing the Wizards

Accessing the Wizards
You can access all the Business Communications Manager wizards through the Wizards button
that appears on the first page of the Unified Manager.
If the Quick Start Wizard button does not appear, it means the Wizard has already been run on this
system. You can allow the button to appear again by clicking the Enable Quick Start link.
However, if you run the Wizard again, you will wipe out all system settings and data.
Refer to “Locating Wizards” on page 80 for a description of the function of the other wizards
which are accessed through the icons on the Setup and Management Wizards page.
1

Open up the Unified Manager.
Refer to “Getting started with Unified Manager” on page 77 if you need instructions.

2

Click the Wizards button.

A login dialog box appears.

3

In the Login field, type your login name.
The default login name is ee_admin.
Note: You must have administrator-level privileges to use the wizards.

4

In the Password field, type your password.
The default password is PlsChgMe!.

5

Click on the Login button.
The Wizards page appears with all the Wizards icons.
READ first: “Wizard Warnings”.
Then refer to these sections for details about “What you need to know before you use the
wizard” on page 93, “Using the Quick Start Wizard” on page 96, and “Entering information
into the Quick Start Wizard” on page 97.

P0609326 1.1

Accessing the Wizards

93

Wizard Warnings
Read the following Warnings before you attempt to use any of the Wizards.
Warning: Users
Unified Manager allows multiple users to log on to the Business Communications
Manager system. If more than one user logs on to configure the same or related
subsystems, the most recent modification remains in effect and overwrites changes
previously made.
Maintain one user profile with system administrator privileges. If you have more than one
system administrator, you must plan configuration changes carefully. Refer to “Managing
system and user security access levels” on page 105.
Warning: Wizard timeouts
When the Wizard Instance Timeout message appears, it indicates that the wizard
was inactive for 30 minutes, the wizard has already been applied, or the Business
Communications Manager or the server-side wizard component was restarted.
Warning: Operations during Wizard application
Do not use Windows NT login sessions while you are using the wizards or while there are
wizards being applied.

What you need to know before you use the wizard
Use the following table to enter information that you want to enter into the wizard.
Screen 1, General information
•

What do you want to call your Business Communications Manager?

(System Name)

•

What region do you want to use for the Business Communications
Manager CallPilot system?
Refer to “CallPilot regions” on page 859 for a description of the
available choices. If you do not specify a region, the system defaults
to North America.

(CallPilot Region)

•

What time zone is your system in?

(Time Zone)

Screen 2, Data information
(which fields appear will depend on your current data hardware configuration)
•

LAN settings
IP address

LAN 1:
LAN 2:

Subnet mask

LAN 1:
LAN 2:
Business Communications Manager 3.6 Programming Operations Guide

94

•

•

Accessing the Wizards

Primary Wins Address

LAN 1:
LAN 2:

Secondary Wins Address

LAN 1:
LAN 2:

WAN settings
IP address

WAN 1:
WAN 2:

Subnet mask

WAN 1:
WAN 2:

Port (read-only)

WAN 1: T1
WAN 2: V.35

Link Protocol

WAN 1:
WAN 2:

Default Next Hop Router

(Next Hop on Primary Link)

What is the IP address of the next router or link on the network?
•

DNS

(IP Domain)

What is the domain name of the DNS server?
What are the IP addresses (primary and secondary) for the server?
Note: Use a space to separate the groups of numbers.




Screen 3, Telephony information
•

What is the mobility protocol your system requires?
(Mobility protocol)
Etiquette
For more information, refer to “Mobility services by region” on page CT2+
848.
(Carrier protocol)
E1
T1

•

What is the carrier profile that your system requires?
TIP: most North American systems use a T1 protocol, while most
European-base systems use E1
Refer to “Core software and regions” on page 846.

•

What is the telephony Region where your system is located?
(Region)
Refer to “Core software and regions” on page 846 if you do not know
your region.

•

Software Version (determined by choice of Region)

read-only

•

What system template do you want to use for your system?

(Default template)
PBX
DID

•

How many digits will you be using for your system extensions
(Start DN Length)
(DNs)?
Remember, if your system is part of an MCDN or tandem network,
this must be the same length as in all the other nodes if you are using a
Uniform dialing plan (UDP).

P0609326 1.1

DECT

Accessing the Wizards

•

What extension (DN) do you want to start at for your sets?
Note: the number of digits must agree with the Start DN Length.
Default: 221.

Received # length
This setting determines how much of an incoming public telephone
number the system reads to identify a telephone in the system.
Notes:
• The fields default to the number entered in the Start DN length
field. When you manually change the value for one or both of
these fields, the system does not attempt to update the field.
• If the Template field is set to DID, these fields are read-only
• What is the received number length for calls from the Private
network?
•

What is the received number length for the network?

95

(Start DN)

(Public length)

(Private length)
(Public length (max))

The default is equal to the number of digits entered in the Start DN
length field.
Ignore the following questions if you do not have IP telephones on your system.
•

Are you planning to deploy a large number of IP telephones?
The field beside 3/5 DS30 Split to increase IP telephony capacity
determines how many voice channels the Business Communications
Manager provides.

No =
Yes =

2/6 split (default)
3/5 split

If you need more information to help you decide, click the help link.
You can also refer to Chapter 26, “Configuring the MSC resources,”
on page 609.
•
•

Do you want to be able to immediately start registering Nortel IP
terminals on the system?

(Registration)
On

Do you want to change the default IP telephone access password?

(Password)

Off

This is the password that installers will need to enter before they can
configure an IP telephone in the field.
•

Do you want the system to automatically assign extension numbers
(DNs) to your IP telephones when you install them?

(Auto Assign DNs)
On
Off

Screen 4, CallPilot Initialization (complete this section if you intend to use CallPilot on your system.
•

Do you want to initialize CallPilot on your system?

(Call Pilot System
Initialization)
Yes No

•

Do you want to create a new System Administrator password?

(System Administrator
Password)

(Default: 0000)
•

If you create a new password, retype it in this field.

(System Administrator
Password Confirmation)

Business Communications Manager 3.6 Programming Operations Guide

96

•

Accessing the Wizards

Do you want to specify an Attendant DN length?

Attendant DN

This DN must be the same length as the DN length you specified on
the Telephony page.
•

Which system are you going to use for your primary interface?

(Primary UI Style)
NVM
CallPilot

•

In which language do you want your system prompts to appear?

(Primary Language)

The wizard will enter a choice, based on your selection of the
CallPilot Region on the General Page. You can change that default
choice here.
•

Do you want to initialize Auto-attendant?

•

If you choose to initialize Auto-attendant, enter the line and ring
information.
First line in the range you want to assign to the Auto-attendant.
Last line in the range you want to assign to the Auto-attendant.
Number of rings before Auto-attendant answers.

(Auto-attendant Initialize?)
Yes
No

from line:
to line:
number of rings:

Using the Quick Start Wizard
Use the Quick Start Wizard to set the basic capabilities of your system, such as the name of your
system, the CallPilot profile, basic data setup, and the telephony region and template.
Do not use this wizard until you have read and complied with the warnings printed in
“Wizard Warnings” on page 93.
You can access a Quick Start Wizard from either a serial port connection or a LAN connection.
The appearance will be slightly different, but the information required is the same. If you have not
already connected your computer to the Business Communications Manager base unit, refer to the
Installation and Maintenance Guide for details. To use the Unified Manager wizard, refer to
“Entering information into the Quick Start Wizard” on page 97
To help you fill out the wizard, you can print out or copy the pages in “What you need to know
before you use the wizard” and collect all the information that you need before you run the wizard.
Warning: Running the Quick Start Wizard
Run the Quick Start Wizard only to configure uninitialized systems. When you click the
Apply button, Business Communications Manager erases the telephony programming
and disables the telephony system temporarily. During application of the Wizard, the
Business Communications Manager base unit reboots several times.

!

P0609326 1.1

Security note: Disable the Quick Start Wizard once it has run successfully. This can
be performed from the Programming Wizards page. On this page, click the Disable Quick
Start link. The Quick Start Wizard button icon disappears from the page.

Accessing the Wizards

97

Entering information into the Quick Start Wizard
This section describes how to use the Quick Start Wizard to set up your system with information
that is unique to your system. Refer to “What you need to know before you use the wizard” on
page 93 for a list of the fields contained in this wizard:
1

On the Wizards page, click the Quick Start icon.

The General page for the Quick Start wizard appears.
2

Enter your system information on the General page, Network page, Telephony page and
CallPilot page.
Refer to the information you entered in the table under “What you need to know before you
use the wizard” on page 93.
Refer to “Navigating the wizards” on page 80 if you do not understand how to move from
page to page.

3

When you reach the Summary page, review all the information you entered.
If required, go back and make changes, then return to the Summary page.

4

On the Summary page, click the Apply button.
A warning dialog box appears, indicating the system changes that will occur if you continue.

Figure 12 Quick Start Wizard application warnings

5

Press OK to continue, or Cancel to exit the Wizard.
If you press OK, a login dialog appears.

6

Enter an administration-level user name and password in the login box.

7

Click OK.
The wizard starts the initialization process and displays a progress screen. This screen does not
automatically update. Click the refresh this page link after 20 minutes to check that the Status
line indicates that the change is Complete.
Business Communications Manager 3.6 Programming Operations Guide

98

Changing system identification parameters

8

Click the close this window link to exit the wizard.

Changing system identification parameters
There are some identification parameters you may choose to change after the Quick Start Wizard
has set up your system.
Warning: Running the Quick Start Wizard a second time will delete any changes you
entered to the default telephony settings, including any telephony data.
The following sections provide information about changing your system identification parameters
through the Unified Manager.
•
•
•
•

“Identifying your system and software version” on page 98
“Changing the Business Communications Manager time and date” on page 99
“Changing the system domain” on page 100
“Changing the CallPilot region” on page 101

Identifying your system and software version
The System heading has a tab that allows you to find or change the name assigned to your system
and to view the current version of BCM software that is running on your system.
This section provides information about:
•
•

“Changing the system name” on page 98
“Viewing the system software version” on page 99

Changing the system name
The system name identifies the Business Communications Manager system on the network.
To change the system name:
1

On the navigation tree, click on System.
The Item screen appears.

2

Click the System Name box.

3

Enter the new system name.

4

Press the Tab key to save your change.

After you change the System Name, restart the Business Communications Manager system. If you
change the System Name and do not restart the Business Communications Manager system,
Scheduled tasks will not run.

P0609326 1.1

Changing system identification parameters

99

Note: The System Name is the NetBIOS name of Business Communications Manager.

Viewing the system software version
The system software version determines which features are available to your system, and,
sometimes, how they work. Each version has a number of new features that only work with that
version and newer versions. If you are having a problem running a feature, this may be one area
where your service technician will ask you to look.
1

Click on the System heading.
The Item screen appears.
The Description box displays a read-only statement about the version of BCM software that
the system is running.

Changing the Business Communications Manager time and date
To change the time, date and time zone for the Business Communications Manager system:
1

Click the key beside System.

2

Click the Identification heading.
The Identification screen appears.

3

Click the Date box and enter the current date.

4

Click the Time box and enter the current time at the site where the Business Communications
Manager system is located.

5

Click the Time Zone box and then click the time zone at the site where the Business
Communications Manager system is located.

6

Press the Tab key to save your changes.

Business Communications Manager 3.6 Programming Operations Guide

100

Changing system identification parameters

Changing the system domain
The system domain is the domain in which the Business Communications Manager system
resides. If you do not know the domain for the Business Communications Manager system, contact
your network administrator.
To change the system domain, add the Business Communications Manager system to a new
domain. This section describes:
• Assigning a workgroup
• Assigning a domain
• Assigning a Windows 2000 domain

Assigning a workgroup
1

Click the key beside System.

2

Click the Identification heading.
The Identification screen appears.

3

Click the Change Domain Membership tab.
The Change Domain Membership screen appears.

4

Click the Add To box and click Workgroup.

5

Click the New Workgroup box and enter the name of the workgroup to which you want to
add the Business Communications Manager system.

6

Press the Tab key to save your change.

7

Restart the Business Communications Manager system.

Assigning a domain
1

Click the key beside System.

2

Click the Identification heading.
The Identification screen appears.

3

Click the Change Domain Membership tab.
The Change Domain Membership screen appears.

4

Click the Add To box and click Domain.

5

Click the New System Domain box and enter the name of the domain to which you want to
add the Business Communications Manager system.

6

Press the Tab key to save your change.

7

Restart the Business Communications Manager system.

P0609326 1.1

Changing system identification parameters

101

Assigning a Windows 2000 domain
1

Click the key beside System.

2

Click the Identification heading.
The Identification screen appears.

3

Click the Change Domain Membership tab.
The Change Domain Membership screen appears.

4

Click the Add To box and click Win2000Domain.

5

Click the Domain User ID box and enter the User ID that the system uses to access this
domain.

6

Click the Password box and enter the password that the system uses to access this domain.

7

Click the New Win 2000 Domain box and enter the name of the domain to which you want to
add the Business Communications Manager system.

8

Press the Tab key to save your change.

9

Restart the Business Communications Manager system.

Changing the CallPilot region
The CallPilot region defines some call-management-related system defaults. For information
about the CallPilot regions, refer to “BRI and PRI line types” on page 857.
To change the CallPilot region:
1

Click the key beside System.

2

Click the Identification heading.
The Identification screen appears.

3

Click the CallPilot Region box.

4

Click the region in which the Business Communications Manager system resides.

5

Press the Tab key to save your change.

Business Communications Manager 3.6 Programming Operations Guide

102

Delayed system restart

Delayed system restart
There may be times when you perform a procedure that requires a system restart, but you want to
delay the restart for a low-activity time.
For instance, some keycodes require a cold start to become effective. You can add the keycode at
any time, then use this procedure to delay the system restart until early morning, when there is no
traffic on your system.
1

On the first page of the Unified Manager, click the Maintenance button.

2

You will be prompted to enter your system ID and password.
These are the same ID and password you use to sign into the Unified Manager.

3

On the left menu, under Maintenance, click on Maintenance Tools.
The Maintenance Tools screen appears in the right frame.

Figure 13 Maintenance Tools screen

4

Beside System Interaction, click Schedule a Restart.
The schedule screens appear in the right frame.

P0609326 1.1

Delayed system restart

103

Figure 14 Job scheduling window

5

Under the first bullet, choose how often you want to schedule a restart.
Example: If you are activating a keycode, click the Today Only radio button.

6

Under the next bullet, enter the time you want the restart to occur.
Example: for a 3 a.m. restart, type in 03:00.

7

Under the next bullet, type in a short note about why you want the restart to occur.

8

Click the Schedule Now button to activate the schedule.

9

Exit the Maintenance pages.

Business Communications Manager 3.6 Programming Operations Guide

104

Delayed system restart

P0609326 1.1

105

Chapter 4
Managing system and user security access levels
This section provides information about how you can set up and maintain the access security to
your system by users and client applications.

!

Security note: This symbol will be used throughout this section to indicate areas of
possible security concern, primarily in regard to default settings that could pose a security
risk if they are not changed.

To define security parameters for the system and for users, you need to consider what level of
security you need to achieve to meet your network security standard. Note that the default security
settings are not set to their maximum secure settings and can be changed to suit your specific
requirements. If you change the default settings, ensure that you understand the interoperability
implications between your system and client applications, the computer you use to access the
system, and network impacts. For instance, some levels of security are not compatible with clients
running Windows© 95©, 98©, or ME©.

!

!

Security note: Minimum configuration should include changing all default system
passwords.

Unified Manager security considerations include:

•

How long you want the Unified Manager to remain open if there is no input from the user.
Refer to “Setting the interface timeout” on page 106.

•

If you want to use secure web access to Unified Manager through SSL (Secure Sockets Layer).
Note that SSL encryption does not secure the Configuration Menu. To secure communication
with the Configuration Menu, a VPN client connection is required. Refer to “Setting system
security compatibility levels” on page 107 and “Virtual Private Networks (VPN)” on page
765.

•

How much access to the Unified Manager interface users are allowed. Access is based on user
privileges defined through user group membership.There are two default administrator
accounts, ee_admin and supervisor, which both also have default dial-in access privileges.
Refer to “Managing access passwords” on page 109. This section also contains information
about determining password and lockout policies.

Business Communications Manager 3.6 Programming Operations Guide

106

Setting the interface timeout

The figure below displays the Unified Manager headings under which security and user
information is configured. The SSH client access application is installed on your desktop. The
Install Clients button on the first Unified Manager page provides a download path.
Figure 15 Security and user access headings
System
Licensing
Identification
Security

System
Resources
Services
Management
User Manager

Setting the interface timeout
Set the amount of time the Unified Manager stays open if there is no input activity. When the
timeout period completes, the program automatically returns to the log-in window. This prevents
unauthorized users from accessing the system.

!

Security note: This is especially important if a password-protected screen saver is
not installed on the client PC.

1

On the navigation tree, click on the Management heading.
A screen with two tabs appears in the right frame.

2

Click on Unified Manager Management tab.

Figure 16 Unified Manager Timeout setting

3

In the Unified Manager Timeout field, enter the period of inactivity the program will allow
before it closes the application and returns to the log-in window.
Note: If you do not want the Unified Manager to time out, enter 0 in this field.

P0609326 1.1

Setting system security compatibility levels

107

Setting system security compatibility levels
Use the Security screen to set authentication, signing, encryption, and other security-related
settings. Some of these settings depend on the Windows operating system used by client
workstations.

!

Security note: The default settings define a mid-level of security which
accommodates Windows 95/98/Me operating systems. If you would like to set a higher
level of security, ensure that all the computers that will be used for client access have
upgraded to at least Windows NT4, 2000 or XP.

1

Click the keys beside BCM and System.

2

Click on Security.
The Security screen appears in the right frame.

Figure 17 System security level settings

3

The following table describes the fields. Set the fields to the values that best fit your system
requirements and that accommodate compatibility issues with interconnecting users or
services.

Table 4 Security settings
Attribute

Value

Description

Authentication LM&NTLM response Compatibility
refuse NTLMv2 session
security
LM & NTLM response
NTLM response only
NTLMv2 response only
NTLMv2 response only refuse LM

Default: LM & NTLM response
This setting determines the type of authentication protocol required by
your system during interactions with client applications.
The default, LM & NTLM response, maintains compatibility with all
Windows OS versions.
Any of the other settings enforce a more secure authentication protocol,
and will prevent access from computers running Windows 95/98/Me,
unless you install the directory services client on the client computer.

Business Communications Manager 3.6 Programming Operations Guide

108

Setting system security compatibility levels

Table 4 Security settings (Continued)
Attribute

Value

Description

Clear Page
File on
Shutdown

Disabled
Enabled

Default: Disabled
If Enabled, this setting prompts the system to clear the virtual memory
swap file on shutdown. When enabled, this option extends system
shutdown by about two minutes.

SMB Client
Signing

Allow
Disabled
Require

Default: Allow
Determine what level of signing you require from SMB clients.
Disabled: None required.
Allow: Tries to perform the digital signature whenever a compatible
client platform is detected. This setting also supports clients running
with Windows 95/98/Me.
Require: Always secures the connection with a digital signature.
However, this setting prevents access from clients running with
Windows 95/98/Me.
Applicable applications: BRU and Archlog

SMB Server
Signing

Allow
Disabled
Require

Default: Allow
Determine what level of signing you require from SMB client servers.
Disabled: None required.
Allow: Tries to perform the digital signature whenever a compatible
client platform is detected. This setting also supports clients running
with Windows 95/98/Me.
Require: Always secures the connection with a digital signature.
However, this setting prevents access from clients running with
Windows 95/98/Me unless you install the directory services client on
the client computer.
Applicable applications: BCM monitor.

Domain
Secure
Channel

Disabled
Allow Sign
Allow Sign & Encrypt
Require Sign or Encrypt

Default: Allow Sign & Encrypt
Define what level of channel security you require.
Disabled: No special security.
Allow Sign or Allow Sign & Encrypt: Tries to perform the digital signature
and/or encryption whenever a compatible client platform is detected.
This level needs to be aligned with your Domain controller setting.
Require Sign & Encrypt: Always secures the connection with a digital
signature and/or encryption. Clients running with
Windows 95/98/Me are not supported.
Applicable applications: CDR and TAPI.

Force Secure
Web Access

Enabled
Disabled

Default: Enabled
If enabled, SSL is used for all web access to the Business
Communications Manager. In that case, the https:// must
be used. As well, old bookmarks will be rerouted to that interface.
If disabled, the http URL references will not automatically redirect to the
SSL-based https interface. Both the unencrypted http://
:6800 and the encrypted https:// interfaces
can be used.

Minimum web Low
encryption
Medium
High

4

Set the encryption strength of the web interface.
Low: all low strength ciphers
Medium: all ciphers with 128 bit encryption
High: all ciphers with 3DES encryption.

Click outside the window to set the changes.

P0609326 1.1

Managing access passwords

109

Managing access passwords
You can grant or restrict specific access within the Unified Manager by assigning new users into
user groups using the User Management screens.

!

Core system configuration, such as resources and network management should be
restricted to an administrator-level account.
Use the group profiles to define other levels of users with access to the headings that
are specific to their task.
This also helps to prevent overlap programming if more than one person is using the
interface at the same time.
Dial-in access: Restrict this user group to users who require this interface. If modem
access is not required, the modem interface can be disabled to provide further security.
Refer to “Enabling and disabling the V.90 modem interface” on page 686.

This section includes information about the viewing and configuring the user profiles and groups:
•
•
•
•
•
•
•

“Viewing the User Manager tabs” on page 110
“Adding or modifying a user profile” on page 111
“Setting up callback for a user” on page 115
“Adding or modifying a group profile” on page 116
“Adding a Domain User Group profile” on page 119
“Setting password lockout policy” on page 120
“Setting password policy” on page 122

!

Callback security
If a user is connecting to the system using a V.90 modem, you can enhance your access
security by assigning that person a specific user account that prompts the system to
acknowledge the user, then hang up and dial back the user at a designated telephone
number, before allowing the person to have access to the system.

The information in this section is found under the Management, User Manager heading.

Business Communications Manager 3.6 Programming Operations Guide

110

Managing access passwords

Viewing the User Manager tabs
The various tabs under User Manager allow you to define user and group profiles and the
parameters that define security levels for user accounts. This heading is located under the
Management heading on the navigation tree.
•

The User Profile tab appears showing the current user profile information.

Business Communications Manager comes with these default administrator user profiles:
— ee_admin (cannot be deleted): Default password: PlsChgMe!. Access privilege:
Read-Write, dial-up access
— supervisor: Default password: PlsChgMe!. Access privilege: Read-Write, dial-up
access

!

Security note: Change the default passwords on the ee_admin and supervisor
account after you initialize your system. The ee_admin account cannot be deleted, but
the group membership can be modified for both accounts.
Remote support: In order for the Nortel Networks support organization to assist
you, dial-in access has been granted to both default administrator accounts. If dial-in
access is removed, then remote access by support organizations may be impacted. It is
recommended that the administrator accounts and dial-in access rights be restricted to
select personnel. Callback capability increases the dial-in security.

•

ISDN note: When you enter an ISDN dial up user interface, the user name shows up on
this list. If you plan to use the secure callback properties for an ISDN user, you need to
specify a static IP address for that interface. Refer to “Configuring an ISDN interface” on
page 691.

•

The User Group List tab shows all the user groups defined in your system.
The system comes with a set of default User Groups that have various access privileges.

P0609326 1.1

Managing access passwords

111

•

The Domain User Group Profile tab lists the domains for all the user group profiles.

•

The Lockout Policy tab provides settings to determine the parameters for locking users
out of the Unified Manager if the lockout policy is enabled.

•

The Password Policy tab allows you to define the complexity policies you want to use for
your system passwords.

Adding or modifying a user profile
To add or modify the profile for a single user, follow these steps:
1

Click the key beside Management.

2

Click on User Manager.
The User Profile screen appears showing the current user profile information.

3

Access the User Profile dialog:
• If you are adding a new user: from the Configuration menu, select Add User.
• If you are editing an existing user: select the user name on the list, then from the
Configuration menu, select Modify User.

The User Profile dialog box appears.

Business Communications Manager 3.6 Programming Operations Guide

112

Managing access passwords

Figure 18 User Profile screen to add or modify a user profile

4

Use the following table to determine what information you need to add or change:

Table 5 User Profile settings
Attribute

Value

Description

User Name



Allows you to enter the user name. The User Name is case-sensitive and
cannot exceed 20 characters in length.
Edit note: You cannot modify a user name. You must delete the complete
User Profile row from the User Profile window and add a profile with the new
name.
ISDN note: When you enter an ISDN dial up user interface, the user name
shows up on this list. If you plan to use the secure callback properties for an
ISDN user, you need to specify a static IP address for that interface. Refer to
“Configuring an ISDN interface” on page 691.

P0609326 1.1

Managing access passwords

113

Table 5 User Profile settings (Continued)
Attribute

Value

Description

Password



Allows you to assign a password for the user. The password is case-sensitive
and can be a maximum of 14 characters long.
Note:
• Password length is determined by the Minimum Password Length setting
in the Password policy table.
• Passwords must contain elements from three of the four following
character sets. This requirement can change, if you change the default
password policy complexity setting (“Setting password policy” on page
122):
— upper case alphabet
— lower case alphabet
— westernized Arabic numerals
— nonalphanumeric characters ($, !, %, ^)
• A user who fails to enter the correct password can be locked out of the
system after a defined number of retries (account lockout threshold). For
information about setting the lockout threshold, refer to “Setting password
lockout policy” on page 120.

Confirmed
Password

Requires you to enter the same password again to validate the new or
modified password.

Member of

AdminUserGroup
CDRUserGroup
DATAUserGroup
DialUpUserGroup
ReadOnlyUserGroup
VoiceUserGroup

Allows you to select the level of access associated with the user name.
The following levels of access are default settings:
AdminUserGroup: Can see and change any menu items (default).
CDRUser Group: Can see everything but cannot make changes. This user
is restricted to accessing the CDRs.
DATAUserGroup: Can only configure pre-defined data fields (default).
DialUpUserGroup: All menus are invisible, and no menus are configurable
(default). This group allows the user to access the system through a dial-up
connection.
ReadOnlyUserGroup: Can see everything but cannot make changes
(default).
VoiceUserGroup: Can only configure pre-defined voice fields (default).
Note: You cannot modify default user groups.
Dial-up note: If any of the users will be using a dial-up connection to access
the system, they must be assigned to the DialUpUserGroup.
For information about adding new groups, refer to “Adding or modifying a
group profile” on page 116.

Callback

Disabled/Enabled

If this user is going to use a dial-up connection to connect to the system and
the user requires callback, ensure that Callback is enabled. If the user is
configured as an ISDN interface, ensure that a static IP address has been
specified for the interface. Refer to “Configuring an ISDN interface” on page
691.
If this user is not using a dial-up connection or does not require callback, set
Callback to Disabled.
Note: The system supports one dial-up connection at a time.

Callback
Number

This is the number the system uses to call back to the user’s dial-up location.
Ensure that the appropriate routing codes are added to the dial string.

Business Communications Manager 3.6 Programming Operations Guide

114

Managing access passwords

Table 5 User Profile settings (Continued)
Attribute

Value

Description

Status

Unlocked
Unlock

This field indicates the current state of the user’s password. If the password
becomes locked and the user does not want to wait the lock-out time, the
Administrator can choose Unlock on the user’s password record to release
the password.

5

Click the SAVE button to save your settings.
The new user profile information is added to the list on the User Profile window.

!

Security note: An integral part of your system security is password management. This
includes changing default passwords after the system is installed.
Also, to further increase access security, minimize the number of user accounts,
especially the administrator accounts, and change them frequently.

Deleting a user profile
To delete a user profile:
1

Select Management, User Manager.
The User Profile window appears showing a list of the current user profiles.

2

Click the line for the user you want to delete.

3

From the Configuration menu, select Delete User.
A confirmation dialog will ask you to confirm that you want to delete the user record.

Figure 19 User Manager delete confirmation dialog

4

Click the YES button to delete the user profile.

!

P0609326 1.1

Security note: You cannot delete the ee_admin user.

Managing access passwords

115

Setting up callback for a user
If the user will be accessing the system through a dial-up connection, you need to add that group to
the user account. As well, in this case, callback will be enabled to ensure that the system security is
maintained.
1

Select Management, User Manager.
The User Profile screen appears showing the current user profile information.

2

Access the User Profile screen:
• If you are adding a new user: from the Configuration menu, select Add User.
• If you are editing an existing user: select the user name on the list, then from the
Configuration menu, select Modify User.

3

Enter a User Name, if one does not already exist.

4

Enter and confirm a password, if one has not already been specified.

5

Click to highlight the DialUpUserGroup name. Then, hold the  key down and click on
any other groups to which you want to assign the user.

6

Select Enabled from the Callback menu.

7

Enter the number the system will dial to contact the client modem. Ensure you include the
correct routing codes.

8

Click OK at the bottom of the screen to save the settings.

Figure 20 User profile for dial-up user

Business Communications Manager 3.6 Programming Operations Guide

116

Managing access passwords

Adding or modifying a group profile
The access privileges inherent in the various predefined group profiles control user access within
the Unified Manager interface. The administration group maps to administrator privileges on the
Business Communications Manager host system. The other group profiles map to
non-administration groups.
To add or modify the profile for a group, follow these steps:
1

Select Management, User Manager.
The User Profile screen appears showing the current user profile information.

2

Click the User Group List tab, to view the existing groups.

Figure 21 Default user groups

Total access
CDR requests only
Data setup access only
Dial-up access (read-only)
Read only
Telephony configurations access

3

Add or change a user group:
•
•

P0609326 1.1

If you are adding a new group: from the Configuration menu, select Add User Group.
If you are editing an existing group: select the user group name on the list, then from the
Configuration menu, select Modify User Group.

Managing access passwords

117

The User Group List dialog box appears.
Figure 22 User Group List add/modify screen

4

Use the following table to determine the user profile information that needs to be added or
changed:

Table 6 User Group Profile settings
Attribute

Description

UserGroupName

This is the name of the user group. If you are modifying an existing record, you will not be able to
change this field.

Invisible menus

This box allows you to choose which menus you want to keep hidden from the user group. The
Configurable Menus box shows these fields covered by a grey box.

Configurable
menus

For the headings not covered by grey boxes, select the ones for which you want the users to be
able to change settings. All headings that are left white will appear on the menu, but will be
read-only for this group.

5

Click the SAVE button to save your settings.
The new user group information is added to the list on the User Group List window.

Business Communications Manager 3.6 Programming Operations Guide

118

Managing access passwords

Deleting a Group profile
If you want to delete a group profile, follow these steps:
1

Select Management, User Manager.
The User Profile screen appears showing the current user profile information.

2

Click the User Group List tab, to view the existing groups.

3

From the Configuration menu, select Delete User Group.
A confirmation dialog will ask you to confirm that you want to delete the record.

Figure 23 User Manager delete confirmation dialog

4

Click the YES button to delete the user group profile.

P0609326 1.1

Managing access passwords

119

Adding a Domain User Group profile
The Domain User Group Profile screen displays a table of members of the Windows NT CDR
User group. This screen is used to add external domain users into a CDR User group. Members of
CDR user group have the sole ability to download CDR files from this Business Communications
Manager system. For details about Call Detail Report processes, refer to the CDR documentation.
You can only add valid users currently assigned to CDR user groups. Refer to “Adding or
modifying a user profile” on page 111. When you add local users, the user name is automatically
added to this list. If you are entering an external user, they must be members of a domain that
recognizes this Business Communications Manager, and you add their user name.
1

Select Management, User Manager.
The User Profile screen appears showing the current user profile information.

2

Click the Domain User Group Profile tab, to view the existing groups.

3

From the Configuration menu, select Add Domain User.

The Domain User Group Profile dialog box appears.
Figure 24 Domain User Group Profile add/modify screen

4

Use the following table to add the new Domain user Group profile name:

Table 7 Domain User Group Profile settings
Attribute

Description

Domain\User Name

Enter the user name.

Group

CDR (only choice)

Business Communications Manager 3.6 Programming Operations Guide

120

Managing access passwords

5

Click the SAVE button to save your settings.
The new user group information is added to the list on the Domain User Group Profile screen.

Deleting a Domain User Group profile
If you want to delete a Domain user Group, follow these steps:
1

Select Management, User Manager.
The User Profile screen appears showing the current user profile information.

2

Click the Domain User Group Profile tab, to view the existing groups.

3

From the Configuration menu, select Delete Domain User.
A confirmation dialog will ask you to confirm that you want to delete the record.

4

Click the YES button to delete the Domain User Group profile.

Setting password lockout policy
If you have Lockout Policy enabled, you can choose the parameters that will determine when a
user will be locked out of the system if an incorrect password is entered repeatedly.

!

Security note: Lockout policy is enabled as the default setting. This policy is
particularly important to stop unauthorized logon attempts to your Business
Communications Manager system.
You can further tighten the access security to the system by setting the account lockout
threshold to a recommended value of 5.

1

Select Management, User Manager.
The User Profile screen appears showing the current user profile information.

2

Click the Lockout Policy tab.
The default is to have Lockout Policy enabled.

Figure 25 Lockout Policy screen

P0609326 1.1

Managing access passwords

3

121

Use the information provided in the following table to determine the lockout policy for your
system. The settings are effective as soon as they are entered.

Table 8 Lockout policy settings
Attribute

Value

Description

Lockout Policy

Enabled
Disabled

The Enabled setting allows you to set the following three
parameters.
If you choose Disabled, no configurable parameters display.

Failed Logon Attempts 
Before Lockout

Default: 50
Enter the number of times the user can attempt to enter a
password before the user is locked out.

Reset Failed Logon
Attempts Count after
(min)

Default: 30
The amount of time before the lockout counter is reset.
Note: This does not necessarily mean the user was locked out.



Lockout Duration (min) 

Default: 30
The amount of time that passes after the user is locked out and
before they are allowed to try to log in again, and the Reset count
is set back to zero.

Business Communications Manager 3.6 Programming Operations Guide

122

Managing access passwords

Setting password policy
You can define the system parameters for the passwords that you assign to users by determining
the length, age and history that the passwords must meet.
1

Select Management, User Manager.
The User Profile screen appears showing the current user profile information.

2

Click the Password Policy tab.

Figure 26 Password Policy tab

3

Use the information provided in the following table to determine the lockout policy for your
system.

Table 9 Password policy settings
Attribute

Value

Description

Minimum Password Length

1 to 8

Default: 8
Determines the minimum number of characters that must be
entered for a new password. Passwords can be a maximum
of 14 characters long.

Password Complexity

0
2
3

Default: 3
Define the level of complexity for the system user
passwords.
0 (zero): none of the Password policies are required
2: at least two different types of characters are required
3: at least three different types of characters are required.

At highest complexity, passwords must contain elements from three of the four
following character sets:
• upper case alphabet (English)
• lower case alphabet (English
• westernized Arabic numerals
• non-alphanumeric characters ($, !, %, ^)
Network note: If you are using Network Configuration Manager, password policies will be applied, regardless
of the Unified Manager settings.

P0609326 1.1

123

Chapter 5
Configuring resources — media bay modules
This chapter describes the Unified Manager headings that define and control the settings for the
media bay modules installed on your system.
Task:
Check settings for the media bay modules installed in the system.
Trunk modules:
• Confirm that the DIP switch setting matches the intended DS30 bus placement.
• Verify module type and programmed bus type settings under intended DS30 bus are correct for
the type of module installed
• Configure the module parameters of individual modules installed on each DS30 bus
Station modules:
• Confirm that the DIP switch setting matches the intended DS30 bus placement.
• Verify module type and programmed bus type settings under intended Bus # are correct for the
type of module installed
Note: Data and split-telephony/data module configuration are described in the section “Data and
split-line configuration” on page 151.
This section contains information about:
•
•
•
•
•
•

“Explaining the Media Bay Modules headings” on page 124
“Defining trunk module types and settings” on page 130
“Viewing station module information” on page 143
“Internally-driven channels” on page 146
“Working with the modules” on page 146
“Configuring DECT resources” on page 149

Media bay modules provide the Business Communications Manager with physical interfaces to
trunk (CO) lines and your system telephones, which are defined by directory number (DNs)
records. When media bay modules are first installed in your system you need to configure them
using the procedures described in this section. Media bay module DIP switch settings and
installation procedures are described in the BCM1000 Installation and Maintenance Guide and the
BCM200/400 Installation and Maintenance Guide.
The Installation and Maintenance Guide also describes the concept of the 2/6 and 3/5 split, which
determines how many channels are available for media bay modules. When to choose to change
the DS30 split is discussed in the MSC section of this guide, refer to Chapter 26, “Configuring the
MSC resources,” on page 609.
The Installation and Maintenance Guide also describes the concept of partial double density
(PDD) and full double density (FDD). If your system is set to PDD (the default), and you have
installed a media bay module that supports double density, the system can support 32 lines on
Business Communications Manager 3.6 Programming Operations Guide

124

Explaining the Media Bay Modules headings

whatever buses from 02 to 05 have the module installed. If your system was changed to FDD, the
system supports double density on all six buses. Refer to Chapter 26, “Configuring the MSC
resources,” on page 609.

Explaining the Media Bay Modules headings
The Resources, Media Bay Modules heading allows you to view and change settings for each
media bay module installed in Business Communications Manager.
When you choose a region during your system startup, the Business Communications Manager
installs a default set of media bay module settings under Resources, Media Bay Modules.
However, these may not be the settings that you want for the modules you install. Therefore, when
you install a module, you must go to the appropriate Resources, Media Bay Modules, Bus ##
record and verify the settings for the module you installed.
This section includes information about:
•
•
•
•

“Media bay module Bus numbers” on page 125
“Identifying the module” on page 125
“Module types and capacities” on page 128
“Ports on Bus” on page 130

The following figure illustrates the headings found under Resources, Media Bay Modules
heading on the navigation tree. The exact items displayed below the Bus XX headings depends on
the type of module configured for that DS30 number.
Figure 27 Resources, Media Bay Modules menus
Resources
LAN
WAN
Media Services Card

Media Bay Modules
Bus 01
Bus 02
Ports on Bus
Port 0201 to Port 0216
Channels
B1
Addons
B2
Addons
Bus 03
Modules on Bus
Module 1
Provision Loops
Loop 301 to Loop 304
Lines on Loop
Module 2
Module 3
Ports on Bus

P0609326 1.1

Media Bay Modules (continued)
Bus 04
Modules on Bus
Module 1
Call-by-call service selection
Foreign Exchange (FX)
Inwats (800)
T1 Parameters
Provision lines
Line 211 to Line 233
Module 2
Module 3
Ports on Bus
Port 0201
Channels
B1
Addons
Addon 01
Addon 02
Bus 05
Bus 06
Bus 07
Bus 08
Dial Up
DECT

Explaining the Media Bay Modules headings

125

Tips: Some modules are region-based. If your system does not have the correct region
installed during setup, the modules will not work. Refer to “Media bay module availability
by region” on page 849.
Note: Dimmed fields are read-only and cannot be changed.
Note: If you receive the error message Telephony programming is currently not
available. Please try again later. when you click on one of the headings, this means
that the part of the system that handles MSC is doing a reset. Wait about 1-1/2 minutes and try
again.

Media bay module Bus numbers
Under the headings for DS30 02 to 07 (or 02 to 06 if your system has a 3/5 DS30 split):
•
•

•

Station or analog station modules (“Viewing station module information” on page 143) display
the Ports on Bus heading.
Trunk modules (“Defining trunk module types and settings” on page 130) display from one to
four Module <#> headings. These modules correspond to the offset configured on the module.
A Ports on Bus heading also appears for some types of modules (DTM set to PRI, and the
BRI modules).
If you have a WAN board installed in the base unit, DS30 08 does not appear. Bus 08 and Bus
01 are used for internal media channels. (“Internally-driven channels” on page 146). If you
system is set to a 3/5 split, DS30 07 is also used for media channels.

Identifying the module
Use these steps to define a Programmed Bus Type. This setting notifies the Unified Manager about
what type of module is installed on the DS30 bus.
1

Click on the keys beside Resources, and Media Bay Modules.

2

Click a Bus (Bus 02 to 07).
Tips: Bus number is determined by the DS30 number set on the DIP switches of the module
before it was installed.
The Bus screen appears.

3

Ensure the entry in the Programmed Bus Type field agrees with the Actual Bus Type of
module that is installed for the DS30 bus, as shown in the following figure. Refer also to
“Module types and capacities” on page 128.

Business Communications Manager 3.6 Programming Operations Guide

126

Explaining the Media Bay Modules headings

Figure 28 Confirming the Programmed Bus Type

These fields must agree.

Programming tips: If the Actual Bus Type reads None, choose the correct setting in the
Programmed Bus Type field. After the system initializes to the module, the Actual Bus Type
should change to the correct module type. You may also have to disable, then re-enable the
module to force the system to re-initialize (under the Configuration menu). Refer to “Viewing
Media Bay Module status” on page 147 for details about enabling and disabling modules.
Some modules take a few minutes to reinitialize.
If these actions do not cause the fields to display correctly, you may have a damaged module
or backplane. Try installing the module in a different media bay and retry the configuration.
Refer to the Installation and Maintenance Guide for your hardware for information about
removing and installing media bay modules.
4

The other headings on the Bus screen describe the current status of the modules, as described
in the following table.

Table 10 Bus XX record settings
Heading

Value

Description

Number of sets



This setting indicates the number of sets that are currently
attached to the module.

Number of busy sets



This setting indicates the number of sets that are currently
using the module.

State

Enabled
Disabled

This setting indicates the state of the module.
Use the Configuration menu item to change this setting.

Station module

P0609326 1.1

Explaining the Media Bay Modules headings

127

Table 10 Bus XX record settings (Continued)
Heading

Value

Description

Trunk module, Analog Station Module or Data Module
Number of busy ports



This setting indicates how many ports on the module are
currently being used.

State

Enabled
Disabled

This setting indicates the current state of the module.
Use the Configuration menu item to change this setting.

5

Your next steps depend on which type of module you are configuring:
• If you are configuring a station or analog station module, ensure that the bus type is correct
and the Programmed Bus Type field displays the correct module type. The State field
displays Enabled, indicating that the module is active and ready to have telephones
connected. Refer to “Module types and capacities” on page 128.
• If you are configuring trunk modules, you must now ensure each module associated with the
DS30 bus is set up. This process is described in the next section, “Defining trunk module
types and settings” on page 130.

Business Communications Manager 3.6 Programming Operations Guide

128

Explaining the Media Bay Modules headings

Module types and capacities
Refer to the following table for a description of the Bus types settings.
Table 11 Programmed Bus Types

Programmed
Bus Type

Hardware unit

Station module •

Capacity

Digital Station Media Bay Single density
Module
• DSM16/16+ = 1 per bus/16
(DSM 16/16+ or DSM 32/
digital sets per module
32+)
• DSM 32/32+ = 2 buses/
32 digital sets per module

Available line types (some
line types are
region-dependent)
N/A

Double density
•
•
•

4X16 Media Bay Module
(4X16)
(counts as one DSM 16)

•

Norstar station module
•
(SM) connected to a FEM

Analog station •
module

•

DSM16+ = 2 per bus/
16 digital sets per module
DSM 32+ = 1 per bus/
32 digital sets per module
4X16 = 1 offset (trunk) and
additional bus/
16 digital sets
SM = 1 bus/16 digital sets

Analog Station Media Bay Single density
Module (ASM 8)
• ASM8 = 2 per bus/8 analog
sets for each module

N/A

Double density
•
•

(Global) Analog Station
Media Bay Module
(ASM8+)

ASM8 = 4 per bus/16 analog
sets for each module

Single density
•

2 per bus/8 analog sets for
each module

Double density

Trunk module

•

4 per bus/8 analog sets for
each module

•

Norstar analog station
•
module (ASM) connected
to a FEM

FEM = 1 per bus/16 digital
sets

N/A

•

Digital Trunk Media Bay
Module (DTM)

•

DTM = 1 per bus/16 lines
(max. three DTMs on a
system)

•

DTMs can be set to module
types: Loop, E&M, DID, T1,
PRI (NI or ETSI are
region-specific)

•

CLID Trunk Media Bay
Module (CTM4 or CTM8)
Global Analog Trunk
Module (GATM4 or
GATM8) (released with
BCM version 3.5)

•

CTM4/GATM4=1 per offset/
4 lines per module
CTM8/GATM8= 2 per bus/
8 lines per module

•

CTMs/GATMs can be set to
module types: Loop

•

P0609326 1.1

North America: Provides
CLID passthrough, Message
Waiting Indication and
Disconnect Supervision
UK: Provides Message
Waiting Indication

•

Explaining the Media Bay Modules headings

129

Table 11 Programmed Bus Types (Continued)

Hardware unit

Capacity

Available line types (some
line types are
region-dependent)

•

4X16 Media Bay Module
(4X16) (counts as one
CTM)

•

4X16=1 per offset (4 lines)
and additional bus (station)

•

4X16s can be set to module
types: Loop

•

BRI Media Bay Module
(BRI)

•

BRI=3 per bus, 4 loops (8
lines) per module

•

BRI can be set to module
types BRI S/T, BRI U2, BRI
U4 (setting must match
physical module type). U2
and U4 are region-specific

Data/trunk
module*

•

Digital Drop and Insert
(DDI) Mux module

•

•

T1

Specialized
modules

•

DECT Media Bay Module •
(DECT)

DECT=1 per bus, 4 loops,
supports 36 handsets

•

Norstar trunk expansion
•
modules, with Analog
Trunk cards, connected to
a FEM

FEM=1 per bus, can support •
up to three analog trunk
cards (in one trunk
expansion unit)/4 lines each

Norstar analog trunk cards:
Loop, E&M, DID

•

Norstar trunk expansion
modules with BRI cards,
connected to a FEM

FEM=1 per bus, can support •
up to three BRI cards (in one
trunk expansion unit)/4 loops
each

Norstar BRI cards: BRI S/T,
BRI U2, BRI U4 (setting must
match physical module type).
U2 and U4 are
region-specific

Programmed
Bus Type
Trunk module
(continued)

Data module

Universal T1=1 per two
buses, supports 24 lines
* Also refer to the section that
describes the UTWAN, which
provides the data connections
through a WAN card.

•

• DECT (region-specific)*
*This module type only appears
when a DECT module is present
on the system. If the DIP
switches are set incorrectly, the
setting appears, but the module
displays as unequipped.

Refer to the data section of this book (“Configuring a data module” on page 178) for
details about setting up a data module on DS30 08. This process includes any Norstar
Data Modules connected to a FEM.

GATM (Global Analog Trunk module)
These trunk modules can be adjusted to have static trunk parameters (pre-BCM 3.5 software), or to
allow the system to download new parameters when they become available (BCM 3.5 and newer
software). If the trunk is set to the latter state, trunk parameters are downloaded every time the
module boots up, or when the parameters change while the module is working. You can also set
line and telephone impedance to either 600ohm or 900ohm for modules with downloadable
parameters. The impedance settings are located under Lines and Telephone Services,
respectively. Refer to the installation guides for details about the module.

Business Communications Manager 3.6 Programming Operations Guide

130

Defining trunk module types and settings

Ports on Bus
Both types of modules have a Ports on bus heading. This heading shows the state of the port that
connects the module to the trunk line or system device.
•
•

Trunk modules, each port maps to an incoming line. Trunk port status is either idle or active.
Refer to “Trunk module ports programming” on page 142.
Station modules, each port maps to a connection to a system device (telephones, fax machines,
doorphone). For station modules, port status is either equipped (device connected) or
unequipped (no device connected). You can also determine what type of device is attached to
the port. Refer to “Viewing station module information” on page 143.

Bus 01 and 08 note: Bus 01 and 08 ports on bus are really virtual ports, since they connect to
services supported by the MSC. These ports are used for such devices and services as IP
telephones and Symbol NetVision handsets and voice mail traffic.

Defining trunk module types and settings
MSC bus numbers assigned to a trunk module display module numbers under the Bus heading that
correspond to the offset number set on the module DIP switches. For instance any trunk module
that has an offset of 0, will display under the heading Module 1, and so on to a maximum of four
modules (CTM4s/GATM4s).
The Module menu, which appears only under a Bus record that is configured for trunk modules,
allows you to configure line or loop provisioning for the module associated with a particular bus.
This record shows the number of lines or loops assigned to the module. It also provides the first
and last loop or line number. These settings are read-only.
The fields that appear on the module screen vary, depending on the module type you specify.
Trunk lines can also require configuration of settings such as the protocol type/version, frame
structure, clocking, and timers. These parameters depend on how the interface of the service
provider that the module connects to has been configured.
This section refers to these topics:
•
•
•
•
•
•
•
•

“Configuring the trunk module to line type” on page 131
“Determining Clock Sources for DTMs or BRIs” on page 135
“T1 interface parameters (region-specific)” on page 136
“E1 parameters (region-specific)” on page 138
“PRI Call-by-Call service selection” on page 138
“Provisioning lines (PRI, T1, DASS2)” on page 140
“PRI B-channel provisioning” on page 142
“Trunk module ports programming” on page 142

P0609326 1.1

Defining trunk module types and settings

131

Configuring the trunk module to line type
Follow these steps to define the modules to the system:
1

Click on the keys beside Resources, Media Bay Modules, Bus , and Modules on
Bus.

2

Click on the Module  you want to program.
The Bus -Module:  screen appears. The following figure shows an
example of the fields that display for a PRI module type.

Figure 29 Example of PRI module settings

3

Click on the arrow beside the Module type field and choose the correct setting that defines the
type of lines for the module.
The module installed in the system and Module Type must match the defined type of loop or
trunk and associated services provided by the central office line that you intend to be
connected to the module.
Note: When you configure a media bay module for PRI, BRI, or DECT, the system may
download new software to the module. This takes a couple of minutes to complete. Allow the
download to finish before continuing to program the module.

4

Press  on your keyboard to update the record.
Tips: To refresh the record, you may need to click on another navigation tree heading and then
re-enter the module record you were working on.

Business Communications Manager 3.6 Programming Operations Guide

132

Defining trunk module types and settings

5

Check the settings to ensure they reflect the line requirements. Note that only some of the
fields appear for all module types.
Refer to the following table for a description of each field.

Table 12 Module record values
Attribute

Value

Module mode DS/CLID, Global,
Legacy
•
•
•

# of lines/
loops

Module/line type
Loop

DS/CLID: displays for old North American LS/DS or CLID analog trunk modules, the old analog
MBM, or the GATM with North American DIP switch settings.
Global: displays for the GATM MBM with no regional DIP switches set.
Legacy: displays for all other (old) analog trunk modules


Loop E&M DID T1

PRI

BRI
S/T

BRI U2 BRI U4

The total number of lines or loops provided by the loops or trunks on this module.
Low/line loop View only
Loop E&M DID T1

PRI

BRI
S/T

BRI U2 BRI U4

The lowest line or loop number assigned by the system to the module based on the Bus
number, module type, and the module position on the Bus (offset on module DIP switch).
High/line loop View only
Loop E&M DID T1

PRI

BRI
S/T

BRI U2 BRI U4

The highest line or loop number assigned by the system to the module based on the Bus
number, module type, and the module position on the Bus (offset on the module DIP
switch).
Disconnect
timer

60, 100, 260, 460,
or 600 milliseconds Loop

T1

Specify the duration of an Open Switch Interval (OSI) before a call on a supervised external
line is considered disconnected. This setting must match the setting for the line at the
central office (CO).
You must enable disconnect supervision by changing the Trunk mode attribute. Under the
Telephony Services sub-heading, choose Lines and Line/trunk Data. See “Assigning Trunk/
line data” on page 236 for more information.
Note: Available to all supported countries for BCM 3.6 and newer software.
Answer timer 1, 2, 3, 4, or 5 sec.

E&M

PRI

Set the minimum duration of an answer signal before a call is considered to be answered.

P0609326 1.1

Defining trunk module types and settings

133

Table 12 Module record values (Continued)
Attribute

Value

Module/line type

Protocol

NI, DMS100,
DMS250,
AT&T4ESS, SL-1,
Euro, ETSI Q-Sig

PRI

Choose the trunk protocol used by your service provider.
The supported protocols are:
PRI-T1: NI (NI-1 and NI-2), DMS100, DMS250, AT&T4ESS, SL-1
PRI-E1: ETSI QSIG, Euro, SL-1
Note: SL-1 and ETSI QSIG require an MCDN keycode to display.
BRI: Protocol can also be selected on BRI T-loops under the Services/Telephony/Loops
heading.
Note: Always check the line protocol with the central office.
Protocol type User, Network

PRI

When you select SL-1 protocol, an additional setting, Protocol type, appears.
SL-1 protocol is a private networking protocol. This allows you to designate a Business
Communications Manager node as a Network (Master). The default setting is User (Slave).
In public network configurations, the CO is generally considered the Network side or
Master.
Applies to SL-1 protocol only.
NSF
Extension

None, WATS, ALL

PRI

The Network Specific Facilities (NSF) information element is used to request a particular
service from the network. Settings are based on the type of switch to which the line
connects.
Suggested settings:
DMS100/250: NONE
Siemens ESWD, Lucent 5ESS: WATS
GTD5, DMS10: ALL
When you select NONE, the NSF extension bit is not set for any service.
When you select WATS, the NSF extension bit is set for unbanded OUTWATS calls.
When you select ALL, the NSF extension is always set for all CbC services.
Appears only for NI protocol.
B-channel
selection
sequence

Ascending
Sequential
Descending
Sequential

PRI

Defines how B-channel resources are selected for call processing. For more information,
see “PRI B-channel provisioning” on page 142.

Business Communications Manager 3.6 Programming Operations Guide

134

Defining trunk module types and settings

Table 12 Module record values (Continued)
Attribute

Value

Module/line type

Clock Source Primary,
Secondary, Timing
Master

T1

PRI

*BRI
S/T

*BRI
U2

*BRI
U4

DASS2

Designates whether the DTM/BRI acts as a primary or secondary timing slave or as a
Timing Master.
Note: A BRI module can be programmed with primary/secondary clock source, however, it
is recommended that a BRI module always be Timing Master if a DTM exists on the system
to be the Primary clock source.
*BRI clock source is set on the Services, Loops, Loop XXX screen. Refer to “Identifying BRI
T-loops (T1 profiles)” on page 267 or “Identifying BRI T-loops (ETSI, QSIG)” on page 271.
For more information, see “Determining Clock Sources for DTMs or BRIs” on page 135.
Send Name
Display

Y, N
PRI

*BRI
QSIG

When set to Y, the system sends a specified outgoing name display (OLI) from the calling
telephone.
Appears only for Protocols: SL-1, NI, DMS100, DMS250, or PRI QSIG.
*BRI QSIG Send Name Display is set on the Services, Loops, Loop XXX screen. Refer to
“Identifying BRI T-loops (ETSI, QSIG)” on page 271.
Remote
Capability
MWI

Y, N

PRI

This setting allows you to indicate MWI compatibility on the specific loop(s) that you are
using to connect to the central voice mail system on a Meridian 1 which has the MWI
package installed, with the RCAP setting set to MWI.
Appears only for SL-1 protocol.

Max Transits Default: 31

PRI

Indicate the maximum number of times that a call will be transferred within the SL-1 network
before the call is dropped. Protocol must be set to SL-1 to display this field.
Host node

M1, Embark, IDPX,
DSM

DNPSS

DPNSS cards connected to Embark switches have a different way of handling call
diversion, therefore, when you provision a DTM for DPNSS, you must indicate what type of
switch the lines are connected to.
When you select the Embark switch, calls are diverted using the Call Forwarding feature
instead of call diversion.

Programming Tips - DECT module: The Module Type for the DECT module is DECT.
Refer to “Configuring DECT resources” on page 149 for a description of the Resources
headings for DECT, and to the DECT Installation and Maintenance Guide for details about
setting up the DECT system.
6

Press  to save the settings.

P0609326 1.1

Defining trunk module types and settings

135

7

If your module is set to T1, PRI, or DASS2, refer to “PRI Call-by-Call service selection” on
page 138 to continue with the configuration.

8

After you have completed your module configurations, refer to Chapter 9, “Configuring
lines,” on page 227 to set up the lines the trunk modules will use.

Determining Clock Sources for DTMs or BRIs
Clock Source allows you to designate the DTM or BRI on the system that obtains the timing
reference for synchronization from the network.
Systems with digital interfaces need to synchronize to the network in order to function.
Synchronization follows a hierarchical path. Each device (switch) obtains the network clock from
the device above it in the synchronization hierarchy. The device then passes the network clock to
the device below it in the synchronization hierarchy. The synchronization levels are referred to as
strata.
Business Communications Manager systems are stratum 4E equipment and are usually used as
termination points in a network.
For each DTM and BRI, choose one of the following settings: Primary, Secondary, or Timing
Master:
•

Primary reference —The DTM/BRI obtains the timing reference from the network and the
system synchronizes to it. This is the default value for the first DTM in Business
Communications Manager. Note that there should only be one defined Primary clock source
on a System.
Private network: If this system is in a private network and is intended to provide the master
clock for that private network, the system must have one and only one Primary clock reference
on a DTM or BRI. If this system is intended to act as clock master in a private network, then
all clock sources should be set to Timing Master on this system.

•

Secondary reference —The DTM/BRI acts as a standby reference. If there are excessive errors
on the Primary reference link, or the DTM/BRI designated as Primary reference fails, the
Secondary DTM/BRI obtains the timing reference from the network to be used for system
synchronization. This is the default value for the second DTM in a Business Communications
Manager.
Private network: If this system is in a private network and is intended to provide the Master
clock for that private network, then there should be no Secondary reference defined on any
DTM/BRI. Note that there should only be one defined Secondary clock source on a system.

•

Timing Master —The DTM/BRI does not obtain timing from the network, but transmits the
internally-generated system timing, which is derived from the Primary/Secondary source, to
equipment connected to it.
Note that while in the absence of a DTM Primary clocking source a BRI module can be used
for the primary timing reference, it is always recommended that, when possible, DTM(s) be
used as primary (and secondary) clock sources and that any remaining DTMs/BRIs be set to
Timing Master.

Business Communications Manager 3.6 Programming Operations Guide

136

Defining trunk module types and settings

Warning: Changing the clock source may disconnect calls.
If you change the clock source for your system, you may cause your system DTM
interface(s) to reset, resulting in dropped calls. Choose a suitable time to change the clock
source and use the Page feature to inform users of possible service disruptions.

Timing within networks
In most T1/E1 network configurations, you need one DTM or BRI configured as Primary to act as
a primary reference and obtain clocking from the network.
The only application where you might not have a DTM/BRI designated as a primary reference is in
a private DTM/BRI network where your Business Communications Manager system is connected
to other equipment using T1/E1/BRI interface(s) that require a clock source and your system had
been designated as the source of clocking for that private network.
•

If the other switches are to be clocked to your Business Communications Manager system, all
your DTMs/BRIs should be designated as Timing Master.

•

If your Business Communications Manager system has two DTMs, you cannot assign both
DTMs as primary reference or both DTMs as secondary reference.
You can have one Primary reference and one Secondary reference per system.

•

A T1, PRI(T1), PRI(E1), or BRI can act as the clock source.

T1 interface parameters (region-specific)
The T1 parameters heading appears for module types that have been configured as T1 or PRI. It
allows you to define a number of settings that are dependent on your T1 service provider settings.
1

Click the keys beside Resources, Media Bay Modules, Bus , Modules on Bus,
and Module .

2

Click on T1 Parameters.

3

Configure the T1 parameters according to the information in the following table.

Table 13 TI parameters
Attribute

Value

Description

CO fail

TIA-547A or
TR62411

Select the carrier failure standard used by your T1 or PRI service
provider. Consult your T1 or PRI service provider for the proper
setting.

Interface levels

ISDN or PSTN

Define a loss plan setting. For more information, see “Interface
levels” on page 137.

Framing

ESF or SF

Select the framing format used by your T1 or PRI service
provider: Extended Superframe (ESF) or Superframe (SF).
Contact your T1 or PRI service provider for the proper setting.
(SF or Superframe is sometimes known as D4.)

P0609326 1.1

Defining trunk module types and settings

137

Table 13 TI parameters (Continued)
Attribute

Value

Description

Internal CSU

On or Off

Turn the internal T1 channel service unit (CSU) on or off. For
more information, see “Internal CSU” on page 137.

CSU line build

0, 7.5, or 15 dB

Set the gain level of the transmitted signal. This setting appears
only when the Internal CSU is set to On.

DSX1 build

000-100, 100-200,
200-300, 300-400,
400-500, 500-600,
or 600-700 feet

Set the distance between Business Communications Manager
and an external channel service unit. This setting only appears
when the Internal CSU is set to Off. Contact your service provider
for the proper settings.

Line coding

B8ZS or AMI

Define the encoding signals on a T1 line. Select the standard
used by your T1 service provider. Contact your T1 service
provider for the proper setting.

Interface levels
The default Interface levels are the ISDN loss plan settings.
Check with your telecommunications service provider to determine if your Business
Communications Manager system is connected to a central office (CO) with digital network loss
treatment (ISDN I/F levels) or analog network loss treatment (PSTN I/F levels).
The ISDN setting requires digital access lines (DAL) that have digital network loss treatment. On
a DAL network, the PBX system administers the dB loss not than the CO. DALs may have ISDN
signaling or digital signaling (for example, T1). The loss plan follows the Draft TIA-464-C loss
plan, which uses a send loudness rating (SLR) of 8 dB. You must contact your service provider to
get DAL network loss treatment on a line with digital signaling.
The PSTN setting requires analog access lines (AAL) that have analog network loss treatment and
digital signaling. On an AAL(D) network, the CO administers the dB loss.
The loss plan follows the Draft TIA-464-C loss plan. The ISDN loss plan uses a send loudness
rating (SLR) of 8 dB and a receive loudness rating (RLR) of 2 dB. The PSTN loss plan uses an
SLR of 11 dB and an RLR of -3 dB. If you choose the wrong setting, the voice signal can be too
loud or too soft.

Internal CSU
Internal CSU allows you to turn the internal T1 channel service unit on or off. The channel service
unit gathers performance statistics for your T1 lines or PRI with public interface. Contact your
service provider for the correct settings.
Note: You must disable the DTM before you can change this setting. See “Disabling/enabling a
single module” on page 147 for details.
You can view the performance statistics for your T1 lines in Maintenance under the CSU stats
heading. Before you set the internal CSU to off, you must ensure there is an external CSU
connected to your T1 lines.

Business Communications Manager 3.6 Programming Operations Guide

138

Defining trunk module types and settings

E1 parameters (region-specific)
The E1 Parameters command appears for modules that have been configured as PRI in an E1
region. There is only one setting in the E1 Parameters menu - the CRC4 setting. CRC4 checking is
enabled at the other end.
1

Click on the keys beside Resources, Media Bay Modules, Bus , Modules on Bus,
and Module .

2

Click on E1 Parameters.

3

Configure the E1 CRC4 parameter as being On or Off to correspond to the CRC4 setting at the
far end of the E1 interface.

PRI Call-by-Call service selection
This section provides information about how to configure the PRI Call-by-call Service Selection,
which is region-specific to North America, for a DTM set to a PRI Module type.
By default, incoming calls on a PRI are routed based on the Called Party Number information
within the call request. The last number of digits of the called party number which matches the
Received Number Length setting, are used as Receive Digits to find a target line.
For example, assume an incoming called party number is 800-555-1234. The received digit
number length is 4, and the result is 1234. These last four digits are used to route the call.
In North American PRI, the Call-by-Call services allows alternate routing maps to be defined in
various ways, depending on the protocol defined for this PRI.
Use this process to define call-by-call services:
1

Click on the keys beside Resources, Media Bay Modules, Bus , Modules on Bus,
and Module .

2

Click on Call-by-call service selection.
The following table lists the applicable services for the protocol defined on the Module
 record.

Table 14 Services available for each PRI protocol
Services Available
Protocol

Foreign
Exchg

Inwats (800)

Intl-800

Switched
Digital (SDS)

Nine Hundred
(900)

NI

SID or All

By number or All

N/A

N/A

N/A

DMS-100

SID or All

SID, By number, or All

N/A

N/A

N/A

DMS-250

SID or All

SID, By number, or All

N/A

N/A

SID, or By
number, or All

4ESS

N/A

By number or All

By number By number or
or All
All

P0609326 1.1

By number or
All

Defining trunk module types and settings

3

Select the service you want to change.
A configuration screen appears in the right frame. The Translation mode default is None.

4

The following table shows the possible settings for the services.

139

Table 15 Module record values
Attribute

Value

Description

Translation None
Mode
All
By SID
By Number

Define how the system maps incoming digits for this service type to
the line number within the system.
In all cases, the received digits are used to find a target line or to
activate remote access.

Translation mode value
definitions:

None: No mapping is applied. The last digits of the Called Party
Number which match the Received Number Length setting are used
as received digits. Note that if there is no called party number (may
occur with some FX calls) the call will ring at the incoming trunk prime
set.
All: Allows you to define the received digits used for all calls with this
service type, regardless of the called party number or service
identifier (SID). For this option, all calls with this service type on this
PRI will ring the same target line.
Depending on the service type and the protocol, you may be able to
map the called party number (By number) and the service identifier
(SID).
By SID: Allows you to associate different received digits with different
calls of this service type based on the service identifier.
By Number: Allows you to associate different received digits with
different calls of this service type based on party number.
NOTE: Any calls that do not match any entry defined in the map table
will ring at the prime set.

Map Table

Enter the incoming line number to the internal line number, such as
Select Add on the
the target line.
Map Table screen
to create a new map
entry
From digits
To digits

Business Communications Manager 3.6 Programming Operations Guide

140

Defining trunk module types and settings

Provisioning lines (PRI, T1, DASS2)
The Provision lines heading allows you to provision and deprovision lines associated with a T1
PRI, E1 (DASS2), or BRI ST/U interface.
Provisioning a line or loop makes it available for system use. A deprovisioned line/loop is not
available for use. If you are purchasing a partial PRI trunk, the lines that have not been assigned
must be set to Deprovisioned.
The line number listed in each Line  entry corresponds to the line numbers listed under
the Services, Telephony Services, Lines, Physical Lines, Enabled Physical Lines menu
heading.

Provisioning a line
Note that all PRI lines are provisioned by default.
1

Click the keys beside Resources, and Media Bay Modules.

2

Choose the a bus number (Bus 02 to 07) associated with the trunk module you want to
provision.

3

Click the key beside the Modules on Bus heading.
The single DTM module on this bus appears.

4

Choose the module.
Expand Provision lines.
All the available lines appear as Line  headings.

5

Click the line you want to provision.

6

From the Status box, click Provisioned.

P0609326 1.1

Defining trunk module types and settings

141

Provisioning BRI loops/lines
In order to provision lines on a BRI module you must first provision the loop on which the lines
exist.
1

Click the keys beside Resources and Media Bay Modules.

2

Click the key beside the bus number (Bus 02 to 07) associated with the trunk module you want
to provision.

3

Click the key beside Modules on Bus.

4

Choose the BRI module where you want to provision loops.

5

Expand Provision Loops.
All the available loops appear as Loop  headings.

6

Click the Loop  you want to provision.

7

In the Status box, click Provisioned.

8

After provisioning one or more loops on the module:
a

Refresh the Loop  entry and you will see two Line  entries under
this loop.

b

Click on the Line  you wish to provision.

c

In the Status box, click Provisioned

Deprovisioning a line/loop
When you are not using a line/loop, or when you want to cancel it, you can deprovision that line or
loop.
Follow these steps to deprovision a line/loop:
1

Click the keys beside Resources and Media Bay Modules.

2

Click the key beside the bus number (Bus 02 to 07) associated with the module you want to
provision.

3

Click the key beside Modules on Bus.
A list of the modules assigned to the Bus appears.

4

Choose the module you want to provision.
For example, click on Module 1.

5

Click the key beside Provision lines or Provision Loops.
All the available lines/loops appear.

6

Choose the line/loop you want to deprovision.

7

From the Status box, click Deprovisioned.

Use this procedure if your system configuration requires/receives fewer than the standard number
of channels delivered from the PRI line. This is called Fractional T1/PRI. Your service provider
might offer you Fractional T1/PRI service to address specific needs on your system.
Business Communications Manager 3.6 Programming Operations Guide

142

Defining trunk module types and settings

You should only have as many lines provisioned on a T1/PRI as you have B-channels being
delivered on the T1/PRI from your service provider. Having more lines provisioned and assigned
to users may occasionally result in the attempt to perform calls over a line failing because of a lack
of B-channel resources being available.
Provisioning notes:
•
•

Deprovisioning all of the lines on a DTM does not disable the module.
BRI loops/lines are deprovisioned by default in the N1 ISDN protocol regions, otherwise they
are provisioned by default.

PRI B-channel provisioning
When you purchase PRI from your service provider, you can request the number of B-channels
that are allocated for you to use. For example, you may want to use only 12 B-channels instead of
23 B-channels. If you do not have all of the PRI B channels, you should disable all the B-channels
that you do not need.
It is recommended that the number of lines that are deprovisioned on an DTM (configured as PRI)
be the same as the number of B-channels that are disabled. For example, If the DTM is on bus 07,
when B-channels 13-23 are disabled, you should deprovision lines 73 to 83.
1

Choose Diagnostics, Trunk Modules.

2

Choose a bus, and then choose a module.

3

Choose B channels.
A list of the B channels on this module appears.

4

Click a channel, for example, B 01
The display shows the status of the PRI channel.

5

On the Configuration menu, click Enable or Disable to change the setting for the channel.

Trunk module ports programming
Click on the Port XXX (where XXX is a port number) heading, located under Ports on Bus, to
access information about the state of the module ports. Each port maps to an incoming line.
Figure 30 Finding state of port on Bus

P0609326 1.1

Viewing station module information

143

PRI version information
DTM modules that are set to PRI and BRI modules display additional PRI information under
Ports on bus, Port , Channels, B1/B2, Addons. By clicking on the Addon 01 heading,
you can view information about the version of the downloadable firmware component being used
in this module. By clicking on the Addon 02 heading, you can view information about the version
of the downloadable protocol component being used on this module.
You can enable or disable any port. Refer to “Disabling or enabling a port channel setting” on page
148.

Viewing station module information
The following figure shows a typical example of the headings for a station media bay module.
Figure 31 Station media bay module Bus headings

Partial Double Density bus
Bus 06
Ports on Bus
Port 0201
Channels
B1
Addons
B2
Addons

Double Density bus
Bus 02
Ports on Bus
Port 0201
Channels
B1
Addons

When you click on a bus that has a station module installed, you will see a screen that indicates the
type of module, the number of ports that are busy on the module, and the operational state of the
module.
Figure 32 Bus assigned to a station module

Programming Note: If the Actual Bus Type reads None, choose the correct setting in the
Programmed Bus Type field. After the system initializes to the module, the Actual Bus Type
Business Communications Manager 3.6 Programming Operations Guide

144

Viewing station module information

should change to the correct module type. You may also have to disable, then re-enable the module
to force the system to re-initialize (under the Configuration menu). Refer to “Viewing Media Bay
Module status” on page 147 for details about enabling and disabling modules.
Some modules take a few minutes to reinitialize.
If these actions do not cause the fields to display correctly, you may have a damaged module or
back plane. Try installing the module in a different media bay and retry the configuration. Refer to
the Installation and Maintenance Guide for your hardware for information about removing and
installing media bay modules.

Determining station port state
Click on the Port  heading, located under Ports on Bus, to access information about the
state of the device (media bay module).
Figure 33 Finding state of port on Bus

Viewing port device information
Under the Port heading, the Channels heading provides access to device information about the B1
(and B2 for Bus 06 and 07 on PDD systems) media channels. Clicking on the B1 heading displays
the information about the device assigned to that media channel, including the DN of the device,
the type of device (model), the version of the firmware on the device, and the state of the device, as
set on the Port XXXX screen.
Figure 34 Ports on Bus, B1 screen

P0609326 1.1

Viewing station module information

145

You can enable or disable any port. Refer to “Disabling or enabling a port channel setting” on page
148.

Station module line deployment
The MSC presents 32 physical ports for each bus number assigned to a station or analog station
module. The DIP switch settings on the module determine which ports support telephone
connections. The first 16 ports are based on the B1 channel; the second 16 ports are based on the
B2 channel. Therefore, if a single-density DSM 16 module is used, only the first 16 DNs are
available for system telephones. Any module that was installed on a BCM version 2.5 or earlier
system is single density, which means it would support some of the first 16 ports, depending on the
type of module.
On systems running BCM version 3.0 and newer software, if you install DSM 16+ or DSM32+
modules, you can set them to be either single density or double density. An ASM8+ installed on a
double density bus can populate all four offsets. If a DSM16+ or DSM32+ are set to double
density 32 ports are available, depending on the module and the dip switch settings. Example: A
DSM16+ set to double density accesses either the first 16 ports or the second 16 ports, depending
on the offset setting. A DSM32+ set to double density accesses the first 16 ports on the lower
connector and the second 16 ports on the upper connector.
Partial Double Density systems (PDD), which is the default system setting for BCM version 3.0
and newer software, retain a single-density identity for buses 06 and 07, to allow support for
Companion installations which support two handsets for each B1/B2 port. Each port in single
density configurations are assigned a B1 and a B2 channel. If you set your system to
fully-deployed double density (FDD), both bus 06 and 07 are configured as double density and are
no longer available for applications that require both B1 and B2 ports.
You can change your system density from PDD to FDD under the Configuration menu in the MSC
programming. (Services, Diagnostics, MSC)
Upgraded systems: BCM version 2.5 systems upgraded to BCM version 3.0 or newer systems
have a different DN deployment than newly-deployed BCM version 3.0 systems. In upgraded
systems, the first 16 DNs are assigned to DS30 02, the next 16 are assigned to DS30 03, and so on,
down to DS30 07. Then the first 16 DNs following this list is assigned to the second 16 lines (B2)
on DS30 02, and so on down the list again.
New BCM version 3.0 and newer systems: The DN deployment in these systems is sequential.
That is, the first 32 DN numbers are assigned to DS30 02, the second 32 DN numbers are assigned
to DS30 03, and so on.
DN numbering for each type of system is displayed in tables in “DN mapping for digital
telephones” on page 355

Business Communications Manager 3.6 Programming Operations Guide

146

Internally-driven channels

Internally-driven channels
You cannot change headings for buses that are used for internal processing. This section describes
how these buses fit into the system.
Bus 01 and Bus 08 provide access to telephony operations for internal processing, applications,
and IP sets on the Business Communications Manager system. These two buses are commonly
referred to as virtual buses since they have no external physical connections.
Bus 01 has 32 virtual ports. Bus 08 has 28 virtual ports. Each of these ports has one media channel
associated with it. These channels are labeled as B1 on the configuration menu. When IP
telephones are assigned to the system, they will appear on these ports. The ports are allocated
sequentially as telephones are added.
Bus 08 can also be used for a virtual data module (NA only) when a Business Communications
Manager data service such as WAN service is activated. Refer to “Configuring a data module” on
page 178 for further programming. Note that Bus 08 does not display when there is a WAN active
on the system.
By default, Bus 07 is used for a media bay module connection (2/6 channel split). However, if
your system was set to a 3/5 DS30 split, then Bus 07 becomes a virtual bus with 32 ports. The
headings under Bus 07 become invalid in this configuration. Refer to the “Configuring the MSC
resources” on page 609 for further details.

Working with the modules
When you need to find out information about a module, you can determine the status of any of the
settings under the media bay modules headings. To correct a problem, or change a module setting,
you may need to enable or disable a port, a module, or an entire bus. This section provides the
procedures got:
•
•
•
•

“Viewing Media Bay Module status” on page 147
“Disabling/enabling a DS30 bus” on page 147
“Disabling/enabling a single module” on page 147
“Disabling or enabling a port channel setting” on page 148

P0609326 1.1

Working with the modules

147

Viewing Media Bay Module status
Media Bay Modules selection allows you to view the status of all the modules as well as identify
any device or lines connected to the system. This allows you to isolate any malfunctioning part of
the system. In addition, you can use the Media Bay Module selection to disable and enable
modules and devices. For more information, refer to one of the following procedures.
Use this procedure to display module type, the number of sets connected to the module, the
number of busy sets and the module state:
1

On the navigation tree, click the Resources key and click the Media Bay Modules key.
The window displays Bus 02 through to 08.

2

Click heading of the bus you want to view. For example, Bus 02.
The Configuration menu is enabled and the status information of the module associated with
that bus appears.

Disabling/enabling a DS30 bus
The following procedure describes the process for enabling or disabling a bus. This means that if
there is more than one module assigned to the DS30 bus, all modules will be disabled.
1

Click the keys beside Resources and Media Bay Modules.
Buses 01 to 07 are displayed.

2

Click on the bus number of the module you wish to enable/disable (Bus 02 to 07).

3

On the top menu, click Configuration, and then, click Enable or Disable.
The system prompts you to confirm your request.

4

Click the OK button.
Programming reminder: If your system has a 3/5 DS30 split, BUS 07 will not have a module
assigned to it.

Disabling/enabling a single module
The following procedure describes the process for enabling or disabling a single module if there is
more than one module assigned to a DS30 bus.
1

Click the keys beside Resources and Media Bay Modules.
Buses 01 to 07 are displayed.

2

Click on the key beside the Bus number of the module you wish to disable (Bus 02 to 07).

3

Click on the Module number of the media bay module you want to enable/disable.

4

On the top menu, click Configuration, and then, click Enable or Disable.
The system prompts you to confirm your request.
Business Communications Manager 3.6 Programming Operations Guide

148

Working with the modules

5

Click the OK button.
Programming reminder: If your system has a 3/5 DS30 split, bus 07 will not have a module
assigned to it.

Disabling or enabling a port channel setting
If you need to isolate a problem or block access from the module, you may need to turn off
individual port channels, rather than the entire module.
To turn off a channel:
1

Click on the keys beside Resources, Media Bay Modules, and beside the Bus number where
the module is located.

2

Click the key beside Ports on bus.

3

Click the key beside the port that contains the channel you want to disable.

4

Click the key beside Channels.

5

Click on the B channel you want to disable (B1 or B2).

6

On the top menu, click Configuration and select Disable or Enable.
If you are disabling the channel, you will be prompted by a dialog box to confirm your action.
The State field indicates the mode of operation for the port, as shown in the figure below. If
the port is enabled, this field is blank unless a device is physically connected.

P0609326 1.1

Configuring DECT resources

149

Configuring DECT resources
There are three areas on the Unified Manager that you need to program or look for DECT module
information:
•

•

The DECT module is enabled on the system through the Resources, Media Bay Module,
Bus  record, as with all other modules. The difference is that you set the Module
Type to DECT.
The Resources, DECT menu allows you to view the identification information for the DECT
media bay module installed in Business Communications Manager. Refer to the following
figure.

Figure 35 DECT media bay module description

•

The Maintenance Selection tab opens a screen from which you select the DECT module. This
allows you to collect maintenance information that can be viewed through the maintenance
console under Services, DECT. Refer to the following figure.

Figure 36 DECT maintenance selection

The entries on this screen fill automatically when a DECT module is plugged into the Business
Communications Manager and the system is powered up. The DIP switch settings on the DECT
module define the bus and the slot (offset, always set to 0). The information on the module
provides the Version and Description information. The status information is obtained from the
Provision Lines heading found under Resources, Media Bay Modules, Bus .

Business Communications Manager 3.6 Programming Operations Guide

150

Configuring DECT resources

The DECT module contains four internally-accessible BRI loops. These loops are also
automatically populated when the module is installed.
Note: The module BRI loops are defined within the module to act as a line pool. DNs are assigned
to the loops from within the DECT module interface. This also occurs if you configure your
system using the DECT wizards. Refer to the DECT Installation and Maintenance Guide for
details.

P0609326 1.1

151

Chapter 6
Data and split-line configuration
This section discusses configuration for modules and applications that require data or combination
data/telephony line configuration.
•

DDI MUX modules require two DS30 bus positions. This module supports combinations of
data channels and T1 lines. A DTM (digital trunk module) contained within the module is
programmed using normal DTM line configuration. The data portion of the lines are
configured under the second DS30 bus as data lines. The DDI MUX supports using either the
internal router or an external router. Refer to “Configuring the DDI Mux module” on page 151.

•

The UT-WAN application, performs a similar function as the DTM module, only without
using a physical data module. This feature uses an installed DTM for lines and the internal
router for data. Refer to “Universal T1 WAN (UTWAN)” on page 159

•

Data modules used to configure channels on a WAN interface are always configured under
DS30 Bus 08. Refer to “Configuring a data module” on page 178.

Configuring the DDI Mux module
The Digital Drop and Insert (DDI) Mux media bay module enables a Business Communications
Manager system to share its connection to a Universal T1 network with a local area network
(LAN). A DDI Mux allows you to make more efficient use of your digital network resources and
reduces the amount of equipment needed to support your voice and data networks. This module is
currently available only for North American installations.
This section contains the following information:
•
•
•
•
•

“Configuring DDI Mux connections” on page 154
“Assigning the DDI mux modules” on page 154
“Assigning lines for voice traffic” on page 155
“Assigning lines to the data module” on page 155
“Configuring the DDI Mux to work with the DTE” on page 157

DDI Mux features
The DDI Mux performs the following services:
•
•
•
•

provides the functionality of a DTM media bay module (T1 digital lines only)
splits the incoming T1 line so that some of the lines are used for voice traffic and some of the
lines are used for data traffic
provides either the CSU (Channel Service Unit) or DSU (Data Service Unit) functionality to
support connections to data terminal equipment (DTE), such as a router or a bridge
connects to network devices that support V.35 interfaces
Business Communications Manager 3.6 Programming Operations Guide

152

Configuring the DDI Mux module

•
•

provides end-to-end transparent bit service
supports loopbacks between the DDI Mux and the internal Business Communications
Manager components, and between the DDI Mux and digital terminal equipment
Note: The DTE cable that connects the Business Communications Manager to the router
is ordered separately from the module. If you do not have this cable, ask your customer
service representative about how to obtain one.

The following figures provide examples that use internal and external routers with the DDI Mux.
Figure 37 Network overview: DDI MUX connected to 2.5 hardware internal router

Switch/Hub
T1 mux service

DTE cable

P0609326 1.1

Service Provider/
PSTN

Configuring the DDI Mux module

153

Figure 38 Network overview: DDI MUX connected to BCM400 internal router

Switch/Hub
T1 mux service

Service Provider/
PSTN

DTE cable

Figure 39 Overview of network using DDI Mux module with an external router

Switch/Hub

Router
T1 mux service
DTE cable

Service Provider/
PSTN

Business Communications Manager 3.6 Programming Operations Guide

154

Configuring the DDI Mux module

Configuring DDI Mux connections
After you have installed the DDI Mux, configure the module settings in the Unified Manager.
To configure the DDI Mux, you need to:
•
•
•
•

assign the DDI Mux modules under Resources, Media Bay Modules
assign the lines for voice traffic under Services, Telephony Services, Lines
assign lines to the Data Module portion of the module
configure the DDI Mux to work with the DTE

Before you start, record the settings for the DDI Mux in the form provided in the Programming
Records. At the very least, you need the following configuration information:
Table 16 Configuring DDI Mux connections
Protocol

V.35

❑

Loopback state:

Off ❑
Manual DS30

Manual DTE ❑
Automatic DTE ❑

❑

Fixed Access
Line ____ Channel ____
Line ____ Channel ____
Line ____ Channel ____

Line ____ Channel ____
Line ____ Channel ____
Line ____ Channel ____

Line ____ Channel ____
Line ____ Channel ____
Line ____ Channel ____

Line ____ Channel ____
Line ____ Channel ____
Line ____ Channel ____

Line ____ Channel ____
Line ____ Channel ____
Line ____ Channel ____

Line ____ Channel ____
Line ____ Channel ____
Line ____ Channel ____

Line ____ Channel ____
Line ____ Channel ____
Line ____ Channel ____

Line ____ Channel ____
Line ____ Channel ____
Line ____ Channel ____

Assigning the DDI mux modules
1

Click the keys beside Resources and Media Bay Modules.

2

Click the DS30 Bus heading that was assigned to the DDI Mux.
This Bus is the same as the DS30 bus you assigned to the DDI Mux using the DIP switches on
the module.

3

Make sure the option in the Programmed Bus Type drop list is Trunk module.

4

Click the heading of the next DS30 Bus.
This Bus is the DS30 bus automatically assigned to the Data Module portion of the DDI Mux.

5

Click the Programmed Bus Type drop list, then click Data module.

P0609326 1.1

Configuring the DDI Mux module

155

Assigning lines for voice traffic
A digital T1 line has up to 24 telephone lines available for use. On the DDI Mux, you can assign
some of these lines to telephony traffic and some to data traffic.
For the lines that you want to use for telephony traffic, configure the lines in the same manner as
you configure lines for a DTM. For information about how to configure digital lines on a DTM,
refer to “Provisioning lines (PRI, T1, DASS2)” on page 140.

Assigning lines to the data module
The number of lines you assign to the data module determines the bandwidth of your data
networking connection. The following table shows the allocated bandwidth for the DDI Mux
according to the number of lines assigned. The allocated bandwidth also depends on the line data
rate indicated by the B-channel data rate parameter.
Table 17 List of all the multiples of 56000 and 64000 bits/s
Number of
lines
selected

56000 bits/s

64000 bits/s

1

56000

64000

2

112000

3
4

Number of
lines selected

56000 bits/s

64000 bits/s

13

728000

832000

128000

14

784000

896000

168000

192000

15

840000

960000

224000

256000

16

896000

1024000

5

280000

320000

17

952000

1088000

6

336000

384000

18

1008000

1152000

7

392000

448000

19

1064000

1216000

8

448000

512000

20

1120000

1280000

9

504000

576000

21

1176000

1344000

10

560000

640000

22

1232000

1408000

11

616000

704000

23

1288000

1472000

12

672000

768000

24

1344000

1536000

To assign a line to the data module, you must change the line type to Fixed Data Channel and then
assign the line to the data module.

Changing the line type
1

In the Unified Manager, click the keys beside Services and Telephony Services.

2

Click the Lines key and then click the Physical lines key.

3

Click the All physical lines key.

4

Click the key of one of the line numbers assigned to the Data Module.

Business Communications Manager 3.6 Programming Operations Guide

156

Configuring the DDI Mux module

5

Click the Trunk/line data heading.

6

Click the Trunk type drop list and then click Fixed data channel.

7

Repeat steps 5 to 7 for each line you want to assign to the Data Module.

Assigning the line
1

Click the Resources key and then the Media Bay Modules key.

2

Click the key beside the Bus number assigned to the Data Module.
In this release of Business Communications Manager, the Data Module is always Bus 08.

3

Click the Data module key and click the Interfaces key.

4

Click the key beside the Interface to which you want to add a line. For example, click the key
beside Interface 02.
Note: You can add all of the lines to the single Interface, or you can the lines to
multiple interfaces.

5

Click the Line assignment heading below you Interface to which you are adding lines.

6

Click the Add button.
The Add Fixed line assignment dialog box appears.

7

In the Line box, enter the line number of one of the lines assigned to the Data Module.
Note: You can assign up to 24 lines to the DDI Mux.
You can assign only Fixed lines.

8

Click the Save button.

9

If you are adding all of the lines to a single Interface, repeat steps 6 to 8 for each line you want
to assign to the Data Module.
If you are adding the lines to multiple Interfaces, repeat steps 4 to 8 for each line you want to
assign to the Data Module.

Removing a line assignment
If you decide you want to remove a line assignment from the Data Module and use it as a
telephony line, use the procedure below:

Removing the line
1

Click the Resources key and click the Media Bay Modules key.

2

Click the key beside the Bus number assigned to the Data Module.

3

Click the Data module key and click the Interfaces key.

4

Click the key beside the Interface number from which you want to remove the line assignment.

P0609326 1.1

Configuring the DDI Mux module

5

Click the Line assignment heading.

6

Click on the line number you want to remove.

7

Click the Delete button.

8

On the confirmation dialog box, click the Yes button.

157

Configuring the line for telephony
1

Click the keys beside Services and Telephony Services.

2

Click the keys beside Lines, Physical lines and All physical lines.

3

Click the key of the line number you want to assign to telephony use.

4

Click the Trunk/line data heading.

5

Click the Trunk type drop list and then click on the correct type of trunk.

Configuring the DDI Mux to work with the DTE
After you have assigned the lines to the data module, you need to configure the DDI Mux so it can
work with the DTE.
1

Click the keys beside Resources and Media Bay Modules.

2

Click the key of the Bus number for the Data Module portion of the DDI Mux.

3

Click the Data Module key and then click on Configuration.

4

Configure the setting to match the DTE you are connecting to the DDI Mux.
The following table describes the Data Module configuration settings.

Table 18 DDI Mux Configuration settings
Setting

Value

Description

Protocol

V.35

The DDI Mux supports a V.35 interface standard through its data interface port.
You can select V.35.

B channel data
rate

64 K
56 K

Select the transmission rate per channel (Fixed data lines) assigned to the
module.

Transmit clock
source

Auto
DCE
DTE

The DDI Mux requires a timing signal to clock data transmitted by the DTE. This
signal can be supplied by the DTE or generated internally by the [Product Name
(short)]. If the signal is generated by the DTE, the clock must be locked to the
frequency of the DDI Mux clock.
• Auto: The DDI Mux checks if the clock provided by the DTE is valid. If the
clock is valid, the module uses DTE clocking. If the DTE clocking is not valid,
the module uses its own internal clock (DCE).
• DCE: The internal TxSync clock is used to clock data.
• DTE: The TXClk clock provided by the DTE is used by the DDI Mux to clock
data.
Note: Use the DTE option only for diagnostic purposes.
For all options, the DTE must synchronize to the module.

Business Communications Manager 3.6 Programming Operations Guide

158

Configuring the DDI Mux module

Table 18 DDI Mux Configuration settings (Continued)
Setting

Value

Description

Transmit clock
inversion

Off
On

When the internal DCE signal is used to clock in data, signal delays caused by
cable length can cause clocking errors. To adjust for round trip delays between
the DDI Mux and DTE, invert the internal clock used by the module to clock in
data from the DTE.
To enable clock inversion, select the DTE clock or Auto clock.

Data inversion

Off
On

When Data Inversion is on, the DDI Mux inverts the data before routing it to the
T1 connection and DTE. Inversion allows the module to use the properties of
protocols such as HDLC/SDLC (a transmission standard for data) to meet the
ones density requirement of the network. This feature must be available and
activated at the far end.

P0609326 1.1

Universal T1 WAN (UTWAN)

159

Universal T1 WAN (UTWAN)
The UTWAN enables a Business Communications Manager system to use a Universal T1
connection to send and receive voice and data information. By sharing this connection you can
make more efficient use of your digital network resources and reduce the amount of equipment
needed to support your voice and data networks. The UTWAN is currently available only for
North American installations.
Net Link Manager provides continuous WAN connection status monitoring. For information about
Net Link Manager, see “Configuring Net Link Manager” on page 749.

UTWAN connection
The UTWAN connection supports frame relay or Point-to-Point protocol (PPP) at the link layer.
The link protocol you use depends on the existing network or on the service you buy from your
Internet service provider.

Frame Relay
In Frame Relay mode, the UTWAN interface allows up to 50 PVCs (permanent virtual circuits) to
be configured. You can assign the same IP for multiple PVCs, or a unique IP for each PVC. To
avoid IP routing confusion, it is important that each unique IP belongs to a unique subnet.
The available Data Link Control interface numbers are 0-1023. Of the 1024 PVCs, 16 are
reserved. The maximum number of PVCs allowed is 1008.
The range of the Data Link Control Interface (DLCI) numbers is between 0 and 1023. However,
within this range, only 16 through 991 are available for user connections. The other ports are
reserved as follows:
•
•
•

0 and 1023 are reserved for the Local Management Interface (LMI) handshake
992 through 1007 are reserved for Frame Relay management at layer 2
1 through 15 and 1008 through 1022 are reserved for future use

Point-to-Point-Protocol (PPP)
Point-to-Point Protocol (PPP) is a full-duplex transmission protocol for communication between
two computers using a serial interface. A typical PPP connection is a personal computer connected
by telephone line to a server. For example, your Internet service provider (ISP) provides you with
a PPP connection so that the ISP server can respond to your requests, pass them on to the Internet,
and return your requested Internet responses to you.

Business Communications Manager 3.6 Programming Operations Guide

160

Universal T1 WAN (UTWAN)

Fragmentation
Frame Relay fragmentation and PPP fragmentation are link-layer fragmentation schemes.
Over a slow link, the major advantage of using link-layer fragmentation over IP layer
fragmentation is that while it reduces the jitter effect for voice packets, it also reduces the
end-to-end delay for data packets that is introduced by IP layer fragmentation.

RTP Header compression
The RTP Header Compression feature allows you to compress the 40 byte IP/UDP/RTP header to
2 or 4 bytes. This reduces the header-to-payload ratio of a data transmission. This is particularly
true of data transmissions with smaller payloads, such as a IP telephony packets. By reducing the
header-to-payload ratio, you can increase your bandwidth utilization. With slower links, this
allows more data or simultaneous IP telephony conversations to be carried over the link at the
same time.

Data compression
Business Communications Manager provides a WAN Data Compression feature.
On the UTWAN connection, Business Communications Manager supports the following data
compression protocols:
• Frame Relay Forum standard FRF.9 data compression protocol with STAC compression
algorithm
• PPP Compression Control Protocol (RFC 1962) with STAC compression algorithm

P0609326 1.1

Universal T1 WAN (UTWAN)

161

Configuring the Business Communications Manager to use the
UTWAN
The UTWAN interface allows circuit-switched voice traffic and packet-switched data traffic
(including IP Telephony) to use the same physical link. This requires you to assign some of the T1
lines for voice traffic and some of the lines for data traffic. After you have assigned the lines, you
must configure UTWAN link layer parameters for data traffic.
•
•
•

“Assigning lines for voice traffic” on page 161
“Assigning lines for data traffic” on page 161
“Configuring the UTWAN Network Interface parameters” on page 164
Note: Only one DTM can be used for UT1 connection.
Of the 24 available T1 lines, the maximum number of lines that can be assigned for data
traffic is 16.

Assigning lines for voice traffic
A digital T1 line has up to 24 telephone lines available for use. When using the UTWAN feature,
you can assign some of these lines to telephony traffic and some to data traffic. For the lines that
you want to use for telephony traffic, configure the lines in the same manner as you configure
other telephony lines. For information about how to configure digital lines, refer to “Provisioning
lines (PRI, T1, DASS2)” on page 140.

Assigning lines for data traffic
The number of lines you assign for data traffic determines the bandwidth of your data networking
connection. The following table shows the available bandwidth for data traffic on the UTWAN
according to the number of lines assigned.
Table 19 Bandwidth available per channel
Number of lines

Bandwidth (bps)

Number of lines

Bandwidth (bps)

1

64000

9

576000

2

128000

10

640000

3

192000

11

704000

4

256000

12

768000

5

320000

13

832000

6

384000

14

896000

7

448000

15

960000

8

512000

16

1024000

Note: The maximum number of lines you can assign for data traffic is 16.
Both ends of the WAN link must be using the same number of lines for data traffic and
start with the same time slot.
Business Communications Manager 3.6 Programming Operations Guide

162

Universal T1 WAN (UTWAN)

To assign a line for data traffic, you must change the line type to Fixed Data Channel and then
assign the line to the data module.

Determining which lines are available to the UTWAN
The lines that are available to the UTWAN are determined by the DIP switch settings on the DTM
you are using for the UTWAN connection. Refer to the table below for a list of lines assigned per
DS30 bus.
Table 20 Line numbers for the UTWAN based on the DS30 bus of the DTM
DS30 bus

Type of module

Default Line numbers

02

Digital Trunk Module (DTM)

211-234

03

Digital Trunk Module (DTM)

181-204

04

Digital Trunk Module (DTM)

151-174

05

Digital Trunk Module (DTM)

121-144

06

Digital Trunk Module (DTM)

91-114

07

Digital Trunk Module (DTM)

61-84

Changing the line type
1

In the Unified Manager, click the Services key and click the Telephony Services key.

2

Click the Lines key and click the Physical lines key.

3

Click the All physical lines key.

4

Click the key of one of the line numbers you want to assign for data traffic.

5

Click the Trunk/line data heading.

6

Click the Trunk type drop list and click Fixed data channel.

7

Repeat steps 4 to 6 for each line you want to assign for data traffic.

Assigning lines to the Data Module
1

Click the Resources key and the Media Bay Modules key.

2

Click the key beside the Bus number assigned to the Data Module.
In this release of Business Communications Manager, the Data Module is always Bus 08.

3

Click the Data module key and click the Interfaces key.

4

Click the key beside the Interface to which you want to add a line. For example, click the key
beside Interface 02.
Note: You can add all of the lines to the single Interface, or you can the lines to
multiple Interfaces.

5

Click the Line assignment heading below you Interface to which you are adding lines.

P0609326 1.1

Universal T1 WAN (UTWAN)

163

6

Click the Add button.
The Add Fixed line assignment dialog box appears.

7

In the Line box, enter the line number of one of the lines assigned to the Data Module.

8

Click the Save button.

9

If you are adding all of the lines to a single Interface, repeat steps 6 to 8 for each line you want
to assign to the Data Module.
If you are adding the lines to multiple Interfaces, repeat steps 4 to 8 for each line you want to
assign to the Data Module.

Removing a line assigned for data traffic
If you decide you want to stop using a line for data traffic and use it as a telephony line, use the
procedures below:

Removing the line from the Data Module
1

Click the Resources key and click the Media Bay Modules key.

2

Click the key beside the Bus number assigned to the Data Module.

3

Click the Data module key and click the Interfaces key.

4

Click the key beside the Interface number from which you want to remove the line assignment.

5

Click the Line assignment key.

6

Click on the line number you want to remove.

7

Click the Delete button.

8

On the confirmation dialog box, click the Yes button.

Configuring the line for telephony traffic
1

Click the Services key and click the Telephony Services key.

2

Click the Lines key and click the Physical lines key.

3

Click the All physical lines key.

4

Click the key of the line number you want to assign to telephony use.

5

Click the Trunk/line data heading.

6

Click the Trunk type drop list and then click on the correct type of trunk.

7

Configure the line in the same manner as you configure other telephony lines. For information
about how to configure digital lines, refer to “Provisioning lines (PRI, T1, DASS2)” on page
140.

Business Communications Manager 3.6 Programming Operations Guide

164

Universal T1 WAN (UTWAN)

Configuring the UTWAN Network Interface parameters
The first step to configuring the UTWAN Network Interface parameters is:
•

“Configuring the UTWAN Summary parameters” on page 164

One of the UTWAN Summary parameters is the link protocol used on the T1 line. When you
select the appropriate link protocol, the screen changes to show the parameters required for that
link protocol.
The second step to configuring the UTWAN interface is to use one of the following procedures to
configure the link protocol specific parameters.
•
•

“Configuring the UTWAN to use a Frame Relay link” on page 166
“Configuring the UTWAN to use a PPP link” on page 170

If the UTWAN interface has multiple IP addresses, the third step is:
•

“Configuring additional IP addresses for the UTWAN” on page 176

Using multiple IP addresses is a common scenario when there are more than one frame relay PVC
circuits. When you configure an IP address for each frame relay PVC, each IP address must be
valid in the sense that the IP address must have been configured as the primary IP for the
UTWAN, or as an additional IP for UTWAN.

Configuring the UTWAN Summary parameters
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Configure the Summary settings according to the information in the following table.

Table 21 UTWAN Summary parameters
Attribute

Description

IP Address

Enter the IP address of the UTWAN interface. The UTWAN IP address must be in the proper
dotted format, for example 255.255.255.255.
You can obtain this information from your system administrator or your Internet service provider.

SubNet Mask

Enter the subnet mask address of the UTWAN. The subnet mask must be in the proper dotted
format, for example 255.255.255.255.
You can obtain this information from your system administrator or your Internet service provider.

Physical Address

Shows the physical address of the UTWAN interface.

Description

Provides a description of the UTWAN connection.

Version

Shows the version of the UTWAN interface.

MTU Size

Enter the value for MTU Size.

P0609326 1.1

Universal T1 WAN (UTWAN)

165

Table 21 UTWAN Summary parameters (Continued)
Attribute

Description

Status

Shows the current resource status of the UTWAN interface. The possible states are:
Up: The UTWAN is operational.
Down: The UTWAN is not operational.

Link Protocol

Lets you select a link protocol. The link protocol you choose depends on the existing network or
the service you buy from your Internet service provider.
The options for Link Protocol are:
FrameRelay_DCE: Select this option if you are connecting two Business Communications
Manager systems back to back and the other Business Communications Manager system is
configured as FrameRelay_DTE.
FrameRelay_DTE: Select this option if the other end of the WAN link is a Frame Relay router, a
Frame Relay switch or a Frame Relay server provided by your Internet service provider.
PPP: Select this option if the other end of the WAN link is configured to use PPP.
The default is PPP.
If you change the link protocol, the configuration screen changes to include fields corresponding
to the link protocol you choose. To ensure proper operation, always refresh the page by clicking
View and then Refresh.

4

Press the TAB key to save your settings.
Note: Unified Manager refreshes the UTWAN screen according to the chosen protocol.
Your choice of protocol depends on the existing network or the service you buy from your
Internet service provider. PPP is the default link protocol. If you change the link protocol
the following message appears: “Reminder! Previous setting requires rebooting the system
to take effect. Please reboot the system...” Click OK.

Caution: Reboot the system.
You must remember to reboot your system for the changes you made to the link protocol
to take effect. You can continue UTWAN configuration and reboot the system at a
convenient time.

Business Communications Manager 3.6 Programming Operations Guide

166

Universal T1 WAN (UTWAN)

Configuring the UTWAN to use a Frame Relay link
Configuring the UTWAN to use a Frame Relay link consists of the following:
•
•
•

“Configuring the UTWAN Summary parameters” on page 164
“Configuring the Frame Relay parameters” on page 166
“Configuring the PVC Configuration parameters” on page 167

Configuring the Frame Relay parameters
To set the UTWAN Frame Relay Parameters.
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the Frame Relay Parameters tab.
The Frame Relay Parameters screen appears.

4

Configure the Frame Relay Parameters by referring to the following table.

Table 22 UTWAN frame relay parameters
Attribute

Description

LMI Type

Select the type of local management protocol used on this link. The link management type
must be the same as the one used by the frame relay service provider. The available
options are Original LMI, ANSI T1.617 Annex D or ITU-T Q.933 Annex A.
The default setting is ANSI T1.617 Annex D.
Note: The most commonly used setting for this parameter is ANSI T1.617 Annex D.

Polling Interval

Enter an interval, in seconds, between Status Enquiry messages.
Possible values are between 1 and 100 seconds.
The default setting is 6.

Missing Status Enquiry

Enter the maximum number of consecutive failures permitted in the Status Enquiry before
dropping the link. It is also the number of successful consecutive Status Enquiry messages
that must be received before marking a link as operational.
If you have a backup WAN connection and Net Link Manager configured, the backup
connection is started and traffic is routed to the backup when this link is dropped. Also, the
backup WAN connection is dropped and traffic is routed to this link when the link is
operational. For information about Net Link Manager, refer to “Configuring Net Link
Manager” on page 749.
Possible values are between 1 and 100 messages.
The default setting is 3.

Expected Status Enquiry Enter the number of events sampled for making decisions about the Missing Status
Enquiry. This value must be set to a higher number than the value set in the Missing
Status Enquiry box.
Possible values are between 1 and 100 messages.
The default setting is 6.
LMI Polling Interval

P0609326 1.1

Enter an interval, in seconds, between LMI status inquiry messages. The polling interval
must be the same as the one used by the frame relay service provider’s switch.
Possible values are between 1 and 100 seconds.
The default setting is 10.

Universal T1 WAN (UTWAN)

167

Table 22 UTWAN frame relay parameters (Continued)
Attribute

Description

Status Enquiry Msg Wait Enter the Status Enquiry Message Wait interval in seconds.
Interval
Possible values are between 1 and 100 seconds.
The default setting is 15.
Fragmentation Status

Select EtoE_Enabled to enable Frame Relay end-to-end fragmentation on this link.
Select Disabled to disabled Frame Relay Fragmentation on this link.
The setting you choose for Fragmentation Status must be the same as the setting on the
other end of the Frame Relay link.
The default setting is Disabled.
Note: If any PVC needs to do fragmentation, you must select EtoE_Enabled for this
parameter and then select the End to End Frag option for that PVC.

Low Water Mark

This is one of the parameters that controls the link layer queuing behavior if link layer
fragmentation is enabled for this PVC.
The possible values are between 1 and 7.
The default value is 6.
Note: Nortel Networks highly recommends that you do not change the Low Water Mark
from the default value.

High Water Mark

This is one of the parameters that controls the link layer queuing behavior if the link layer
fragmentation is enabled for this PVC.
The possible values are between 2 and 8.
The default value is 7.
Note: Nortel Networks highly recommends that you not change the High Water Mark from
the default value.
Note: The high water mark must be larger than the low water mark.

5

Press the Tab key to save the settings.

Configuring the PVC Configuration parameters
You must configure the PVC Configuration parameters for each PVC.

Adding a PVC Configuration record
Follow these steps to add a PVC Configuration record:
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the PVC Configuration tab.
The PVC Configuration screen appears.

4

On the Configuration menu, click Add PVC Configuration.

Business Communications Manager 3.6 Programming Operations Guide

168

Universal T1 WAN (UTWAN)

5

Configure the WAN PVC Configuration parameters according to the information in the
following table.

Table 23 WAN PVC Configuration parameters
Column

Description

Entry (CC#)

Define each PVC Configuration entry on the interface. A PVC Configuration entry must use
the following format: CC#, where the prefix 'CC' is followed by a number. For example,
'CC2' is a valid PVC Configuration entry. Each entry must use a different number. You
must use consecutive numbers when entering PVC Configuration entries. If you do not use
consecutive numbers, the system adjusts them to be consecutive. If you add an existing
entry, the existing entry is modified with new values. When you modify an entry, the name
cannot be changed.

PVCName

Enter a name for this PVC Configuration entry.

DLCI

Enter the Data Link Connection Identifier (DLCI) number for this PVC.

Local IP

Enter the IP address for the PVC.
You must enter the IP address in the dotted format, for example 255.255.255.255.

Subnet Mask

Enter the Subnet Mask for the PVC.
You must enter the subnet mask in the dotted format, for example, 255.255.255.255.

CIR

Enter the committed information rate in Kbps. The CIR is the rate the carrier guarantees
that the router transmits at over a predetermined time interval when congestion is not
present.
The possible values are 0 are 1024.
The default is 64.
Contact your service provider for the correct setting.
Business Communications Manager uses one-second intervals to measure this
parameter.

Excess Burst BE

Combined with the committed burst rate, lets you set, in Kbps, the maximum number of
bits the router transmits over a predetermined time interval if there is no congestion. The
combined value of committed burst and excess burst must be less than or equal to the line
speed.
The possible values are 0 to 1024.
The default value is 64.

DC Retry Time

Enter the Data Compression Retry Time is seconds.
The possible values are 1 to 15 seconds.
The default value is 3 seconds.

DC Retry Count

Enter the Data Compression Retry Count.
The possible values are 1 to 128 retries.
The default value is 10 retries.

Compression

Select RTP Header to enable RTP Header compression on this PVC.
Select Data to enable data compression on this PVC.
Select None to disable compression.

Broadcast

Select Enabled to enable broadcast capability on this PVC. When broadcast is enabled,
broadcast messages are sent out over this PVC.
Select Disabled to disable broadcast capability on this PVC.
The default setting is Disabled.

P0609326 1.1

Universal T1 WAN (UTWAN)

169

Table 23 WAN PVC Configuration parameters (Continued)
Column

Description

End to End Frag

Select Enabled to enable End-to-End Fragmentation on this PVC.
Select Disabled to disable End-to-End Fragmentation on this PVC.
The default setting is Disabled.

Frag Size

Enter the maximum frame size in bytes.
Any packets that have a frame size larger than this value will be fragmented.
The possible values are 200 to 800 bytes.
The default value is 200 bytes.

6

Click the Save button.

Modifying the PVC Configuration settings
Follow these steps to modify a PVC Configuration setting:
1

On the navigation tree, click the Resources key and click the UTWAN Key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the PVC Configuration tab.
The PVC Configuration screen appears.

4

Click the entry you want to modify in the PVC Configuration table

5

On the Configuration menu, click Modify PVC Configuration.
The PVC Configuration dialog box appears.

6

Change the PVC Configuration parameters.

7

Click the Save button.

Deleting a PVC Configuration record
Follow these steps to delete a PVC Configuration record.
1

On the navigation tree, click the Resources key and click the UTWAN Key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the PVC Configuration tab.
The PVC Configuration screen appears.

4

Click the entry you want to delete in the PVC Configuration table.

5

On the Configuration menu, click Delete PVC Configuration.
A message prompts you to confirm the deletion.

6

Click the Yes button.

Business Communications Manager 3.6 Programming Operations Guide

170

Universal T1 WAN (UTWAN)

Configuring the UTWAN to use a PPP link
Configuring the UTWAN to use a PPP link consists of the following:
•
•
•
•

“Configuring the PPP Parameters” on page 170
“Configuring the LCP Options” on page 171
“Configuring the IPCP Options” on page 173
“Configuring the PPP User List” on page 174

Configuring the PPP Parameters
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the PPP Parameters tab.
The PPP Parameters screen appears.

4

Configure the PPP Parameters settings according to the information in the following table.

Table 24 PPP Parameters
Attribute

Description

Compression
Status

Select RTP Header to enable RTP Header compression on this PPP link.
Select Data to enable data compression on this PPP link.
Select None to disable compression.

Fragmentation
Status

Select Enabled to enable fragmentation on this link.
Select Disabled to disabled fragmentation on this link.
The setting you choose for Fragmentation Status must be the same as the setting on the other
end of the PPP link.
The default setting is Disabled.

Fragmentation
Trigger

Select FrameSize if you want Business Communications Manager to use the size of the packet
to decide if the packets need to be fragmented.
Select DelayTime if you want Business Communications Manager to use delay time to decide if
the packets need to be fragmented.

Frame Size

This parameter is only available if you selected FrameSize for the Fragmentation Trigger
parameter.
Enter the maximum frame size in bytes. Any packets that have a frame size larger than the size
specified are fragmented.
Possible values are 160 to 800 bytes.
The default value is 256 bytes.

Delay Time

This parameter is only available if you selected DelayTime for the Fragmentation Trigger
parameter.
Enter the maximum delay time, in milliseconds, for the packets. If the delay time exceeds this
value the packets are fragmented.
Possible values are 10 to 40 milliseconds.
The default value is 10.

P0609326 1.1

Universal T1 WAN (UTWAN)

171

Table 24 PPP Parameters (Continued)
Attribute

Description

Low Water Mark

This is one of the parameters that controls the link layer queuing behavior for PPP when link layer
fragmentation is enabled.
Possible values are 1 to 7.
The default value is 6.
Note: Nortel Networks highly recommends that you do not change the Low Water Mark from the
default value.

High Water Mark

This is one of the parameters that Controls the link layer queuing behavior for PPP when link
layer fragmentation is enabled.
Possible values are 2 to 8.
The default value is 7.
Note: Nortel Networks highly recommends that you do not change the High Water Mark from the
default value.
Note: The High Water Mark must be a larger than the Low Water Mark.

5

Press the TAB key to save your settings.

Configuring the LCP Options
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the LCP Options tab.
The LCP Options screen appears.

4

Configure the LCP Options according to the information in the following table.

Table 25 LCP Options
Attribute

Description

Receive packet
size

Enter the maximum size of the received packets.
Possible values are 64 to 1614 octets.
The default value is 1500 octets.

Authentication
Mode

Specify the Authentication mode used by this link.
Select CHAP if you are using CHAP authentication on this link.
Select PAP if you are using PAP authentication on this link.
Select None if no authentication is required on this link.
The default value is None.

MultilinkMRRU

Enter the maximum number of octets that can be in the information field of the reassembled
packet.
Possible values are 64 to 1614 octets.
The default value is 1500 octets.

Business Communications Manager 3.6 Programming Operations Guide

172

Universal T1 WAN (UTWAN)

Table 25 LCP Options (Continued)
Attribute

Description

MultilinkSSN

Select if you want to receive fragments with short, 12-bit sequence numbers
Select Enabled if you want to receive short sequence numbers.
Select Disabled if you do not want to receive short sequence numbers.
The default value is Disabled.

MultiLinkEDClass Enter the Multilink Class for the Endpoint Discriminator.
Possible values are 0 to 5.
The default value is 1.
MultiLinkEDValue Enter the Multilink identifier address for the Endpoint Discriminator.
LCP Timeout
Value

Enter the number of seconds waited before retransmitting Configure-Request and
Terminate-Request packets.
Possible values are 1 to 60 seconds.
The default value is 3 seconds.

LCP Max
Terminate
Request

Enter the maximum number of Terminate-Request packets sent.
Possible values are 1 to 5.
The default value is 2.

LCP Max
Configure
Request

Enter the maximum number of Configure-Request packets sent.
Possible values are 1 to 15.
The default value is 10.

LCP Max
Configure Nak

Enter the maximum number of Configure-NAK packets sent.
Possible values are 1 to 10.
The default value is 5.

LQ Reporting
Period

Enter the maximum time in 100th of seconds between the transmission of packets.
Possible values are 100 to 60000.
The default value is 1000.

Retry Timer
Timeout Value

Enter the number of seconds waited before retransmitting LCP Configure-Request packets.
Possible value are 30 to 180.
The default value is 60.

5

Press the TAB key to save your settings.

P0609326 1.1

Universal T1 WAN (UTWAN)

173

Configuring the IPCP Options
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the IPCP Options tab.
The IPCP Options screen appears.

4

Configure the IPCP Options according to the information in the following table.

Table 26 IPCP Options
Attribute

Description

IPCP Timeout
Value

Enter the number of seconds waited before retransmitting Configure-Request and
Terminate-Request packets.
Possible values are 0 to 65000 seconds.
The default value is 3 seconds.

IPComp Protocol

Enter the IPComp Protocol.
Possible values are 0 to 65000.
The default value is 0.

IPCP Max
Terminate
Request

Enter the maximum number of Terminate-Request packets sent.
Possible values are 0 to 65000.
The default value is 2.

IPCP Max
Configure
Request

Enter the maximum number of Configure-Request packets sent.
Possible values are 0 to 65000.
The default value is 10.

IPCP Max
Configure Nak

Enter the maximum number of Configure-NAK packets sent.
Possible values are 0 to 65000.
The default value is 5.

5

Press the TAB key to save your settings.

Business Communications Manager 3.6 Programming Operations Guide

174

Universal T1 WAN (UTWAN)

Configuring the PPP User List
You can restrict access to the network using the PPP User List. Business Communications
Manager uses the information on this list to verify and confirm the identity of the user. Only those
users whose names appear on the PPP User List can access the network. The PPP User List
configuration allows you to add, modify or delete an item on the list.

Adding an interface to the PPP User List
To add an item to the PPP Password List:
1

On the navigation tree, click the Resources key and click the UTWAN heading.
The Resources screen appears.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the PPP User List tab.
The PPP User List screen appears.

4

On the Configuration menu, click Add PPP User&Password.
The Interface List dialog box appears.

5

Configure the PPP User List parameters according to the following table.

Table 27 PPP User parameters
Attribute

Description

Entry (PP#)

Enter the PPP User identifier.
The Entry number uniquely identifies an user on the PPP User List. The value for this setting
must follow certain conventions. You must type the prefix 'PP' followed by a unique number
identifying the PPP User. For example, 'PP2' is a valid name. If you specify an existing Entry
number, you receive an error message. If you use non-sequential numbers the system
automatically reassigns sequential numbers. The Entry number does not have any significance,
other than uniquely identifying a PPP User.

Interface Name

Enter the name for the interface. This is the name that is used to identify this specific interface.

Host Name

Enter a name for the remote host.
The host name can be up to 32 characters in length.

PPP User Name

Enter the user name associated with the computer you want Business Communications
Manager to identify as a valid network user.
The User Name can be up to 32 characters in length.
You must overwrite the default user name User with the user name you want to add to the list.

PPP Password

Enter the password you want to assign to the user defined in the PPP User Name box. The
password can contain a combination of lowercase and uppercase letters and numbers.
The Password can be up to 32 characters in length.

P0609326 1.1

Universal T1 WAN (UTWAN)

175

Table 27 PPP User parameters (Continued)
Attribute

Description

PPP Remote User
Name

Enter the user name associated with the computer you want Business Communications
Manager to identify as a valid network user.
The Remote User Name can be up to 32 characters in length.
You must overwrite the default user name User with the user name you want to add to the list.

PPP Remote
Password

Enter the password you want to assign to the user defined in the PPP User Name box. The
password can contain a combination of lowercase and uppercase letters and numbers.
The Remote Password can be up to 32 characters in length.

6

Click the Save button.

To modify an existing item on the PPP User List:
1

On the navigation tree, click the Resources key and click the UTWAN heading.
The Resources screen appears.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the PPP User List tab.
The PPP User List screen appears.

4

Click the PPP User you want to modify.

5

On the Configuration menu, click Modify PPP User&Password.
The PPP User List dialog box appears.

6

Change the PPP User parameters.

7

Click the Save button.

To delete an item from the PPP User List
1

On the navigation tree, click the Resources key and click the WAN heading.
The Resources screen appears.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the PPP User List tab.
The PPP User List screen appears.

4

Click the PPP User you want to delete.

5

On the Configuration menu, click Delete PPP User&Password.
A confirmation dialog box appears.

6

Click the Yes button.

Business Communications Manager 3.6 Programming Operations Guide

176

Universal T1 WAN (UTWAN)

Configuring additional IP addresses for the UTWAN
You can assign multiple IP addresses to a single WAN interface that is configured to use frame
relay. Using this functionality, you can configure the Business Communications Manager as the
hub in a hub and spoke configuration. When Business Communications Manager is the hub or
central site, Business Communications Manager can provide at least two IP address classes on the
primary WAN interface. This allows the system to provide Direct Mode capability.

Examples of uses of multiple IP addresses
•
•

You can use a single WAN physical link to connect to both an intranet and the internet using
separate addressing schemes.
A network service provider can create a separate IP address for management functions over
the WAN interface.

In both of these examples, broadcast traffic destined for one IP address would not be transmitted
on the links associated with the other IP address.

Restrictions when using multiple IP addresses
•
•
•

Nortel Networks does not recommend using more than two IP address classes.
Multiple IP addresses supports RIP routing.
IPSec does not support the use of these multiple IP addresses for Branch Office Local
Endpoint Addresses, Remote Endpoint Addresses or the Destination IP Address for IPSec
VPN Clients

Adding an additional IP address
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the Additional IP Address tab.
The Additional IP Address screen appears.

4

On the Configuration menu, click Add Additional IPAddress.
The Additional IP Address screen appears.

5

Configure the Additional IP Address parameters with the information in the following table.

P0609326 1.1

Universal T1 WAN (UTWAN)

177

Table 28 Additional WAN IP addresses
Attribute

Description

Range (AA#)

Enter the Additional IP Address identifier.
The Range number uniquely identifies an Additional IP Address. The value for this setting must
follow certain conventions. You must type the prefix 'AA' followed by a unique number
identifying the Additional IP Address. For example, 'AA2' is a valid name. If you specify an
existing Range number, you receive an error message. If you use non-sequential numbers the
system automatically reassigns sequential numbers. The Range number does not have any
significance, other than uniquely identifying an Additional IP Address.

IP Address

Enter the Additional IP address of the WAN interface in the following format: 255.255.255.255.

Subnet Mask

Enter the subnet mask of the WAN interface in the following format: 255.255.255.255.
If you do not know your subnet mask address, contact your system administrator or your
Internet service provider.

6

Click the Save button.

Modifying an additional IP address
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the Additional IP Address tab.
The Additional IP Address screen appears.

4

Click the Additional IP Address you want to modify.

5

On the Configuration menu, click Modify Additional IPAddress.
The Additional IP Address screen appears.

6

Change the Additional IP Address parameters.

7

Click the Save button.

Deleting an additional IP address
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

Click the Additional IP Address tab.
The Additional IP Address screen appears.

4

Click the Additional IP Address you want to delete.

5

On the Configuration menu, click Delete Additional IPAddress.
A confirmation dialog box appears.

6

Click the Yes button.

Business Communications Manager 3.6 Programming Operations Guide

178

Configuring a data module

Viewing the UTWAN performance
To access the UTWAN performance graphs and tables:
1

On the navigation tree, click the Resources key and click the UTWAN key.

2

Click the UTWAN1 heading.
The Summary screen appears.

3

On the Performance menu, click UTWAN1 Graph.
The WAN Graph: Statistic Chart appears.

4

On the Performance menu, click UTWAN1 Table.
The WAN Table: Statistic Table appears.

Viewing UTWAN resources
To view the UTWAN resource:
1

On the navigation tree, click the Resources key and click the UTWAN heading.
The Resources screen appears.

Configuring a data module
DS30 bus 08 is reserved for configuring circuit switched B-channels as a WAN interface for the
Business Communications Manager. This allows the Integrated QoS Routing feature to create one
or more dial up ISDN connections via the PSTN network using PRI or BRI trunks. Business
Communications Manager automatically configures the Module type as a Data Module and sets
the Data module type to Baystack. Baystack is the only setting supported on Business
Communications Manager.
This section includes information about:
•
•

“Viewing the data module settings”
“Programming the BayStack settings”

Viewing the data module settings
Use the following procedure to view the current settings for the data module.
1

On the navigation tree, click the Resources key and click the Media Bay Modules key.

2

Click the Bus 08 heading.
The Bus 08 screen appears.

Programming the BayStack settings
When you select the BayStack data module, the following configuration settings appear:
P0609326 1.1

Configuring a data module

•
•
•

179

Line pool access
Line assignment
Interfaces

This section provides information about:
•
•
•
•

“Fixed access” on page 179
“Switched access (PRI & BRI)” on page 180
“Line assignment” on page 180
“Line pool access” on page 181

Fixed access
Fixed access is supported for the Norstar Data Interface (NDI) only. To assign one or more Fixed
lines to the data module:

Adding line assignments
1

On the navigation tree, click the Resources key and click the Media Bay Modules key.

2

Click the Bus 08 key and click the Data Module key.

3

Click the Interfaces key.

4

Click the key of the interface to which you want to assign lines.

5

Click the Line assignment heading.

6

Click the Add button.
Or, right click the Line assignment heading and click Add.
The Add Line assignment screen appears.

7

Enter the number of the Fixed line you need to assign to the interface.

8

Click the Save button.

9

Click the heading for the line you added.

10 Select Unassigned or Assigned.
11 Record each channel and line combination. Each channel used by the BayStack data module
maps to a line.

Deleting line assignments
1

On the navigation tree, click the Resources key and click the Media Bay Modules key.

2

Click the Bus 08 key and click the Data Module key.

3

Click the Interfaces key.

4

Click the key of the interface from which you want to delete lines.

5

Click the Line assignment key and click the heading for the line you want to delete.
Business Communications Manager 3.6 Programming Operations Guide

180

Configuring a data module

6

Click the Delete button.
Or, right click the heading for the line assignment you want to delete and click Delete.
A confirmation dialog box appears.

7

Click the Yes button.

Switched access (PRI & BRI)
You can assign ISDN lines to the BayStack data module to provide:
•
•

normal data network access for the data module
dial-up backup and overflow bandwidth (additional channels or trunks) as needed

Line assignment
You can assign one or more lines to the BayStack data module for incoming data transmission.
Note: The data module will answer data calls only. It will not answer voice calls.

Adding line assignments
1

On the navigation tree, click the Resources key and click the Media Bay Modules key.

2

Click the Bus 08 key and click the Data Module key.

3

Click the Line assignment heading.

4

Click the Add button.
Or, right click the Line assignment heading and click Add.
The Add Line assignment screen appears.

5

In Line box, enter the number of the trunk or a target line you need to assign to the BayStack
data module.

6

Click the Save button.

7

Click the heading for the line you added.

8

In the Dial-in number box, enter the Dial-In Number for the line (up to 24 digits). The
number must match the Dial-In Number entered for the line and channel in BayStack data
module programming.

9

Assign additional lines to the BayStack data module as required.

Deleting line assignments
1

On the navigation tree, click the Resources key and click the Media Bay Modules key.

2

Click the Bus 08 key and click the Data Module key.

P0609326 1.1

Configuring a data module

3

Click the Line assignment key and click the heading for the line you want to delete.

4

Click the Delete button.
Or, right click the heading for the line assignment you want to delete and click Delete.
A confirmation dialog box appears.

5

Click the Yes button.

181

Line pool access
You can give the BayStack data module access to a line pool for outgoing data transmission.

Adding line pool access
1

On the navigation tree, click the Resources key and click the Media Bay Modules key.

2

Click the Bus 08 key and click the Data Module key.

3

Click the Line pool access heading

4

Click the Add button.
Or, right click the Line pool access heading and click Add.
The Add Line pool access screen appears.

5

In Pool box, enter the letter of the line pool to provide access to the BayStack data module.
You must program line pool access when you select the switched access settings for the
BayStack data module. To use PRI line pools, program the BayStack data module to use a
destination code.

6

Click the Save button.

Deleting line pool access
1

On the navigation tree, click the Resources key and click the Media Bay Modules key.

2

Click the Bus 08 key and click the Data Module key.

3

Click the Line pool access key and click the heading for the line pool you want to delete.

4

Click the Delete button.
Or, right click the heading for the line pool you want to delete and click Delete.
A confirmation dialog box appears.

5

Click the Yes button.

Business Communications Manager 3.6 Programming Operations Guide

182

Configuring a data module

P0609326 1.1

183

Chapter 7
Telephony Services overview
The following sections provide a general overview of the Unified Manager Telephony Services
headings. This group of settings is located under the Services heading on the Unified Manager
main navigation tree. The records under this heading allow you to define how the lines and
telephones in your system operate.
Caution: Programming affects system operation.
Only a qualified system administrator should perform startup, installation and
maintenance programming. Many of the settings affect correct system operation.
This overview describes the following general process information:
•
•
•

“Process map: Creating telephony services” on page 185
“Telephony Services headings” on page 186
“Planning your telephony services” on page 188

Planning:

When you are ready to start planning your telephony system, the sections
called “Telephony feature planning” on page 193 provides a quick reference
guide to programming telephony features. Features are divided into sections
based on task, and each feature provides links to the part of the document
where detailed programming information resides.

Using Wizards:

When you need to configure a number of telephones, the Edit DN Record
Template and Add Users Templates wizards provide many of the
programming details for telephone operations in easy-to-apply wizard
applications. Refer to “Configuring DNs using the Wizards” on page 369.

Connecting:

What lines and what type of devices are available to the system is determined
by which media bay modules are active on your system. Refer to Chapter 5,
”Configuring resources — media bay modules” on page 123, and to the
installation charts from the Business Communications Manager Installation
and Maintenance Guide.

Configuring:

The headings under Telephony Services allow you to program and manage
all the voice components associated with Business Communications
Manager. You can set up lines and trunks, define settings for individual
telephones, and customize your telephone network to suit your requirements.

IP telephony:

IP telephones and voice over IP (VoIP) trunk configurations have additional
screens not located under Telephony Services. These screens are located
under Services, IP Telephony. Refer to the IP Telephony Configuration
Guide for details about configuring IP telephones, NetVision wireless IP
telephones, and voice over IP (VoIP) trunks.

Doorphone

The Business Series Terminal doorphone provides an intercom system at
security doors. One or more internal telephones can receive notification from
the doorphone. Refer to the BST doorphone documentation for configuration
details for this piece of telephony hardware.
Business Communications Manager 3.6 Programming Operations Guide

184

Voice mail

If you are using the voice mail application for this unit, you can set up mail
boxes for system telephones as well as for telephones from other systems on
the same private network. Voice mail configuration information is contained
in the CallPilot suite of documents.

IVR

This application allows callers to receive assistance through an interactive
interface. Configuration information is contained in the IVR document.

IP music

Music on hold can be configured either from an external source wired to the
Business Communications Manager equipment, or by using computer-based
music files (IP music). IP music configuration is explained in ........

P0609326 1.1

Process map: Creating telephony services

185

Process map: Creating telephony services
The figure below lists the tasks involved in creating telephony services on your system.
Figure 40 Tasks for installing the telephony components

System
hardware
installed

Identify
installed
modules

Set up
lines, loops,
routes

Set up
call
controls

Refer to the Installation and Maintenance Guides for hardware setup
and wiring for peripheral equipment, including the computer you are
going to use for programming.

After media bay modules are installed, they need to be identified to the
system, so the system can assign lines or DNs. Refer to “Configuring
resources — media bay modules” on page 123.

When the media bay modules are installed, the system automatically
assigns line or loop numbers. You may need to change some of the line
settings. Refer to “Configuring lines” on page 227.

Set up call controls for voice traffic into and out of the system:
“Configuring outgoing calls” on page 301.
“Controlling access into the system” on page 283.
“Configuring public networks” on page 499.
“Configuring private networks” on page 505.

and voice
networks

Voice over IP (VoIP) trunk configuration is contained in the IP Telephony
Configuration Guide.

Set up
telephone
records

DNs define each telephone or piece of equipment connected to the
system. Within the System DNs headings, you can define how individual
telephones will interact in the system. Refer to “Configuring DNs for
system devices” on page 387. IP telephone configuration is contained in
the IP Telephony Configuration Guide.

Confirm
system
settings

A number of settings affect all lines or sets, including System Speed dial
and voice mail access numbers. Most of these settings are default.
However, confirm that they suit your purposes. Refer to “Configuring
system settings” on page 451.

Configure
special
features

After the basic telephony information is set, you can configure the
special features such as Schedules, Hunt groups, Hospitality services,
portable handsets, and voice mail. Portable handsets and voice mail
have separate documentation within the Business Communications
Manager documentation suite.

Business Communications Manager 3.6 Programming Operations Guide

186

Telephony Services headings

Telephony Services headings
The following two figures show the Telephony Services headings in the Unified Manager.
Figure 41 Telephony Services menu options
Telephony Services
System DNs
Active Set DNs
DN XXX-XXX
General
Line Access
Line assignment
Line pool access
Answer DNs
Capabilities
Call forward
Hotline
Intrusion
User Preferences
Button Programming
User speed dials
Restrictions
Set restrictions
Schedules
Line/set restrictions
Telco Features
Active Companion DNs
Active Application DNs
Inactive DNs
Set DNs
Companion DNs
All Inactive DNs
All ISDN/DECT DNs
All System DNs
All System B2s
DN Registration
Active DNs reg’d
Inactive DNs reg’d
All DNs reg’d
DNs avail for reg’d
IP set DNs reg’d
Active
Inactive
Voice port DNs reg’d
Active
Inactive
IP wireless DNs reg’d
Active
Inactive
CTE media DNs reg’d
Active
Inactive
OAM DN reg’d

P0609326 1.1

Lines
VoIP Lines
Enabled VoIP Lines
All VoIP Lines
Physical Lines
Enabled Physical Lines
All Physical Lines
Target Lines
All Lines
Line 001-492
General
Trunk/Line Data
Restrictions
Line Restrictions
Remote
Restrictions
Loops
Loop XXX
SPID
Restriction Filters
Filter 00-99
Restrictions
Restriction 01-XX
Overrides
Override XXX
Call Routing
Routes
Route XXX
Destination Codes
XXX
Schedules
Scheduled Services
Ringing Service
Ring Groups
Ring GroupXXXX
Sets
Restriction Service
Routing Service
Common Settings
Schedule names
Schedule Times
Monday - Sunday
Schedules
System speed dial
General Settings
Feature Settings
SWCA controls
Call Log Space

General Settings ....
Nortel IP Terminals
Feature labels
IP trunking
Timers
Direct dial
Set 1-5
CAP/KIM Assignment
CAP/KIM 1-12
Dialing Plan
Private Network
Public Network
Public DN lengths
Access Codes
Line Pool Codes
Carrier Codes
Remote Access Packages
Package 00-15
Line pool access
COS Passwords
COS 00-99
DN lengths
Received # length
CbC Limits
Pool XXX
Release Reasons
Network Services
ETSI
MCDN
Silent monitor
Hunt groups
Hunt group 01-30
Members
Line assignment
Companion
Registration
Portable DNs
Radio data
Re-evaluation
Radios
Cells
Hospitality
Set/room settings
Call permissions
Alarm Data
Telco Features
Voice message center
ONN Blocking

Telephony Services headings

187

Typical DN record headings
Figure 42 Headings found under typical DN heading
DN XXX-XXX
General
Name
Model/DN type
Device port
Control set
Call log passwords
Line Access
Prime line
Intercom keys
OLI number
Line Assignment
(Line 001)
Appearance type
Appearances
Caller ID set
Vmsg set

Capabilities
DND on busy
Handsfree
HF answerback
Pickup group
Page zone
Paging
Direct dial
Priority call
Auto hold
Aux ringer
Allow redirect
Redirect ring
Keep DN alive
Receive short tones
SM supervisor
Auto hold for
incoming page
Call forward
Fwd no answer to
Fwd no answer delay
Fwd on busy to
Hotline
ATA settings
ATA answer timer
ATA use
Msg indicate
ATA dvc
Intrusion

Line Pool Access
Pool A
Answer DNs

User Preferences
Model
Call log options
Dialing options
Language
Contrast
Distinct rings in use
Ring type
Button programming
External autodial
Blank
Feature/Value
Internal Autodial
User speed dial
Speed dial #
Restrictions
Set restrictions
Set lock
Allow last number
Allow saved number
Allow link
Schedules
Line/set restrictions
Telco features
First display
Auto called ID
Set log space
Available log space

The following table summarizes the Telephony Services subheadings. The headings are arranged
in the order in which they appear under the Telephony Services heading, not necessarily in the
order you would use them to program your system.
Table 29 Telephony Services subheadings

System DNs

Allows you to assign settings to each telephone, including IP telephones.
“Configuring DNs for system devices” on page 387

Lines

Allows you to assign settings to each trunk, including voice over IP (VoIP)
trunks. Target lines are also defined under this heading. Target lines direct calls
to specific sets or groups within the system. “Configuring lines” on page 227,
“Assigning target lines” on page 287.

Loops

Allows you to configure settings for BRI loops. “Configuring BRI Loops” on
page 265

Restriction filters

Allows you to apply restriction filters for external lines. “Defining restriction
filters” on page 344,

Business Communications Manager 3.6 Programming Operations Guide

188

Planning your telephony services

Table 29 Telephony Services subheadings (Continued)

Call Routing

Allows you to define how calls are routed out of your system. “Configuring
call routing” on page 320

Scheduled Services

Allows you to schedule services, such as night ringing, routing and restrictions.
“Configuring schedules” on page 483

System Speed Dial

Allows you to create speed dial codes that can be accessed from any telephone
in the system. “Configuring system speed dial numbers” on page 475

General Settings

Allows you to change system-wide settings. “Configuring system settings” on
page 451

Hunt groups

Allows you to create and manage Hunt groups. “Configuring Hunt groups” on
page 573

Companion

Allows you to assign settings for portable telephones.Companion
configuration is described in the Companion Configuration Guide.

Hospitality

Allows you to assign Hospitality settings. “Configuring Hospitality Services”
on page 589

Telco Features

Allows you to assign settings for external voice message services. “Setting
system telco features” on page 478

Planning your telephony services
Nortel Networks strongly recommends that you use the planning tables from the Installation and
Maintenance Guide or the Programming Records spreadsheets to understand what lines and set
numbers (DNs) are available to you. Programming records, which are set up in Microsoft Excel*,
provide a reference for your system programming. These forms are located on the documentation
CD.
Coordinate this information with call planning to assess your system requirements (“Telephony
feature planning” on page 193).
Chart this information to determine how to set up your lines and telephones. “Three basic system
telephony configurations” on page 189 provides examples of three basic, single-office,
configurations on which you can base your planning.
DN lengths and the Start DN are identified during initialization of the system, when you run the
Quick Start Wizard. Ensure these settings are correct before you do any other programming. This
is especially important if your system is part of a network, where your DN length and numbering
plan must match that of the other systems in the network.
The Programming Records are divided into three sections:
•
•
•

Start-up forms for system programming
Data forms for the protocols you use to connect your Business Communications Manager to
your business network
Telephony forms, which you fill out for your system telephony configuration.

P0609326 1.1

Planning your telephony services

189

Three basic system telephony configurations
This section provides a broad overview of the telephony setup for three of the most common office
telephone configurations.

Square system
This is a typical small-office setup, where all lines are available on any telephone. There may not
be a designated attendant.
Figure 43 Square system

Assigned all four lines/
appearance only

CO line 1
Assigned all four lines/
appearance only

CO line 2
CO line 3
CO line 4

Assigned all four lines/
appearance only

Receptionist (optional)
Assigned all four lines/
appearance and ring

Incoming calls
1

Call comes in on a line.

2

Call rings and flashes at the Reception telephone (flashes, but no ring, on other telephones).

3

Receptionist answers and finds out who the call is for.

4

Receptionist calls or pages the person and tells them what line to pick up.

5

The person can pick up the call at any of the telephones.

Outgoing calls
1

User selects a line button and dials the number.

Business Communications Manager 3.6 Programming Operations Guide

190

Planning your telephony services

PBX system
This setup is for a larger offices which have fewer CO lines than there are telephones. In this case
the lines are pooled, and the line pool is assigned to all telephones. As well, there is a designated
attendant with a telephone that has all lines individually assigned.
Figure 44 PBX system

Lines are assigned to a line pool

CO line 1
CO line 2
All telephones
are assigned
access to the line
pool for
out-going calls

CO line 3
CO line 4

Receptionist
Assigned all lines/
appearance and ring

Incoming calls
1

A call comes in on a line.

2

The receptionist answers the call and finds out who the call is for.

3

The receptionist transfers the call to a specific telephone (DN).

4

The person can pick up the call at that telephone only.

Outgoing calls
1

User selects the intercom button or dials a line pool access code, which selects a line in the line
pool.

2

The user dials the outgoing CO number.

P0609326 1.1

Planning your telephony services

191

DID system
This setup allows you to assign a dedicated phone number to each telephone. The CO assigns a list
of available numbers for each DID (Direct Inward Dial) line. You can change your DN range to
match these numbers, or you can use target lines to match each number with a DN.
Figure 45 DID system

Target line mapped to
DN (4005)

CO DID line i.e. 769
with range of call
numbers (i.e. 4005 to
4020)

Target line mapped to
a DN (4006)

Target line mapped to
DN (4007)

Target line mapped to
DN (4008)

Incoming calls
1

DID trunks are assigned to be auto-answer.
Note: PRI and BRI lines are automatically set to auto-answer.

2

All telephones are assigned target lines.

3

A caller dials a system code and a DN. In the example shown above, it might be 769-4006.

4

The call comes into the trunk, which answers and forwards the call on the target line assigned
to that number.

5

The telephone assigned to that target line rings.

You can assign unanswered or busy telephones to Call Forward to a prime set, if you have a
designated attendant, or to a voice mail system.

Business Communications Manager 3.6 Programming Operations Guide

192

Telephony metrics

Telephony metrics
The system provides call metrics for Hunt groups (“Monitoring Hunt groups” on page 585), PRI
Call-by-Call services limits (“Viewing CbC limit metrics” on page 343), and IP telephony fallback
(IP Telephony Configuration Guide).

P0609326 1.1

193

Chapter 8
Telephony feature planning
This section provides a quick reference to telephony programming basics, which you need to
understand before you can decide what defaults you want to change, and how you want to
configure your telephones and routing.
•

Understand how to plan system numbering strings and codes
“Creating numbering plans” on page 194. It is important that you understand how calls get
directed out of your system and accepted into the system. In a stand-alone system, only PSTN
routing may be required (“Configuring public networks” on page 499). For systems on a
private network, more complicated numbering plans and routing may be required
(“Configuring private networks” on page 505).

•

Understand how the system features work to provide call function. This section provides an
overview of the various call features that are programmed through the Unified Manager. The
features are divided into task categories, or categories of similar features. Each feature
includes a link to the specific programming section.
Refer to your Telephony Features Handbook for information about using these features and to
view the display prompts and error prompts for the features.
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—

“Name a telephone, a line or a Hunt group” on page 200
“Programming line access” on page 202
“Answering calls” on page 205
“Make a call” on page 209
“Handling calls” on page 212
“Communicating in the office” on page 216
“Using handsfree and mute” on page 218
“Track your incoming calls” on page 218
“Use alternate or scheduled services” on page 220
“Special telephones” on page 220
“Auxiliary devices” on page 221
“Call out to external systems using host system dialing” on page 222
“Call in from outside the system” on page 224
“Controlling telephone programming access” on page 224
“Special features” on page 225

Not all features require programming; for example, if they are a default function of the system.
Refer to Appendix B, “System Features,” on page 861 for a comprehensive list of the features that
are available on a fully-configured system.

Business Communications Manager 3.6 Programming Operations Guide

194

Creating numbering plans

Creating numbering plans
Access to and from and within your system is based on dialing strings and how the system adds or
deletes from this sequence to route the call. A dialing string is the numbers that the caller
physically enters on a telephone or programs onto a memory key. This can also include numbers
the system adds to a dial string when a call goes through call routing. This process also includes
how the receiving system reads the sequence. All of which means that coordination is required at
both ends of the call to ensure that calls are routed correctly. This is especially important if calls
need to be routed through your system, or through a remote system, to reach another node on the
network. Refer to “Creating tandem private networks” on page 520.
The system performs some number programming checks on the initial digits of a dial string, such
as for access codes. However, dial strings can contain more than one imbedded code, therefore, it
is important that your dialing plan dials out the segments in the correct order. Refer to “Outgoing
calls” on page 197.
Basic numbering: The first numbering that you set is your DN length (Start DN length) and Start
DN and Public and Private Received # length. DN length and Start DN information is entered
when the Quick Start Wizard runs at system setup. These numbers can be changed after the system
has been set up, but only at the risk of compromising other numbering in the system. If your
system is part of a network, these numbers must be coordinated with the other nodes in the
network to ensure that the network dialing plans are consistent. Refer to “Incoming calls” on page
198.
For detailed information about the Quick Start Wizards, refer to the wizards help. For information
about private networking, refer to Chapter 19, “Configuring private networks,” on page 505.
Variable

Example settings

Start DN

2 (221)

DN length, Received # length
Private length
Public length (max)

3
10 (North America)

Remote call-in: When you set up lines that do not offer DISA directly on the line, you can
determine if remote access prompts with DISA or allows auto answering. This determines the
Public/Private Auto DN and Public/Private DISA DN settings, which are set under Services,
Telephony Services, General settings, Access codes. These numbers will have the same first
number as you specified in the Start DN and be of the same length. Remote callers dial the system
public or private access number, and then dial either the Private/Public Auto DN or Private/Public
DISA DN, as determined by the line setup.
Variable

Example or default settings

Private Auto DN

2XX

Public Auto DN

2XX

Private DISA DN

2XX

Public DISA DN

2XX

P0609326 1.1

Creating numbering plans

195

Incoming calls: If your system is networked with other systems, you will also need to determine a
private access code that tells your system when a call is to be dialed out over the private network
instead of over the public network. This access code is also entered under Services, Telephony
Services, General settings, Access codes. This code is included as part of any destination code or
dialing sequence that is to be routed over the private network.
Variable

Example or default settings

Private Access Code

6

MCDN special call types: If your system is networked to other types of systems, such as
Meridian 1, which sends calls through one or more Business Communications Manager systems to
the public network, you need to specify specific call-type codes. These codes append to the
incoming dial string, so that the call-type remains intact as it passes through the Business
Communications Manager call processing:
Variable

Example or default settings

Local Access Code

9

National Access Code

61

Special Access Code

911

Coordinate these settings with Meridian
routing for these calls types and the Private
Access Code.

Calls coming in over private networks or PRI/BRI lines can either terminate at one telephone,
called the prime telephone, or target lines can be set up for each telephone or group of telephones
to which the calls are directed. As with other incoming calls, these calls can have a public or
private call type that matches to a public or private received number assigned to a target line.
Variable

Example or default settings

Private received number




Public received number




Outgoing calls: Other network codes include the information about private and public dialing
codes that you enter under Services, Telephony Services, General settings, Dialing Plans
Variable

Example or default settings

Private network ID

Number that identifies the system as part of the private network

Location code

UPD networks

Private DN length

DPNSS systems only

Public DN lengths (prefixes)

Public dialing table

Business Communications Manager 3.6 Programming Operations Guide

196

Creating numbering plans

Internal feature access: Meanwhile, you need to keep in mind that the leading digit of any of the
above dialing codes cannot conflict with the other system access codes that you want to use:
Variable

Example or default settings

Park Prefix

1 (101-125)

Direct Dial Digit

0

Line pool and destination access codes: Once these basic numbers have been picked, you can
decide what numbers to use for line pool access codes and/or destination codes. The system will
not allow these codes to start with any of the numbers currently assigned. If you are working with
an established system of dialing, you may want to ensure that the numbers that the users are
familiar with dialing are reserved for these codes.
For instance, if the users are familiar with dialing 9XXXXXXX to access numbers outside of their
own offices, you will want to reserve this number for the destination codes. If you are setting up a
new system, you could opt to use the location codes of the other systems as destination codes, or
you could define one number for local calls (but which are still outside the system) and one
number for long haul calls. For example: The users may dial 6 for calls within a
local system, but dial 8 for calls in another city over the public network.
Variable

Example or default settings

Line pool codes (first character)

5

Destination codes (first character)

6
9

Analog telephones require a code to dial out of the system, since the intercom button only accesses
the internal system. The external access code may be the same as a line pool code, in which case,
the line pool code overrides this setting.
Variable

Example or default settings

External code

9

P0609326 1.1

Creating numbering plans

197

Outgoing calls
Outgoing calls require line pool access codes or destination code (with defined routes) to leave the
system.
•

Access codes provide direct, unscheduled access to an analog, digital (T1), of Voice over IP
(VoIP) line pool. Refer to “Programming access codes” on page 310.

•

Destination codes also provide access to line pools, but they also allow more flexibility in
dialing, which allows for more complex routing options, such as scheduling, fallback routing
(VoIP trunks), call definition, and multiple routing (least-cost routing). Routing also allows
you to minimize the dialout for the user, especially to systems on the same private network.
Refer to “Configuring call routing” on page 320.

Outgoing calls can be either public or private, which is defined by the route. The public or private
designation determines which dialing plan is used to determine the validity of the call. Normally,
public calls are routed over PSTN trunks and private calls are routed over a private network.
However, MCDN trunks can also pass calls designated as public to allow remote nodes on the
network to call out of the PSTN of a local node. This is called tandem dialing. Refer to “Outgoing
private calls routing” on page 305, “Outgoing public calls routing” on page 307 and “Using the
MCDN access codes (tandem calls)” on page 315.
•

If the outgoing call is designated as private, the system checks the beginning of the string for a
destination code that routes to a private network. It also checks that the dial string is the correct
length. The destination code routing determines what the final dial out string will be, adding or
removing digits, as required.

•

If the outgoing call is designated as public, the system checks the beginning of the string for a
destination code that routes to a PSTN or an MCDN trunk. If the call routes to a public route,
the system checks the public dialing table to ensure that the dialout string has legitimate
leading digits and is the correct length. If the call routes to an MCDN trunk, the call is passed
as dialed, minus the private networking codes. The call will pass through the system until the
system with the matching destination code receives it, at which point it will be sent through the
local PSTN of that system.

Business Communications Manager 3.6 Programming Operations Guide

198

Creating numbering plans

Incoming calls
Incoming call handling also depends on the call type. The system also uses the Public and Private
DN # length settings to determine call handling. Refer also to “Defining DN length” on page 284.
The system processes a call in the following way:
1

The system receives a call from the public or private network.

2

The system identifies the call type:
Public calls:
•
•
•
•

If the call is from the MCDN network and is a local, national, or special call type, the
system prepends the appropriate access code.
If the call is from ETSI-QSIG, MCDN, NI, DMS100, DMS250) and tagged as
Private/Subscriber, the system prepends the Private access code, if the dialing plan is UDP.
If the call is tagged as Unknown/Unknown or Private/Unknown (ETSI-QSIG, MCDN, N1,
DMS100, DMS250 trunks), no access code is added.
For all other call types, the system truncates the trailing digits to the Public Received #
Length. (Go to step 5)

Private calls:
•
•

If the call is tagged as Private/Subscriber or Private/UDP, the system prepends the Private
access code.
If the call is tagged as Private/CDP, no access code is added.

3

The system tries to match the first digit(s) of the dial string to a destination code. If the digit(s)
matches, the dial string is routed out of the system.

4

If the system cannot match the first digit(s) to a destination code, it truncates the trailing digits
to the Public Received # length or Private Received # length, as appropriate to the call type.

5

The system again tries to match the leading digit(s) to a destination code. If the digit(s) match,
the dial string is routed out of the system.

6

If the system cannot match the first digit(s) to a destination code, the system tries to match the
dial string to a target line (Public or Private Received Number). If the dial string does not
match any target lines, the call is routed to the prime line.

Refer to the figure below for a graphic illustration of incoming call processing.

P0609326 1.1

Creating numbering plans

199

Figure 46 Incoming public and private call coding

Call
comes in

System checks call type
Public
Default incoming
call handling

Private

MCDN Local/
National/Special

Unknown/Unknown
or Private/Unknown

Private/Subscriber
or Private UDP

Prepend
appropriate
access code

Private/CDP

Prepend private
access code

Match Dest. code?

Yes

No
Truncate digits to Public Received # length/Private Received # length

Match Dest. code?

Call routed
out of the
system as a
tandem call

Yes

No

Match Public/Private
Rx digits?

Yes

Call
routed to
target line

No
Call
routed to
Prime set

Business Communications Manager 3.6 Programming Operations Guide

200

Name a telephone, a line or a Hunt group

Name a telephone, a line or a Hunt group
You can assign names to identify external lines, target lines, and your colleagues’ telephones.
During a call, the name (if programmed) appears on the telephone display instead of on the
external line number or internal telephone number of the caller.
Names can contain both letters and numbers, but cannot be longer than seven characters. You
cannot use the # and * symbols.
Note: You can give the same name to a telephone and a line in your system. Use initials,
abbreviations, or even nicknames to give each telephone a unique name to avoid confusion.
Programming:
•

Name a line/target line: “Using the General record” on page 235
(Services, Telephony Services, Lines)

•

Name a telephone: “Identifying the telephone (General heading)” on page 391
(Services, Telephony Services, System DNs)

•

Name a hunt group: “Identifying a Hunt group” on page 575
(Services, Telephony Services, Hunt Groups)

•

Determine what displays first: “Configuring telco features” on page 445 (First
display)

You can also determine if the calling line ID (CLID) is received by a telephone, or if the CLID
information from a system telephone gets sent out over the network. Refer to “Incoming and
outgoing call display” on page 201.

Naming components in the system
K9 Unit
5553465
K9 Unit
Trunks

Target line

K9help
Hunt group

P0609326 1.1

Public or
Private
network

Incoming and outgoing call display

201

Incoming and outgoing call display
If you subscribe to Call Display services from your local telephone company, one line of
information about an external caller appears on the display after you answer a call. If you answer
before the Call Display information appears on your display, press FEATURE 811 to view the
line number or line name. When you transfer an external call to another telephone in your system,
the same information appears on the recipient telephone display.
Depending on the services you subscribe to, incoming Call Display information can contain up to
three parts:
•
•
•

the name of the caller
the number of the caller
the name of the line in your system that the call is on

Call display information can also be sent out when a system telephone calls out of the system.
What displays at the called party’s telephone, depends on what the private or public lines allow.
Outgoing call display information can be allowed or blocked at the system level or single
telephone level.
For each telephone, you can determine which information appears on the display first.
Programming:
•

Lines: Determine which telephones display incoming CLID for an analog line or that
provides CLID (ASM8+ module), or for a target line: “Determining line
assignments” on page 397. (Caller ID set)

•

Lines: Determine which PRI or BRI modules will allow outgoing CLID:
“Configuring the trunk module to line type” on page 131. (Send name display)

•

Loops: Determine which BRI modules will allow outgoing CLID (QSIG trunks,
only): “Identifying BRI T-loops (ETSI, QSIG)” on page 271. (Send name display)

•

VoIP trunks: Determine which VoIP trunks will allow outgoing CLID (Services,
Telephony Services, General settings, IP trunking). (Send name display)

•

Incoming call display, alpha tagging: Program a name to appear as call display when
a call comes in on an analog line that supports number-only CLID, or on target lines.
Refer to “Using alpha tagging for name display” on page 455.

•

System: Determine whether name, line number, or system number appears first on
the telephone display: “Configuring telco features” on page 445.

•

Outgoing call display, telephones: Determine what number is displayed to a
destination telephone when a call is made from a system telephone to a telephone on
the private or public network: “Configuring line access” on page 393. (Public and
Private OLI)

•

Determine the system-wide name that displays for calls made to external numbers:
“Programming Business name display” on page 455. FEATURE 819 blocks call
display for an outgoing call.

Business Communications Manager 3.6 Programming Operations Guide

202

Programming line access

Sending and receiving call display
DogFood
5556897
5553465

Business name
display: RCMP

K9 Unit
5552354

*Public or
Private
network

*Trunks

RCMP K9 Unit
5552354

Incoming Name, Number, Line display
Outgoing Name display

DogFood
5556897

Programming line access
There are a number of ways you can configure your lines. You can assign each line to each
telephone, or a specific line to a specific telephone. You can also pool your lines so that a number
of telephones have access to several lines.
This section contains the information split into these sections:
•
•
•

“Making lines available” on page 202
“Incoming calls” on page 204
“Outgoing calls” on page 204

Refer to “Three basic system telephony configurations” on page 189 for examples of line settings
for three common types of systems.

Making lines available
•

You can determine whether a line will be assigned solely to one telephone, or if a group of
users will have access to the line.

•

Even when you use line pools, it is possible that a line pool will be unavailable for outgoing
traffic. To alleviate this, you can determine overflow paths for any routes that you designate.
Refer to “Using multiple routes and overflow routing” on page 336 for more information
about overflow routing.

•

Incoming lines can be assigned to telephones as individual lines or through target lines,
depending on the type of trunk supplied from the central office (CO). Incoming lines do not
need to have an appearance on the telephone. Target lines are for incoming calls only.
Two-way single lines, such as analog lines, allow the user to make an outgoing call by

P0609326 1.1

Programming line access

203

pressing the (idle) assigned line button or, if the line is part of a line pool, by entering a line
pool access code or destination code to access the line pool. These lines can also be redirected
on a per-trunk basis or from the telephone by using FEATURE 84.
•

PRI lines are always configured into line pools. These lines require a destination code for
outgoing calls. Incoming calls use target line assignments.

•

Voice over IP (VoIP) trunks use the data network to provide line service in and out of the
system. VoIP trunk configuration is described in the IP Telephony Configuration Guide. VoIP
trunks use target lines for incoming calls, and require line pool codes or destination codes for
outgoing calls.

•

You can assign a line a maximum of 93 times.

Programming:
•

Creating dialing plans: “Configuring the public and private dialing plans” on page
302

•

Setting up the modules for the trunks: “Defining trunk module types and settings” on
page 130

•

Creating restriction filters: “Defining restriction filters” on page 344.

•

Creating line pools and redirecting lines: “Assigning Trunk/line data” on page 236.

•

Creating line pool codes: “Setting up line pool access codes” on page 317.

•

Creating routes and destination codes: “Configuring call routing” on page 320.

•

Creating scheduling for routes, ringing groups and restrictions: “Configuring
schedules” on page 483.

•

Assigning lines and line pools to telephones: “Assigning lines to telephones” on
page 398, “Assigning line pool access” on page 402.

Business Communications Manager 3.6 Programming Operations Guide

204

Programming line access

Incoming calls
For incoming calls, you can have a central reception point, or you can specify target lines to one or
more telephones to receive directed calling.
You can arrange your telephones in Hunt groups, ringing groups, or call groups that use
system-wide call appearance (SWCA) assignments to share calls.
You can also configure lines for use by system users who call in from outside the system. You can
give them direct access to the system with an Auto DN, or you can configure the line so they hear
a stuttered dial tone, at which point they need to enter a password (COS) to gain access (DISA
DN). Refer to “Call in from outside the system” on page 224.
Programming:
•

Assigning lines to telephones: “Determining line assignments” on page 397.

•

Creating and assigning target lines (PRI and VoIP trunks): “Target lines and DASS2
fields” on page 247 (configuring target lines) and “Received #” on page 259
(received #, if busy); “Assigning target lines” on page 287; “Configuring line
access” on page 393 (appearances).

•

Creating direct-dial telephones: “Creating Direct Dial sets” on page 313.

•

Configuring Hunt groups: “Adding a Hunt group member” on page 579.

•

Configuring and scheduling ringing groups: “Defining ring groups” on page 490.

•

Creating a group using SWCA keys: “Configuring system-wide call appearance
groups” on page 462.

•

Setting up users and remote access packages to support calling in from outside the
system into the system: “Configuring for remote access” on page 291

•

Refer to the Call Center documentation for information about setting up call centers.

Outgoing calls
For outgoing calls, you can assign one or more intercom keys to directly link to a line pool or
prime line, or allow line pool access codes, destination code, or internal system numbers to direct
the call. Telephones without intercom keys on the telephone, still have intercom keys assigned, but
to access calls, they must pick up the handset to connect. In this case, the intercom key is
Calls within the system: All telephones are virtually linked within the system. To call another
telephone inside the system, you can lift the handset and dial the local DN. In this case, the prime
line has to be set to intercom or none.
Calls going outside the system:

P0609326 1.1

Answering calls

205

•

If you assign the prime line to a line pool, all the lines in that line pool must be assigned to the
telephone. When you pick up the handset, the telephone automatically grabs the first available
line from the assigned line pool. In this configuration, you must ensure that the outgoing
number is allowed by the line pool.

•

If you assign the prime line to an intercom button, when you press the intercom button you get
system dial tone. Then, you enter a line pool access code or a destination code to direct the
outgoing call to the appropriate line pool, where it exits the system on any available line in that
pool.

Programming:
•

Creating restriction filters: “Defining restriction filters” on page 344.

•

Creating line pools and redirecting lines: “Assigning Trunk/line data” on page 236.

•

Creating line pool codes: “Setting up line pool access codes” on page 317.

•

Creating routes and destination codes: “Configuring call routing” on page 320.

•

Assigning prime lines, intercom keys, and outgoing number display to each
telephone: “Assigning line access” on page 394.

•

Assigning lines and line pools to telephones: “Determining line assignments” on
page 397, “Assigning line pool access” on page 402.

•

Creating scheduling for routes, ringing groups and restrictions: “Configuring
schedules” on page 483.

Answering calls
Incoming calls do not have to both appear and ring at a telephone. They can be programmed to
only show an appearance on a line or intercom button. They can also be programmed to only ring.
How a call alerts at a telephone is determined when you assign lines to each telephone. “Assigning
lines to telephones” on page 398.
This section contains information about:
•
•
•

“Distinctive ring patterns” on page 205
“Centralized and group answering” on page 206
“Pick up features” on page 207

Distinctive ring patterns
There are four Distinctive ring patterns (DRP) that can be assigned to lines, telephones, or Hunt
groups to differentiate incoming calls on telephones where Ring has been allowed:
DRP 4

Highest priority

DRP 3

2nd highest priority

Business Communications Manager 3.6 Programming Operations Guide

206

Answering calls

DRP 2

3rd highest priority

DRP 1 (or None) (default)

Lowest priority

Call Ringing: When more than one call rings at a telephone, highest priority DRP rings first.
Hunt groups: If the Hunt Group DRP is higher than the DRP of line of the incoming call and the
telephone DRP, all telephones in the group will ring with the ring pattern assigned to the Hunt
Group.
Note: External calls have a higher priority than internal calls. You cannot press FEATURE *6 to
change the ring type on a telephone when the Distinctive Line Ring feature is in service. When the
call is finished, your telephone reverts to the ring you set.
Programming:
•

Lines: “Assigning Trunk/line data” on page 236 (Services, Telephony Services,
Lines)

•

Telephones: “Defining user preferences” on page 415 (Services, Telephony Services,
System DNs,)

•

Hunt groups: “Identifying a Hunt group” on page 575 (Services, Telephone Services,
Hunt groups)

Centralized and group answering
•

Prime telephone: The prime telephone is usually the monitored telephone in a reception area
or at the desk of the designated attendant. Calls not answered at their normal destinations
transfer to the prime telephone. Business Communications Manager allows for a prime
telephone for each line, if needed.
Programming:

•

•

Lines: “Assigning Trunk/line data” on page 236

•

Telephones: “Assigning line access” on page 394

Central answering position (CAP station): A CAP can consist of a BST T7316E plus one to
four eKIMs (key indicator modules) or one to nine OKIMS, or a M7324(N) plus one or two
CAP(N)s (Central Answer Position modules). When the CAP is assigned under CAP/KIM
assignment in the Unified Manager it becomes an enhanced CAP (eCAP). The T7316E
modules become known as eKIMs.
An eCAP can monitor system telephone status, answer external calls on line buttons, and send
up to 30 messages to other system telephones. Additionally, the eKIMs can monitor Hunt
group appearances and support multiple appearances of a target line. You can configure a
maximum of 12 telephones as eCAPs on each Business Communications Manager. One eCAP
station can be designated as the prime telephone and direct-dial telephone for the system lines

P0609326 1.1

Answering calls

207

and telephones.
Telephones with KIMs or CAP modules that are not configured in system programming allow
only memory button programming on the modules. In this case, the KIM is known as an
OKIM (ordinary KIM).
Programming:

•

•

“Identifying the telephone (General heading)” on page 391

•

“Configuring CAP/KIM assignment” on page 436

•

“Programming CAP/KIM buttons” on page 438

Hunt groups: This feature allows you to create groups of telephones that are assigned to a
single DN. This provides the capacity for call groups that are dedicated to specific products or
projects, and provides the flexibility of determining how the calls will be presented to the
group.
Programming: “Configuring Hunt groups” on page 573

•

Ringing groups: If you set up call scheduling on the system, you can define groups of
telephones into ring groups, which allows you to specify schedules where Trunk Answer can
be used within the ring group to answer incoming calls, even on telephones which do not have
that line specifically assigned. You can also define a second direct dial set for a ringing group.
Programming: “Configuring ringing service” on page 490

•

Other options: There are optional applications which allow you to set up service centers and
customized mailboxes. These are described in the CallPilot documentation suite.

Pick up features
There are a number of features you can use to pick up calls, including calls that do not come
directly to your line buttons:
•

Call Queuing: This feature code (FEATURE 801) allows you to answer the next incoming
call. The feature selects the call with the highest priority, if there are a number of calls arriving
at the same time. Call Queuing answers incoming external calls before callback, camped, and
transferred calls. There is no programming for this feature.

•

Directed Pickup: This feature allows a user to answer any telephone that is ringing in the
system.
Programming: “Programming Feature settings” on page 457

Business Communications Manager 3.6 Programming Operations Guide

208

Answering calls

•

Group Pickup: Your system can support nine pickup groups. If a telephone has been assigned
as a member of a pickup group, the user can pick up a call that is ringing at any telephone in
the pickup group (FEATURE 75).
Programming:

•

•

“Configuring the Capabilities features” on page 406

•

“Configuring ringing service” on page 490

Trunk Answer: By pressing FEATURE 800 the user can answer a ringing call in any area in
the system from any telephone in the system. The line being answered does not have to appear
or ring at the telephone being used to answer the call. This feature is only active when a
ringing service schedule is running.
Programming:

•

•

“Configuring ringing service” on page 490

•

“Turn services on and off” on page 484

Answer DNs: Telephone DNs can be assigned to indicator buttons on other telephones to
provide backup answering. The indicator buttons on your telephone that are assigned to
answer DNs are called answer keys. You can assign a maximum of eight answer DNs to a
telephone. You cannot assign Answer DNs to analog telephones or Model 7000 or 7100
telephones.
On the answer telephone, an indicator beside the answer key lights when a call comes in from
the original telephone. When the call is answered, the indicator disappears on the
non-answering telephone, freeing that line for another call. You can also determine which calls
alert at Answer DNs (Answer key access levels).
For systems running BCM 3.6 and newer software, the Answer DN can be used as an autodial
button to the assigned telephone.
On systems running BCM 3.5 and newer software, if call logging is set, then calls received
through Answer DN are logged at the receiving telephone that picks up the call.
Programming:

•

•

Answer DNs: “Assigning Answer DNs” on page 403

•

Answer Keys access levels: “Programming Feature settings” on page 457

Listen to a call as a group: This feature (FEATURE 802) allows more than one person to
listen to a telephone, without the caller hearing everyone in the group (the handset is offhook).

P0609326 1.1

Make a call

209

Make a call
You can set up your system in several ways that will determine how users can make calls.
This section includes:
•
•
•
•
•

“Emergency 911 Dialing” on page 210
“Select how you dial your calls” on page 210
“Receive a busy signal on an internal call” on page 210
“Create a conference call” on page 211
“Time-saving features” on page 211

Some of the ways you can set up the system and the telephones to make calls includes:
•

You can assign every line to every telephone, in which case, the user presses a line button or
intercom button to dial out a call.
Programming: “Assigning line access” on page 394

•

You can assign lines to pools (Line pool A to O and PRI pool A to F) and assign the pools to
all telephones. To make a call over line pools, users use the line pool feature code (FEATURE
64) and then enter a line pool access code.
Programming:

•

•

“Assigning Trunk/line data” on page 236

•

“Setting up line pool access codes” on page 317

You can assign line pools to routes and assign the routes with destination codes. To make calls
with destination codes, the user enters the destination code, and then dials out the required
digits to contact the destination telephone. The digits the users dial will depend on what the
destination code is, and what dial-out digits have been specified within the route record.
Note: All PRI line pools must be accessed through routes, using destination codes.
Programming: “Configuring call routing” on page 320

•

If a prime line is specified for the telephone, the telephone will automatically dialout on this
line if an intercom button is pushed, or the handset is picked up.
Programming: “Assigning line access” on page 394

•

Auto dial: You can program an internal or remote dialout string onto a memory key. When the
user presses the key, the system automatically dials the digits stored on the button.
Programming: “Configuring buttons from the DN record” on page 420

Business Communications Manager 3.6 Programming Operations Guide

210

Make a call

Emergency 911 Dialing
Emergency 911 dialing is the capability to access a public emergency response system. State and
local requirements for support of Emergency 911 dialing service by Customer Premises
Equipment vary. Ask your local telecommunications service provider about compliance with
applicable laws and regulations.
Emergency 911 dialing may not apply to International systems.
IP telephones: If you allow this service on IP telephones that are installed or used off-site, you
must ensure that the 911 telephone number is not mapped to the system address in the emergency
response system.

Select how you dial your calls
The system digital telephones provide three methods for dialing calls:
•

Standard dial: allows you to make a call by selecting a line and dialing the number. If you
have a prime line, it is selected automatically when you lift the handset or press the handsfree
button.

•

Automatic dial: allows you to dial a number without selecting a line. Your prime line is
selected when you start dialing a number. Your Prime line must be free to make a call.

•

Pre-dial: allows you to enter a telephone number, check it, then change it before making the
call. The call does not dial until you select a line or line pool, or pick up the handset. You can
pre-dial both external and internal numbers. You must, however, select the correct type of line
(external or internal) for the type of number you have entered.
Programming: “Defining user preferences” on page 415

Receive a busy signal on an internal call
When the internal number you dialed is busy, there are three possibilities:
•

Priority Call: You can use this code to override a busy signal or Do Not Disturb.
Programming: “Defining device capabilities” on page 405. (FEATURE 69)

•

Ring Again: You can use this code to tell you when a telephone you want to call is no longer
busy or when a line pool becomes available. (FEATURE 2)
Programming: There is no system programming to allow/disallow this feature.

•

Message: Use this code to leave a message on the display of the telephone you are trying to
call. (FEATURE 1)
Programming: There is no system programming to allow/disallow this feature.

P0609326 1.1

Make a call

211

Create a conference call
You can establish calls to two people at the same time, and allow each caller to hear the other two
callers. You must have at least two intercom buttons assigned to your telephone to initiate a
conference call (FEATURE 3).
The person who establishes the conference call, has several options available to provide control
within a conference call.
•

remove callers temporarily (put on Hold), or permanently

•

split the conference into two separate calls

•

leave the conference, and allow the other two callers to remain connected
Programming: “Assigning intercom (I/C) buttons (keys)” on page 396

The Telephony Features Handbook describes the feature codes and the dial pad actions that are
required for controlling conferences.

Time-saving features
There are a number of features that allow you to save time when dialing, including:
•

Autodial: You can program memory buttons for one-touch dialing of internal or external
telephone numbers. When you program an external autodial, you must specify a path out of
the system.
Programming: “Programming telephone buttons” on page 419

•

Last Number Redial: This feature (FEATURE 5) allows the user to redial the last external
number that was dialed from that telephone. This feature records a maximum of 24 digits.
Programming: “Programming restrictions for DNs” on page 441 (allow or disallow feature)

•

Speed dialing: Business Communications Manager provides two types of speed dialing:
— System Speed Dial programming allows you to assign two or three-digit speed dial codes
to the external numbers called most often. You can set the system to have 01 to 70 codes or
001 to 255 codes. To activate a speed dial, enter FEATURE 0 and the speed dial code.
The names you enter for speed dials are also used as CLI display for calls that come in on
lines that offer number-only CLID on telephones that are configured to receive CLID for
those lines. (Services, Telephony Services, System speed dial)
— User Speed Dial programming (FEATURE *4) allows users to program their own speed
dial numbers. (Services, Telephony Services, System DNs, Active Set DNs, DN XXXX,
User Preferences, User speed dials)
Speed dial numbers are subject to the same restriction filters as normally-dialed numbers.
However, your system administrator can program system speed dial numbers to bypass dialing
restrictions.

Business Communications Manager 3.6 Programming Operations Guide

212

Handling calls

Programming:

•

•

System speed dials: “Configuring system speed dial numbers” on page 475.

•

Alpha tagging: “Using alpha tagging for name display” on page 455.

•

User speed dials: “Configuring user speed dialing” on page 432.

Saved Number Redial: This feature allows you to save the number of the current external
call, provided that you dialed the call, so that you can call it again later. Each telephone can
save one number at a time. You can also copy a number from an autodial using this feature.
Programming: “Defining telephone dialing restrictions” on page 442

Handling calls
Once you answer a call, there are a number of ways of passing the call to someone else to deal with
or holding the call until it can be dealt with.
This section includes:
•
•
•
•
•

“Holding calls” on page 212
“Parking or transferring calls” on page 213
“Sharing calls by parking on SWCA buttons” on page 213
“Forwarding calls” on page 214
“Prevent calls from ringing at your telephone” on page 215

Holding calls
•

Use Hold: You can put a call on hold by pressing HOLD. If you have system-wide call
appearance (SWCA) keys defined, this might also park the call on a SWCA key and allow
others who have the same SWCA keys defined to pick up the call. Refer to the SWCA section
for more details.

•

Hold automatically (Auto Hold): If a line or the telephone are programmed with full auto
hold, you can answer a second call without dropping the first call and without pressing
HOLD. Model 7100 and 7000 telephones, and NetVision, DECT and Companion wireless
handsets, which do not have line keys, also use the HOLD key to toggle between active calls.
FEATURE 73 activates this feature. FEATURE #73 cancels the feature.
Programming: “Defining device capabilities” on page 405

•

Hold a call exclusively: You can put a call on Exclusive Hold so that you can retrieve it only
at your telephone (FEATURE 79 or FEATURE HOLD).

P0609326 1.1

Handling calls

213

Parking or transferring calls
•

Transfer calls (call forward): Allows you to direct a call to another telephone internally or
externally. To transfer a call to an external destination, you need to know the line pool or
destination code to route the call. (FEATURE 70). You can also set up a telephone to
automatically send calls to another telephone or to a voice mail box if the telephone is not
answered or if it rings busy.
Programming: “Forwarding calls” on page 214

•

Camp-on: Use this feature to (FEATURE 82) transfer an external call to another telephone
when all the lines assigned to that telephone are busy. A message appears on their display and
they hear the camp-on tone if all lines remain busy, or the call gets transferred to a free line
when one becomes available. If your system is part of a private network that uses the Meridian
call attendant as part of a centralized voice mail system, the attendant can use camp-on to
camp a call on any telephone in any system on the network.

•

Call Park (FEATURE 74): Use one of 25 possible codes to park a call on the system. These
codes include the Call Park prefix, which can be any digit from 1 to 9, and a two-digit call
number between 01 and 25. For example, if the Call Park prefix is 1, the first parked call is
assigned Call Park retrieval code 101. You must also set a delay period for when the call
returns to the telephone from which it was parked. You can also determine the order used to
assign the codes (Park mode).
Programming:

•

•

“Understanding access codes” on page 309

•

“Setting system timers” on page 472

•

“Programming Feature settings” on page 457

Callback: When you direct a call you have answered to another telephone, the system
monitors the call to make sure it is answered. If no one answers the call within a set length of
time, the system returns it to you.
Programming: “Setting system timers” on page 472

Sharing calls by parking on SWCA buttons
System-wide call appearance (SWCA) keys (FEATURE *521 to FEATURE *536) allow you
to control call park and retrieval features on any type of line, across the local system. These
features expand the Business Communication Manager call park and call retrieve features by
providing visual indications of the status of any call parked on a SWCA button that has indicators.
The calls can also be controlled by directly entering the SWCA feature codes.

Business Communications Manager 3.6 Programming Operations Guide

214

Handling calls

You can use SWCA programming to define logical groups of telephones. Each group can be
assigned a set of the SWCA codes, which allows them to pass calls within the group. Each
telephone in the group also displays the current status of the call, so users can determine which
calls are being dealt with.
Programming: “Configuring system-wide call appearance groups” on page 462

Forwarding calls
•

External call forward: This feature allows you to transfer a call to an external number. To
allow external destination programming ensure that Allow Redirect to Y (enabled). The other
programming is the same as for the following call forward features.
Programming:
•

•

“Configuring the Capabilities features” on page 406 (Allow redirect)

Call Forward no answer: redirects calls to another telephone in your system or to the voice
mail system when there is no answer at your telephone. Line Redirection takes priority over
Call Forward no answer.
Programming:

•

•

“Assigning Call Forward” on page 409

•

“Configuring centralized voice mail” on page 559

Forward no answer delay: Determines the number of times that an incoming call rings at
your telephone before the system forwards the call. To estimate the delay time in seconds,
multiply the number of rings by six.
Programming: “Assigning Call Forward” on page 409

•

Call Forward on busy: redirects calls to another telephone on your system or to a voice mail
system when you are busy on a call, or when you have Do Not Disturb activated at your
telephone. Telephones that have this active can still receive priority calls. If you are busy on a
target line call, another call to that target line redirects to the prime telephone for that line or to
the designated voice mail system. Line Redirection takes priority over this feature. Call
Forward programming does not affect calls redirected by Line Redirection.
Programming:

•

•

“Assigning Call Forward” on page 409

•

“Configuring centralized voice mail” on page 559

Call Forward and voice mail: If you want a voice mail system to pick up unanswered calls:
— use the internal number of your voice mail as the destination when you program Forward
no Answer and Forward on busy
— if your voice messaging system or service automatically retrieves calls, make the ring
delay greater than the delay used by your voice mail system

P0609326 1.1

Prevent calls from ringing at your telephone

215

— if the voice mail system is on a remote system, ensure that the correct routing codes are
added to the voice mail forwarding dial string.
— if calls are being forwarded to telephones or voice mail outside the system, ensure that
Allow redirect is set for the telephones.
Programming:

•

•

“Configuring centralized voice mail” on page 559

•

“Configuring the Capabilities features” on page 406 (Allow redirect)

Line redirection: This feature (FEATURE 84) allows you redirect all calls coming in on a
specific line to a telephone outside the office. You can decide to redirect all, or just some, of
your external lines. You also specify whether the user will hear a ring each time a call is
redirected. In programming, you can allow/disallow this feature for each telephone. The
telephone must have this setting enabled to allow call forward outside the system, such as for
external voice mail.
You can also set up line redirection on a system level. This can be cancelled for the line(s)
from a telephone with line redirection allowed.
Programming:
•

Allow redirect: “Configuring the Capabilities features” on page 406

•

System-level redirect: “Assigning Trunk/line data” on page 236

Prevent calls from ringing at your telephone
To maintain your privacy, you can use one of these features to block calls or ensure a private line:
•

Do Not Disturb: Use this feature (FEATURE 85) to forward your calls to the prime
telephone when there is no other telephone on which the line appears. If there is another
telephone that shares the same line, the call can be answered by that person. The Delayed Ring
Transfer feature transfers all calls not answered, to the prime telephone after a defined time.
Do Not Disturb also prevents voice calls from alerting at your telephone. Voice calls appear as
normal intercom calls. Use FEATURE #85 to cancel DND.

•

DND on Busy: When you are busy on a call and a second call comes in, your telephone alerts
you to the second call with a light ring. If you find this second call and ring is disruptive, you
can prevent a second call by assigning Do Not Disturb (DND) on Busy to your extension.
If you use DND, the line indicator for an external incoming call flashes, but your telephone
does not ring. Internal and private network callers hear a busy tone instead of ringing when
you are on the telephone. External callers are transferred to the prime set used in your system
or to your voice mail. Forward on Busy takes priority over DND on Busy.

Business Communications Manager 3.6 Programming Operations Guide

216

Communicating in the office

If an external call uses a target line, the call is processed according to the programming of the
target line. If the target line is busy, the caller hears a busy tone or routes the call to the prime
set for the target line or to the voice mail system, even if there is DND on Busy programming.
Programming: “Configuring the Capabilities features” on page 406 (DND on busy)
•

Turn Privacy on or off: When you have lines assigned to more than one telephone, anyone
with the line appearance can take a call, or join a call in progress. To provide exclusive access
for a user, you can program privacy on a line, in which case, only one person at a time can use
the line. If privacy is enabled, it can be turned off by the user (FEATURE 83).
Privacy control cannot be used for internal or conference calls.
When another telephone joins a call on a non-private line, the participants on the call hear a
tone, and a message appears on the display.
Programming:

•

•

“Assigning Trunk/line data” on page 236

•

“Turn Privacy on or off for a call” on page 258

Intrusion controls: If your system is part of a private network that uses the Meridian call
attendant on a centralized voice mail system, the attendant can use the break-in feature to
interrupt a call, regardless of any other settings on your line. The exception is if you have a
higher intrusion priority than the attendant. If this is the situation, the attendant would be
forced to camp the call at your telephone or redirect the call elsewhere in the system.
Programming:
•

“Setting intrusion controls” on page 414

•

“Break-in” on page 568

Communicating in the office
Your system allows you to communicate in ways other than making a phone call.
•

Page (FEATURE 60 to FEATURE 63): The page feature can be allowed/disallowed for
individual telephones. You can also assign each telephone to specific page zones. Zone paging
allows a user to alert a select group of users without disturbing other users. However, external
pages will be broadcast wherever the external speakers are mounted.
You can also determine whether a tone sounds before the page begins and what the maximum
length of the page will be.
— Creating page zones: A zone (1-6) is any group of telephones grouped together for paging,
regardless of their location. The maximum number of telephones in a page zone is 50.
— Using Page with external equipment: When you make a page that uses external paging
equipment (external page or combined page), the Long Tones feature automatically
activates for the external paging system only. This allows you to control optional
equipment with the Long Tones feature.

P0609326 1.1

Communicating in the office

217

Programming:

•

•

“Configuring the Capabilities features” on page 406

•

“Programming Feature settings” on page 457

•

“Setting system timers” on page 472

Messages: This feature allows you to leave a message on the display of another telephone in
your system or to analog telephones connected to an Analog Station Module (ASM/ASM8+).
The Messages feature indicates if you have any messages waiting.
The Messages feature uses a message waiting list to keep a record of your internal messages
and your (external) voice mail messages.
Note: To keep a record of external voice mail messages, you must have access to Business
Communications Manager Voice Messaging service with visual message waiting indication
and a Business Communications Manager digital telephone.
Programming: There is no system programming for this feature, other than the voice
messaging requirements which are discussed in the voice messaging documentation.
However, the message waiting indicator (MWI) feature on some telephones, may require
system programming.
Programming:
•

“Determining analog settings” on page 412

•

“Message Waiting Indication” on page 565 (MCDN programming)

•

“Configuring MWI on DPNSS 1 networks” on page 569 (DPNSS 1 features)

User codes for messaging:
— Send message FEATURE 1 (Cancel using FEATURE #1)
— Reply message FEATURE 65
— Cancel Message Waiting (FEATURE #65)
— Log into mail box to leave message (FEATURE 980)
— Log into mail box to play message (FEATURE 981)
•

Voice Call: Use this feature (FEATURE 66) to make an announcement to a specific person
through their telephone. This feature includes the ability to sound a tone or mute the tone
before the call is heard. You can set up your telephone to deny voice calls (FEATURE 88).
Note: Voice calls made to portable handsets, such as Companion, the BST T7406 cordless
handset, and NetVision telephones, will occur as a ringing call.
Programming: If you want to a use to be able to respond to a voice call without picking up
the handset, enable HF answerback (“Configuring the Capabilities features” on page 406).

Business Communications Manager 3.6 Programming Operations Guide

218

Using handsfree and mute

Using handsfree and mute
If the telephone you program has a speaker, you can configure a button that allows the user to
speak to the caller without lifting the handset, or to use a headset instead of the handset. If this
feature is assigned, the system automatically assigns:
•

the bottom, right button on the telephone to be the handsfree/mute button on all M-series
telephones and on the T7208 Business Series Terminals (BST).

•

handsfree-only to the bottom right button for IP telephones and T7316 telephones, which have
a separate mute button located under the dial pad.

•

handsfree and mute to the buttons located under the dial pad for T7316E telephones.

•

T7406 handsets must have handsfree active or the telephone will not work. NetVision
handsets, model 7000 and 7100 telephones and i2001 IP telephones do not use this feature.

•

Handsfree speaker volume: The handsfree speaker volume returns to the telephone volume
default setting after a call is released.
Programming: “Configuring the Capabilities features” on page 406.
Note: Ensure that the Handsfree field is set to Auto for T7316E telephones.

Track your incoming calls
You can track your calls using these features:
•

Call log: If your system has the appropriate equipment and you subscribe to the call
information feature supplied by your service provider, you can record information about calls
received on an external line. The line does not need to be assigned to the telephone that
receives the call for it to be logged (BCM version 3.5 and newer software, passive logging).
Nor does an assigned line need to be a ringing line to log a call. ISDN service packages that
come with calling line identification (CLID) can supply the same feature.
Note: Portable telephones: Your portable telephone may not support this feature, or it
may only support some of the functions of the feature.
Call Log creates a record of incoming external calls. For each call, the log can contain:
— sequence number in the Call Log
— name and number of the caller
— indication if the call was long distance
— indication if the call was answered and by whom
— time and date of the call
— number of repeated calls from the same source
— name of the line on which the call came

P0609326 1.1

Track your incoming calls

219

Call Log can help you to
— keep track of discarded calls or calls not answered
— track patterns for your callers (for example volume of calls and geographic area of calls)
— record caller information quickly and accurately
— build a personal telephone directory from log items
This feature allows users to:
— manually log a call (FEATURE 813)
— delete old log items (FEATURE 815)
— view the log (FEATURE 812) or about a current call (FEATURE 811)
— view charges for a call (FEATURE 818)
— view details about a specific item
— make a call using a call log entry
Information such as long distance indicator and the caller name and number may not show in
the log. The appearance depends on the Call Display services provided by your local telephone
company and the local telephone company of the caller.
Programming:
•

“Identifying the telephone (General heading)” on page 391 (call log password)

•

“Defining user preferences” on page 415 (call log options)

•

“Call log notes” on page 417

Auto dumping: Ensure that you have autodumping (FEATURE 815) is enabled on any
telephones that have call logging active, otherwise, the logs fill up and subsequent calls do not
get logged.
•

Malicious Caller ID (MCID): This feature records caller information at the central office for
the last external call on the active ETSI ISDN line. This feature must be available from your
service provider before you activate it in your system.
If this service is active on the line, you must press FEATURE 897 within 30 seconds after a
caller hangs up, and before you hang up.
Programming: “ETSI Euro network services” on page 545

Business Communications Manager 3.6 Programming Operations Guide

220

Use alternate or scheduled services

Use alternate or scheduled services
There are three types of services for Business Communications Manager to handle calls in a
different way on different days, and at different times of the day. These services for scheduling call
restrictions, ringing groups, and routing services are controlled through the control telephone. A
password is required to access the Restriction and Routing service schedules from the control
telephone.
You can also determine time tables and specific names for each schedule.
Programming:
•

Set up system schedule information:
Programming:

•

•

“Defining common schedule settings” on page 485

•

“Defining service schedules” on page 489

•

“Turn services on and off” on page 484

Set up ring groups and ringing schedules
Programming: “Configuring ringing service” on page 490

•

Set up routing schedules:
Programming: “Configuring routing service” on page 495

•

Set up restriction schedules:
Programming: “Configuring restriction service” on page 493

Special telephones
•

Hotline telephone: You can define a telephone that automatically dials an emergency or direct
number when the handset is picked up.
Programming: “Assigning a Hotline” on page 411

•

Control telephone: This telephone allows you to control other telephones in the system by
turning service schedules off and on.
Programming: “Identifying the telephone (General heading)” on page 391

•

Prime telephone: This telephone, which is defined for each line, receives unanswered calls
when call forward when the line cannot deposit the call at the intended telephone.
Programming: “Assigning Trunk/line data” on page 236

P0609326 1.1

Special telephones

•

221

Direct dial telephone: This is the telephone that system users can dial with one digit (direct
dial access code). An example of this would be a receptionist telephone. This telephone is also
usually the control telephone for system scheduling. You can create up to five direct dial
telephones, however, they all respond to the same direct dial access code.
Programming:
•

“Programming access codes” on page 310

•

“Creating Direct Dial sets” on page 313

•

“Configuring the Capabilities features” on page 406

•

“Defining ringing service schedules” on page 491 (extra dial telephone)

Auxiliary devices
A music source or an auxiliary ringer can be connected to the system hardware. In programming,
you need to define how these features will be accessed and used.
•

Background music: If there is an external music source connected to your system or if you
have the IP music feature set up to use internet-based music distributors or download music
clips onto your system, you can listen to music through the speaker on the telephone
(FEATURE 86), or you can allow the music to be heard by callers who have been put on hold.
Programming:

•

•

“Programming Feature settings” on page 457 (Background music and On hold)

•

“Configuring the music source” on page 601 (IP music)

Auxiliary ringer: This optional device can be connected through a RJXX connection to your
system. The auxiliary ringer is best suited to factory type locations that require loud ringing
bells or horns.
Programming:

•

•

“Assigning Trunk/line data” on page 236 to turn the feature on/off for a line

•

“Configuring the Capabilities features” on page 406 to turn the feature on for
specific telephones

•

“Assigning ringing groups to lines” on page 492, for the ring group settings

Companion handset: This portable handset communications with the Business
Communications Manage through radio base stations connected to digital trunk modules
(DTM) installed in the system. Note: Telephony region restrictions.
Programming: Refer to the Companion Installation and Configuration Guide. The handsets
also come with a user guide that describes the handset features.

Business Communications Manager 3.6 Programming Operations Guide

222

Call out to external systems using host system dialing

•

DECT handset: This portable handset communications through radio base stations connected
to a DECT media bay module installed in the system. The module also provides access for
configuration of the firmware that controls the handset function. Note: Telephony region
restrictions.
Programming: Refer to the DECT deployment documentation and the DECT Installation
and Configuration Guide on your documentation CD. Deployment documentation is also
available. The handsets also come with a user guide that describes the handset features.

•

Symbol NetVision handsets: These portable handsets connect to the internet through an IP
access point which is connected to the LAN or WAN to which the Business Communications
Manager is also connected. They can call out using physical or VoIP trunks. Target lines direct
incoming calls to the handsets.
Programming: Refer to the IP Telephony Configuration Guide. Handsets also come with
user guides that describe the handset features.

•

BST T7406 cordless handset: This handset communicates with the BCM through a station
module that supports three handsets. The station module connects to a digital trunk installed
on the system. The handset emulates the T7324, although it only has six memory buttons.
Programming: Same as for T7310/T7316 telephone. This telephone has six display keys.

•

BST Doorphone: This is a device that installs at security entrances. This device uses a DN
record in the system DNs range. The DN record for a doorphone will display M7324.
However, there are specific required settings for the doorphone. Also, the doorphone does not
use the user preferences or the Telco features settings. Installation and configuration
information is contained in the BST Doorphone Installation and Configuration Guide.

Call out to external systems using host system dialing
When you make external calls, or forward calls to external systems, such as private branch
exchanges (PBX system), you may need to insert one or more Host System dialing signals to
connect the call. These features are also known as end-to-end signaling. Signaling features either
send a special signal to the host system or allow you to program delays required by host systems in
external autodial or speed dial sequences.
•

Link: If you connect the system to a private branch exchange (PBX), you can use a Link
signal to access special features. On some telephones, Link is called FLASH. You can include
the Link signal as part of a longer stored sequence on an external autodial button or in a speed
dial code. The Link symbol uses two of the 24 spaces in a dialing sequence. (FEATURE 71)
Programming:

P0609326 1.1

•

“Assigning Trunk/line data” on page 236 (Link at CO)

•

“Defining telephone dialing restrictions” on page 442 (Allow link)

•

“Setting system timers” on page 472

Call out to external systems using host system dialing

•

223

Pause: This feature enters a 1.5-second delay in a dialing sequence on an external line. The
use of this feature is often required for signaling remote devices, such as answering machines,
or when reaching through to PBX features or host systems. You can program more than one
pause in an external autodial or speed dial sequence. (FEATURE 78)
The Pause symbol uses one of the 24 spaces in a dialing sequence.
For pulse dialing, pressing * inserts a 1.5-second pause into the dialing sequence.
Programming: There is no system programming for this feature.

•

Long Tones: This feature (FEATURE 808), when invoked while a call is active, allows you
to control the length of a tone to signal devices such as fax or answering machines, which
require tones longer than the standard 120 milliseconds. You can use Long tones on any call
except a conference call. You can use internal lines of the system to activate a device
connected to an ATA2 or an ASM in another area of your office, or external lines to access
devices outside the system.
Programming: There is no system programming for this feature.

•

Run/Stop: This feature (FEATURE *9) inserts a break point into a sequence of dialed
numbers or characters used for automatic dialing. This can be necessary when you are
connecting to a PBX or similar host system. For example: you can call a company with an
automated attendant that instructs you to dial the internal number you need. You can program
the company number, a Run/Stop, then the internal number on one external autodial button.
The Run/Stop symbol uses one of the 24 spaces in an autodial or speed dial sequence.
You can include up to three Run/Stop commands in a dialing string. The system ignores a
fourth Run/Stop, and any digits or commands that follow three Run/Stop commands in a
programmed dialing sequence.
To use:
a
b

Press the autodial button one time to dial the company number.
When you hear the automated attendant, press the autodial button again to dial the internal
number.

Programming: There is no system programming for this feature.
•

Wait for Dial Tone: This feature (FEATURE 804) causes a sequence of numbers to pause
until dial tone is present on the line before continuing to dial. You can use this feature if you
must dial a remote system and then wait for dial tone from that system before dialing the
remainder of your number. The Wait for Dial Tone symbol uses two of the 24 spaces in an
autodial or speed dial sequence.
Programming: There is no system programming for this feature.

•

Pulse or tone dialing: If your external lines use pulse dialing, you can switch temporarily to
tone dialing. Tone dialing allows you to communicate with devices such as answering
machines or automatic switchboards, to access the features that PBX systems can provide, or
to access another system remotely.
Press # while on an active line. After you hang up, your telephone returns to pulse dialing.

Business Communications Manager 3.6 Programming Operations Guide

224

Call in from outside the system

Call in from outside the system
Callers can access the system over the public telephone network when away from the office, or
you can call from another system, over a private network.
•

You can determine which lines will be available for remote access, and define further
restrictions.

•

You can control which lines and what features are available to these callers by specifying class
of service (COS) passwords and identifying restrictions for each password.
Programming:
•

“Using the General record” on page 235 (use remote package)

•

“Creating Direct Inward System Access (DISA)” on page 291

•

“Remote access line settings” on page 292

•

“Defining remote access packages” on page 294

•

“Using COS passwords” on page 296

Security Note: It is important to maintain the security of your system by limiting access
to authorized users and limiting those users to the features they need.

!

Controlling telephone programming access
You can control the amount of access users have to the programming features on their telephones
using the Set lock feature.
Programming: “Defining telephone dialing restrictions” on page 442

P0609326 1.1

Special features

225

Special features
This section describes features on the system which serve a specific purpose that is optional to the
general function of the system.
•

Hospitality services: This feature allows small to medium service facilities to provide
customer telephone service, as well as administration services through a telephone interface.
Programming: Besides the general line and telephone programming required for individual
group members, Chapter 24, ”Configuring Hospitality Services” on page 589 explains the
feature in detail.

•

Hunt groups: This feature allows you to group your call center operators so you can target
specific types of calls to specific groups. As well, you can define how calls enter the group, so
you can control the work load based on your requirements for your operators.
Programming: Besides the general line and telephone programming required for individual
group members, Chapter 23, ”Configuring Hunt groups” on page 573 provides details about
setting up hunt groups and hunt group features.

•

Silent Monitor: This feature allows specified two-line display telephones to be used to
monitor Hunt group and Call Center operators. You can specify whether the system sound a
tone before breaking into a call, or whether the break-in will be silent. Display prompts on the
supervisor telephone allows the supervisor to unmute or move from user to user.
Programming:
•

“Defining device capabilities” on page 405 (SM supervisor)

•

“Monitoring Hunt groups” on page 585 (General settings, Silent monitor)

•

Call Center: The Business Communications Manager provides a suite of applications that
support call center activities through the CallPilot application. This information is explained in
detail in separate documentation, including: Call Center Set Up and Operation Guide, Call
Center Agent Guide, Call Center Supervisor Guide, and the Call Center Reporting Set Up and
Operation Guide

•

CallPilot: The Business Communications Manager provides an on-board voice mail system,
however, external voice mail systems can also be used, including a centralized system off a
Meridian 1 if the Business Communications Manager is networked to the Meridian through
PRI SL-1lines or VoIP trunks with the MCDN protocol active. This information is explained
in detail in separate documentation, including: CallPilot Manager Set Up and Operation
Guide, CallPilot Reference Guide, CallPilot Quick Reference Guide, CallPilot Programming
Record, CallPilot Message Networking Set Up and Operation Guide, CallPilot Message
Networking User Guide, CallPilot Unified Messaging Installation and Maintenance Guide,
CallPilot Desktop (Unified) Messaging Quick Reference Guide, CallPilot Fax Set Up and
Operation Guide, CallPilot Fax User Guide.

•

Call activity: The Call Detail Recording part of the Business Communications Manager
allows you to monitor call activity for specific calls or telephones. Configuration information
is detailed in Call Detail Recording System Administrator Guide.

Business Communications Manager 3.6 Programming Operations Guide

226

Information matrices

•

IVR: The Interactive Voice Response feature allows your customers greater interaction with
your call centers. Configuration information is located in Interactive Voice Response
Installation and Configuration Guide (IVR)

Information matrices
Each section in this book provides a matrix containing the field information from that section. You
can use this information to create a spreadsheet record of your system configuration or for a quick
overview of the information that you require for each type of programming.
Programming Record forms set up in Microsoft Excel* are available on your documentation CD.
•

“Line matrix” on page 263

•

“Loop matrix” on page 281

•

“Dialing Plans matrix” on page 307

•

“CbC matrix” on page 342

•

“Routing matrix” on page 338

•

“Restriction filters matrix” on page 350

•

“Direct dial matrix” on page 314

•

“Target lines matrix” on page 290

•

“Remote access matrix” on page 300

•

“Digital telephones DN record matrices” on page 447

•

“System features matrix” on page 471

•

“Timers matrix” on page 473

•

“System speed dial matrix” on page 477

•

“Telco features matrix” on page 480

•

“Services matrix” on page 496

•

“Hunt group matrix” on page 584

•

“Hospitality matrix” on page 595

P0609326 1.1

227

Chapter 9
Configuring lines
This section describes the information accessed under the Services, Telephony Services, Lines
headings.
Task:
• Configure the lines connected to the system, or call channels configured as Voice over IP
(VoIP) trunks or target lines.
This section contains:
•
•
•
•
•
•

“Understanding the process of line configuration” on page 228
“Understanding how the system identifies lines” on page 229
“Using the General record” on page 235
“Assigning Trunk/line data” on page 236
“Assigning Restrictions” on page 261
“Setting line telco features” on page 263

The screens accessed through these headings define the line numbers that correspond to the DIP
switch settings that were configured on the trunk media bay modules installed on your system.
Check your Programming Record to see which modules are installed, and what settings were
chosen. The screens also are used to assign Voice over IP (VoIP) trunks and target lines, however,
the process for defining these lines is described in other sections since they are not related directly
to external hardware.
Note: External lines are also referred to as trunks. External lines include the lines between the
public network (PSTN) and between the nodes in a private network. Non-physical connections,
such as voice over IP (VoIP) and target lines, are also referred to as trunks and lines, respectively,
even though they do not describe actual wired connections.
All physical trunks connect to the Business Communications Manager through a media bay
module of some sort. All non-physical trunks and lines use a LAN or WAN connection (VoIP
trunks) or internal call processing (target lines).
However, the connection, all lines are configured under the Lines or loops headings.
Other configuration options or equirements:
•
•

BRI loops require configuration and provisioning before the BRI lines can be configured.
Refer to Chapter 10, “Configuring BRI Loops,” on page 265.
The Business Communications Manager also offers facilities for splitting trunks to deliver
both data and telephony services. Refer to the chapter titled “Data and split-line configuration”
on page 151 for a description of how the Business Communications Manager uses data
modules and WAN programming in this context.

Business Communications Manager 3.6 Programming Operations Guide

228

Understanding the process of line configuration

Understanding the process of line configuration
Refer to the process map below, which leads you through the order for configuring the lines for
your system.
Figure 47 Process map: Configuring the lines for your system
VoIP lines

Trunk module lines
Modules are
installed and
system is
running.

Note the lines that are active.
Services, Telephone Services, Physical
LInes or VoIP lines, Active LInes
Select the line you want to configure. Refer to
“Determining which lines you need to program” on
page 230
Configure the lines to suit your system,
including assigning them to line pools, where
applicable.

Keycodes
have been
entered

Set up the gateway and IP requirements.
Refer to IP Telephony Configuration Guide.

•
•

“Copying line programming” on page 230
“Using the General record” on page 235

•

“Assigning Trunk/line data” on page 236

•
•

“Assigning Restrictions” on page 261
“Setting line telco features” on page 263

Assign line pool codes or assign line pools to routes, and create destination codes for
the routes. Refer to Chapter 12, “Configuring outgoing calls,” on page 301.

Assign lines, line pools and target lines to DNs with the Add Users Wizard.
Line pools, routing, and target lines: Chapter 11, “Controlling access into the system,” on
page 283.
Assign to DNs: Chapter 15, “Configuring DNs for system devices,” on page 387
Set up target lines to direct incoming calls from unsupervised lines, such as DID, PRI and
VoIP lines, to specific telephones or groups. Refer to “Assigning target lines” on page 287.

Set up optional line features such as name display and services. Refer to Chapter 16,
“Configuring system settings,” on page 451.

P0609326 1.1

Understanding how the system identifies lines

229

Understanding how the system identifies lines
On a new system, lines and loops are numbered and assigned defaults based on the type of media
bay modules that have been connected to the system. The exception is the voice over IP (VoIP)
trunks, which require a keycode to activate.
The Unified Manager displays all active physical lines under:
Lines, Physical Lines, Enabled Lines.
These screens allow you to easily view which lines have been enabled through a media bay
module. (Refer to “Configuring resources — media bay modules” on page 123 for information
about configuring media bay module records.)
From this heading, you can access each line record and assign attributes, as you require.
This section describes:
•
•

“Copying line programming” on page 230
“Determining which lines you need to program” on page 230

The following figure shows a detailed view of the Lines navigation tree headings.
Figure 48 Lines menus and fields

Lines
VoIP Lines
Enabled VoIP Lines
All VoIP Lines

Physical lines
Enabled Lines
All Physical Lines

Target lines
All lines
Line 001-492
General
Name
Control set
Use remote package

Trunk/Line Data
Trunk type
Line type
Dial mode
Received number
If busy
Prime set
Distinct rings in use
Distinct ring
Auto privacy
Trunk mode
Answer mode
Answer with DISA
Link at CO
Use auxiliary ringer
Full autohold
Loss package
Impedance (ohms)
Signalling
ANI number
DNIS number

Restrictions
Line Restrictions
Normal
Night
Evening
Lunch
VoIP
Sched 5
Sched 6
Remote Restrictions
Normal
Night
Evening
Lunch
VoIP
Sched 5
Sched 6
Telco features
Voice Message Center

Business Communications Manager 3.6 Programming Operations Guide

230

Understanding how the system identifies lines

Copying line programming
The Copy command allows you to duplicate programming for a line and apply it to another line.
You cannot copy programming between lines on different types of media bay modules. The
Received number of a target line is a unique number and cannot be copied.
When you copy data from a physical trunk to a target line (or the other way around), only the data
in common is copied. For example, copying a target line to a T1 E&M trunk copies only the Line
data settings because there are no Trunk data settings for a target line.
Follow these steps to copy a line setting to a single line.
1

Click on the keys beside Services, Telephony Services, Lines, Physical Lines,
Enabled Lines.

2

Click the line number from which you want to copy settings.

3

Choose the subheading for the information that you want to copy:
Trunk/Line data, Restrictions, or Telco features.

4

From the Edit menu, click Copy.

5

In the Copy to box, type the line number where you want to copy the settings.

6

Click the OK button.

Determining which lines you need to program
Under Lines, note that line types are divided into three headings. The fourth heading contains all
line numbers.

VoIP lines (require keycode)
Voice over IP (VoIP) lines are signaling channels that simulate how CO lines work. However,
VoIP lines transmit data to the IP network over a LAN or WAN rather than over physical lines.
Once the VoIP trunks are set up, you can assign them to line pools, and program their behavior in
the same way you would PRI lines.
VoIP lines use line numbers 001 to 060. These line records appear under Services, Telephony
Services, Lines, VoIP Lines. To access VoIP lines, you need to enter software keycodes. Each
keycode supports a specific number of lines. If you are using both SIP and H.323 trunks, the H.323
trunks start numbering up from 001, and the SIP trunks start numbering down from 060. No entries
appear in the Enabled VoIP lines field until you complete the IP Trunks Settings field, which
displays when you click on IP Trunks under Services, IP Telephony.
VoIP trunks should be configured to use a single line pool, per trunk type. Do not mix other trunk
types on the same line pool. The VoIP line pools are assigned to routes, which, in turn, are
configured with destination codes that route calls to the designated remote gateways of other

P0609326 1.1

Understanding how the system identifies lines

231

Business Communications Manager systems or Meridian 1-IPT systems. Note: SIP trunks can
only be used between Business Communications Managers.
You can also create a fallback for the trunk. This is a situation where the system reroutes the call to
a PSTN line pool if the primary route is not available or the call quality is not suitable. If you do
not configure your network for fallback and the call quality is below threshold, the IP call fails.
Refer to the IP Telephony Configuration Guide for information about configuring VoIP trunks.

Target lines
Target lines are internal communications paths that directly connect auto-answer trunks to system
telephones. These lines are in-coming only.
Target lines allow you to make more efficient use of DID line resources.You can map a range of
target lines for each DID line. The incoming call is routed according to the mapped dialed digits,
rather than a one-to-one line assignment. Refer to “DID system” on page 191 for an example of a
system using DID trunks and target lines. Systems configured using the DID template,
automatically assign target lines to all assigned DNs.
You also require target lines when you use PRI or VoIP trunks.
Target lines use line numbers 241 to 492. These lines are found under Services, Telephony
Services, Lines, Target Lines. Record this information in your system Programming Records so
you have a clear view of where each line is assigned.Refer to “Assigning target lines” on page 287
for instructions about setting up target lines.
Other features:
•
•

Each target line also can be assigned to more than one telephone.
A telephone can have multiple appearances of a target line.

Physical lines
Physical lines are the central office (CO) trunks assigned to the trunk media bay modules. Which
lines are enabled is determined by the DIP switch settings on the installed trunk modules.
You can change the line types to suit your system. For instance, BRI and DTM modules can be
designated to a number of line types, depending on the type of line service provided through the
central office (CO). However, the line numbers are associated for specific tasks or to specific
DS30 bus numbers.
Refer to the table below for a list of lines assigned per bus (DS30 bus and offset), based on the
module type configured with that address. You can use this chart to note which lines should be
active for the modules you installed. You can also note which line pool you put the lines in, and
note the line pool access codes or routes and destination codes to which you assigned the line pools
(or use your programming records).

Business Communications Manager 3.6 Programming Operations Guide

232

Understanding how the system identifies lines

Follow these steps to use the table.
1

For each bus number, circle the module you set to that number.

2

Beside the module name, circle the group of line numbers appropriate for the offset you set on
the modules.

3

In the Line pool column, indicate a line pool name if you want to associate lines into a pool.
This enables assigned telephones to grab any free line from the pool.

4

On the far right column, list the access codes and routes associated with the lines.

Table 30 DS30 number and offset line-loop default list
DS30
bus

Type of module

Line/Loop numbers (default)
Offset
0
1
2

3

Default Start DN: 221
02

Trunk modules
DTM (T1) 211-234
DTM (NA-PRI) 211-233
DTM (E1 PRI) 211-240
DDI MUX DTM 211-234*
BRI 211-218

219-226

227-234

CTM4, GATM4 and 4X16 211-214

219-222

227-230

235-238

CTM8, GATM8 (upper/ 211-214
lower) 219-222

219-222
227-230

227-230
235-238

N/A

205-208

209-212

ISDN loops
BRI ST/U2/U4 201-204

*Note which lines are for data and which are for telephony.
03

Trunk module
DTM (T1) 181-204
DTM (NA-PRI) 181-203
DTM (E1 PRI) 181-210
DDI MUX DTM 181-204*
BRI 181-188

189-196

197-204

CTM4, GATM4 and 4X16 181-184

189-192

197-200

205-208

CTM8, GATM8 (upper/ 181-184
lower) 189-192

189-192
197-200

197-200
205-208

N/A

305-308

309-312

ISDN loops
BRI ST/U2/U4 301-304

*Note which lines are for data, and which are for telephony.

P0609326 1.1

Line pool
A-O/PRI

Access codes
and routes

Understanding how the system identifies lines

233

Table 30 DS30 number and offset line-loop default list (Continued)
DS30
bus

Type of module

04

Trunk module

Line/Loop numbers (default)
Offset
0
1
2

3

Line pool
A-O/PRI

Access codes
and routes

DTM (T1) 151-174
DTM (NA-PRI) 151-173
DTM (E1 PRI 151-180
DDI MUX DTM 151-174*
BRI 181-188

189-196

197-204

CTM4, GATM4 and 4X16 151-154

159-162

167-170

175-178

CTM8, GATM8 (upper/ 151-154
lower) 159-162

159-162
167-170

167-170
175-178

N/A

405-408

409-412

ISDN loops
BRI ST/U2/U4 401-404

*Note which lines are for data and which are for telephony.
05

Trunk module
DTM (T1) 121-144
DTM (NA-PRI 121-143
DTM (E1 PRI) 121-150
DDI MUX DTM 121-144*
BRI 151-158

159-166

167-174

CTM4, GATM4 and 4X16 121-124

129-132

137-140

145-148

CTM8, GATM8 (upper/ 121-124
lower) 129-132

129-132
137-140

137-140
145-148

N/A

505-508

509-512

ISDN loops
BRI ST/U2/U4 501-504

*Note which lines are for data, and which are for telephony.
06

Trunk module
DTM (T1) 91-114
DTM (NA-PRI) 91-113
DTM (E1 PRI) 91-120
DDI MUX DTM 91-114*
BRI 91-98

99-106

107-114

CTM4, GATM4 and 4X16 91-94

99-102

107-110

115-188

99-102
107-110

107-110
115-188

N/A

CTM8, GATM8 (upper/ 91-94
lower) 99-102
ISDN loops
BRI ST/U2/U4 601-604

*Note which lines are for data and which are for telephony.

Business Communications Manager 3.6 Programming Operations Guide

234

Understanding how the system identifies lines

Table 30 DS30 number and offset line-loop default list (Continued)
DS30
bus

Type of module

07

Trunk module

Line/Loop numbers (default)
Offset
0
1
2

3

DTM (T1) 61-84
DTM (NA-PRI) 61-83
DTM (E1 PRI) 61-90
DDI MUX DTM 121-144*
BRI 61-68

69-79

77-84

CTM4, GATM4 and 4X16 61-64

69-72

77-80

85-88

CTM8, GATM8 (upper/ 61-64
lower) 69-72

69-72
77-80

77-80
85-88

N/A

705-708

709-712

ISDN loops
IBRI ST/U2/U4 701-704

*Note which lines are for data, and which are for telephony.

All lines
This heading contains all possible lines available to the system.

P0609326 1.1

Line pool
A-O/PRI

Access codes
and routes

Using the General record

235

Using the General record
The Lines XXX General record allows you to assign a name, a control telephone, and a remote
package for a line.
1

Choose the type of line with which you want to work.

2

Under that heading, choose the line number record you want configure.

3

Click General.

Figure 49 Using the Lines General screen

*
lines are incoming, only.
*Target
They do not show this field.

4

Change the headings to fit your requirements.
The following table shows the possible settings for the General record.

Table 31 General record values
Attribute

Value

Description

Name



Identify the line in a way that is meaningful to your system, such as
by the type of line and line pool or the DN it is attached to in the
case of target lines.

Control set

DN 
Default: 221 (default Start DN)

Enter a telephone DN for a telephone that you want to use to turn
service off or on for other telephones using this line.
The control telephone must have the line assigned, or must be
assigned to the line pool the line is in. Refer to “Assigning line pool
access” on page 402

Tips: External lines and telephones must be programmed to use one of the Scheduled Services:
Ringing, Restriction, and Routing Services.
For maximum flexibility, Nortel Networks recommends that you create two different control
telephones, one for the lines and one for the telephones.
You can turn on a service manually or automatically for all external lines from an assigned control
telephone. However, you cannot combine schedules. A service can only be active as normal
service or one of the six schedules at any one time. Several schedules can be active at one time,
but they must use different services.
Use remote
package



Package 00: Prohibits remote access to:
• line pools
• external page
This package cannot be changed.
Package 01-15 are programmable.
Refer to “Defining remote access packages” on page 294

Business Communications Manager 3.6 Programming Operations Guide

236

Assigning Trunk/line data

Table 31 General record values (Continued)
Attribute

Value

Description

Tips: You can program a line pool access code under Telephony Services, General Settings,
Access Codes. Refer to “Setting up line pool access codes” on page 317.

Assigning Trunk/line data
The Trunk/line data heading allows you to program settings for lines that affect how the Business
Communications Manager communicates with other switches. These settings also allow you to
determine how lines, including target lines, are used in Business Communications Manager.
1

Under the line number you are configuring, click the Trunk/line data heading.

2

The Trunk type field is read-only unless the trunk type is T1.
Note: You can change the trunk type setting only for lines connected to a T1 line. All other
lines are automatically configured, based on the type of media bay module present.
Trunk types:
•
•
•
•
•

VoIP
DTM: TI types (Loop, E&M, DID, Ground, or fixed data channel), PRI, DASS2, DPNSS.
The DDI MUX module contains a DTM.
CTM (North America): Loop
BRI: BRI S/T, BRI U2, U4
Target lines

BRI note: BRI U2 and BRI U4 are only available through a FEM module connected to a
Norstar trunk module with a BRI U2 or BRI U4 card.
3

Configure the line settings.
The fields that appear will depend on the type of line. Refer to the charts below for
descriptions of applicable fields:
•
•
•
•
•
•

P0609326 1.1

“Loop start analog/digital fields” on page 237
“Ground start fields” on page 240
“DID fields” on page 242
“E&M fields” on page 244
“Target lines and DASS2 fields” on page 247
“PRI fields” on page 249

Assigning Trunk/line data

•
•
•
•

237

“BRI fields” on page 250
“DPNSS fields” on page 252
“VoIP fields” on page 253
“Lines field cross-reference chart” on page 255

Loop start analog/digital fields
Table 32 Loop start analog and digital fields
Attribute

Value

Description

Unsupervised line
Supervised line
Line type

Public
Private to:
Pool A to O

Define how the line is used in relation to other lines in the system.
• Public line: can be accessed by more than one telephone.
• Private line: can be assigned only to one telephone and the prime telephone for
that line. Enter the internal number of the telephone.
• Pool A - O: assigns the line to one of the line pools. If a line is assigned to a line
pool, but is not assigned to any telephone, that line is available only for outgoing
calls.
For more information and tips, refer to “Line pool tips” on page 259.

Dial mode

Pulse
Tone

Specify whether the system uses dual tone multifrequency (DTMF) or pulse
signaling on the trunk.

Business Communications Manager 3.6 Programming Operations Guide

238

Assigning Trunk/line data

Table 32 Loop start analog and digital fields (Continued)
Attribute

Value

Description

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on the line. For an Auto
Answer line, calls are redirected if the received number is invalid or the target line is
busy, and if the
If busy parameter is set To prime.
Each line can be assigned only one prime telephone.
Doorphone note: Ensure that this DN does not belong to a doorphone.

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already been assigned to at
least one line.

Distinct ring

Choose the distinctive ring pattern that you want to assign to the line. This allows
you to provide selective service to calls with differing answer priorities.
When more than one line with the distinct ring settings rings at a telephone, the line
with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

None
Pattern 2
Pattern 3
Pattern 4

Warning:
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern has
already been assigned to a telephone, all telephones with that ring pattern will be
reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
Auto privacy

Y or N

Define whether one Business Communications Manager user can select a line in
use at another telephone to join an existing call. Refer to “Turn Privacy on or off for
a call” on page 258 (FEATURE 83).

Trunk mode

Unspr
Supervised
* Earth calling
*Loop guarded
*Loop
unguarded
^Reversal on
Idle (ROI)

Define whether disconnect supervision, also referred to as loop supervision,
releases an external line when an open switch interval (OSI) is detected during a
call on that line. You must set this to Supervised if a loop trunk has its Answer
mode set to Auto or if you enable Answer with DISA. Disconnect supervision is also
required to conference two external callers. The line must be equipped with
disconnect supervision from the central office for the Supervised option to work.
* These listing only appears for UK analog lines. Note that Earth calling is only
supported by a FEM connected to a Norstar analog trunk module. The GATM does
not support Earth calling, even though the setting appears for the lines on the
module.
^This listing appears only for the Australia profile.
Tips: The duration of an open switch interval (OSI) before Business
Communications Manager disconnects a call is programmed by the Disconnect
timer setting. Refer to “Configuring the trunk module to line type” on page 131.

P0609326 1.1

Assigning Trunk/line data

239

Table 32 Loop start analog and digital fields (Continued)
Attribute

Value

Description

Answer
mode

Manual
Auto

Define whether a trunk is manual or automatic answer.
Auto answer mode allows the trunk to be a shared resource by the system
telephones.
For auto answer trunks being used to allow remote call-in from system users, the
trunk can be configured to answer with a straight dial tone, if DISA has not been
enabled. It can also be configured to answer with a stuttered dial tone if DISA is
enabled and the caller is expected to enter a COS password. The COS password
defines which system features the caller is permitted to access.
Manual answer trunks are assigned to one or more telephones. The assigned
telephones exclusively own the line.
Note: You require Disconnect supervision on the line if loop start trunks are to
operate in auto-answer mode (Trunk mode).

Answer with
DISA

Y or N

If Y, when a remote user calls into the system on an unsupervised line, the system
prompts a caller for a six-digit class of service (COS) password.
If N, when a remote user calls into the system on an unsupervised line, the call is
connected as dialed.

Link at CO

Y or N

Some exchanges respond to a Link signal (FEATURE 71) by providing an
alternative line for making outgoing calls.
Enabling Link at CO causes the system to apply the restrictions on outgoing calls to
the digits dialed after the Link signal. As well, the call on the alternative line is
subject to all restrictions.
Disabling Link at CO prevents a Link signal from resetting the Business
Communications Manager restrictions in cases where the host exchange does not
provide an alternative line.
You also need to ensure that telephones using the line have the feature allowed.
Refer to “Defining telephone dialing restrictions” on page 442.

Use auxiliary Y or N
ringer

Turn the auxiliary ringer on or off for all telephones using this line.
When programmed on a line, the auxiliary ringer will ring every time a call is
received.
Note: When programmed only on a telephone, no ring occurs for a transferred call.
An auxiliary ringer can also be programmed in Services to ring for a line placed into
a scheduled Ringing service. Refer to “Configuring ringing service” on page 490

Full autohold Y or N

Enables or disables Full autohold.
When enabled, if a caller selects an idle line but does not dial any digits, that line is
automatically placed on hold if you then select another line.
The default setting should be changed only if Full autohold is required for a specific
application.

Loss
Packages

Short CO
Medium CO
Long CO
Short PBX
Long PBX

Select the appropriate loss/gain and impedance settings for each line.
For more information refer to “Using loss packages” on page 260.

Impedance

600 ohm
900 ohm

The GATM can be set to a specific impedance level. This is determined by local
line requirements.

Business Communications Manager 3.6 Programming Operations Guide

240

Assigning Trunk/line data

Table 32 Loop start analog and digital fields (Continued)
Attribute

Value

Description

Redirect to



Enter a dial string (including routing code) to redirect the line to an external
telephone, such as a call attendant on another system.
If you want to stop redirection, you need to delete the dial string and allow the
record to update.

WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them now to
ensure your system will function properly.

Ground start fields
Table 33 Ground start fields
Attribute

Value

Description

Manual answer line

Auto answer line

Line type

Public
Private to:
Pool A to O,

Define how the line is used in relation to other lines in the system.
• Public line: can be accessed by more than one telephone.
• Private line: can be assigned only to one telephone and the prime telephone for
that line. Enter the internal number of the telephone.
• Pool A - O: assigns the line to one of the line pools. If a line is assigned to a line
pool, but is not assigned to any telephone, that line is available only for outgoing
calls.
For more information and tips, refer to “Line pool tips” on page 259.

Dial mode

Pulse
Tone

Specify whether the system uses dual tone multifrequency (DTMF) or pulse
signaling on the trunk.

P0609326 1.1

Assigning Trunk/line data

241

Table 33 Ground start fields (Continued)
Attribute

Value

Description

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on the line. For an Auto
Answer line, calls are redirected if the received number is invalid or the target line is
busy, and if the If busy parameter is set To prime.
Each line can be assigned only one prime telephone.

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already been assigned to at
least one line.

Distinct ring

Choose the distinctive ring pattern that you want to assign to the line. This allows
you to provide selective service to calls with differing answer priorities.
When more than one line with the distinct ring settings rings at a telephone, the line
with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

None
Pattern 2
Pattern 3
Pattern 4

Warning:
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern has
already been assigned to a telephone, all telephones with that ring pattern will be
reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
Auto privacy

Y or N

Define whether one Business Communications Manager user can select a line in
use at another telephone to join an existing call. Refer to “Turn Privacy on or off for
a call” on page 258. (FEATURE 83)

Answer
mode

Manual
Auto

Define whether a trunk is manual or automatic answer.
Auto answer mode allows the trunk to be a shared resource by the system
telephones.
For auto answer trunks being used to allow remote call-in from system users, the
trunk can be configured to answer with a straight dial tone, if DISA has not been
enabled. It can also be configured to answer with a stuttered dial tone if DISA is
enabled and the caller is expected to enter a COS password. The COS password
defines which system features the caller is permitted to access.
Manual answer trunks are assigned to one or more telephones. The assigned
telephones exclusively own the line.

Answer with
DISA

Y or N

If Y, when a remote user calls into the system on an unsupervised line, the system
prompts a caller for a six-digit class of service (COS) password.
If N, when a remote user calls into the system on an unsupervised line, the call is
connected as dialed.

Use auxiliary Y or N
ringer

Turn the auxiliary ringer on or off for all telephones using this line.
When programmed on a line, the auxiliary ringer will ring every time a call is
received.
Note: When programmed only on a telephone, no ring occurs for a transferred call.
An auxiliary ringer can also be programmed in Services to ring for a line placed into
a scheduled Ringing service. Refer to “Configuring ringing service” on page 490

Business Communications Manager 3.6 Programming Operations Guide

242

Assigning Trunk/line data

Table 33 Ground start fields (Continued)
Attribute

Value

Description

Redirect to



Enter a dial string (including routing code) to redirect the line to an external
telephone, such as a call attendant on another system.
If you want to stop redirection, you need to delete the dial string and allow the
record to update.

WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them now to
ensure your system will function properly.

DID fields
Table 34 DID line fields
Attribute

Value

P0609326 1.1

Description

Assigning Trunk/line data

243

Table 34 DID line fields (Continued)
Attribute

Value

Description

Line type

Public
Private to:
Pool A to O

Define how the line is used in relation to other lines in the system.
• Public line: can be accessed by more than one telephone.
• Private line: can be assigned only to one telephone and the prime telephone for
that line. Enter the internal number of the telephone.
• Pool A - O: assigns the line to one of the line pools. If a line is assigned to a line
pool, but is not assigned to any telephone, that line is available only for outgoing
calls.
For more information and tips, refer to “Line pool tips” on page 259.

Dial mode

Pulse
Tone

Specify whether the system uses dual tone multifrequency (DTMF) or pulse
signaling on the trunk.
Tone does not appear if Signaling is set to Immediate
(T1 DID &T1 E&M trunk types only).

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on the line. For an Auto
Answer line, calls are redirected if the received number is invalid or the target line
is busy, and if the If busy parameter is set To prime.
Each line can be assigned only one prime telephone.

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already been assigned to at
least one line.

Distinct ring

Choose the distinctive ring pattern that you want to assign to the line. This allows
you to provide selective service to calls with differing answer priorities.
When more than one line with the distinct ring settings rings at a telephone, the line
with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

None
Pattern 2
Pattern 3
Pattern 4

Warning:
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern has
already been assigned to a telephone, all telephones with that ring pattern will be
reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
Auto privacy

Y or N

Use auxiliary Y or N
ringer

Define whether one Business Communications Manager user can select a line in
use at another telephone to join an existing call. Refer to “Turn Privacy on or off for
a call” on page 258. (FEATURE 83)
Turn the auxiliary ringer on or off for all telephones using this line.
When programmed on a line, the auxiliary ringer will ring every time a call is
received.
Note: When programmed only on a telephone, no ring occurs for a transferred call.
An auxiliary ringer can also be programmed in Services to ring for a line placed into
a scheduled Ringing service. Refer to “Configuring ringing service” on page 490

Signaling

WinkStart
Immediate
DelayDial

Select the signal type for the line. The immediate setting does not appear for T1
E&M or T1 DID trunks connected to a DTM if the Dial mode is set to tone.
Make sure that this matches the signal type programmed for the trunk at the other
switch.

Business Communications Manager 3.6 Programming Operations Guide

244

Assigning Trunk/line data

Table 34 DID line fields (Continued)
Attribute

Value

Description

ANI Number

Y or N

Define whether the telephone number of the caller will be collected for this line.
For T1 E&M and T1 DID trunks connected to a DTM, this setting only appears if
Signaling is set to WinkStart.
The central office must deliver ANI/DNIS in DTMF mode. No additional equipment
is required.

Redirect to



Enter a dial string (including routing code) to redirect the line to an external
telephone, such as a call attendant on another system.
If you want to stop redirection, you need to delete the dial string and allow the
record to update.

WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them now to
ensure your system will function properly.

E&M fields
Table 35 E&M line fields
Attribute

Value

E&M trunk

P0609326 1.1

Description

T1 E&M

Assigning Trunk/line data

245

Table 35 E&M line fields (Continued)
Attribute

Value

E&M trunk

Description

T1 E&M

Line type

Public
Private to:
Pool A to O

Define how the line is used in relation to other lines in the system.
• Public line: can be accessed by more than one telephone.
• Private line: can be assigned only to one telephone and the prime telephone for
that line. Enter the internal number of the telephone.
• Pool A - O: assigns the line to one of the line pools. If a line is assigned to a line
pool, but is not assigned to any telephone, that line is available only for outgoing
calls.
For more information and tips, refer to “Line pool tips” on page 259.

Dial mode

Pulse
Tone

Specify whether the system uses dual tone multifrequency (DTMF) or pulse
signaling on the trunk.
Tone does not appear if Signaling is set to Immediate
(T1 DID &T1 E&M trunk types only).

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on the line. For an Auto
Answer line, calls are redirected if the received number is invalid or the target line is
busy, and if the If busy parameter is set To prime.
Each line can be assigned only one prime telephone.

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already been assigned to at
least one line.

Business Communications Manager 3.6 Programming Operations Guide

246

Assigning Trunk/line data

Table 35 E&M line fields (Continued)
Attribute

Value

Description

Distinct ring

None
Pattern 2
Pattern 3
Pattern 4

Choose the distinctive ring pattern that you want to assign to the line. This allows
you to provide selective service to calls with differing answer priorities.
When more than one line with the distinct ring settings rings at a telephone, the line
with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

Warning:
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern has
already been assigned to a telephone, all telephones with that ring pattern will be
reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
Auto privacy

Y or N

Define whether one Business Communications Manager user can select a line in
use at another telephone to join an existing call. Refer to “Turn Privacy on or off for
a call” on page 258. (FEATURE 83)

Answer
mode

Manual
Auto

Define whether a trunk is manual or automatic answer.
Auto answer mode allows the trunk to be a shared resource by the system
telephones.
For auto answer trunks being used to allow remote call-in from system users, the
trunk can be configured to answer with a straight dial tone, if DISA has not been
enabled. It can also be configured to answer with a stuttered dial tone if DISA is
enabled and the caller is expected to enter a COS password. The COS password
defines which system features the caller is permitted to access.
Manual answer trunks are assigned to one or more telephones. The assigned
telephones exclusively own the line.

Answer with
DISA

Y or N

Define whether the system prompts a caller for a six-digit class of service (COS)
password (Y). This setting appears for T1 loop start and T1 E&M lines that have
auto-answer mode. Set this option to No for T1 E&M lines on a private network that
have auto-answer mode.

Use auxiliary Y or N
ringer

Turn the auxiliary ringer on or off for all telephones using this line.
When programmed on a line, the auxiliary ringer will ring every time a call is
received.
Note: When programmed only on a telephone, no ring occurs for a transferred call.
An auxiliary ringer can also be programmed in Services to ring for a line placed into
a scheduled Ringing service. Refer to “Configuring ringing service” on page 490

Signaling

WinkStart
Immediate
DelayDial

Select the signal type for the line. The immediate setting does not appear for T1
E&M or T1 DID trunks connected to a DTM if the Dial mode is set to tone.
Make sure that this matches the signal type programmed for the trunk at the other
switch.

ANI Number

Y or N

Define whether the telephone number of the caller will be collected for this line.
For T1 E&M and T1 DID trunks connected to a DTM, this setting only appears if
Signaling is set to WinkStart.
The central office must deliver ANI/DNIS in DTMF mode. No additional equipment
is required.

P0609326 1.1

Assigning Trunk/line data

247

Table 35 E&M line fields (Continued)
Attribute

Value

Description

DNIS
Number

Y or N

Defines whether the digits dialed by an external caller on this line will be
collected.For T1 E&M trunks connected to a DTM, this setting only appears if
Signaling is set to WinkStart and Answer mode is set to Manual.
These digits are required for some third-party software applications.

*Gain

Normal
High

Set the level of gain for the channel.
*E&M trunks only. T1 E&M trunks do not have this field.

Redirect to



Enter a dial string (including routing code) to redirect the line to an external
telephone, such as a call attendant on another system.
If you want to stop redirection, you need to delete the dial string and allow the
record to update.

WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them now to
ensure your system will function properly.

Target lines and DASS2 fields
Table 36 Target lines and DASS2 line fields
Attribute

Value

Description

Line type

Public
Private to:

Define how the line is used in relation to other lines in the system.
• Public line: can be accessed by more than one telephone.
• Private line: can be assigned only to one telephone and the prime telephone for
that line. Enter the internal number of the telephone.

If busy

To Prime
Busy Tone

Define whether a caller receives a busy tone or the call forwards to the prime
telephone when the target line is busy. Busy tone only works for PRI trunks.

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on the line. For an Auto
Answer line, calls are redirected if the received number is invalid or the target line is
busy, and if the If busy parameter is set To prime.
Each line can be assigned only one prime telephone.

Business Communications Manager 3.6 Programming Operations Guide

248

Assigning Trunk/line data

Table 36 Target lines and DASS2 line fields (Continued)
Attribute

Value

Description

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already been assigned to at
least one line.

Distinct ring

Choose the distinctive ring pattern that you want to assign to the line. This allows
you to provide selective service to calls with differing answer priorities.
When more than one line with the distinct ring settings rings at a telephone, the line
with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

None
Pattern 2
Pattern 3
Pattern 4

Warning:
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern has
already been assigned to a telephone, all telephones with that ring pattern will be
reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
Use auxiliary Y or N
ringer

Turn the auxiliary ringer on or off for all telephones using this line.
When programmed on a line, the auxiliary ringer will ring every time a call is
received.
Note: When programmed only on a telephone, no ring occurs for a transferred call.
An auxiliary ringer can also be programmed in Services to ring for a line placed into
a scheduled Ringing service. Refer to “Configuring ringing service” on page 490

Received #
(Private
Number/
Public
Number)



Specify the digits to make a specific target line ring.
• A received number cannot be the same as, or be the start digits, of a line pool
access code, a destination code, the DISA DN or the Auto DN.
• If you are configuring auto-answer BRI trunks to map to target lines, the
received number should be the same as the Network DN supplied by your
service provider. The call will be directed to the prime telephone for the
incoming line if the Network DN is not used.
For further information, refer to “Received #” on page 259.

Redirect to



Enter a dial string (including routing code) to redirect the line to an external
telephone, such as a call attendant on another system.
If you want to stop redirection, you need to delete the dial string and allow the
record to update.

WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them now to
ensure your system will function properly.
Assign target lines

P0609326 1.1

Refer to “Assigning target lines” on page 287.

Assigning Trunk/line data

249

PRI fields
Table 37 PRI line fields
Attribute

Value

Description

Line type

PRI A to PRI-F

Define how the line is used in relation to other lines in the system.
• PRI A to PRI F: you must use routes and destination codes to direct PRI lines.

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on the line. For an Auto
Answer line, calls are redirected if the received number is invalid or the target line is
busy, and if the If busy parameter is set To prime.
Each line can be assigned only one prime telephone.

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already been assigned to at
least one line.

Distinct ring

Choose the distinctive ring pattern that you want to assign to the line. This allows
you to provide selective service to calls with differing answer priorities.
When more than one line with the distinct ring settings rings at a telephone, the line
with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

None
Pattern 2
Pattern 3
Pattern 4

WARNING:
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern has
already been assigned to a telephone, all telephones with that ring pattern will be
reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them now to
ensure your system will function properly.

Business Communications Manager 3.6 Programming Operations Guide

250

Assigning Trunk/line data

BRI fields
Table 38 BRI line fields
Attribute

Value

Description

Manual answer line

Auto answer line

Line type

Public
Private to:
PRI A to PRI-F

Define how the line is used in relation to other lines in the system.
• Public line: can be accessed by more than one telephone.
• Private line: can be assigned only to one telephone and the prime telephone for
that line. Enter the internal number of the telephone.
• PRI A to PRI F: assigns the line to one of the line pools. If a line is assigned to a
line pool, but is not assigned to any telephone, that line is available only for
outgoing calls.
For more information and tips, refer to “Line pool tips” on page 259.

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on the line. For an Auto
Answer line, calls are redirected if the received number is invalid or the target line is
busy, and if the If busy parameter is set To prime.
Each line can be assigned only one prime telephone.

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already been assigned to at
least one line.

Distinct ring

Choose the distinctive ring pattern that you want to assign to the line. This allows
you to provide selective service to calls with differing answer priorities.
When more than one line with the distinct ring settings rings at a telephone, the line
with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

None
Pattern 2
Pattern 3
Pattern 4

P0609326 1.1

Assigning Trunk/line data

251

Table 38 BRI line fields (Continued)
Attribute

Value

Description

Warning:
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern has
already been assigned to a telephone, all telephones with that ring pattern will be
reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
Auto privacy

Y or N

Define whether one Business Communications Manager user can select a line in
use at another telephone to join an existing call. Refer to “Turn Privacy on or off for
a call” on page 258. (FEATURE 83)

Answer
mode

Manual
Auto

Define whether a trunk is manual or automatic answer.
Auto answer mode allows the trunk to be a shared resource by the system
telephones.
For auto answer trunks being used to allow remote call-in from system users, the
trunk can be configured to answer with a straight dial tone, if DISA has not been
enabled. It can also be configured to answer with a stuttered dial tone if DISA is
enabled and the caller is expected to enter a COS password. The COS password
defines which system features the caller is permitted to access.
Manual answer trunks are assigned to one or more telephones. The assigned
telephones exclusively own the line.

Answer with
DISA

Y or N

Define whether the system prompts a caller for a six-digit class of service (COS)
password. This setting appears for T1 loop start and T1 E&M lines that have
auto-answer mode. Set this option to No for T1 E&M lines on a private network that
have auto-answer mode.

Use auxiliary Y or N
ringer

Turn the auxiliary ringer on or off for all telephones using this line.
When programmed on a line, the auxiliary ringer will ring every time a call is
received.
Note: When programmed only on a telephone, no ring occurs for a transferred call.
An auxiliary ringer can also be programmed in Services to ring for a line placed into
a scheduled Ringing service. Refer to “Configuring ringing service” on page 490

Full autohold Y or N

Enables or disables Full autohold.
When enabled, if a caller selects an idle line but does not dial any digits, that line is
automatically placed on hold if you then select another line.
The default setting should be changed only if Full autohold is required for a specific
application.

WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them now to
ensure your system will function properly.

Business Communications Manager 3.6 Programming Operations Guide

252

Assigning Trunk/line data

DPNSS fields
Table 39 DPNSS line fields
Attribute

Value

Description

Line type

Public
Private to:
PRI A to PRI-F

Define how the line is used in relation to other lines in the system.
• Public line: can be accessed by more than one telephone.
• Private line: can be assigned only to one telephone and the prime telephone for
that line. Enter the internal number of the telephone.
• PRI A to PRI F: assigns the line to one of the line pools. PRI line pools must be
used in conjunction with routes and destination codes.

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on the line. For an Auto
Answer line, calls are redirected if the received number is invalid or the target line is
busy, and if the
If busy parameter is set To prime.
Each line can be assigned only one prime telephone.

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already been assigned to at
least one line.

Distinct ring

Choose the distinctive ring pattern that you want to assign to the line. This allows
you to provide selective service to calls with differing answer priorities.
When more than one line with the distinct ring settings rings at a telephone, the line
with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

None
Pattern 2
Pattern 3
Pattern 4

Warning:
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern has
already been assigned to a telephone, all telephones with that ring pattern will be
reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
Refer to “Defining user preferences” on page 415 for information about assigning a
distinctive ring pattern to a telephone.
You can also assign a distinctive ring pattern to a Hunt group. Refer to “Identifying a
Hunt group” on page 575.
Answer
mode

Manual
Auto

P0609326 1.1

Define whether a trunk is manual or automatic answer.
Auto answer mode allows the trunk to be a shared resource by the system
telephones.
For auto answer trunks being used to allow remote call-in from system users, the
trunk can be configured to answer with a straight dial tone, if DISA has not been
enabled. It can also be configured to answer with a stuttered dial tone if DISA is
enabled and the caller is expected to enter a COS password. The COS password
defines which system features the caller is permitted to access.
Manual answer trunks are assigned to one or more telephones. The assigned
telephones exclusively own the line.

Assigning Trunk/line data

253

Table 39 DPNSS line fields
Attribute

Value

Use auxiliary Y or N
ringer

Description
Turn the auxiliary ringer on or off for all telephones using this line.
When programmed on a line, the auxiliary ringer will ring every time a call is
received.
Note: When programmed only on a telephone, no ring occurs for a transferred call.
An auxiliary ringer can also be programmed in Services to ring for a line placed into
a scheduled Ringing service. Refer to “Configuring ringing service” on page 490

Full autohold Y or N

Enables or disables Full autohold.
When enabled, if a caller selects an idle line but does not dial any digits, that line is
automatically placed on hold if you then select another line.
The default setting should be changed only if Full autohold is required for a specific
application.

WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them now to
ensure your system will function properly.

VoIP fields
Table 40 VoIP line data fields
Attribute

Value

Description

Line type

Public
Private to:
Pool A to O

Define how the line is used in relation to other lines in the system.
• Public line: can be accessed by more than one telephone.
• Private line: can be assigned only to one telephone and the prime telephone for
that line. Enter the internal number of the telephone.
• Pool A - O/PRI A to PRI F: assigns the line to one of the
15 line pools. If a line is assigned to a line pool, but is not assigned to any
telephone, that line is available only for outgoing calls.
For more information and tips, refer to “Line pool tips” on page 259.

Business Communications Manager 3.6 Programming Operations Guide

254

Assigning Trunk/line data

Table 40 VoIP line data fields (Continued)
Attribute

Value

Description

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on the line. For an Auto
Answer line, calls are redirected if the received number is invalid or the target line is
busy, and if the If busy parameter is set To prime.
Each line can be assigned only one prime telephone.

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already been assigned to at
least one line.

Distinct ring

Choose the distinctive ring pattern that you want to assign to the line. This allows
you to provide selective service to calls with differing answer priorities.
When more than one line with the distinct ring settings rings at a telephone, the line
with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

None
Pattern 2
Pattern 3
Pattern 4

Warning:
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern has
already been assigned to a telephone, all telephones with that ring pattern will be
reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
Auto privacy

Y or N

Use auxiliary Y or N
ringer

This setting has no effect on VoIP lines.
Turn the auxiliary ringer on or off for all telephones using this line.
When programmed on a line, the auxiliary ringer will ring every time a call is
received.
Note: When programmed only on a telephone, no ring occurs for a transferred call.
An auxiliary ringer can also be programmed in Services to ring for a line placed into
a scheduled Ringing service. Refer to “Configuring ringing service” on page 490

Full autohold Y or N

Enables or disables Full autohold.
When enabled, if a caller selects an idle line but does not dial any digits, that line is
automatically placed on hold if you then select another line.
The default setting should be changed only if Full autohold is required for a specific
application.

WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them now to
ensure your system will function properly.

P0609326 1.1

Assigning Trunk/line data

255

Lines field cross-reference chart
The following table provides a quick cross reference that shows common line fields, noted by
trunk type.
Table 41 Combined line settings table
Trunk types

Attribute

Value

Description

All

Line type

Public
Private to:
Pool A to O,
PRI A to PRI-F

Define how the line is used in relation to other lines in the
system.
• Public line: can be accessed by more than one telephone.
• Private line: can be assigned only to one telephone and
the prime telephone for that line. Enter the internal
number of the telephone.
• Pool A - O (digital lines and VoIP trunks/PRI-A to PRI-F
(PRI and BRI lines): assigns the line to one of the line
pools. If a line is assigned to a line pool, but is not
assigned to any telephone, that line is available only for
outgoing calls.
PRI line pools must be used in conjunction with routes
and destination codes. target lines cannot be put into line
pools.
For more information and tips, refer to “Line pool tips” on
page 259.

Loop start analog
Loop start digital
Ground start digital
DID
E&M

Dial mode

Pulse
Tone

Specify whether the system uses dual tone multifrequency
(DTMF) or pulse signaling on the trunk.
Tone does not appear if Signaling is set to Immediate
(T1 DID &T1 E&M trunk types only).

Target lines
DASS2

Received #
(Private
Number/
Public
Number)



Specify the digits to make a specific target line ring.
• A received number cannot be the same as, or be the start
digits, of a line pool access code, a destination code, the
DISA DN or the Auto DN.
• If you are configuring auto-answer BRI trunks to map to
target lines, the received number should be the same as
the Network DN supplied by your service provider. The
call will be directed to the prime telephone for the
incoming line if the Network DN is not used.
For further information, refer to “Received #” on page 259.

Target lines
DASS2

If busy

To Prime
Busy Tone

Define whether a caller receives a busy tone or the call
forwards to the prime telephone when the target line is busy.
Busy tone only works for PRI trunks.

All

Prime set

DN:
None

Assign a telephone to provide backup answering for calls on
the line. For an Auto Answer line, calls are redirected if the
received number is invalid or the target line is busy, and if the
If busy parameter is set To prime.
Each line can be assigned only one prime telephone.

All

Distinct rings read-only
in use

This field shows the Distinct Ring Patterns that have already
been assigned to at least one line.

Business Communications Manager 3.6 Programming Operations Guide

256

Assigning Trunk/line data

Table 41 Combined line settings table (Continued)
Trunk types

Attribute

Value

Description

All

Distinct ring

None
Pattern 2
Pattern 3
Pattern 4

Choose the distinctive ring pattern that you want to assign to
the line. This allows you to provide selective service to calls
with differing answer priorities.
When more than one line with the distinct ring settings rings
at a telephone, the line with the highest priority will ring first.
• Pattern 4 has the highest ring priority
• Pattern 3 has second highest ring priority
• Pattern 2 has third highest ring priority
• None has the lowest ring priority.
By default, all telephones and lines are set to None

WARNING
If you assign a distinctive ring pattern to a line, and that distinctive ring pattern
has already been assigned to a telephone, all telephones with that ring pattern
will be reset to pattern 1.
If you assign a distinctive ring pattern to a telephone, and that distinctive ring
pattern has already been assigned to a line, all lines with that ring pattern will be
reset to None.
Refer to “Defining user preferences” on page 415 for information about
assigning a distinctive ring pattern to a telephone.
You can also assign a distinctive ring pattern to a Hunt group. Refer to
“Identifying a Hunt group” on page 575.
Loop start analog
Loop start digital
Ground start digital
DID
E&M
BRI
VoIP

Auto privacy

Y or N

Define whether one Business Communications Manager
user can select a line in use at another telephone to join an
existing call. Refer to “Turn Privacy on or off for a call” on
page 258 (FEATURE 83).
Note: This setting has no effect on VoIP lines.

Loop start analog
Loop start digital

Trunk mode

Unspr
Supervised
*Earth calling
*Loop guarded
*Loop
unguarded

Define whether disconnect supervision, also referred to as
loop supervision, releases an external line when an open
switch interval (OSI) is detected during a call on that line.
You must set this to Supervised if a loop trunk has its Answer
mode set to Auto or if you enable Answer with DISA.
Disconnect supervision is also required to conference two
external callers. The line must be equipped with disconnect
supervision from the central office for the Supervised option
to work.
* These listing only appear for UK analog lines. Note that
Earth calling is only supported by a FEM connected to a
Norstar analog trunk module. The GATM does not support
Earth calling, even though the setting appears for the lines on
the module.
Tips: The duration of an open switch interval (OSI) before
Business Communications Manager disconnects a call is
programmed by the Disconnect timer setting. Refer to
“Configuring the trunk module to line type” on page 131.

P0609326 1.1

Assigning Trunk/line data

257

Table 41 Combined line settings table (Continued)
Trunk types

Attribute

Value

Description

Loop start analog
Loop start digital
Ground start digital
E&M
BRI
DPNSS

Answer
mode

Manual
Auto

Define whether a trunk is manual or automatic answer.
Auto answer mode allows the trunk to be a shared resource
by the system telephones.
For auto answer trunks being used to allow remote call-in
from system users, the trunk can be configured to answer
with a straight dial tone, if DISA has not been enabled. It can
also be configured to answer with a stuttered dial tone if
DISA is enabled and the caller is expected to enter a COS
password. The COS password defines which system
features the caller is permitted to access.
Manual answer trunks are assigned to one or more
telephones. The assigned telephones exclusively own the
line.
Note: You require Disconnect supervision on the line if loop
start trunks are to operate in auto-answer mode.

Loop start analog
Loop start digital
Ground start digital
E&M
BRI

Answer with
DISA

Y or N

Define whether the system prompts a caller for a six-digit
class of service (COS) password. This setting appears for T1
loop start and T1 E&M lines that have auto-answer mode.
Set this option to No for T1 E&M lines on a private network
that have auto-answer mode.
To program DISA on a PRI trunk you need to specify a DISA
DN, see “Creating Direct Inward System Access (DISA)” on
page 291 and “Programming access codes” on page 310.

Loop start analog

Link at CO

Y or N

Some exchanges respond to a Link signal (FEATURE 71) by
providing an alternative line for making outgoing calls.
Enabling Link at CO causes the system to apply the
restrictions on outgoing calls to the digits dialed after the Link
signal. As well, the call on the alternative line is subject to all
restrictions.
Disabling Link at CO prevents a Link signal from resetting the
Business Communications Manager restrictions in cases
where the host exchange does not provide an alternative
line.

Loop start analog
Loop start digital
Ground start digital
DID
E&M
BRI
Target lines
VoIP
DASS2
DPNSS

Use auxiliary Y or N
ringer

Turn the auxiliary ringer on or off for all telephones using this
line.
When programmed on a line, the auxiliary ringer will ring
every time a call is received.

Loop start analog
Loop start digital
BRI
VoIP
DPNSS

Full autohold Y or N

Note: When programmed only on a telephone, no ring
occurs for a transferred call.
An auxiliary ringer can also be programmed in Services to
ring for a line placed into a scheduled Ringing service. Refer
to “Configuring routing service” on page 495.
Enables or disables Full autohold.
When enabled, if a caller selects an idle line but does not dial
any digits, that line is automatically placed on hold if you then
select another line.
Full autohold is always in place for T1 E&M trunks because it
has no meaning for incoming-only T1 DID trunks.
The default setting should be changed only if Full autohold is
required for a specific application.

Business Communications Manager 3.6 Programming Operations Guide

258

Assigning Trunk/line data

Table 41 Combined line settings table (Continued)
Trunk types

Attribute

Value

Description

Loop start analog

Loss
Packages

Short CO
Medium CO
Long CO
Short PBX
Long PBX

Select the appropriate loss/gain and impedance settings for
each line.
For more information refer to “Using loss packages” on page
260.

DID
E&M

Signaling

WinkStart
Immediate
DelayDial

Select the signal type for the line. The immediate setting
does not appear for T1 E&M or T1 DID trunks connected to a
DTM if the Dial mode is set to tone.
Make sure that this matches the signal type programmed for
the trunk at the other switch.

DID
E&M

ANI Number

Y or N

Define whether the telephone number of the caller will be
collected for this line.
For T1 E&M and T1 DID trunks connected to a DTM, this
setting only appears if Signaling is set to WinkStart.
The central office must deliver ANI/DNIS in DTMF mode. No
additional equipment is required.

E&M

DNIS
Number

Y or N

Defines whether the digits dialed by an external caller on this
line will be collected.For T1 E&M trunks connected to a DTM,
this setting only appears if Signaling is set to WinkStart and
Answer mode is set to Manual.
These digits are required for some third-party software
applications.

E&M

*Gain

Normal
High

Set the level of gain for the channel.
*E&M trunks only. T1 E&M trunks do not have this field.

Loop Start (GATM
only)

Impedance

600 ohm
900 ohm

The GATM can be set to a specific impedance level.

Loop start analog
Loop start digital
Ground start digital
DID
E&M
Target lines
DASS2

Redirect to



Enter a dial string (including routing code) to redirect the line
to an external telephone, such as a call attendant on another
system.
If you want to stop redirection, you need to delete the dial
string and allow the record to update.

WARNING: Enable modules
If you disabled any trunk media bay modules prior to performing programming, enable them
now to ensure your system will function properly.

Turn Privacy on or off for a call
You can configure lines in your system to have automatic privacy. With a line not programmed
with privacy, anyone with the line assigned to their telephone can join your call by pressing the
line button. With a line programmed with privacy, one person at a time can use the line.
Use Feature 83 to turn the privacy feature off and on.
Privacy control cannot be used for internal or conference calls.
When another telephone joins a call, the participants on the call hear a tone, and a message appears
on the telephone display. It is not possible to join a call without everyone hearing this tone.
P0609326 1.1

Assigning Trunk/line data

259

Note: The Auto privacy setting does not apply to target lines, PRI lines or VoIP trunking lines.

Received #
Target lines provide an additional record under Trunk/Line Data, and that is the Received
number. You can specify received numbers for both private (VoIP and MCDN) and public
network connections. This allows the system to identify the source of the call on a per-call basis.
1

Click on Received Number.
The Line XXX Received Number screen appears.

Figure 50 Target line Private and Public received numbers

2

Public number: The Network DN supplied by your service provider.
Private number: The DN number of the telephone or Hunt group.

3

Go to the DN record for that telephone and ensure that the target line number is specified in
the Line Assignment section.
Caution: Changing the received # length:
If you change the received number length for your system, the Public number entry for
the target lines will clear if the new received # length is less than the number entered in this
field.
If the new received # length has more digits than the number entered in this field, you need
to change the entry manually, if changes are required. Refer to “Changing the received #
length” on page 286.

Line pool tips
Read these tips before you assign your line pools.
•
•
•
•

Line pools must never contain a mixture of lines. All lines in a given line pool should go to the
same location.
Avoid putting unsupervised loop start lines in a line pool. These lines can become unusable,
especially when a remote user uses the line pool to make an external call.
Assign line pool access to telephones in Line access programming.
Assign system-wide line pool access codes in General settings (not applicable to PRI pools).

Business Communications Manager 3.6 Programming Operations Guide

260

Assigning Trunk/line data

•

•
•

A telephone can be administered to search automatically for an idle line from several lines that
appear on the telephone. Assign a line pool as the prime line (in Line access) and all the lines
in the line pool must appear on that telephone. When the user lifts the receiver or presses
Handsfree, any one of the lines, if idle, can be selected by Automatic Outgoing Line selection.
Changes in the settings for trunk type on a system that is in use, can result in dropped calls.
When assigning lines to line pools, consider your network configuration. You can create a
unified dialing plan by assigning lines to the same location to the same line pool on each of
your systems. For example, if system A and system B each have tie lines to system C, assign
the tie lines to pool D on each of the systems. You cannot assign target lines to a line pool, as
they are incoming-only.

Using loss packages
The Loss package settings allow you to select the appropriate loss/gain and impedance settings for
each line. The setting is based on the terminating switch type and the distance between Business
Communications Manager and the terminating switch.
When measuring the distance from Business Communications Manager to CO and from Business
Communications Manager to PBX systems, use 600 ohms as the termination resistance setting.
Table 42 Loss package settings
Loss
Package

Receive
Loss

Transmit
Loss

Impedance

Distance to switch/cable loss/terminating switch

Short CO

0 dB

3 dB

Short

Short/<2 dB/Business Communications Manager to CO

Medium CO

0 dB

0 dB

TIA/EIA 464

Medium/>2 dB and <6 dB/Business Communications
Manager to CO

Long CO

-3 dB

0 dB

TIA/EIA 464

Long/>6 dB/Business Communications Manager to CO

Short PBX

0 dB

0 dB

Short

Short/<2 dB/Business Communications Manager to PBX

Long PBX

-3 dB

0 dB

TIA/EIA 464

Long/>2 dB/Business Communications Manager to PBX

A loss of 4 dB corresponds to a cable length of approximately 2700 m (9000 ft).

P0609326 1.1

Assigning Restrictions

261

Assigning Restrictions
Restrictions prevent you from making certain kinds of calls from specific lines on the telephone.
You can also restrict some features. This section describes how to apply restriction filters to lines.
You can assign a different restriction filter for normal service and for each of six schedules.
Refer to “Defining service schedules” on page 489 for more information about setting up
schedules. For PRI, line restriction changes apply to all 23 lines.
Note: The template has a set of default restrictions in Restriction 02, only. You must create your
own restriction files if you want to use other settings. For details about creating restriction files,
refer to “Defining restriction filters” on page 344.

Setting line restrictions
The Line Restrictions heading allows you to specify the filter applied to this line to restrict the
dial-out numbers. Follow these steps to create line restrictions:
1

Choose Services, Telephony Services, Lines, Line nnn, Restrictions,

2

Click on the key beside Line restrictions.

3

Click the schedule heading that you want to configure.
For example, Night.
The Line restriction window for that schedule appears.

Figure 51 Entering a line restriction filter

4

In the Use filter box, type in the number of the restriction filter you want to assign as the line
restriction for this schedule.
The default restriction filters are listed in the following table.

Table 43 Default restriction filters
Schedule

Restriction filter

Normal

03

Schedule

Restriction filter

Schedule 1 (Night)

21

Schedule 4

00

Schedule 2 (Evening)

22

Schedule 5

00

Schedule 3 (Lunch)

23

Schedule 6

00

Business Communications Manager 3.6 Programming Operations Guide

262

Assigning Restrictions

Note: When a remote user places an external call on a line, any filters used with the line still apply.
However, if DND is active on the line, no set or set/line restrictions apply.

Setting remote restrictions
Specify the restriction filter for the line that remote callers use to call in to Business
Communications Manager.
1

From the Lines headings, choose the line you want to set restrictions for.

2

Click on the key beside Remote restrictions.

3

Click the schedule heading that you want to configure. For example, Night.
The Remote restriction window for that schedule appears.

Figure 52 Enter remote restriction filters for a line

4

In the Use filter box, type in the number of the restriction filter you want to assign as the
remote restriction for this schedule.

5

Select the remote restrictions for each schedule. The default restrictions are shown in the
following table.

Table 44 Default remote restrictions
Schedule

Restriction filter

Schedule

Restriction filter

Normal

04

Schedule 1 (Night)

31

Schedule 4

00

Schedule 2 (Evening)

32

Schedule 5

00

Schedule 3 (Lunch)

33

Schedule 6

00

Note: The remote restriction restricts the numbers a user can dial on an incoming auto-answer line.
If a remote user then selects a line to place an external call, any filter used with the line still
applies.

P0609326 1.1

Setting line telco features

263

Setting line telco features
If you subscribe to a voice message service outside your office, you can access it through your
Business Communications Manager system. You can specify what voice message center you use
for each external line that receives message waiting indication.
1

Click on the keys beside Services, Telephony Services, Lines.

2

Click on the Line record.

3

Click the Telco features heading.
The Telco features window for the line appears.

Figure 53 Choosing a remote voice message center

4

Select the Voice message center for the line, Center 1 - Center 5 or None.
Note: To program the external numbers for each Center, refer to “Configuring centralized
voice mail” on page 559. If you have an MCDN private network set up, where the voice
message center is on a voice message device attached to the Meridian, this feature would have
to be set in all systems to point to that system, except for the telephones directly attached to the
Meridian system.

Line matrix
To help you with your line planning, transfer the following information to a spreadsheet and fill
out the values for each line you provision.
Table 45 Line attributes
General
Name
Control set
Use remote package
Trunk/line Data
Trunk Type
Line Type

Answer with DISA

Dial mode

Link at CO

Received #

Use auxiliary ringer

If busy

Full autohold

Business Communications Manager 3.6 Programming Operations Guide

264

Setting line telco features

Table 45 Line attributes (Continued)
Prime set

Loss package

Auto privacy

Signaling

Trunk mode

ANI Number

Answer mode

DNIS Number

Received #

Distinctive Ring

Line restrictions

Remote restrictions

Normal

03

Normal

04

Schedule 1 (Night)

21

Schedule 1 (Night)

31

Schedule 2 (Evening)

22

Schedule 2 (Evening)

32

Schedule 3 (Lunch)

23

Schedule 3 (Lunch)

33

Schedule 4

00

Schedule 4

00

Schedule 5

00

Schedule 5

00

Schedule 6

00

Schedule 6

00

Telco features: Voice message center

P0609326 1.1

Center 1 to 5 or None

265

Chapter 10
Configuring BRI Loops
The following sections describe the information accessed under the Services, Telephony
Services, Loops headings. The Loops headings allow you to program BRI S, T, U2, and U4 ISDN
loop settings.
Task:
Configure the BRI loops connected to the system through BRI modules.
Note: DECT programming is contained in separate documentation.
This section includes information about:
•
•
•
•
•
•
•

“BRI configuration process map” on page 266
“Identifying BRI T-loops (T1 profiles)” on page 267
“Identifying BRI T-loops (ETSI, QSIG)” on page 271
“Configuring D-packet service for T loops” on page 273
“Provisioning the loop variables” on page 274
“Setting BRI for ISDN device connections” on page 278
“Loop matrix” on page 281

The Loops screens define the loop numbers and loop attributes that correspond to the DIP switch
settings that were configured on the BRI trunk media bay modules installed on your system. Check
your Programming Record to see which modules are installed, and what settings were chosen.
Available BRI trunk loop attributes are determined by the country profile that is assigned to your
system. All profiles allow BRI programming, however, there is a difference between T1-based
profiles and for E1-based profiles. Refer to “Core software and regions” on page 846 for a list of
countries and profiles.
Once loops are provisioned, the system assigns two line numbers per loop. These lines are then
programmed as you would any other lines. Refer to “BRI fields” on page 250 for a description of
the headings that appear for lines defined for BRI loops. Lines programming is explained under
Chapter 9, “Configuring lines,” on page 227.
Note: DECT modules contain BRI lines, however, these lines are configured as part of the DECT
programming. Refer to the DECT Installation and Configuration Guide for details.

Business Communications Manager 3.6 Programming Operations Guide

266

BRI configuration process map

The following figure shows a detailed view of the Loops headings.
Figure 54 Loops headings
T-loops (North America):
Telephony Services
Loops

T-loops (ETSI, QSIG):
Telephony Services
Loops

Loop 201-xxx
SPIDs
Network DNs
DN 01
D-packet service
TEIs

S-loops (all profiles):
Telephony Services
Loops

Loop 201-xxx
D-packet service
TEIs

Loop 201-xxx
DNs on loop
Assigned DNs
DN XXX

BRI configuration process map
The following process map shows the steps for configuring loops for T-1 based BRI modules.
Figure 55 Process map: Configuring the loops for your BRI module
BRI module is installed and system is running.

Note the loops that are active. (Services, Telephony Services, Loops)

Configure loops to support ISDN trunks or ISDN terminals.

Trunk (T) loops
Configure trunk loop variables.
“Identifying BRI T-loops (T1 profiles)”
on page 267
“Identifying BRI T-loops (ETSI, QSIG)”
on page 271
Set up D-packet service, if required.
“Configuring D-packet service for T
loops” on page 273

S loops
Configure terminal loop variables. “Setting
BRI for ISDN device connections” on page
278
Configure ISDN device records.
“Configure the ISDN terminal records” on
page 281

Provision the loops and lines.
“Provisioning the loop variables” on
page 274
Configure the line records. Put into line
pools. “BRI fields” on page 250

Assign lines and line pools to telephone
records. “Assigning the lines to
telephones” on page 277

P0609326 1.1

Test

Identifying BRI T-loops (T1 profiles)

267

You can program a loop to support either trunking services to the ISDN network, or terminal
services to one or more ISDN devices. The following sections describe the programming for each
type of loop. For complete module installation instructions and safety precautions, see the
Installation and Maintenance Guide.

Using an NT-1 for BRI U2/BRI U4
The Business Communications Manager supports the BRI S/T protocol. If your ISDN service
provider provides U-type ISDN service or the BRI devices are U-type devices, you need to obtain
a network terminal (NT-1) device. This device is installed between the ISDN network feed and the
Business Communications Manager for trunking loops. It is installed between the Business
Communications Manager and the ISDN device or the ISDN bus connecting several ISDN devices
on a BRI terminal loop.

Identifying BRI T-loops (T1 profiles)
T1-based BRI loops have three parameters that identify loop characteristics.
1

In the Unified Manager, click on the keys beside Services, Telephony Services, Loops.

2

Click on the loop number you want to configure as an ISDN trunk connection.

Figure 56 T-loop screen (T1 profiles)

3

Configure the loop settings according to the following table:

Table 46 Loop settings
Attribute

Value

Type

T

Clock Source

Primary
Secondary
Master

Description

Default: Master
This setting determines whether the system uses this module as the clock
source for the network.

Business Communications Manager 3.6 Programming Operations Guide

268

Identifying BRI T-loops (T1 profiles)

Table 46 Loop settings (Continued)
Attribute

Value

Description

ONN blocking state

Suppression bit,
Service code

Set the Outgoing Name and Number (ONN) Blocking.
When you activate ONN, a user can press FEATURE 819 to block the
outgoing name and number on a per call basis.
Suppression bit: the system flags the call to the Central Office (CO) so
that the name and number is not sent to the person you call.
Service code: VSC digits are dialed out before the called number to
activate ONN at the central office. These codes are supplied by your
service provider for the lines. Refer to “Configuring ONN blocking service
codes” on page 480. PRI lines have only one code, so do not require
specific configuration.
Programming note: Ensure that all telephones that have this feature
available are assigned valid OLI numbers. Refer to “Assigning line access”
on page 394.

Adding SPIDs
System running with T1 country profiles (North American) support additional BRI services
offered by ISDN service providers and defined by network service profile identifiers (SPIDs). The
SPID allows you to enter a network connection that provides a path for voice or data services.
1

Collect the information supplied by your service provider: SPIDs, Network DNs, TEIs.
For ISDN BRI service, your service provider supplies Service Profile Identifiers, network
DNs. You need to assign a SPID to a loop before you can assign Network DNs to that loop.

2

Click on the keys beside Services, Telephony Services, Loops, Loop XXX, where Loop
XXX is the loop where you want to assign SPIDs.

3

Click the SPIDs heading.

4

Click the Add button.
The SPID dialog box appears.

Figure 57 Adding a SPID

5

Type in the SPID number.

6

Click Save.
SPID 1 appears as a sub-heading.

P0609326 1.1

Identifying BRI T-loops (T1 profiles)

269

Identifying the SPID B-channels
1

Click on the keys beside Services, Telephony Services, Loops, Loop XXX, SPIDs.

2

Click the SPID # heading for the SPID record for which you want to assign B-channels.

Figure 58 Assign number of B-channels per SPID

3

Select 1 or 2 in the Number of B-channels box.

4

Click outside the window to save the setting.

Adding SPID network DNs
1

Under the SPID # heading, click the Network DNs heading.

2

Click the Add button above the navigation tree.

Figure 59 Add Network DN to SPID X

3

Type the ISDN DN number in the DN box for the device you want to use.

4

Click the Save button. DN 01 appears as a sub-heading.

5

Click the first DN #.

6

In the Call type field, select Voice, Data or Both.

Business Communications Manager 3.6 Programming Operations Guide

270

Identifying BRI T-loops (T1 profiles)

Figure 60 Specifying a Network DN call type

7

Repeat for all the DNs assigned to the Network DN.

P0609326 1.1

Identifying BRI T-loops (ETSI, QSIG)

271

Identifying BRI T-loops (ETSI, QSIG)
BRI loops for ETSI and ETSI-QSIG provide some flexibility in defining the T-loop
characteristics. Refer to “Core software and regions” on page 846 for a detailed list of countries
that use these profiles.
1

Collect the information supplied by your service provider.

2

In the Unified Manager, click on the keys beside Services, Telephony Services, Loops.

3

Click on the loop number you want to configure as an ISDN trunk connection.

Figure 61 T-loop screen (UK profile)

4

Configure the loop settings according to the following table:

Table 47 Loop settings
Attribute

Value

Description

Type

T

Protocol

Euro, QSIG

Select the appropriate ISDN protocol.
The values displayed depend on both the market profile and software
keycodes.
Euro - ETSI ISDN standard
QSIG - also an ETSI standard. Only appears if the ETSI QSIG keycode is
loaded.

Clock Source

Primary
Secondary
Master

Default: Master
This setting determines whether the system uses this module as the clock
source for the network.
Note: Most service providers will be the Master, so this field will be set to
Primary or Secondary.

Overlap receiving

Y or N

Supports target lines in markets which use Overlap receiving signaling on
the BRI trunks. Overlap receiving must be configured for each BRI loop.

Business Communications Manager 3.6 Programming Operations Guide

272

Identifying BRI T-loops (ETSI, QSIG)

Table 47 Loop settings (Continued)
Attribute

Value

Local number length 0-10

Description
Set the local number length for loops to interfaces that receive overlap
rather than enbloc digits. This number is the total length of the called party
number received. This number is used to calculate the number of leading
digits that need to be removed by the system.
Note: This parameter appears only when Overlap receiving is set to Y.
Example:
Public received number = 4502303
Target line received numbers = 303
Local number length = 7
Public received number length = 3
Thus the first four digits are deleted by the system.

ONN blocking state

Suppression bit,
Service code

Send Name Display Y, N
(Type: QSIG trunks
only)

P0609326 1.1

Set the Outgoing Name and Number (ONN) Blocking. When the user
presses FEATURE 819, on a per-call basis, the system flags the call to the
Central Office (CO) so that the name and number is not sent to the person
being called.
Set this field to Suppression bit to use the Calling Line Information
Restriction (CLIR) service.
For ETSI ISDN lines that do not use the ETSI CLIR service, the Central
Office (CO) may use a Service code to provide blocking service. In that
case, this field must be set to Service code. The service provider code
must then be programmed into the ONN blocking section. Refer to
“Configuring ONN blocking service codes” on page 480.
Programming note: Ensure that all telephones that have this feature
available are assigned valid OLI numbers. Refer to “Assigning line access”
on page 394.
If you want the OLI of the calling telephone to display on the called
telephone, with this type of trunk, set this field to Y.
If this field is set to N, no outgoing call display is sent. Refer also to “Setting
BRI for ISDN device connections” on page 278.

Configuring D-packet service for T loops

273

Configuring D-packet service for T loops
This configuration occurs for all profiles.
A T-loop can be used in combination with an S-loop to provide D-packet service for a
point-of-sale terminal adapter (POSTA) or other D-packet device. To deliver D-packet service, a
network connection (T-loop) is programmed to work with a terminal connection (S-loop). The
loops must be on the same physical module. This service is disabled by default.
1

Under the T-loop you want to configure, click on D-packet service.

2

Beside D-packet enabled, choose N (disabled) or Y (enabled).

3

If you enable D-packet service, beside Associated loop, enter the S-loop you want to
associate.

Figure 62 Enable/disable D-packet service, and associate a loop

4

At the top of the navigation tree, click on the Add button.

5

In the Add D-packet dialog, enter a service number.

Figure 63 Add a D-packet service

6

Click on TEI.

7

At the top of the navigation tree, click on the Add button.

8

In the Add TEI dialog, enter the TEI number supplied by your service provider.

Business Communications Manager 3.6 Programming Operations Guide

274

Provisioning the loop variables

Figure 64 Add a TEI to the D-packet service

Provisioning the loop variables
When you assign a BRI loop as a trunk loop, you need to return to the media bay module settings
and provision the loop, and the lines assigned to the loop. Once the loop is provisioned, it displays
the two line numbers that are assigned to the loop, these also need to be provisioned.
Once the lines are provisioned, you can configure them in the same way as you would other lines.
Refer to “Programming BRI lines” on page 276.

Provisioning the Loop
1

Click the keys beside Resources, Media Bay Modules, Bus 0X, Modules on bus, Module X,
Provision loops
where Bus 0X is the bus to which the BRI module is configured; Module X is the offset (1, 2,
or 3) to which the BRI module was set.

2

Click on Loop XXX.
Loop XXX is the BRI loop that you specified as a trunk loop (T)

3

Beside the Status field, select Provisioned from the drop down list.

4

Click outside the Bus 0X-Module X-Loop XXX window to invoke the change of status.

Figure 65 Provisioning BRI loops

5

Click the key beside Loop XXX twice to close and then reopen the heading.

P0609326 1.1

Provisioning the loop variables

275

Provisioning the lines
Once you provision the loop, two numbers are assigned to the loop. These also need to be
separately provisioned.
1

Click the keys beside Resources, Media Bay Modules, Bus 0X, Modules on bus, Module X,
Provision loops, Loop XXX, Lines on Loop.
where Bus 0X is the bus to which the BRI module is configured; Module X is the offset (1, 2,
or 3) to which the BRI module was set, and Loop XXX is the BRI loop that you specified as a
trunk loop (T).

2

Click on Line XXX.

3

Beside the Status field, select Provisioned from the drop down list.

Figure 66 Provisioning BRI loop lines

4

Click outside the Bus 0X-Module X-Loop XXX window to invoke the change of status.

5

Repeat for second line, if there is one.

6

Make a note of the line numbers.

Business Communications Manager 3.6 Programming Operations Guide

276

Provisioning the loop variables

Programming BRI lines
Once the loops and lines are provisioned (“Provisioning the Loop” on page 274 and “Provisioning
the lines” on page 275), you program the lines in the same manner as you do for non-BRI lines,
under the Services, Telephony Services, Lines heading. Refer to “BRI fields” on page 250.
Figure 67 Configuring an auto-answer BRI line

Programming note: BRI lines can be configured as manual answer or auto-answer lines. If the
lines are configured as auto-answer lines, you need to set up target lines with the received # set to
the network number supplied by the ISDN service provider, then assign the target line to the ISDN
devices and other system telephones that will receive calls over this line. Refer to “Assigning
target lines” on page 287.
BRI lines can also be assigned restrictions (“Assigning Restrictions” on page 261) and the Telco
features (“Setting line telco features” on page 263).

P0609326 1.1

Provisioning the loop variables

277

Assigning the lines to telephones
Once the line records are programmed, assign the BRI lines or target lines and BRI line pools to
the DN records for the telephones that will use the line(s) to receive/send calls. Refer to
“Determining line assignments” on page 397 and “Assigning line pool access” on page 402.
Figure 68 Assigning the BRI line to a DN record.

Business Communications Manager 3.6 Programming Operations Guide

278

Setting BRI for ISDN device connections

Setting BRI for ISDN device connections
BRI S-loops support devices that use an ISDN interface. You can assign a single device to a loop,
or multiple devices connected through an NT-1 interface (“Using an NT-1 for BRI U2/BRI U4” on
page 267).
•
•
•

You can assign a maximum of eight devices to a loop.
Any device can only be configured to one loop.
S-loops do not supply any voltage for ISDN devices requiring power, such as video cameras.
Voltage for these devices must be supplied by an external source on the S-loop.

Wiring internal connections
The following diagram shows how to wire the BRI to connect to such S-Loop devices as video
phones, terminal adapters, and Grp 3 Fax machines.
Figure 69 BRI RJ45 wiring array
BRI connector

RJ45 sockets
87654321

P0609326 1.1

Pin #/connection
1 not used
2 not used
3 +RX
4 +TX
5 - TX
6 -RX
7
not used
8
not used

System side

+TX
+RX
- RX
-TX

Setting BRI for ISDN device connections

279

Configuring S-loops
1

Click on the keys beside Services, Telephony Services, Loops.

2

Click on the loop number you want to configure.

Figure 70 S-loop screen (North American profile)

3

Configure the loop settings according to the following table:

Table 48 Loop settings
Attribute

Value

Description

Which fields appear depends on the loop type.
Type

S

Sampling

Adaptive, Fixed

Select a sampling rate for the S-loop.
Fixed: two or more S-interface devices use the loop, and the length of the
loop is less than 200 m (650 ft.).
Adaptive: two or more S-interface devices use the loop, and the length of
the loop is greater than 200 m (650 ft.). If one device is using the loop, the
length of the loop can be a maximum of 1000 m (3230 ft)

ONN blocking state

Suppression bit,
Service code

Set the Outgoing Name and Number (ONN) Blocking.
When you activate ONN, a user can press FEATURE 819 to block the
outgoing name and number on a per call basis. The system flags the call to
the Central Office (CO) so that the name and number is not sent to the
person you call.

S loops allow you to assign ISDN DN record numbers for the terminal equipment on the loop. As
well, one of the terminal records must be designated as the Loop DN, to act as the termination
point for incoming data calls that do not get answered by the target device.

Business Communications Manager 3.6 Programming Operations Guide

280

Setting BRI for ISDN device connections

Assigning DNs to the S- loop
You can have a maximum of 58 ISDN DNs on your system. However, there are only 28 default
DNs provided. The default ISDN DN range is 597 to 694. To add to the defaults, you need to use
DNs from the Companion range: 565 to 597 (change DN type to ISDN and DECT)
Companion: If you have either a Companion wireless system, which uses the
Companion DNs, or a DECT portable system, which uses the ISDN and DECT DNs, ensure you
do not overwrite any DNs assigned to the handsets for these systems.
To assign device DNs to the loop DN (maximum of eight devices per loop):
1

Choose Services, Telephony Services, Loops.

2

Click the key beside the loop number (for example, Loop 201) where you want to assign DNs,
and beside the DNs on loop heading.

3

Click the Loop DN heading.

4

At the top of the navigation tree, click on the Add button.

5

In the Add DNs dialog, enter an ISDN DN.

Figure 71 Adding a DN to the Loop DN group

6

Click Save to add the DN.

7

Repeat steps 4 to 6 for all the DNs you want to add to the loop.

8

Click the DNs on loop heading.

9

In the Loop DN field, enter an ISDN DN that you assigned to the Assigned DNs group in the
previous procedure. This telephone acts in a similar way that a Prime telephone works.
Incoming calls that are not answered go to this device. Also, if the other devices on the loop do
not have specified DNs, calls coming into the Loop DN ring at all these devices.
•
•

P0609326 1.1

If you leave None in the field, unanswered calls will be dropped.
If the field is left blank, none of the Assigned DNs will be able to make or receive data
calls.

Loop matrix

281

Figure 72 Adding a Loop DN

10 Click outside the right frame to save the entry.

Configure the ISDN terminal records
You configure the ISDN terminal records in the same way that you do any other DN record. These
records are found under the Services, System DNs, All ISDN/DECT DNs heading. For
information about each heading within the DN record, refer to “Configuring DNs using the
Wizards” on page 369 and “Configuring DNs for system devices” on page 387.

Loop matrix
To help you with your loop planning, transfer the following information to a spreadsheet and fill
out the values for each BRI loop.
Table 49 Loop attributes
Type

SPIDS

Protocol

Network DNs

Overlap receiving

Call type

Local number length

D-packet service

ONN blocking state

TEIs

Sampling (S loop only)

DNs on loop

Note: The loop type dictates which fields appear.

Assigned DNs

Business Communications Manager 3.6 Programming Operations Guide

282

Loop matrix

P0609326 1.1

283

Chapter 11
Controlling access into the system
This section describes the telephony configurations that are used to control system access within
the system and to control remote access into the system to access system features.
Task:
• Ensure that the DN length and Received # length are correct. “Defining DN length” on page
284 (Changing the DN length, Using the Received # length)
• Assign target lines for all telephones, if required. “Assigning target lines” on page 287
• Set up the system parameters for system users to call into the from a remote location. Note that
Remote Access Packages are required for private network trunks, as well. Creating Direct
Inward System Access (DISA), Defining remote access packages, Using COS passwords
The following figure highlights the Unified Manager navigation tree headings that will be
discussed in this chapter.
Figure 73 Process map: Access headings
Telephony Services
Lines
VoIP Lines
Physical Lines
Target Lines
Line 241-412
General
Trunk/Line Data
Received Number
Restrictions
Line Restrictions
Remote Restrictions
Telco features
All Lines
.....

General Settings
Feature Settings
Nortel IP Terminals
IP trunking
Timers
Direct dial
Set 1-5
CAP/KIM Assignments
Dialing Plan
Access Codes
Park Prefix
External code
Direct Dial Digit
Auto DN
DISA DN
Private Access Code
Local Access Code
National Access Code
Special Access Code
Line Pool Codes
Carrier Codes
Remote Access Packages
Package 00-15
COS passwords
COS 00-99
DN lengths
Received # length
CbC Limits
....

Business Communications Manager 3.6 Programming Operations Guide

284

Defining DN length

Defining DN length
The DN lengths setting allows you to change the number of digits for the Received number length
and the DN length, which are used by the system to determine if an incoming call is valid for the
system.
Each increase in length repeats the first digit in front of any existing DN. For example, if DN 234
was increased to a length of 4, the new DN would be 2234.
This section contains this information:
•
•

“Changing the DN length” on page 285
“Using the Received # length” on page 286
Warning: Do not change DN length immediately after a system startup.
You must wait for at least two minutes after a system startup before you change the DN
length. It is preferable that you change this setting at system startup using the Quick Start
Wizard. Refer to “What you need to know before you use the wizard” on page 93.
If you change the DN length after startup:
• Data devices using B2 channels drop calls when you change the DN length during
system operation.
• The change takes up to two minutes, depending on the size of the system. System
response can briefly slow down during this time.

Warning: Increasing the DN length affects other areas of the system:
If the DN length change creates a conflict with the Park prefix, external line access code,
direct-dial digit, or any line pool access code, the setting for the prefix or code changes to
None, and the corresponding feature is disabled.
Optional applications affected by DN length changes:
Voice mail, and Call Center applications are reset if you change the DN length after these
services are installed.
If you are using IVR, you will need to correct the scripting.
If you have a DECT system, you will need to rerun the DECT Wizard to ensure that the
DECT module firmware recognizes the change in DN numbers.

P0609326 1.1

Defining DN length

285

Changing the DN length
Warning: If your system is running with a PBX telephony template, the Public and
Private received # length are hardcoded to 3 (digits) at startup. Increasing the DN length
after system startup does not change these digits, so you will need to manually change the
Public and Private receive # length. Refer to “Changing the received # length” on page
286.
Private OLIs are automatically assigned to the DN records if the DN length and the Private
received # length are the same. If this changes, the Private OLIs are cleared, or are not
assigned (PBX template). Refer to “Assigning line access” on page 394.
Network note: If your system is part of a private network, ensure that you confirm the
numbering plan for the network before changing this length. If you change the length,
ensure that you check all DN-related settings after the change.
To change the DN length after startup, follow these steps:
1

Click the keys beside Services, Telephony Services, General settings

2

Click on DN lengths.
The DN lengths window appears in the right frame.

Figure 74 DN length screen

3

In the DN length field, enter a new length (3, 4, 5, 6, 7) or use the drop down list to select a
new setting. The default DN length is 3.

4

Press  to save the new DN length.
The prompt appears: If Business Communications Manager Voice Messaging is installed all
messages and mailboxes will be deleted.

5

Click OK to save the new DN length.
Click Cancel to restore the original value.

Business Communications Manager 3.6 Programming Operations Guide

286

Defining DN length

Using the Received # length
If you change the DN length of your system, you may need to change the Received # length, which
is what the system uses, in conjunction with the dialing table coding, private and public
networking, and the access codes to determine a route for an incoming call over an auto-answer
trunk.
On systems running the DID telephony template, the Private and Public Received # length is set to
the same length as the DN length for the system. On systems running the PBX telephony template,
the Private and Public Received # length default to 3, unless the DN length is changed during the
Startup procedure.
These digits identify target lines (“Assigning target lines” on page 287), Auto DNs, and DISA
DNs (“Programming access codes” on page 310).
TIPS: The target line number (for example, line 241) and the Received number for the target line
(for example, Received number: 123 maps to line 241) must be different numbers. (“Target lines
and DASS2 fields” on page 247).
However, the received number can be shorter if network or central office constraints require this.
This number cannot be greater than the system DN length on a networked system using a
coordinated dialing plan (CDP) or a universal dialing plan (UDP). On a standalone system it is
possible that the received number length would be greater than the DN length.
Warning: Decreasing the received number length clears all programmed received digits.

Changing the received # length
1

Click the keys beside Services, Telephony Services, General settings, and DN lengths.

2

Click on Received # length.

3

On the navigation tree, click on Received # length.
The Received # length screen appears in the right frame.

Figure 75 Received # length, (PBX template default)

P0609326 1.1

Assigning target lines

4

287

The following table provides the possible values for each field.

Table 50 Private and Public received numbers
Attribute

Value

Description

Private length

1, 2, 3, 4, 5, 6, 7

The number of digits that the system uses to determine if a call tagged
as Private fits the system private DN numbering. Default: DID, same as
DN length; PBX: 3

Public length (max)

2, 3, 4, 5, 6, 7

The maximum number of digits (2, 3, 4, 5, 6, 7) that the system uses to
determine if a call tagged as public fits the system public DN numbering.
Default: DID, same as DN length; PBX: 3

5

Check all equipment assigned to DNs.

6

Check target line received numbers and OLI entries.
•

•
•

7

If you change the received number length for your system, the Public number entry for
the target lines will clear if the new received # length is less than the number entered in
this field. Refer to “Configuring the target line received number” on page 289.
If the new received # length has more digits than the number entered in the target lines
Public Number field, the entry remains, but does not update to the new DN length.
A private OLI is automatically assigned to the DNs if the DN length and the Received #
length are the same. If either changes so that they are not the same, the private OLI field is
cleared or not assigned (PBX template). Refer to “Assigning line access” on page 394.

Reapply whatever voice mail applications you had installed. If you have a DECT system,
rerun the DECT wizard to update the DECT module firmware.

Assigning target lines
Target lines are internal direct links the Business Communications Manager uses to allow external
callers to dial specific system telephones, or a group of system telephones. You assign the target
line to one or more telephone DNs (“Assigning a target line to a telephone”), and then configure
the target line to function as you require (“Configuring the target line received number” on page
289). You can also assign multiple appearances of a target line to one telephone. This allows more
than one call to simultaneously use the target line. Target lines are required by lines that support
multiple numbers over one trunk (DID trunks, T-1 DID trunks, PRI trunks, and voice over IP
(VoIP trunks).
Note: You can also assign target lines to telephone DNs using the Add Users Wizard.
Refer to “Creating telephone records with the Add Users Wizard” on page 375. The
wizard can Auto Assign target lines to all the selected DNs. As well, the prime set DNs
are also automatically updated to be the DN to which the target line is assigned.
If a target line in a sequence specified on the Wizard is already assigned to an existing DN,
the system will also assign the line to one of the DNs on the list. If this is not what you
want, you need to go into Unified Manager and change the target line number for one of
the DNs.
Business Communications Manager 3.6 Programming Operations Guide

288

Assigning target lines

Assigning a target line to a telephone
1

Ensure you have auto-answer lines such as analog DID, T1 lines set to auto answer, PRI, or
VoIP trunking lines.

2

Click the keys beside Services, Telephony Services, System DNs, Active Set DNs.

3

Choose the DN of the set where you want the line to be directed.

4

Choose Line assignment and click the Add button.

5

Enter the number of the target line you want to assign to the set (241-492).

6

Click on the line number. The DN/Line screen appears in the right frame.

Figure 76 Assigning a target line to a set

7

Ensure the Appearance type is set to Appr&Ring.
The following table shows the possible settings for the line record.

Table 51 General record values
Attribute

Value

Description

Appearance type

Appr&Ring
RingOnly
Appr

Always choose Appr&Ring for target lines.
Choose RingOnly if the telephone does not have any line buttons to support
target line appearances.

Appearances



This is how many line appearances will appear on the telephone

Caller ID set

Y or N

Specify whether the telephone can display caller ID information.

Vmsg set

Y or N

Select whether an indicator shows on the telephone for voice message
waiting to an external voice message system.
The line must appear on receiving telephone.
Note: the Message Waiting Indicator (MWI) is currently supported exclusively
by Meridian Mail and CallPilot.
MCDN note: If your system is part of an MCDN network connected to a
Meridian 1 system, and you are using the voice mail system off the
Meridian 1, you need to set this field to Y.
Note: Contact your voice message service provider to find out if your voice
message service works with Business Communications Manager, or if you
have any problems with your service.

P0609326 1.1

Assigning target lines

8

289

Repeat steps 3 to 7 for all the DNs you want to assign with target lines.

Configuring the target line received number
Configure the numbers that the system uses to identify the destination for the target line.
1

Click the keys beside Services, Telephony Services, Lines, Target Lines.

2

Click the Line XXX you want to set.

3

Click the key beside Trunk/line data.
Note: For Trunk/line data programming, refer to “Target lines and DASS2 fields” on page
247.

4

Click on Received number. Refer to “Notes about the Public and Private Received Numbers”
on page 290 for details.

Figure 77 Defining a Received number

5

Press  to save the changes.

6

Program the General, and Telco features as you would for any other line. Refer to “Target
lines and DASS2 fields” on page 247.

7

Repeat steps 2 to 6 for all the target lines you want to configure.
Caution: Changing the received # length:
If you change the received number length for your system, the Public number entry for
the target lines will clear if the new received # length is less than the number entered in this
field.
If the new received # length has more digits than the number entered in this field, you need
to change the entry manually, if changes are required. Refer to “Changing the received #
length” on page 286.

Business Communications Manager 3.6 Programming Operations Guide

290

Assigning target lines

Notes about the Public and Private Received Numbers
If the received number is different than the regular DN number, enter the number in the Private
number and/or Public number field. For instance, in North America, you can enter the 10-digit
public number in the Public number field. If you leave these fields blank, the system will use the
DN of the telephone assigned with this line.
Upgrade note: If you upgraded your system from a version of Business Communications
Manager previous to BCM 3.6, the Private number field of assigned target lines will autofill with
the same value that is in the Public number field (usually the assigned DN). However, if the DN
length of the system was different from the Received number length, this field will be blank after
the upgrade. Systems running with a DPNSS keycode will also need to reenter the information in
this field after an upgrade to BCM 3.6 or newer software.
Programming note: The following trunks use one or both of these settings to route calls:
•
•

•

DPNSS lines use the Private received number to route calls in the system.
BRI ETSI-QSIG, PRI ETSI-QSIG, MCDN, DMS100, DMS250 and VoIP trunks route calls on
a per-call basis to either the public or private received digits. Note: VoIP trunking MCDN calls
do not support Auto DN/DISA DN functionality.
BRI (ETSI-Euro, NI), PRI (ETSI-Euro, NI, 4ESS), T1 (LoopStart, E&M, DID, GroundStart),
Analog LEC (LoopStart, E&M, DID), and DASS2 trunks route calls using the Public received
number.

Other settings to note:
•
•

“Programming access codes” on page 310 (Public/Private DISA DNs and Auto DNs)
“Assigning line access” on page 394 (Public/Private OLI)

Target lines matrix
To help you with your target line planning, transfer the following information to a spreadsheet and
fill out the values for each target line you create.
Table 52 Target line record
Target line no. (3 digits)

Entered in target DN record with appr and ring?

Telephone number (DN)

Is DN length tied to Public Length (MAX)?

Control set

Use Aux. ringer

Y

Line type

Public
Private to:_____________

If busy

PrimeSet

Rec’d #

None

DN

Distinct Ring

None

Prime Set

221

None

Voice Message Center

P0609326 1.1

N
BusyTone
2

3

4

Configuring for remote access

291

Configuring for remote access
If you want callers from a different node on the network or from the public network to be able to
access system features or the system network lines, you need to set up remote access packages and
COS passwords to control outside access.
Programming note: If your system is hosting a centralized voice mail system, all calls from
non-host systems to the voice mail on your system are considered remote calls and you need to set
up the lines and remote access packages to accommodate this. If your system is using centralized
voice mail on another system, users on your system need to be advised of the appropriate voice
mail access codes.
This section provides information about:
•
•
•
•

“Creating Direct Inward System Access (DISA)” on page 291
“Defining remote access packages” on page 294
“Using COS passwords” on page 296
“External access tones” on page 299

Creating Direct Inward System Access (DISA)
To control access from the public or private network, you can configure auto-answer trunks to
answer with DISA. Remote callers hear a stuttered dial tone and must then enter a COS password
that determines what they are allowed to do in the system.
•
•

•

Auto-answer T1 loop start and T1 E&M trunks are configured to answer with DISA by
default.
T1 DID trunks: You cannot configure T1 DID trunks to answer with DISA. If you want
incoming T1 DID calls to be answered with DISA, configure the system with a DISA DN.
Incoming T1 DID calls that map onto the DISA DN are then routed to a line that has DISA.
You cannot program a DISA DN or Auto DN to VoIP trunks, because they act as auto-answer
lines for private networks. However, you still need to assign remote access packagess to the
VoIP trunks, to ensure that remote access restrictions are properly applied to incoming calls
trying to access the system or the system network.

This section also includes information about:
•
•
•
•
•
•

“Remote access line settings”
“Remote access on loop start trunks” on page 292
“Remote access on T1 DID trunks” on page 292
“Remote access on PRI” on page 293
“Remote access on DPNSS lines” on page 293
“Remote access on a private network” on page 293

Business Communications Manager 3.6 Programming Operations Guide

292

Creating Direct Inward System Access (DISA)

Remote access line settings
The remote access feature allows callers elsewhere on the private or the public network to access
your Business Communications Manager by dialing directly and not going through the attendant.
After the remote user is in the system, they can use some of the system resources. You must enable
remote access in programming before callers can use it.
Business Communications Manager supports remote system access on a number of trunk types
which may require the remote caller to enter a password for DISA.
The system resources, such as dialing capabilities, line pool access and feature access, that a
remote user may access depends on the COS password assigned to them. See “Using COS
passwords” on page 296.
Note: Callers remotely accessing the Business Communications Manager press * followed by the
feature code to use the system features. Even if you are calling from another Business
Communications Manager system, press * instead of the Feature key.

Remote access on loop start trunks
Loop start trunks provide remote access to Business Communications Manager from the public
network. They must be configured to be auto-answer to provide remote system access.
A loop start trunk must have disconnect supervision if it is to operate in the auto-answer mode.
T1 E&M trunks always operate in disconnect supervised mode.
When a caller dials into the system on a line that has auto-answer without no DISA, the system
answers with system dial tone and no COS password is required. In this case, the restriction filters
assigned to the line control system capabilities available to the caller.
When a caller dials in on a line that has auto-answer with DISA, the system answers with stuttered
dial tone. This is the prompt to enter a COS password that determines which system capabilities
are available to the caller.

Remote access on T1 DID trunks
Remote system access on T1 DID trunks is similar to that of T1 E&M trunks connected to a
private network. The main differences are:
•
•
•

A remote caller is on the public network dialing standard local or long distance telephone
numbers.
The digits received are delivered by the central office.
DISA cannot be administered to a T1 DID trunk. You can program the dialed digits to match
those of a specific target line DN, the DISA DN or the Auto DN. If you program the dialed
digits to the DISA DN, only the incoming calls that match the programmed DN will receive a
DISA dial tone. Incoming calls with other digits will route to a target line.

P0609326 1.1

Creating Direct Inward System Access (DISA)

293

Remote access on PRI
Remote system access on PRI trunks is similar to that of T1 E&M trunks connected to a private
network. The main differences are:
•
•
•

A remote caller is on the public network dialing standard local or long-distance telephone
numbers.
The digits received are delivered by the central office.
Answer with DISA cannot be administered to a PRI trunk. Instead, you can program the dialed
digits to match those of a specific target line DN, the DISA DN or the Auto DN.

Remote access on DPNSS lines
A remote caller can access a Business Communications Manager system dial tone, select a line
pool that contains exchange lines or DPNSS lines, then dial a number. The procedure is identical
to dialing an outside number from an extension in the local system. The main features are:
•

Calls coming from another switch to the Business Communications Manager system are
routed in two ways, depending on the Answer mode that you program. If the Answer mode is
set to Manual, and the line is assigned to ring at an extension, the incoming call automatically
rings at the assigned extension. If Answer mode is set to Auto, Business Communications
Manager automatically answers the incoming call. Because most other DPNSS features are
extension-specific, Nortel Networks recommends that all DPNSS lines are configured as
auto-answer lines.

•

The Page feature is available to both remote callers and callers within the system. A remote
caller must have DTMF capability to access the Page feature.

•

The line redirection feature allows the originating party to redirect a call that is waiting a
connection or re-connection to an alternate destination after a time-out period. Failed calls can
be redirected. Priority calls cannot be redirected.

Remote access on a private network
Systems connected to the private network deliver the last dialed digits to the destination Business
Communications Manager system for interpretation. The destination Business Communications
Manager system matches the digits to a target line or interprets the digits as a remote feature
request. Business Communications Manager then routes the call to the specified target line or
activates the remote feature.
•

By default, T1 E&M trunks are set to answer with DISA. For auto-answer T1 E&M trunks
connected to a private network, change the default so that the trunks are not answered with
DISA. If an auto-answer T1 E&M trunk is configured to answer with DISA, the system tries to
interpret any received digits as a COS password.

•

The DISA DN and the Auto DN allow auto-answer private network and DID calls, in the same
way that calls on auto-answer loop start and auto-answer T1 E&M trunks can be answered,
with or without DISA. These DNs are described in “Understanding access codes” on page
309.
Business Communications Manager 3.6 Programming Operations Guide

294

Defining remote access packages

•

Answer with DISA cannot be administered to a PRI trunk. Instead, you can program the dialed
digits to match those of a specific target line DN, the DISA DN or the Auto DN on the other
system.

•

Answer with DISA cannot be administer to voice over IP (VoIP), since they do not connect
systems outside the private network. However, a user calling in remotely on another system on
the network can use the trunk to access the system or a user calling in on a PSTN line can use
the trunk to access the private network. To provide control for this type of access, ensure that
you specify remote access packages for the trunk.

Defining remote access packages
The Remote access packages setting allows you to control the remote use of line pools.
Create a remote access package by defining the system line pools remote users can access. You
then assign the package to individual lines, (refer to “Defining line pool access for remote
packages”), and to a particular Class of Service password (see “Using COS passwords” on page
296).

Defining line pool access for remote packages
Perform the following procedure for each package you defined in the previous section:
1

Click on the key beside Line pool access.

2

Click the Add button.
The Add Pool Access dialog box appears.

3

In the Pool field, enter a line pool.

4

Click Save.

5

Repeat steps 1 to 4 for all packages you require line pool access codes for.

P0609326 1.1

Defining remote access packages

295

Defining remote Page for remote packages
To define Remote access packages, follow these steps:
1

Click the keys beside Services, Telephony Services, General settings, and Remote access
packages.

2

Click a Package number (00 to 15).
The Package window appears. Refer to Figure 78.

3

Type in Y or N to enable/disable remote paging for each pool in the Remote access package.

4

Repeat steps 3 and 4 until you have defined all the package values you require.

Figure 78 Setting remote page for a remote access package

Business Communications Manager 3.6 Programming Operations Guide

296

Using COS passwords

Using COS passwords
COS passwords permit controlled access to the system resources by both internal and remote
users.
•

When an internal user enters a COS password at a telephone, the restriction filters associated
with the COS password apply instead of the normal restriction filters.

•

Similarly, when a remote user enters a COS password on an incoming auto-answer line, the
restriction filters and remote package associated with their COS password apply instead of the
normal restriction filters and remote package.

This section includes information about:
•
•
•
•

“Creating COS parameters” on page 296
“Notes about COS passwords” on page 297
“COS examples” on page 298
“External access tones” on page 299

Creating COS parameters
Follow these steps to create COS groups and passwords:
1

Click the keys beside Services, Telephony Services, General Settings, and COS Passwords.

2

Click on a COS group (COS 00-99).
The COS window appears in the right frame.

Figure 79 Assigning COS password and remote access parameters

...
COS 99

P0609326 1.1

Using COS passwords

3
Table 53

297

Use the information in the following table to determine which values to set for each password.
COS password values

Attribute

Values

Description

Password



Enter a combination of numbers that the user needs to dial to get into
the system. Refer to “Notes about COS passwords” on page 297.

User filter

None
Filter 

Assign a restriction filter to a Class of Service password.
The user filter associated with the Class of Service password
replaces any normally-applicable set restriction, line/set restriction,
and remote restriction.
The default setting (None), means that any normally- applicable
filters (set restriction, line/set restriction, or remote restriction) still
apply.

Line filter

None
Assign a specific line restriction to a Class of Service password. The
Filter 
that any normally applicable line filter still applies.

Remote package None
Package 

Refer to “Defining remote access packages” on page 294 for more
information.

Notes about COS passwords
The COS password can define the set of line pools that may be accessed and whether or not the
user has access to the paging feature.
The class of service (COS) that applies to an incoming remote access call is determined by:
•

the filters that you apply to the incoming trunk

•

the COS password that the caller used to gain access to Business Communications Manager.

•

in cases where DISA is not automatically applied to incoming calls, the remote caller can
change the class of service by dialing the DISA DN and entering a COS password.

Remote users can access system lines, line pools, the Page feature, and remote administration (if
enabled through Software Keys). The exact facilities available to you through remote access vary
depending on how your installer set up your system.
Note: If the loop start line used for remote access is not supervised, auto-answer does not function
and the caller hears ringing instead of a stuttered tone or the system dial tone.

Business Communications Manager 3.6 Programming Operations Guide

298

Using COS passwords

Security note:
!

COS password security and capacity

•

Determine the COS passwords for a system randomly and change them on a
regular basis.

•

Users should memorize their COS passwords and keep them private.
Typically, each user has a separate password. However, several users can
share a password or one user can have several passwords.

•

Delete individual COS passwords or change group passwords when
employees leave the company.

•

A system can have a maximum of 100 six-digit COS passwords (00 to 99).
You can copy the restriction filters and remote package from one COS
password to another. COS passwords must be unique.

To maintain the security of your system, the following practices are recommended:
• Warn a person to whom you give the remote access number to keep the
number confidential.
• Change COS passwords often.
• Warn a person to whom you give a COS password, to memorize the password
and not to write it down.
• Delete the COS password of a person who leaves your company.

!

Security note: Remote users can make long distance calls.
Remember that a remote user can make long distance calls that are charged to your
company. They can also access line pools and make page announcements in your office.

COS examples
Example: Using the COS feature to access a restricted line
A sales representative out of the office needs to make long distance calls to the European office.
Your system has a leased line to Europe with reduced transatlantic charges. You provide the sales
representative with a Class of Service password that gives access to the transatlantic line. The sales
representative can telephone into the system (DISA DN) from a hotel, enter the Class of Service
password, and then use a destination code to access the leased transatlantic line to make calls.
To bypass the restriction filters on a line or telephone:
1

Press FEATURE 68.

2

Enter the six-digit COS password that allows the required type of call.

3

Enter the number to be dialed.

P0609326 1.1

Using COS passwords

299

Example: Remote access over the public network
Follow this procedure to access the system over a public network.
1

Dial the system remote access number.

2

When you hear a stuttered dial tone, enter your COS password.

3

Wait for the system dial tone.

To use the system at a distance, you must use a telephone with tone dialing to call the system.
Remote access is possible only on lines that your installer programs to auto-answer calls.
To use features on a remote system, press * followed by the feature code. When you are calling
from within Business Communications Manager, press * instead of FEATURE.
In some conditions, you can experience lower volume levels when using the system from a
distance.

External access tones
You can hear some of the following tones when accessing Business Communications Manager
from a distance. The following table shows the different types of tone and what they mean.
Table 54 External access tones
Tone

What it means

System dial tone

You can use the system without entering a COS password.

Stuttered dial tone

Enter your COS password.

Busy tone

You have dialed a busy line pool access code. You hear system dial tone again
after 5 seconds.

Fast busy tone

You have done one of the following:
• Entered an incorrect COS password. Your call disconnects after five seconds.
• Taken too long while entering a COS password. Your call disconnects after five
seconds.
• Tried to use a line pool or feature not permitted by your Class of Service. You
hear system dial tone again after five seconds.
• Dialed a number in the system which does not exist. Your call disconnects after
five seconds.
IP trunk lines do not produce tones when accessed from a remote location.

Business Communications Manager 3.6 Programming Operations Guide

300

Remote access matrix

Remote access matrix
To help you organize your external access, transfer the following information to a spreadsheet and
fill out the external access information you want to use.
Table 55 Remote access matrix
Pswd #
(00-99)

Assigned to
(owner of password)

Remote access packages

P0609326 1.1

Password

User filter
(None, Filter#)

Line filter
(None, Filter#)

Package #

Line pool access
A: 9
B: to O:_____ PRI-__

Remote pkg
(None, Filter#)

301

Chapter 12
Configuring outgoing calls
This section describes how you can configure the lines and loops to allow system users to dial out
of the system over a public or private network.
Task:
• Understand what dialing plan is being used for the public and private networks
(“Configuring the public and private dialing plans” on page 302)
• Set up call controls, when required, such as CbC limits
(“Configuring Call by Call services” on page 339)
• Set up access codes, routes, and destination codes
(“Programming access codes” on page 310, “Understanding access codes” on page 309,
“Configuring call routing” on page 320)
• Set up restriction filters, as required (“Defining restriction filters” on page 344)
The following figure shows the position of the headings in the Unified Manager for the
information covered in this chapter.
Figure 80 Unified manager telephony services headings
Telephony Services
...
Restriction Filters
Filter 00-99
Restrictions
Restriction 01-XX
Overrides
Call Routing
Routes
Route XXX
Destination Codes
XXX
Schedules
Normal
Night
Evening
Lunch
Sched 4
Sched 5
Sched 6

General Settings
Feature Settings
Nortel IP Terminals
IP trunking
Timers
Direct dial
CAP/KIM Assignments
Dialing Plan
Dialing timeout
Private Network
Public Network
Public DN lengths
Prefix Default
Prefix 

General Settings ...
Access Codes
Park Prefix
External code
Direct Dial Digit
Auto DN
DISA DN
Private access code
Local access code
National access code
Special access code
Line Pool Codes
Carrier Codes
Remote Access Packages
COS Passwords
DN lengths
CbC Limits
Release Reasons
Network Services
Silent Monitor

Refer also to “Information matrices” on page 226.

Business Communications Manager 3.6 Programming Operations Guide

302

Configuring the public and private dialing plans

Configuring the public and private dialing plans
The dial plan you choose determines the type of numbering required to access a public and private
network by defining the DN lengths for the codes that access the networks. You can define only
one private network per system.
This section provides information about:
•
•
•

“Setting Dialing timeout” on page 302
“Using private network dialing” on page 303
“Setting up public network dialing” on page 305

Setting Dialing timeout
Dialing timeout specifies how long the Business Communications Manager waits between
user-dialed digits. This value allows Business Communications Manager to determine when the
user stops dialing.
The user can also use the # key to indicate that they are finished dialing. This is not usually
required except for international calls where the number of dialed digits varies.
A timeout value that is too small forces the caller to enter the digits very quickly. A timeout value
that is too large causes the system to wait for extra time after the last digit is entered before the call
is actually made.
To view or set the dialing time out, follow these steps:
1

Click the keys beside Services, Telephony Services, General Settings.

2

Click on Dialing plan. The Dialing plan window appears in the right frame.

3

In the Dialing timeout box select a timeout value (in seconds): 3, 4, 5, 6, 8, 10, 15.

For more information about non-PRI routing tables and destination codes, refer to “Configuring
routing service” on page 495.
For more information about how dialing rules are used in networking situations, refer to Chapter
18, “Configuring public networks,” on page 499 and Chapter 19, “Configuring private networks,”
on page 505.

P0609326 1.1

Configuring the public and private dialing plans

303

Using private network dialing
If your Business Communications Manager is part of a private network, you have a choice of
dialing plans. However, all Business Communications Managers on a network must use the same
type of dialing plan and have the same Private DN lengths to ensure proper call direction. Plan out
these settings before you start programming for the network.
•

•

•

UDP plans use a routing code and a location code plus the set DN (i.e. 6-403-XXXX) to
determine where a call gets routed. You specify a Private DN length to allow all required digits
to be dialed. Each node on the network has a unique location code.
CDP plans use a unique steering code that gets dialed as part of the set DN
(i.e. 2XXXX for one node, 3XXXX for another node, and so on) to determine where the call
gets routed. Since each node on the network has a unique code, no other routing is required.
The Meridian system administrator generates the Private Network IDs. These IDs are unique
to each node on a network. Both UDP and CDP must include this code in programming.

Setting up the dialing plan
To set up a private network dialing plan, follow these steps:
1

Click the keys beside Services, Telephony Services, General Settings, and Dialing plan.

2

Click on Private network.

Figure 81 Configuring private network types

3

Use the following table to determine which values to set so callers can access a private
network.
Business Communications Manager 3.6 Programming Operations Guide

304

Configuring the public and private dialing plans

Table 56 Private network values
Attribute

Values

Description

Type

None, CDP, UDP

You can specify if your Private network uses a coordinated
dialing plan (CDP) or a universal dialing plan (UDP).
If you choose None, the private networking supplementary
services are not available.

Location code



This code identifies this particular system for calls within the
network for a UDP dialing plan. This number must be
unique.
Note: The system uses the Private Access Code length,
plus the Location code length, plus the DN length to
determine the DN length required to determine that a call is
a private network call.

*Private DN lengths
(DPNSS only)

3-14

The Private DN lengths parameter specifies the length of a
dial string that the system uses to determine that the call is
a private network call, when the route uses DN Type:
Private.

Private Network ID
(CDP/UDP networks)

1-127

This is the unique number that identifies the system to the
Meridian PRI-MCDN network. Both end points must match
on a PRI-MCDN network.
On a VoIP trunking-MCDN network, this ID must be the
same on all nodes.
This number is supplied by the private network
administrator.
Refer also to “Configuring special IP trunking
interoperability” on page 541.

* CDP and UDP private DN lengths are determined this way:
CDP: the system uses the telephone DN length
UDP: the system combines the private access code length + location code length + telephone DN length. When a call
comes in, the system recognizes the leading digits as a private call and removes (truncates) them, leaving the
telephone DN, which is recognized as the private DN length.

P0609326 1.1

Configuring the public and private dialing plans

305

Outgoing private calls routing
When you set up routing for private calls, the route is set to Private. Refer to “Configuring call
routing” on page 320.
How the system identifies the call depends on the type of trunk chosen for the route. Refer to the
table below.
Dialing plan setting

NPI/TON

Private called number length based on

MCDN trunks send private calls in this way:
None

Private/Subscriber

Private DN length (set on Private Network screen)

UDP

Private/UDP

private access code + home location code (LOC)
+ private received digits

CDP

Private/CDP

private received digit

DMS100/DMS250/ETSI-QSIG trunks send private calls in this way:
None

Private/Subscriber

Private DN length (set on Private Network screen)

UDP

Private/Subscriber

private access code + home location code (LOC)
+ private received digits

CDP

Private/Subscriber

private received digit

Setting up public network dialing
The Public network settings allows you to enter DN lengths for the networks the callers are
allowed to dial, including special numbers such as 411 and 911.
The public DN lengths table is used for all PRI calls except for those routes that use service type
Private or service type Tie with DN Type specified as Private. This table allows the Business
Communications Manager to determine the length of a DN, based on the initial digits dialed.
A set of default Public DN lengths is included with the default template. In most cases it is not
necessary to change the default values.

About the Public DN lengths table
In the public DN lengths table:
•
•
•

•

You can define up to 30 entries.
Each entry consists of a DN prefix string (1 to 10 digits) and a length value (two digits, 1 - 25).
Several entries are predefined in the North America profile. These defaults can handle most
regions in North America without the need for additional programming. If required, you can
remove or modify these entries.
The table always contains one default entry. You cannot remove this entry. You can only
modify the length parameter associated with this entry. The default entry specifies the length
of any dialing string that does not match one of the other table entries.

Business Communications Manager 3.6 Programming Operations Guide

306

Configuring the public and private dialing plans

Adding or modifying dialing plan Public DN lengths
To add or modify Public DN lengths, follow these steps:
1

Click the keys beside Services, Telephony Services, General Settings, Dialing Plan and
Public network.

2

Click on Public DN lengths.

3

At the top of the column, click Add.
The Add Public DN Lengths dialog box appears.

Figure 82 Adding a Public DN length prefix

4

In the DN prefix field, enter the prefix for the public network.

5

Click Save to save the setting.

6

Repeat steps 4 and 5 until you have added all the public DNs you need.

7

Click on Cancel to exit the dialog box.

8

On the menu, click the first Prefix number you added.
The Prefix window appears in the right frame.

Figure 83 Defining the prefix DN length

Example dialout: 0 403 555 9965

9

Enter the DN length for that prefix.
This defines the number of digits the system will scan to find the prefix.

10 Press  to save.
11 Repeat for all DN length records you added or that you need to change.

P0609326 1.1

Configuring the public and private dialing plans

307

Outgoing public calls routing
Outgoing public calls from within the system typically have the routes set to Public. Refer to
“Configuring call routing” on page 320. The NPI/TON gets sent as Unknown/Unknown. The
public called number length is based on the Public DN lengths table in the Public networks dialing
plan.
MCDN trunks also allow public call types when tandeming calls from another system on the
private network. Some of these systems use specific call types that the Business Communications
Manager needs to recognize to pass on correctly. Also refer to “Using the MCDN access codes
(tandem calls)” on page 315.
Type of call

NPI/TON

BCM prepend access code

BCM monitor display

Local

E164/Local

Local access code (9)

E.164/Subscriber

National

E164/National

National access code (X1)

E.164/National

Special calls
(international, 911, etc.)

Private/Special

Special access code (9)

Dialing Plans matrix
To help you understand how you are using networking on your system, transfer the following
information to a spreadsheet and fill out the information you chose.
Table 57 Dialing plan matrix
Private network

Public network

Type

Private Network ID

Location code

Private DN length

None

N/A

N/A

N/A

UDP

N/A

CDP

N/A

Pub DN length DN prefix

DN length

Business Communications Manager 3.6 Programming Operations Guide

308

Determining line access dialing

Determining line access dialing
The next two sections, “Understanding access codes” on page 309 and “Configuring call routing”
on page 320 describe what you do with the lines and loops you previously set up into line pools.
By using access codes or call routing, which uses destination codes, you can determine which lines
(routes) outgoing calls use. When you create a route, you can also specify restrictions that apply to
how or when the line will be used.
The following figure provides an overview of how access codes and routing is used within the
system to direct calls from a telephone in one system to a telephone in another system.
Figure 84 Line management diagram

Extension 2246

Intercom
dialing (2280)

Normal
Access Code
Call (5-2280)

Access Codes

Normal routing call
(9-409-2290)
LD call
Other routing call
(1-403-2280)
(91-409-2290)

Routing (destination) Codes

Other Access Code call
(6-2290)

Access Codes

Line pools

PSTN

Long Distance
PSTN

Extension 2280

P0609326 1.1

Private Network
E&M, T1,
MCDN, PRI
tandem, VoIP

Understanding access codes

309

Understanding access codes
The system uses access codes to direct calls to the correct lines and destinations. If the codes
conflict, some of the features on the system do not work. Refer to “Creating numbering plans”
on page 194 for a general overview about using access codes within the system dialing plan.
Task:
Set up access codes for internal features:
• park prefix
• direct dial digit
Set up access codes that affect users dialing in from remote locations:
• Private Auto DN
• Public Auto DN
• Private DISA DN
• Public DISA DN
Set up access codes that affect calls coming in over the private network:
• Private access code
• Local access code
• National access code
• Special access code
Set up access codes that affect calls leaving the system:
• External code (ATA and analog devices)
• Line pool access codes
• Destination codes
• Carrier codes
The table of default settings shown in the following table can help you plan your access codes so
there are no conflicts.
Table 58 Default codes table
Digit

Use

System screen

0

direct dial digit

Access codes

1

park prefix

Access codes

2XX

first digit of DNs/DN lengths

Set through Quick Start Wizard

9

line pool A access code
(Takes precedence over the External line access code if
there is a conflict.)

Access codes

Business Communications Manager 3.6 Programming Operations Guide

310

Programming access codes

Programming access codes
Your system requirements will determine which access codes you need to set up.
Follow these steps to set up codes found on the Access codes screen:
1

Click on the keys beside Services, Telephony Services, General Settings

2

Click on Access codes.
The Access codes window appears.

Figure 85 Defining access codes

codes apply only to
* These
tandem network calls
received from a node, such
as Meridian 1, which uses
special call markers, and
destined for the local PSTN.

3

*
*
*

Use the following table to determine which values to set for access codes for your system.
Note: Read “Tips about access codes” on page 314 before you choose a value to ensure the
value does not conflict with related variables.

Table 59 Access codes values
Attribute

Values

Description

None


The Park prefix is the first digit of the call park retrieval code that a
user enters to retrieve a parked call. If the Park prefix is set to None,
calls cannot be parked.
Refer to “Call Park codes” on page 312 before choosing a number.
SWCA note: If this field is set to None, you cannot program the
system-wide call appearance (SWCA) feature.

Internal features
* Park prefix

P0609326 1.1

Programming access codes

311

Table 59 Access codes values (Continued)
* Direct dial digit

None


The Direct dial digit setting allows you to specify a single
system-wide digit to call a direct dial telephone.

Remote dial-in (Also refer to “Configuring for remote access” on page 291)
* Private Auto DN



Private network calls answered without DISA require no password
to access the Business Communications Manager. The type of
service that applies to the call depends on the restrictions assigned
to the trunk.

* Public Auto DN



Public network calls answered without DISA require no password to
access the Business Communications Manager. The type of
service that applies to the call depends on the restrictions assigned
to the trunk.

* Private DISA DN 

For private network calls answered with DISA, the system presents
a stuttered dial tone to prompt a caller to enter a valid password.
The Class of Service (COS) that applies to the call is determined by
this COS password.
After a remote user accesses the Business Communications
Manager, they can change the existing COS password using the
DISA DN. This gives you greater flexibility when you create access
privileges. For example, you may want to have a shared DN for
remote access, but separate COS passwords with different dialing
out privileges for individuals.

* Public DISA DN

For public network calls answered with DISA, the system presents a
stuttered dial tone to prompt a caller to enter a valid password. The
Class of Service (COS) that applies to the call is determined by this
COS password.
After a remote user accesses the Business Communications
Manager, they can change the existing COS using the DISA DN.
This gives you greater flexibility when you create access privileges.
For example, you may want to have a shared DN for remote
access, but separate COS passwords with different dialing out
privileges for individuals.



Incoming and tandem calls (Refer also to “Defining routes” on page 322)
Private access
code


MCDN: coordinate with
National access code

This code identifies this system to the private network.
It comes in as the first digit in a dial string defined as private and is
read based on the private DN length.
Example: if the dialed number is 7880, and the private DN length is
4, the system scans the four digits from the right, recognizing the 7
as the private access code for this system.

Private networking also provides access to tandem calling and toll bypass functionality to users
calling into the system.
For example, a PSTN user in Toronto could call a PSTN user in Ottawa and have the call routed
over the private network connection from the Toronto office to the Ottawa office and then out to
the PSTN from the Ottawa office. This bypasses any long distance toll charges.
BCM to BCM to PSTN: Calls are routed as private over the private network, and then flagged as
public to go out to the end node PSTN.
Meridian to BCM to PSTN: Special call codes from the Meridian (Local, National and Special
access codes) need to be recognized by the BCM and correctly passed to the local PSTN.

Business Communications Manager 3.6 Programming Operations Guide

312

Programming access codes

Table 59 Access codes values (Continued)
* Local access
code



MCDN connections only.
This number is prepended to an incoming M1 local dial string and
designates the call as a Local call type (typically 9). Refer to “Using
the MCDN access codes (tandem calls)” on page 315. Refer also to
“Creating numbering plans” on page 194.

* National access
code

 MCDN connections only.
This number is prepended to an incoming call marked as a long
distance call, and designates the call as a National type call (private
access code + 1). Refer to “Using the MCDN access codes (tandem
calls)” on page 315.

* Special access
code



MCDN connections only.
This number is prepended to an incoming international (011....) or
special-case dial string (911, 411) and designates the call as a
special type call (9011 ...., 9911, 9411). Refer to “Using the MCDN
access codes (tandem calls)” on page 315.

None


The External code setting allows you to assign the external line
access code for T7100/T700 telephones and analog telephones
attached to ATA 2s to access external lines. When the caller picks
up the handset, the system tone sounds. The caller then enters this
number to access an external line. Note: This number is overridden
by line pool or destination codes starting with the same digit(s).
Refer to “Tips about access codes” on page 314 before choosing a
number.

Outgoing calls
* External code

Call Park codes
When you park a call (FEATURE 74), the system assigns one of 25 codes for the retrieval of the
call. You can then press the Page display key to announce the code that appears on the display.
These three-digit codes include the Call Park prefix, which can be any digit from 1 to 9, and a
two-digit call number between 01 and 25. For example, if the Call Park prefix is 1, the first parked
call is assigned Call Park retrieval code 101.
XXXXX Numbering cannot conflict with these features

Access numbering

Park
prefix

Park prefix

Direct
External dial
code
digit

Public/ Public/
Private Private Private
access Auto
DISA
Line pool code/
Telephone
code
DN
DN
destination code DN

XXXX

XXXX

XXXX

#XXXX #XXXX #XXXX

#XXXX

# Cannot conflict with first digit.

Note: Other programmable settings may affect what numbers appear in the window during
programming. Although the numbers 0 to 9 are valid Park prefix settings, some may already be
assigned elsewhere by default or by programming changes.
If the DN length changes, and the changed DNs conflict with the Park prefix, the setting changes
to None.
P0609326 1.1

Programming access codes

313

The system assigns Call Park codes to calls in sequence, from the lowest to the highest, until all
the codes are used. A round-robin method means the use of different of codes ensures a call
reaches the right person, especially when more than one incoming call is parked.
The highest call number (the Call Park prefix followed by 25) is used by model 7000 and 7100
telephones, analog telephones, or devices connected to the system using an ATA2. Analog
telephones or devices cannot use the other Call Park codes.
Calls are retrieved by pressing the intercom button and dialing the retrieval code. On model 7000
and 7100 telephones, pick up the receiver, and then dial 25.
You also need to program the delay timer that determines when external parked calls that are not
answered return to the originating telephone. Refer to “Setting system timers” on page 472.
You can disable Call Park by setting the Park Code to None.

Creating Direct Dial sets
The Direct dial setting allows you to dial a single system-wide digit to call a specific telephone,
called a direct dial telephone. The most common example of a direct dial set is a telephone for an
operator, a receptionist or an attendant. You can program a maximum of five direct dial sets on the
system, however, you can only specify one direct dial number for the system (“Programming
access codes” on page 310).
1

Click the keys beside Services, Telephony Services, General Settings, and Direct dial.

2

Click the Set you want to program (Set 1-Set 5).
The Set # window appears.

Figure 86 Direct dial menu and screen

3 Use the following table to determine the settings you want to define direct dial sets.
Table 60 Direct dial values
Attribute

Values

Description

Type

Internal
External
None

This is the type of number for the direct-dial set.

Business Communications Manager 3.6 Programming Operations Guide

314

Programming access codes

Table 60 Direct dial values (Continued)
Internal/External#

DN


The DN number of the telephone to be designated as the direct dial
set. (Internal sets).
The actual phone number of the direct dial set (External sets).

Facility

Line
Pool (A-O)
Use prime line
Use routing table

The facility to be used to route the call to a direct dial set that you
define with an external number.
Note: If you choose Use prime line, ensure that prime line is not
assigned to the intercom buttons for your telephones. When prime
line is assigned as an intercom button, it chooses the first available
line pool assigned to the telephone to make a call. If this line pool
does not have the correct lines for routing the call, the direct dial
call will fail. Refer to “Assigning line access” on page 394.

!

Security note: The Business Communications Manager cannot verify that the number
you assign as an external direct dial set is valid. Check the number before assigning it as a
direct dial set by calling the direct dial you have assigned.

Direct dial matrix
To help you with your direct dial planning, transfer the following information to a spreadsheet and
fill out the values for each target line you create.)
Table 61 Direct dial sets
Direct Dial Set
Set 1
Set 2
Set 3
Set 4
Set 5

None

Internal #

External #
Use Prime line
Use line
Pool code_____
Use routing table

Tips about access codes
Here are some helpful pointers to assist you in planning the access codes for your system.
Table 62 Access/dialing codes: avoiding numbering conflicts
XXXXX Numbering cannot conflict with these features

Access numbering

Park
prefix

Park prefix

Direct
External dial
code
digit

Private Public/
access Private
code
Auto DN

Public/
Private
Line pool code/ Telephone
DISA DN des. code
DN

XXXX

XXXX

XXXX

#XXXX

#XXXX

#XXXX

#XXXX

XXXX

XXXX

#XXXX

#XXXX

*XXXX

#XXXX

XXXX

#XXXX

#XXXX

#XXXX

#XXXX

XXXX

XXXX

External code

XXXX

Direct dial digit

#XXXX XXXX

Private Access code

#XXXX XXXX

Pub//Priv/ Auto DN
Pub//Pri/ DISA DN
Line pool/dest. code

P0609326 1.1

XXXX

#XXXX

#XXXX

#XXXX

#XXXX

XXXX

XXXX

XXXX

#XXXX *

XXXX
XXXX

XXXX

Programming access codes

315

Table 62 Access/dialing codes: avoiding numbering conflicts
XXXXX Numbering cannot conflict with these features
Direct
External dial
code
digit

Access numbering

Park
prefix

Telephone DN

#XXXX #XXXX

Private Public/
access Private
code
Auto DN

Public/
Private
Line pool code/ Telephone
DISA DN des. code
DN

#XXXX

XXXX

* If the line pool code and the External code start with the same digit, the line pool code programming supersedes the
external code.
# Cannot conflict with first digit.

•

External line access code:
If the DN length is changed, and the changed DNs conflict with the external line access code,
the setting changes to None.

•

Direct dial telephone: Another direct dial telephone, an extra dial telephone, can be assigned
for each schedule in Services programming.
If the DN length is changed, and the changed DNs conflict with the Direct dial digit, the
setting changes to None.

•

•

Public/Private Auto DN: The length of the Auto DNs are the same as the Public or Private
Received Number Lengths specified under General Settings, DN lengths. The public/private
Auto DN is cleared if the corresponding Received Number Length is changed.
Public/Private DISA DN: The length of the DISA DNs are the same as the Public or Private
Received number length specified under General Settings, DN lengths. The public/private
DISA DN is cleared if the corresponding Received number length is changed.

Using the MCDN access codes (tandem calls)
Three special codes exist specifically for programming over PRI and VoIP trunks that are using
the MCDN protocol, and which connect to a call server systems that use specific call codes for
special call types, such as the Meridian 1 (M1). The purpose of the codes is to allow easier
programming of the call server systems when calls are tandemed through a Business
Communications Manager to the local PSTN.
Calls tandeming to the public network through the private network need to retain their dialing
protocol throughout the private network. This means that a call from an M1 node tagged as a local
call gets received by the BCM node and is recognized as a call intended for the public network, but
also as a call that needs to maintain the local call tag until it gets to the BCM node that is directly
connected to the PSTN. This is accomplished by ensuring that the destination code, which starts
with this access code, passes the call on using the route designated with the correct call type. Refer
to “Defining routes” on page 322. The following figure charts this process.

Business Communications Manager 3.6 Programming Operations Guide

316

Programming access codes

Figure 87 Local call tandemed through Business Communications Manager nodes
Meridian user

Dialout: 9-823-2222

The Business Communications Manager
receives the call. The system recognizes
9823 as the destination code for the local
PSTN route. Route drops the leading
digit and dials out over the PSTN trunk.
The Meridian system recognizes the call as
a local public call.
Deletes the routing digits.
Tags call as Local call type
Sends out rest of dialout on private network

Dialout: [unknown] 823-2222

Dialout: -823-2222

823-2222
Dialout: 9-823-2222

Local
PSTN

The Business Communications Manager
Adds Local code to front of called number:
9-823-2222
The system knows 9823 is the route to the next
system and routes the call through private network.

This is how the codes relate:
Meridian 1 access codes
Network/long distance code

Local code

Business Communications Manager access codes

Sample code

Private access code

6

National access code

61

Local access code

9

Special access code

9

Calls coming in from the public network need to be translated to their private network destination
before routing/tandeming through the private network. In this case, the route used is defined with
the call type of Private.

P0609326 1.1

Setting up line pool access codes

317

Setting up line pool access codes
Line pool access codes allow you to assign an access code for each of the line pools (A to O).
These codes specify the line pool for making an outgoing external call.
Follow these steps to set line pool access codes:
1

Click on the keys beside Services, Telephony Services, General Settings, Access codes.

2

Click the key beside Line pool codes.
Pool A-Pool O appears on the navigation tree.

3

Click the Pool you want to program.
The Pool window appears.

Figure 88 Defining line pool access codes

4

Type the Access code (up to four digits).
The default Access code is 9 for Line Pool A.
There is no default Access code for Line Pools B to O.
Note: You cannot assign PRI line pools with a line pool access code. You must define PRI line
pools under routing, and create destination codes for the routes.
Note: A line pool access code cannot conflict with:
XXXXX Numbering cannot conflict with these features

Access
numbering

Park
prefix

External Direct dial Private access Public/Private Public/Private Telephone
code
digit
code
Auto DN
DISA DN
DN

Line pool/
destination code

#XXXX *

XXXX

XXXX

XXXX

XXXX

* If the line pool code and the External code start with the same digit, the line pool code programming supersedes the
external code.
# Cannot conflict with first digit.

Business Communications Manager 3.6 Programming Operations Guide

318

Using Carrier codes

VoIP lines and access codes: Although VoIP trunking lines are not physical lines, you can create
a line pool and line pool access codes to access this service. However, if you want to provide
fallback to a CO line, you must use routes and destination codes both for the VoIP lines and for the
physical line pool.
The VoIP keycode must be enabled before you can access any VoIP lines. The VoIP keycode on a
remote target Business Communications Manager must also be enabled for that system to receive
VoIP-based calls from your system.
For detailed information about VoIP lines, refer to the IP Telephony Configuration Guide.

Using Carrier codes
A multi-digit Carrier access code contains an Equal Access Identifier Code (CAC) followed by a
Carrier Identification Code (CIC). The CIC identifies the carrier that handles the call. The Carrier
Access Code table stores the CAC digit pattern that you define for your region.
In most cases it is not necessary to change the default values.

About Carrier access codes
Here are some general points about carrier access codes:
•
•
•
•

You can define up to five carrier codes.
Two entries will be pre-defined in North America, but you can remove these defaults.
Each entry consists of an equal access identifier code prefix (one to six digits) and a carrier
identification code length (one digit, 1 to 9).
Each entry is identified by the prefix digits themselves.

Identifying Carrier access codes
1

Click the keys beside General settings and Access codes.

2

Click Carrier codes.

3

To add a new prefix, click the Add button located above the navigation tree.

Figure 89 Adding Carrier code prefix records

P0609326 1.1

Using Carrier codes

4

319

Click on the Prefix number you created.

Figure 90 Configuring a carrier code prefix ID length

5

Use the following table for information about the two fields on this screen.

Table 63 Carrier access code values
Attribute

Values

Description

Code prefix


(Read-only)

This value defines the prefix that will be used to access the carrier
code.

ID length

1, 2, 3, 4, 5, 6, 7, 8, or 9

This value defines the carrier ID length.

Access code matrix
To help you with your Access code planning, transfer the following information to a spreadsheet
and fill out the access codes you want to use.
Table 64 Access code values
A: 9

B: ______

C:_____

D:_____

L:_____

F:_____

Line pool codes

H:_____ I: _____ J: _____

Park prefix

0 1

2

3

4

5

6

7

8

9

None

Extrnl code

0 1

2

3

4

5

6

7

8

9

None

Direct-dial digit

0 1

2

3

4

5

6

7

8

9

None

Private Auto DN

None

Received #______________________________

Public Auto DN

None

Received #______________________________

Private DISA DN

None

Received #______________________________

Public DISA DN

None

Received #______________________________

Private Access Code

0 1

2

3

4

5

6

7

8

9

None

Local Access Code

0 1

2

3

4

5

6

7

8

9

None

National Access Code 0 1

2

3

4

5

6

7

8

9

None

Special Access Code

2

3

4

5

6

7

8

9

None

0 1

K:_____

E:_____

M:_____

G:_____

N:_____

O:_____

Business Communications Manager 3.6 Programming Operations Guide

320

Configuring call routing

Table 64 Access code values (Continued)
Carrier Codes (five codes)
Code prefix

ID length: 0

1 2

3 4 5

6

7

8

9

None

Configuring call routing
Call routing allows you to define how calls are routed by your Business Communications Manager
system.
Task:
• Set up routes to external numbers using a specific line pool:
— “Defining routes” on page 322
— “Programming the PRI routing table” on page 325
• Enter destination codes to key access to a route: “Using destination codes” on page 326
• Assign schedules for special routing requirements:
— “Setting up a destination for local calling” on page 332
— “Adding Carrier access codes to destination codes” on page 334
— “Programming for least-cost routing” on page 335
— “Using multiple routes and overflow routing” on page 336
The following figure shows a detailed view of the Call Routing programming map.
Figure 91 Call Routing headings
Call Routing
Routes
Route 000
External #
Use pool
Destination Codes
xx
Schedules

Call routing decides what path an outgoing call takes using the digits that are dialed. It is
sometimes called Automatic Route Selection (ARS).
When you select an internal line and dial, the system checks the numbers you enter against the
routing tables. If the number you dial starts with a destination code, the system uses the line pool
and dials out digits specified by the route assigned to that destination code, and then dials the rest
of the number that you dialed.

P0609326 1.1

Configuring call routing

321

Routing service replaces a number of manual tasks, including:
•
•
•

entering a line pool code
dialing an access code for a long distance carrier
deciding which line pool to use according to the time and day

You can set up routing to take advantage of any leased or discounted routes using information
supplied by the customer. The system cannot tell what lines are cheaper to use.
For Call by Call service selection (PRI only), the installer defines destination codes for various call
types over PRI lines (for example, Foreign Exchange, Tie Trunk, or OUTWATS). The user dials a
number using the intercom button without entering any special information. For more information
see “Provisioning for Call by Call limits with PRI” on page 340.
Using routing to create a coordinated dialing plan is explained in “Configuring the public and
private dialing plans” on page 302.
Warning: Plan your routing service before you do any programming.
Routing affects every call placed in the system and must be carefully planned to avoid
conflicts and gaps in the programming. Use tables to design routes and destination codes,
then check for potential problems before you start programming. It also saves you time
when all the settings are written out in front of you.

Routing configuration
The settings for a call routing include:
•
•
•
•
•
•
•

a three-digit route number (000-999)
external # digits (up to 24 digits)
a line pool
destination codes (max. of 500 available, up to 12 digits)
DN type and/or Service Type
public and private DN lengths
a schedule (optional)

TIPS: To dial a telephone number that does not match a programmed destination codes, you must
choose a line and dial the number. For long distance dialing, you can program the area codes in the
North American numbering plan as destination codes.

Business Communications Manager 3.6 Programming Operations Guide

322

Defining routes

Defining routes
Use the Routes command to configure route records that are assigned to telephones.
1

Click on the keys beside Services, Telephony Services, Call Routing.

2

Click Routes.

3

Click the Add button.
The Add Routes dialog box appears.

Figure 92 Add a route

4

Enter a three-digit route number (001-999).
Note: Route 000 is a default route and cannot be changed or deleted.

5

Click Save.

6

Click the Route number in the navigation tree. The Route window appears.

Figure 93 Define route parameters

7

Use the information in the following table to configure the route settings.

P0609326 1.1

Defining routes

323

Table 65 Route settings
Attribute

Value

Description

External #



Enter the external or dial-out number for the route you want the assigned
telephone to use. If all the required numbers are defined in the destination
code/dial string, this box can be left empty.
Optional entries:
F78: 1.5 second pause (counts as one digit in the dialing string)
F804: wait for dial tone (counts as two digits in the dialing string)
F71: Link
F808: Long tones
F*89: Programmed release
F*9: Run/Stop
Leave this entry blank if the route is directed to a VoIP line pool.

Use pool

Pool A to Pool O or
PRI-A to PRI-F

Select a line pool for the route.
The PRI pools only display if you configure an DTM for PRI.

DN type or
Service type

Public
Private
Local (Subscriber)
National
Special (International)
Tie
Foreign exchange (FX)
Outwats
Switched Digital (SDS)

This setting tells the system what type of line protocol the route uses to
process the dial string.
The heading changes between DN type and Service type, depending on
the PRI line protocol. Refer to “Programming the PRI routing table” on
page 325.

MCDN private networks: Local, National and Special are special
designators used to route calls from Meridian 1 systems, through Business
Communications Manager systems, out to the public network. The codes
for these settings are defined in the Access codes table. Refer to “Using
the MCDN access codes (tandem calls)” on page 315.
When the Business Communications Manager receives outgoing calls
from the Meridian 1, it recognizes the call type and appends the
appropriate access code to the Meridian dial string.
This code then matches to a route that uses the same DN type, passing
the call along, either to another node (the route would have the same DN
type) or to the public network (the route would have a Public DN type),
depending on the routing information.
Outgoing call display: If you have the trunks set up to send called
number information (“Defining trunk module types and settings” on page
130 and “Identifying BRI T-loops (ETSI, QSIG)” on page 271), and the DN
type is set to anything, except Private, the system sends the Public OLI
number you specified under line programming. If the DN type is set to
Private, the system sends the Private OLI number. Refer to “Configuring
line access” on page 393.

Refer also to “Call by Call service routing” on page 324 and “Programming the PRI routing table”
on page 325.

Business Communications Manager 3.6 Programming Operations Guide

324

Defining routes

Call by Call service routing
The following table provides an example of a Routing Table containing Call by Call programming
(available in the North America market profile). Refer also to “Configuring Call by Call services”
on page 339.
Table 66 Call by Call routing table example
Route #
(000-999)

Dial Out
(24 digits)

Service
Identifier

Use Pool

Service Type

003

PRI-A

Public

004

PRI-A

FX

xxxxx

005

PRI-A

Tie

xxxxx

006

PRI-B

OUTWATS

xxx

007

PRI-B

Private

008

PRI-B

Switched Digital

Note: The public DN lengths are used for all PRI calls except those whose routes use service type Private or service
type Tie with DN Type specified as Private.

Note: This type of routing only applies to those PRI trunks set with a protocol of NI, DMS100,
DMS250 or 4ESS. Refer to “Configuring the trunk module to line type” on page 131.
The service identifier (SID) depends on the selected service type (for example, with NI-2
protocol).
Service Type

Service Identifier description

Public

None

FX

Facility Number 1-5 digits

Tie

Facility Number 1-5 digits

OUTWATSa

Optional Band Number 1-3 digits

Private

None

Switched Digital

None

a. For NI-2, do not program the Carrier Access Code for banded OUTWAT calls. This call may be
rejected.

When you select or change a PRI protocol, the Service Type and Service ID fields automatically
clear for each entry in the routing table for that PRI.

P0609326 1.1

Defining routes

325

Programming the PRI routing table
The dialing plan must be thoroughly planned out in advance before programming the information
into the Business Communications Manager system.
To program the routing table:
1

Click on the keys beside Services, Telephony Services, Call Routing, Routes.

2

Click on the route number record you want to use.

3

Beside External #:, type a dialout number (up to 24 digits).
If you are creating a route for a VoIP trunk, leave this field blank.

4

Under Use pool, select a PRI line pool.
The PRI pool(s) that are displayed depend on how you allocate PRI lines into pools in the
Trunk/Line Data section of line programming. It is possible to have only pool PRI-A, or only
pool PRI-B, or only pool PRI-C, etc., even if there are three DTMs configured as PRI in the
system.

5

Choose a service type or DN type, refer to the table below:
•
•

Service type: displays for PRI lines with protocol set to NI, DMS100, DMS250, 4ESS.
Service ID:None appears where the service requires an ID.
DN type: displays for PRI lines with protocol set to SL-1 (MCDN, ETSI Euro).

The following table lists the service/DN type choices available for PRI lines:
Table 67 PRI Service type/DN type values
PRI Protocol

Type

Values

MCDN

DN

Public, Private, Local, National, Special

ETSI Euro

DN

None, Overlap

ETSI QSIG

N/A

NI

Service

Public, Tie, Foreign Exchange (FX), Outwats

DMS100

Service

Public, Private, Tie, Foreign Exchange (FX), Outwats

DMS250

Service

Public, Private, Tie, Foreign Exchange (FX), Outwats

4ESS

Service

Tie, Outwats, Switched Digital (SDS)

Enbloc dialing
Enbloc dialing allows the system to determine where a call should be routed on a PRI line. By not
dialing out until all digits are entered, the system looks at the entire code and can tell whether the
call should be routed through public lines, to another system on a network through private lines, or
to the local system.
Public and Private DN lengths and destination codes are used by the system to determine routing.
Any prefixes that need to be added on the dialed number, can be included in these settings.

Business Communications Manager 3.6 Programming Operations Guide

326

Using destination codes

Using destination codes
Destination codes allow you to control how the system interprets and routes dial strings from
internal sources. Destination codes are similar to line pool codes except that by using routes
(which attach dial strings and DN type designators to line pools) and schedules you can control
what digits the user has to dial and how the system routes the call out of the system, including what
numbers from the dial string get added or deleted to the route dialout.
The numbers used for destination codes must not conflict with the following:
Table 68 Destination codes: avoiding numbering conflicts
XXXX Numbering cannot conflict with these features
First digit must not conflict with:

Park
prefix
Destination XXXX
code

Entire code must not conflict with:

Public
Direct
Private
Other
target line
External dial
Auto DISA access Line pool Telephone destination recv’d
code
digit
DN
DN
code
codes
DN
codes
digits
*XXXX

XXXX

XXX

XXX

XXXX

XXXX

You can enter destination codes to a maximum of 12 digits.
This section includes the following information:
•
•
•
•
•
•
•
•
•
•

“Why use destination codes?” on page 327
“Deciding on a code” on page 328
“Grouping destination codes using a wild card” on page 329
“Configuring destination codes with wild cards” on page 330
“Setting up a destination for local calling” on page 332
“Setting up a route through a dedicated trunk” on page 333
“Adding Carrier access codes to destination codes” on page 334
“Programming for least-cost routing” on page 335
“Using multiple routes and overflow routing” on page 336
“Using dialing restrictions with routing” on page 338

P0609326 1.1

XXXX

XXXX

Using destination codes

327

Why use destination codes?
Routes determine path (line or pool) and any required access numbers.
Destination codes determine which route to take (i.e. an end node uses one destination code for all
other nodes in the system). If you choose to use the destination codes Normal schedule, the call
will always go out over the same route. If you choose to use the other destination codes schedules,
you can set up a more responsive plan, whereby calls can go out over more than one route, based
on scheduled times.
Destination codes provide you with the opportunity to create a dialing plan that allows users to
connect to other systems in a relatively seamless or consistent manner, regardless of the lines or
routes that are being used to get there. For example, connecting through VoIP lines requires
significantly different ways of dialing than dialing over T1 lines. However, you can configure
destination codes, such that the user dials the same number of digits regardless of the trunks over
which the calls are routed.
Figure 94 Using destination codes to access another system

User dials
9-1-601-555-2222

Call is directed in
the public system

9-1-601-555-2222

1-601-555-2222
External lines recognize the
long distance access code and
switch to the appropriate
carrier

91 is a destination
code – system uses
Route 001 and Line
Pool A

10222-1-601-555-2222
Routing tables
absorb 9

1-601-555-2222

Dialout programming tells the
system to add the access
code for long distance
(e.g. 10222)

Business Communications Manager 3.6 Programming Operations Guide

328

Using destination codes

Deciding on a code
When deciding on which digit(s) to use to start your destination code(s), you need to take into
consideration:
•

•
•

that the digit or digits you want to start your destination codes with do not match any of the
access codes, including the line pool codes that already exist in your system.
You may find that you need to delete line pool codes and create a route and destination code
instead. This could occur if you want to set up fallback to a public line, for instance. If the
public line is accessed by a line pool code, you would have to change access to a route so you
could create a fallback schedule with the destination code used for the primary line (or lines, if
you have more than one outgoing line pool that requires fallback).
how much of the common part of a dial string you want your users to have to dial, and how
much you can put in the dial string.
if you want specific dial strings to use specific routes, map these out first.
For instance, if you want users to dial between Business Communications Managers over VoIP
lines, you would create destination codes specific to those systems which use the VoIP line
pool, using the digits with which the users are familiar. You can then create a unique
destination code for the call you want to route over the land line.
Example: If users are used to dialing 9-1-555-555- to reach another system
(whose DN codes start with 6), you create a destination code of 915555556A, using the VoIP
line pools (users dial the destination code plus the DN of the telephone they want to reach on
the other system). The letter A at the end of the code represents any number from 0 to 9 which
is not used by any other destination code.
If you need to use land lines for a specific connection on the other system, you can create a
destination code specific to that destination number and attach it to the route set up with the
landline line pool (i.e. 915555556333, 6333 being the DN of the device on the other system.
When the user dials that specific number, the call will always go over the land line). Note that
by entering this code, users dialing with the code in the previous paragraph could never dial
any DN that started with 63XX.

•

•

•

If you want to use VoIP lines as your main lines, but you want to program one or more land
lines as fallback lines, you need to configure the routing and routing schedules so that the user
dials the same number, regardless of which routes get used. You use the external # dialout
string and absorb digits fields under the schedules in Destination code programming for this
purpose.
If a company wants to use VoIP lines between sites for interoffice calls, but not necessarily for
all the voice traffic, they can configure specific destination codes for the VoIP routes. In this
case, the destination code contains the same digits as a user would dial for a landline, thus,
making the shift transparent to the user and, at the same time, ensuring that the most
economical route is being used. Depending on how many exceptions there are, you can use the
wild card at the end of the string to save yourself from the necessity of entering a number of
destination codes with the same leading digits. Refer to “Grouping destination codes using a
wild card” on page 329.
If you are setting up a new system where users do not have previously-established dialing
patterns, you can use simpler destination codes. For example: You can establish 9 as the
destination code for dialing outside the system, 5 for dialing any calls within networks on the

P0609326 1.1

Grouping destination codes using a wild card

329

local exchange, and 7 for dialing any calls within the network to destinations outside the local
exchange.
Therefore:
System A calling to the public network would dial 9XXXXXXX or 91XXXXXXX if the call
is long distance.
System A calling to System B, which is in the same city, would dial 5XXXX
System A calling to System C, which is in another exchange area, would dial 7XXXXXXX
Note: If the network is using CDP for the dialing plan, the destination codes could be the
leading digit of the DN code, since that needs to be unique for each system. However, this
would depend on which digits have already been taken by other coding in the system.

Grouping destination codes using a wild card
If you have a number of destinations that have the same route and digit absorb length, you can
group these codes under one destination code to maximize your destination code table. In this case,
the start digits will be the same, but the last character will be the wild card, and indicates any digit
between 0 and 9. However, if there is a conflict with other digits already programmed or used by
other destination codes, an error message appears.
For instance, you might use the same route (555) to a number of remote sites. Each site is accessed
with the same external # (dial out string), except for the last digit, which is unique to each site.
The exception to this is a site with a totally different access number and line pool requirement
(route 565). This example is shown in the following table.
Table 69 Establishing routes and dialout requirements
Route

Dial Out (external #)

Line Pool

555

0162 237 625

Line Pool C

565

0173 133 2211

Line Pool A

If you do not use wild cards, you would need to create a separate Destination code for each unique
dialout, as shown in the following table.
Table 70 Destination codes not using a wild card
Destination codes

Route

Absorb Length

0621

555

3

Dial Out
0162 237 6251

0622

555

3

0162 237 6252

0623

555

3

0162 237 6253

0624

555

3

0162 237 6254

0625

555

3

0162 237 6255

0626

555

3

0162 237 6256

0627

565

All

0173 133 2211

0628

555

3

0162 237 6258

Business Communications Manager 3.6 Programming Operations Guide

330

Configuring destination codes with wild cards

Table 70 Destination codes not using a wild card (Continued)
Destination codes

Route

Absorb Length

0629

555

3

Dial Out
0162 237 6259

If you use the wild card character A (ANY), you can reduce the number of destination codes you
require to two, as shown in the following table.
Table 71 Destination codes using the ANY character
Destination codes

Route

AbsorbLength

062A

555

3

Dial Out

0162 237 625X
where X is the last digit of the destination code
dialed out, from 1 to 9, but not 7

0627

565

All

0173 133 2211

Tips
The digit absorption setting (absorbed length) applies to a maximum of two schedules. To
minimize the effort involved in preparing destination codes, set the digit absorption to 0.
With set to 0, the actual digits dialed by a caller are preserved in the dial out sequence. The
need to program a dial out sequence as part of the route depends on the required dialout.

Configuring destination codes with wild cards
Create the routes with dialout strings containing the common digits, then follow these steps to
create a destination code with a wild card character.

Create the destination code
1

Click on the keys beside Services, Telephony Services, Call Routing.

2

Click on Destination codes.

3

Click on the Add button.
The Destination code dialog box appears.

4

Enter a destination code, typing the letter A for the last digit of the code.

Figure 95 Adding a destination code with a wild card

5

Click the Save button to save the destination code.

P0609326 1.1

Configuring destination codes with wild cards

331

Set up the destination code schedules
1

Click on the key beside Schedules.

2

Click on the schedule name you want to
program. For example: Normal.

3

Choose the Use route you want the
destination code to refer to during
operation of the schedule.

4

In Absorb Length, choose a number to
define which part of the destination code
will be ignored by the system when it
dials out.
Programming note: All schedules
except Normal allow you to specify up to
three routes, to allow for fallback.

5

Click outside the window to save the
changes.

Enable/disable wild card digits
1

Click on the key beside Wild cards.
The valid numbers for the wild card for
this code are displayed.

2

Click on the number you want to change.

3

In the Wild card state field, choose
Assigned (can be used with this
destination code) or Available (can be
used as part of another destination code).

4

Repeat steps 2 and 3 for all the numbers
you want to change.

Business Communications Manager 3.6 Programming Operations Guide

332

Configuring destination codes with wild cards

Setting up a destination for local calling
An office can have different suppliers for local and long distance telephone service. By
programming a destination code, any call that begins with 9, which is the most common dial out
digit, automatically uses lines dedicated to local service.
Note: 9 is the default setting for the line pool code for Pool A. If you want to use 9 as a destination
code, you must change the Pool A code. Refer to “Assigning line pool access” on page 402.
Follow these steps to build a route to allow local calls.
1

Create a route that uses the line pool you assigned for the PSTN trunks. (“Defining routes” on
page 322).

2

Create a destination code record and enter a destination code, such as 9, which is a common
local call code. (“Configuring destination codes with wild cards” on page 330)
For local calls only, there are no dial out numbers (compare with “Setting up a route through a
dedicated trunk” on page 333).
The destination code can use a different route, depending on what schedule is assigned. In the
current example, the route you define is used when someone dials 9 during Normal mode,
when the other Schedules are turned off.

3

Set up the Normal schedule with the route number you defined in step 1.

Figure 96 Routing Service programming example
Routing Service (Services: Routing Service)
Route #
(000-999)

Dial out (if required)
(max. 24 digits or characters) Use Pool

001

none

A B C D E F G H I J K L M N O

002

none

A B C D E F G H I J K L M N O

The following figure shows an example of a Destination codes programming record filled out
Figure 97 Destination codes for call routing
Destination codes (Services; Routing service; Destination codes)
Service
Schedule
(max. 7 char)

Normal Rte

Route schedule

DestCode
(max. 7 digits)

Use route Absorb
(000-999 Length

1st route
(000-999

9

003

All

1

002

0

P0609326 1.1

Absorb
Length

2nd route Absorb
(000-999 Length

3rd route Absorb
(000-999 Length

Configuring destination codes with wild cards

333

An office can have leased lines or private network trunks that provide cheaper to long distance
calls by routing through the dedicated lines to remote systems, then using the local PSTN from that
system to make the call. The routing should take place automatically when the number of the
outgoing call begins with 1.

Setting up a route through a dedicated trunk
If your long distance is supplied by an alternate service or if you want to use different trunks at
different times of the day, you can configure a route to use a specific trunk.
1

Create a route that uses the line pool containing the discounted lines for long distance calling.
(“Defining routes” on page 322).

2

Create a destination code record and enter a valid destination code (maximum of 12 digits).
(“Configuring destination codes with wild cards” on page 330)
You must use a valid destination code, such as 91 (9, indicating PSTN; 1, indicating a long
distance). See “Using destination codes” on page 326. View existing destination codes before
entering a new code. The destination code can use a different route depending on the Schedule.

3

Under the Normal schedule for the destination code, enter the route you specified in step 1.

Notes about the Absorbed length:
The digit absorption setting (Absorbed Length) applies to a maximum of two schedules.
Setting Absorbed Length to 0 minimizes the effort involved in preparing destination codes. When
the Absorbed Length is at 0, the actual digits dialed by a caller are preserved in the dialout
sequence. It is not necessary to program a dial out sequence as part of the route.
If rates change depending on the time of the day or week, a different route can be used for the same
destination code when a particular schedule is in use. See “Programming for least-cost routing” on
page 335.

Business Communications Manager 3.6 Programming Operations Guide

334

Configuring destination codes with wild cards

Adding Carrier access codes to destination codes
In many cases, long distance service uses the same lines as local service but is switched to a
specific carrier using an access number, which is sometimes referred to as an equal access code
(CAC). Route programming can include the access number so the users do not have to dial it every
time they make a long distance call. The following figure shows an example of how the system
interprets what the user dials into a valid outgoing call.
Figure 98 Carrier code call numbering sequence

User dials
9-1-601-555-2222

9-1-601-555-2222
91 is a destination
code – system uses
Route 001 and Line

Call is directed in
the public system

1-601-555-2222
External lines recognize the
long distance access code
and switch to the appropriate
carrier
10222-1-601-555-2222

Routing tables
absorb 9

Dialout programming tells
1-601-555-2222 the system to add the
access code for long
distance (e.g. 10222)

Follow these steps to program a long distance carrier access code into a destination code.
1

Create a route that uses a line pool containing local lines only.

2

Program the route to use a line pool containing the lines used to access the long distance
carriers.

3

Type the dialout digits, which are the same as the access digits. For example, if the access code
is 10222, the dialout digits are 10222.

4

Create a destination code 91: 9 (for outside access) and 1 (for long distance). You must use a
valid destination code. Refer to “Using destination codes” on page 326.

5

Set Absorbed Length to 1.
The digit 9 is only used internally and should be dropped. The 1 is needed to direct the call to
the public carrier network.

P0609326 1.1

Configuring destination codes with wild cards

335

TIPS: The destination codes 9 and 91 used in the examples cannot be used together. If you need
the destination code 91 to direct long distance calls, you must create a separate set of codes that
use local calling routes. These codes would be, for example, 90, 92, 93, 94, 95, 96, 97, 98 and 99.
Refer to “Grouping destination codes using a wild card” on page 329 for information on
programming destination codes.

Programming for least-cost routing
It can be less expensive to use another long distance carrier at a different time of day. Continuing
with the example used in the previous flowchart, the lines that supply local service in normal mode
are also used for long distance service after 6 p.m. because that is when rates become competitive.
For the system to do this automatically, you must build another route.
Follow these steps to build a route for a secondary carrier:
1

Beside Route: enter an available route number.

2

Choose No number for the dialout.

3

Choose the line pool that contains the local service carrier lines.

4

Now you need to create a destination code and assign the route to the Night schedule.
In this case, the change in route uses the start and stop times for Night Schedule.

5

Add 91 as a Destination code.

6

Make sure Absorbed length is set at 1.

7

Under Night schedule: enter the route you defined in step 1.

Calls that begin with the digits 91 travel out without using the access code when the Night
schedule becomes active or when you turn it on at a control telephone.

Business Communications Manager 3.6 Programming Operations Guide

336

Configuring destination codes with wild cards

Using multiple routes and overflow routing
If all the lines used by a route specified by a destination code are busy when a call is made, you can
program other routes that the system automatically flows the calls to, or you can allow the call to
overflow directly to the Normal route schedule (usually the most expensive route). However, this
only takes effect if an active schedule is applied to the line. Overflow routing is not available in
Normal mode.
You must create overflow routes for each destination code for which you want to allow overflow
routing.
To set up the multiple routing overflow feature, follow these steps:
1

You assign the preferred routes in a Destination code schedule (Services, Telephony
Services, Call Routing, Destination code).

Figure 99 Multiple routing with destination schedules

a

Pick a schedule when you want these routes to be in effect.

b

In the First Route field enter the route number for the preferred route for the call.

c

Choose the absorb length for the first route that is appropriate for the dialout numbers you
entered for the route.

d

Repeat steps b and c for Second Route and Third Route fields.

e

Define the start/stop time as 0100 under the equivalent Routing Services schedule. This
setting means that the schedule is active 24 hours a day. Refer to “Configuring routing
service” on page 495.

P0609326 1.1

Configuring destination codes with wild cards

2

337

Assign an overflow route, usually the most expensive route, to the same Destination Code, but
for the Normal schedule.

Figure 100 Configuring the Normal schedule for overflow

3

Under Scheduled Services, Routing Service, , choose auto for
Service Setting, and Y for Overflow.

4

Use a control telephone to activate the feature on the telephones on which you want preferred
routing to be active.
Note: You must also ensure that the route correctly absorbs or passes dialed digits so that the
number dialed for each line is the same from the user perspective.

When a user dials, and the telephone cannot capture the preferred line (First Route), the system
tries each successive defined route (Second Route, then Third Route). If none of these routes have
available lines, the call reverts to the Normal mode. When the call switches from the preferred
routing mode (First Route, Second Route, Third Route), to Normal mode, the telephone display
flashes an “expensive route” warning.
Note: Overflow routing directs calls using alternate line pools. A call can be affected by different
line filters when it is handled by overflow routing.
VoIP trunking uses a similar process for setting up fallback from the VoIP trunk to a PSTN line.
Refer to the IP Telephony Configuration Guide for details.

Business Communications Manager 3.6 Programming Operations Guide

338

Configuring destination codes with wild cards

Using dialing restrictions with routing
You can further customize routing service by adding dialing filters to lines in line pools. Filters
restrict the use of the line to specific area codes.
To set up restriction filters, refer to “Defining restriction filters” on page 344.
TIPS: host system signaling codes can be part of the dial out.
You can also use routing as an alternate method for a direct-dial number. For example, create a
destination code 0 and program the number of the internal or external destination as the dialout.
Set the digit absorption to 1.

Routing matrix
To help you with your route planning, transfer the following information to a spreadsheet and fill
out the values for each route you create.
Table 72 Routing
Call Routing: Routes
Route #

External #

Use Pool

DN type
Public

Destination code:
*You can specify three
alternate routes for
these services.

Normal
*Night
*Evening
*Lunch
*Sched 4-6

Use route
None
Route:
Route 001

Absorb length
All
1 2 3 4 etc. _____

P0609326 1.1

Private

Configuring Call by Call services

339

Configuring Call by Call services
Call by Call service selection (CbC) allows you to access services or private facilities over a PRI
line without the need for dedicated facilities. The different services represent different types of
access to the network.
This section includes information about:
•
•
•
•
•

“Call by Call services” on page 339
“Switches supporting Call by Call limits” on page 340
“Provisioning for Call by Call limits with PRI” on page 340
“Setting CbC limits” on page 341
“Viewing CbC limit metrics” on page 343

Supporting protocols
The following protocols support Call by Call limits:
•
•
•
•

National ISDN 2 (NI-2)
DMS-100 custom
DMS-250 (MCI, Sprint, Generic)
AT&T 4ESS custom

Call by Call services
Business Communications Manager supports the Call by Call Services listed in the following
table.
Table 73 Call by Call Services available on the system
Service

Description

Public

Public calls connect Business Communications Manager and a Central Office
(CO). Business Communications Manager supports both incoming and
outgoing calls over the public network. Dialed digits conform to the standard
North American dialing plan (E.164 standard).

Foreign Exchange (FX)

Foreign exchange service connects a Business Communications Manager
site to a remote central office (CO). This provides the equivalent of local
service at the remote location.

Tie

Tie lines are private incoming and outgoing lines that connect Private Branch
Exchanges (PBXs) such as another Business Communications Manager.

OUTWATS

Outward Wide Area Telecommunications: This outgoing call service allows a
Business Communications Manager user to call telephones in a specific
geographical area referred to as a zone or band. Typically, a flat monthly fee is
charged for this service.

INWATS

Inward Wide Area Telecommunications: This long distance service allows a
Business Communications Manager user to receive calls originating from
specified areas without charge to the caller. A toll-free number is assigned to
permit reverse billing.
Business Communications Manager 3.6 Programming Operations Guide

340

Configuring Call by Call services

Table 73 Call by Call Services available on the system (Continued)
Service

Description

International INWATS

An international long distance service that allows a Business
Communications Manager user to receive international calls originating from
specified areas without charge to the caller. A toll-free number is assigned to
permit reverse billing.

Switched Digital

This service provides premises-to-premises voice and data transport with call
management and monitoring features.

Nine Hundred

This service is commonly referred to as fixed-charge dialing.

Private

Private incoming and outgoing calls connect Business Communications
Manager to a virtual private network. Dialed digits can conform to the
standard North American dialing plan (E.164 standard) or the dialed digits can
use a private dialing plan.

Switches supporting Call by Call limits
The following table lists the service types and cross-references them with four common switches.
Table 74 Switches and service types chart
Switches
DMS-250
(MCI, Sprint,
Generic)

AT&T 4ESS

Service types1

NI-26

DMS-100
(custom)

FX

FX

FX2

N/A

N/A

Tie

Tie

Tie

Tie

SDN (software defined
network)

INWATS

INWATS

Toll Free MEGACOM

3

INWATS

Eight Hundred

International INWATS Same as INWATS

Same as INWATS

Same as INWATS International Toll Free
Service

OUTWATS

OUTWATS

PRISM

MEGACOM

DMS Private5

VNET (virtual network)

N/A

N/A

N/A

ACCUNET4

IntraLATA OUTWATS
OUTWATS with bands
InterLATA OUTWATS

Private
Switched Digital

N/A

Nine Hundred

N/A

N/A

Nine Hundred

MultiQuest

Public

Public

Public

Public

N/A

1. N/A indicates that the protocol does not support the service.
2. DMS-250 Sprint and UCS support incoming FX only (i.e. Network-to-Business Communications Manager).
DMS-250 MCI does not support FX.
3. NI-2 allows two Tie operating modes: senderized and cut-through. Business Communications Manager supports only
senderized mode.
4. Rates greater than 64 kbps are not supported.
5. Bell Canada VNET.
6. Not all service types may be supported by a switch type. For information, contact your service provider.

Provisioning for Call by Call limits with PRI
To program the system for Call by Call Limits with a PRI interface, you must:

P0609326 1.1

Configuring Call by Call services

•
•
•
•

341

provision a DTM as PRI, if one is not already configured as part of the system
select a protocol, on page 99
program incoming call routing, on page 152
program routes that use the PRI pools, see “Configuring call routing” on page 320.

Other required programming in the Unified Manager
Programming Call by Call on PRI requires these settings:
•
•
•

under Line Access, assign the line pool
under Services, in routing services, assign a pool for routing, and assign the service type and
service id, if required
under General settings, specify the minimum and maximum values for the pools

Setting CbC limits
PRI pool limits for Call by Call services allows you to configure limits for service types without
interacting with the CO. This feature sets the minimum and maximum number of incoming and
outgoing calls per service type for the PRI pool.
The number of active calls are tracked. Whenever a call is setting up, a check determines if the call
is allowed. Calls are not allowed if they exceed the maximum value for that service type or if they
use lines needed to maintain the minimum value of other service types.
Follow these steps to program CbC Limits
1

Click on the keys beside Services, Telephony Services, General settings, and CbC limits

2

Click on the key beside a pool type (PRI-A to PRI-F).

3

Select a service.
For example, Public. The services that display depend on the PRI protocol.

Figure 101 Setting CbC limits parameters

Business Communications Manager 3.6 Programming Operations Guide

342

Configuring Call by Call services

4

The following table lists the possible values to enter into the pool fields.

Table 75 DN length values
Attribute

Values

Description

Minimum incoming

Default: 2

Maximum incoming

Default: 23

Minimum outgoing

Default: 4

Note: The total of the minimum values for incoming or outgoing PRI
services cannot exceed the total number of lines in the PRI pool.
The maximum value for an incoming or outgoing PRI service cannot
exceed the total number of lines in the PRI pool.

Maximum outgoing

Default: 23

PRI line pools
All lines in a PRI interface are in the same PRI line pool. This pool cannot contain any non-PRI
lines. There is one PRI pool available for each PRI interface. Depending on the order that the
modules are configured as PRI, Pool PRI-A represents lines 061 to 083, Pool PRI-B represents
lines 085 to 107, and Pool PRI-C represents lines 109 to 131, etc. to Pool PRI-F. If all PRIs are
connected to the same service provider and use the same protocol, lines 061 to 083, 085 to 107,
and 109 to 1311 etc. can be put in the same pool, PRI-A, PRI-B, PRI-C up to PRI-F.

CbC matrix
To help you organize your PRI call by call limits lines, transfer the following information to a
spreadsheet and fill out the information.
Table 76 CbC matrix
PRI
pool
PRI-A
PRI-B

Type

Incoming lines

Outgoing lines

Public, Tie, Foreign Exchange
OUTWATS, INWATS
International INWATS, Private
Switched Digital, Nine hundred

Minimum incoming: _________

Minimum outgoing: _________

Maximum incoming: _______

Maximum outgoing: _________

P0609326 1.1

Configuring Call by Call services

343

Viewing CbC limit metrics
You can view statistical information about call-by-call limit settings for PRI when the protocol is
set to call-by-call routing.
1

Choose Diagnostics, Service Metrics, Telephony Services, CbC limit metrics.
The display shows the pools that supports CbC routing.

2

Choose a PRI pool.
The display shows the services in the pool. The Call-by-Call services that display are
determined by the PRI protocol of the line.

3

Select a service. For example, Public.
The display shows the settings for the selected service.

Figure 102 Metrics for all CbC options

Business Communications Manager 3.6 Programming Operations Guide

344

Defining restriction filters

4

To clear the settings for a selected service, click Clear metrics on the Configuration menu.

Defining restriction filters
Restriction filters allow you to restrict the numbers that can be dialed on any external line within
Business Communications Manager. Up to 100 restriction filters can be created for the system.
To restrict dialing within the system, you can apply restriction filters to:
•
•
•

outgoing external lines (as line restrictions)
telephones (as set restrictions)
external lines on specific telephones (as line/set restrictions)

Restriction filters can also be specified in Restrictions service for times when the system is
operating according to a schedule. Dialed digits must pass both the line restrictions and the set
restrictions. The line per set (line/set) restriction overrides the line restriction and set restriction.
This section includes the following information:
•
•
•
•

“Adding a restriction filter” on page 345
“Notes about restriction filters” on page 345
“Adding overrides to restrictions” on page 348
“Restriction filter examples” on page 349

The following figure shows the Restriction Filters headings.
Figure 103 Restriction Filters headings
Restriction Filters
Filter 00-99
Restrictions
Restriction 01
Digits
Overrides
Override 001
Digits

P0609326 1.1

Defining restriction filters

345

Adding a restriction filter
Follow these steps to add new restriction filters:
1

Click on the keys beside Services, Telephony Services.

2

Click on Restrictions.

3

Click the Add button located above the navigation tree.
The Add Restrictions dialog appears.

Figure 104 Adding restriction filters

4

Enter the digits you want to restrict.

5

Click Save.
The new restriction is added to the button of the restrictions list for that filter.

6

If you want to add numbers that will override the restrictions, refer to “Adding overrides to
restrictions”.

Removing restrictions
To remove restrictions that no longer apply, click on the Restriction # you want to remove, then
click the Delete button at the top of the column.
Exercise caution when removing overrides.
If you remove a restriction, the overrides associated with the restriction are also removed. This
action also changes the identifying numbers of the subsequent restrictions that you have defined.
For example, if you remove Restriction 01, Restrictions 02 to 08 are renumbered as 01 to 07.

Notes about restriction filters
A restriction filter is a group of restrictions and overrides that specify the external numbers or
feature codes that cannot be dialed from a telephone or on a line. The restriction filters setting
allows you to assign restrictions in one step as a single package of dialing sequences that are not
permitted.

Business Communications Manager 3.6 Programming Operations Guide

346

Defining restriction filters

In addition to restricting telephone numbers, you can prevent people from entering dialing
sequences used by the central office (the public network) to deliver special services and features.
Some of these features provide the caller with dial tone after they have entered the special code
(which often uses # or *), therefore, users have an opportunity to bypass restrictions. To prevent
this from happening, you can create filters that block these special codes.
You create a filter by defining the dialing sequences that are denied. There are also variations of
each sequence that you want users to be able to dial, these are called overrides. Overrides are
defined within each restriction package for each filter.
Once you create the filters, you can assign the restrictions to a telephone (System DNs), to a line
(Lines), to a particular line on a telephone (System DNs), and to remote callers
(Lines, Remote access).
Note: Filter 00 cannot be changed. Filter 01 has a set of defaults. Filters 02 to 99 can be set to suit
your special requirements. See “Default filters (North America)” on page 347.
•

Each programmable filter can have up to 48 restrictions.

•

There is no limit on the number of overrides that can be allocated to a restriction. However,
there is a maximum total of 400 restrictions and overrides allocated to the 100 programmable
filters.

•

The maximum length of a restriction is 15 digits.

•

The maximum length of an override is 16 digits.

•

Entering the letter A in a dialing sequence indicates a wild card, and represents any digit from
0 to 9.

•

You can use * and # in a sequence of numbers in either a restriction or an override. These
characters are often used as part of feature codes for other systems or for features provided by
the central office (the public network).

•

When restricting the dialing of a central office feature code, do not forget to create separate
restrictions for the codes used for DTMF and pulse lines (for example, *67 and 1167).

•

Do not string together a central office feature code and a dialing sequence that you want to
restrict. Create a separate restriction for each.

•

You can copy restrictions and overrides from one filter to another. You can use a restriction or
override in any number of filters. Each time you use a restriction or override, it counts as one
entry. For example, if restriction 411 exists in filters 01, 02 and 03, it uses up three entries of
the 400 entries available.

•

Removing a restriction from a filter has no effect on the contents of other filters, even if the
restriction was copied to them.

•

You cannot delete a filter. Removing the restrictions programmed on a filter makes it an
unrestricted filter but the filter itself is not removed.

P0609326 1.1

Defining restriction filters

347

Default filters (North America)
Filter 00 permits unrestricted dialing and cannot be changed.
Filter 01 is pre-programmed with 10 restrictions and some associated overrides. In Filter 01,
Restriction 02 and Override 001 allow long distance toll free calls.
The dialing string 911, which is the number for emergency assistance in North America, is
included as both a restriction and an override in Filter 01. This arrangement prevents anyone from
blocking calls for emergency assistance on lines or sets using the default filter.
Table 77 Default restriction filters
Filter

Restrictions (denied)

00

Unrestricted dialing

01

01: 0

Overrides

02: 1

001: 1800
002: 1877
003: 1888

03: 911

001: 911

04: 411
05: 976
06: 1976
07: 1AAA976
01

08: 1900
09: 1AAA900
10: 5551212

02 - 99

No restrictions or exceptions programmed

Note: Default filters are loaded only when the system is cold started.
Filters 02, 03, and 04, although not preset with restrictions and overrides, are the default filters in
these programming headings:
Table 78 Default filters for program headings
Filter

Heading

Sub-heading

02

System DNs

Set restrictions

03

Lines

Line restriction

04

Lines

Remote restriction

Business Communications Manager 3.6 Programming Operations Guide

348

Defining restriction filters

Default filters (other)
Three profiles have global overrides which do not appear in Unified Manager restriction
programming and cannot be changed.
Australia: 000, 13144A
Brazil:

194A

UK:

999, 112

Adding overrides to restrictions
1

Click on the keys beside Services, Telephony Services, Restrictions.

2

Click on the restriction number where you want to add an override.
The Add Overrides dialog appears.

Figure 105 Adding overrides to restrictions

3

In the Digits field, enter the number that you want to be able to override the restriction filter.
Note: Enter the letter A as a wild card character that represents any digit from 0 to 9 in a
sequence of numbers when denying numbers or creating overrides.

4

Repeat steps 2 and 3 for all the overrides you want to add

5

Click Save.
The new override is added to the bottom of the Overrides list.

To view an Override to a restriction: click on the Override XXX headings.
To delete an override: Select the override you want to delete, and then click on the Delete button at
the top of the column. If you want to delete all overrides for that restriction, click the Delete All
button.

P0609326 1.1

Defining restriction filters

349

Restriction filter examples
Line and set restrictions are shown in the following figures.
In the first figure, below, a caller using line 001 could only dial long-distance numbers to area
codes 212 and 718. A caller using line 003 could not dial any long-distance numbers. A caller
using line 005 could dial long-distance numbers to area codes 212, 718, and 415.
TIPS: To restrict dialing from outside the system (once a caller gains remote access), apply
restriction filters to incoming external lines (as remote restrictions).
Figure 106 Line restriction example
Line restriction
Set restriction
Line 1
Line 3

no long
distance
except
area codes
212, 718

Line/Set
restriction

Line 5

no long
distance
except area
codes 212,
718, 415

no long
distance
except area
codes 212,

no long
distance

no long
distance

Line 1

Line 3

Line 5

Business Communications Manager 3.6 Programming Operations Guide

350

Defining restriction filters

In the following figure, dialed digits must pass both the remote restriction and the line restriction.
A remote caller can override these filters by dialing the DISA DN and entering a COS password.
Figure 107 Remote line restriction example
Line restriction
Remote restriction

Remote
caller

No long
distance
except area
codes
212, 718

Line
pool
access
code 81

COS restrictions

COS password

No long
distance
except area
codes 212,
718, 416
no long
distance
except area
codes 212,
718, 416
Line pool
access
defined in
remote
package

User filter
Line filter
Remote
package

Line 001

Line 003

Line 082

Restriction filters matrix
Transfer the following information to a spreadsheet and fill out the restriction filter information
you want for your system.
Table 79 Restriction filters matrix
Filter #

P0609326 1.1

Restriction #

Overrides

Enhanced 911 (E911) configuration

351

Enhanced 911 (E911) configuration
Government rules vary about support for Enhanced 911 (E911) dialing service by Customer
Premises Equipment. Legislation may require that the Customer Premises Equipment give a more
precise location of the source of a 911 call than the billing address of the central office line.
Consult your service provider about the laws and regulations.
Task:
Set up emergency access number to comply with local regulations.
Use the following configuration rules when installing the Business Communications Manager
system to assure compliance with local regulations:
•

When equipped with PRI trunks, Business Communications Manager can deliver the Calling
Line ID of a telephone dialing 911 through the Public Switched Telephone Network, if the
proper programming has been implemented and PRI trunk service has been installed by the
service provider. If you are using ISDN PRI, implement OLI programming and Business
Name programming to add the Set ID to the CLASS information.

•

By default, Restriction Filter 02 is assigned to all sets on startup. There are no restrictions
applied in Restriction Filters 02-99. Restriction Filter 01 has restrictions, but 911 is an
exception for this filter. For information on how to change the Restrictions, refer to “Defining
restriction filters” on page 344.

•

When using other trunk interfaces, you can assign separate line pools to groups of telephones
in different areas (for example, in different buildings, floors or sections).

•

Be careful when using the Set Relocation feature. You may have to reprogram the line pool
access to send the right location on 911 calls.

•

Configure the 911 destination code to dial out over a Normal Schedule in all applicable
Service Modes, as this is the default route should any other programmed routing attempts fail.
When using PRI interfaces, make sure all sets can use the PRI line pool that the Normal
Schedule route uses.

911 and IP telephones
DO NOT program IP telephones with a 911 code mapped to a line pool for the Business
Communications Manager, unless it is co-located with the system.

Business Communications Manager 3.6 Programming Operations Guide

352

Enhanced 911 (E911) configuration

P0609326 1.1

353

Chapter 13
Configuring DN records, an overview
This section provides an overview about the process for programming the records of the
telephones and equipment attached to the station modules on the Business Communications
Manager. Refer also to the process map on the next page (“Understanding the configuration
process” on page 354).
For a detailed description about what DNs are, and what the different categories of DNs in the
navigation menu mean, refer to Defining the System DN headings on page 358. System DNs also
contains a DN registration heading, which lists the DNs which are, or which can be, registered
to the system (“DN Registration headings” on page 363).
Task overview: To set up each telephone or device attached to your system:
• Determine which DNs will be assigned to the telephones and devices.
(“DN mapping for digital telephones” on page 355)
• Use the Wizards to configure telephones
(“Configuring DNs using the Wizards” on page 369)
OR
Configure each telephone record individually (“Configuring DNs for system devices” on page
387).
• Determine the call display and log options. (“Configuring telco features” on page 445)
• If you have optional voice mail active on your set, you will also see the active phone number
for each telephone. (“Voice Mail settings” on page 446).
• If your attendants have M7324 telephones with CAP modules or BST T7316E telephones with
KIM modules that are assigned as CAP stations, you need to assign these systems under
“Setting up CAP stations” on page 434.
The new BTS Doorphone, which uses the M7324 model name, has separate installation and
configuration guides.
IP telephones require the programming described in this section, but they also have specific IP
configuration parameters, which are described in the IP Telephony Configuration Guide.

Business Communications Manager 3.6 Programming Operations Guide

354

Understanding the configuration process

Understanding the configuration process
The following process map provides an over-all view of how to set up telephone configurations.
Figure 108 Process map: Configuring DNs for system devices
Lines, station modules
and base stations are
installed, as required.

DN number ranges depend on where station modules are
set, on the type of telephones, and on the vintage of your
system. IP telephones and NetVision wireless IP
handsets use DNs within the digital range. If they are set
to automatically choose a DN, the system chooses DNs
beyond the station module range.
Refer to “DN mapping for digital telephones” on page 355
and “DN mapping for Companion, DECT and ISDN
devices” on page 358.

You have determined
the DN ranges that
you are configuring.

Do you
have a
DN template
defined?

No

Use Edit DN Record Template Wizard
if you are adding a number of devices
that have the same configurations.
Refer to Editing DN Record Templates
on page 369.

Yes
Use the Add Users Wizard to
define the DN records. Refer to
Creating telephone records with
the Add Users Wizard on page 375

Tweak each DN record, including
setting up display and log options,
special button programming, and
restrictions, as required. Refer to
Configuring DNs for system
devices on page 387

Are the
telephones
/devices
connected to
the system?

Yes

No

Refer to the applicable
installation guide, and
install the devices.

Test the devices

Note: References in this document to terminal, set, and telephone all refer to telephones that are
compatible with the Business Communications Manager system.

P0609326 1.1

DN mapping for digital telephones

355

DN mapping for digital telephones
Use the following tables to determine which DNs can be assigned to your telephones if your
system administrator did not provide you with a list of available DNs or did not fill out the
Programming Record forms. You will need to determine which media bay modules are installed,
and to which DS30 bus number they are configured. Your system administrator can determine this
for you, or refer to Chapter 5, “Configuring resources — media bay modules,” on page 123.
As a rule, your station modules will be installed starting from DS30 02 and working down.
• Use the first table, below, if you had an existing 2.5 system that was upgraded with the 3.0 or
later software.
• Use the second table, below, if you are installing telephones on a brand new 3.0 or later system.
Note: The tables below are based on a three-digit DN numbering system. The first digit on your
system may be different, or you may have more than three digits, however, the sequencing will
be the same, unless some DNs have previously been renumbered.

Double Density and DNs
In BCM 3.0 and later software, the system can support double density modules. This means that
twice as many DNs can be assigned per DS30 bus when double density modules are installed on
the channel.
Upgraded systems: The DN number for upgraded systems goes from the Start DN (default is 221)
up to 316 from Bus 02 to 07, respectively. The second level of DNs, then start at Bus 02 (317) and
flow consecutively to Bus 07 (472). Refer to the DN chart in “DN chart for upgraded 2.5 systems”
on page 356.
New 3.0 or later systems: If you are installing a new 3.0 or later system, the DN numbers flow
consecutively. For example, Bus 02 has DN 221 to 253, and so on. Refer to the DN chart in
“DN chart for new 3.0 or newer systems” on page 357.
PDD and FDD: If the system is configured to be in Partial Double Density (PDD) (the default
setting for version 3.0 and later systems), Bus 06 and 07 only have 16 available DNs. The
exception to this is the DN count for the Companion sets, which can use both B-channels, and,
therefore, can support 64 handsets when Bus 06 and 07 are fully loaded using a DSM32 set to
single density. Refer to “DN mapping for Companion, DECT and ISDN devices” on page 358.
You system can bet set to Full Double Density (FDD), in which case Bus 06 and 07 have 32
available DNs, but neither can support Companion.

Business Communications Manager 3.6 Programming Operations Guide

356

DN mapping for digital telephones

DN chart for upgraded 2.5 systems
BCM 2.5 systems upgraded to 3.0 or newer software
Module type
(SD = single density; FDD = full double density; PDD = Partial double density)

Module
location
DS30
bus #4

DSM16 or
Module
DSM
offset
16+PDD

DSM16+
FDD

DSM 32 or DSM32+
PDD
(First 16 DNs for
each DS30)

DSM 32+
FDD
(offset 0)

ASM82

221-2361

02

0
1
2
3

221-236 or 221- 252
377-392

221-236 and
377-392

221-228
229-236
377-384
385-392

237-252

03

0
1
2
3

237-252 or
393-408

237- 268 237-252 and
393-408

237-244
245-252
393-400
401-408

253-268

04

0
1
2
3

253-268 or 253- 284
409-424

253-268 and
409-424

253-260
261-268
409-416
417-424

269-284

05

0
1
2
3

269-284 or
425-440

269- 300 269-284 and
425-440

269-276
277-284
425-431
432-440

0
1
2
3

285-300

285-300 or 285- 316
441-456

285-300 and
441-456

285-292
293-300
441-448
449-456
(PDD offset
1 and 2, only.
441-456 appear
under B2s
heading)

0
1
2
3

301-316

301-316 or
457-472

301-316 and
457-472

301-308
309-316
457-464
465-472
(PDD offset
1 and 2, only.
457-472 appear
under B2s
heading)

06

073

Customized
DNs1

DNs are based on the default, three-digit DN. If your system has another numbering system, make a note of your
DN ranges in the Custom DN column.
2 ASM 8 modules do not have special double density settings. However, on a PDD system, on DS30 06 and 07, only
offset 0 and 1 are available.
3 If you system is set to a 3/5 DS30 split, these DNs are not available to digital telephones.
5 Each Bus has 32 ports, numbers XX (for example: 0201 is the first port on Bus #2). Ports are assigned
sequentially to each DN number. However, if you change the DN number of an assigned telephone, the port number
remains the same.
1

P0609326 1.1

DN mapping for digital telephones

357

DN chart for new 3.0 or newer systems
If your system is a brand new BCM 3.0 or newer system, the DN numbering is consecutive from
DS30 02 to 07.

New BCM 3.0 or newer systems
Module type
(SD = single density; FDD = full double density; PDD = Partial double density)

Module
location
DS30
Offset
bus #4

DSM16 or
DSM 16+
PDD

DSM16+
FDD

221-2361

02

0
1
2
3

221-236 or
237-252

253-268

03

0
1
2
3

253-268 or
269-284

285-300

04

0
1
2
3

285-300 or
301-316

317-332

05

0
1
2
3

317-332 or
333-348

0
1
2
3

349-364

349-364 or
365-380

0
1
2
3

381-396

381-396 or
397-412

DSM 32 or DSM32+
PDD
(First 16 DNs for
each DS30)
(offset 0)
221-236
and
253-268
253-268
and
285-300
285-300
and
317-332
317-332
and
349-364
349-364
and
381-396

DSM 32+
FDD
221-252

221-228
229-236
237-244
245-252

253-284

253-260
261-268
269-275
276-284

285-316

285-292
293-300
301-308
309-316

317-348

317-324
325-332
333-340
341-348

349-380

349-356
357-364
365-372
373-380
(PDD offset
1 and 2, only.
365-380 appear
under B2s
heading)

381-412

381-388
389-396
397-404
405-412
(PDD offset
1 and 2, only.
397-412 appear
under B2s
heading)

06

073

ASM82

Customized
DNs1

DNs are based on the default, three-digit DN. If your system has another numbering system, make a note of your
DN ranges in the Custom DN column.
2 ASM 8 modules do not have special double density settings. However, on a PDD system, on DS30 06 and 07, only
offset 0 and 1 are available.
3 If you system is set to a 3/5 DS30 split, these DNs are not available to digital telephones.
4 Each Bus has 32 ports, numbers 0XX (for example: 0201 is the first port on Bus #2). Ports are assigned
sequentially to each DN number. However, if you change the DN number, the port number remains the same.
1

Business Communications Manager 3.6 Programming Operations Guide

358

Defining the System DN headings

DN mapping for Companion, DECT and ISDN devices
Companion, DECT, and ISDN equipment have pre-set DNs that are automatically assigned on a
default system.
Table 80 DN mapping for DECT, Companion and ISDN
Default DN
range

Media Bay
Module

System version

Equipment

DS30

All

Companion

565-596

DTM

6 and/or 7 (only on PDD systems)

updated from 2.0

DECT

501-532

DECT

6 or 7

updated from 2.5

DECT

597-624

DECT

6 or 7

all

ISDN

597-624

DTM or BRI

any

Defining the System DN headings
This section provides general information about what DN records and how the Unified Manager
categorizes active and inactive DN records.
This section includes information about:
•
•
•
•
•
•
•

“The two sides of a DN record” on page 359
“The System DN headings” on page 361
“DN Registration headings” on page 363
“Moving between the Inactive and Active lists” on page 365
“Deregistering IP and wireless IP devices” on page 366
“Feature DNs” on page 366
“Renumbering DNs” on page 366

P0609326 1.1

Defining the System DN headings

359

The System DN heading provides access to the DN records of telephones that are active on the
system, records of all the DNs that are available, and a comprehensive list of all DN possibilities.
Use the list that is most convenient for what you want to do.
Figure 109 System DNs main headings

System DNs
Active set DNs
DN XXX-XXX

General
Line Access
Capabilities
User Preferences
Restrictions
Telco Features

Active Companion DNs
DN XXX-XXX

Active application DNs
DN XXX-XXX

Inactive DNs
Set DNs
Companion DNs
All Inactive DNs

System DNs (continued)
All ISDN/DECT DNs
DN XXX-XXX

All System DNs
DN XXX-XXX

All System B2s
DN Registration
Active DNs reg’d
DN XXX-XXX
Inactive DNs reg’d
DN XXX-XXX
All DNs reg’d
DN XXX-XXX
DNs avail for reg’n
DN XXX-XXX

System DNs (continued)
IP set DNs reg’d
Active
Inactive
Voice Port DNs reg’d
Active
Inactive
IP Wireless DNs reg’d
Active
Inactive
CTE mediaDNs reg’d
Active
Inactive
OAM DN reg’d
DN XXX-XXX

The two sides of a DN record
There are two sides to DNs that affect system telephones and equipment.
1

On the system side, each telephone on the network is assigned a DN number, which identifies
it to the system. DNs for digital telephones, the M-series telephones and the Business Series
Terminal (BST) telephones map to each wire pair on a station media bay module.
ISDN, DECT, and Companion devices also require media bay modules to operate. However,
they have a specific set of DNs that are not mapped directly to the hardware. Refer to table
entry: Active Companion DNs on page 361 and table entry: All ISDN/DECT DNs on page 362.
IP telephones do not use media bay modules because their connections occur over the internet
and directly through the Media Services Card (MSC) within the Business Communications
Manager hardware. However, the system uses DN records from the digital range to identify
these terminals because their functionality closely mirrors the digital telephones.
As well, certain applications running on the Business Communications Manager are assigned
DNs, so that the system can access the application functionality. These would include direct
inward access (DISA) DNs, and DNs for CallPilot access. Refer to table entry: Active
application DNs on page 361.
When you initialize your system with the Quick Start Wizard, you will be asked to specify a
DN length and a Start DN.

Business Communications Manager 3.6 Programming Operations Guide

360

Defining the System DN headings

Warning: Changing DN settings after system startup:
Changes to the Start DN, DN length or Received # length can affect other applications.
Make changes to these settings only at system installation, before you do any other
programming.
You can also renumber a group of DNs after you initialize your system. For example, if your
service provider has given you a specific list of DID numbers, you might choose to ensure the
DNs mirror those numbers, to make it easier to administer the telephones. The DN Renumber
Wizard allows you to accomplish this quickly. Refer to “Using a wizard to renumber
telephone DNs” on page 367. If you do this after you have programmed telephones to the
DNs, the programming attached to the original DN is transferred to the new DN and the new
DN record displays the new port number.
The exception to this is the DECT DNs. If you change DNs in the range you specified for your
DECT handsets, you must rerun the DECT Configuration Wizard to reset the DNs on the
DECT module.
To view your system settings: Click on Diagnostics, MSC, then select Configuration and
click on System Startup. This screen displays the telephony template that is active for your
system and the start DN that is assigned to the system.
2

The second part of a DN is the content of the DN record. Each DN heading provides a number
of parameters that get assigned to the telephone that accesses that DN. Some of these
parameters can be copied to other telephones, while others, such as the name of the telephone,
and button programming, is unique to each DN record or to each type of telephone.
DN content can be updated at any time, such as if you upgrade the model of telephone. For
details about setting up or changing a DN record, refer to the sections “Defining the System
DN headings” on page 358 and “Configuring DNs for system devices” on page 387.

P0609326 1.1

Defining the System DN headings

361

The System DN headings
These are the types of headings found under System DNs:
Active set DNs

This list displays only the DNs for digital (M-series and BST T-series
telephones), IP telephones, BST T7406 and NetVision telephones that are
actually connected to the system and are activated. Use this list when you
want to change a configuration, or to remove a telephone.
Nortel IP telephone and Symbol NetVision configuration records are
located under Services, IP Telephony. Although you do not have to
assign DNs to configure IP telephony DN records, they will not appear
under this listing unless the telephone has been registered to the system.
Refer to the IP Telephony Configuration Guide for details about
configuring IP telephone telephones.

Active Companion
DNs

This list displays only the DNs for Companion sets that are registered on
the system. Use this list when you want to change a configuration, or
remove a telephone.
Note: This item only appears on the navigation tree for systems set to
regions that support the Companion Wireless system. Refer to “Mobility
services by region” on page 848.

Active application
DNs

This list segregates the list of DNs that are used for running applications,
such as Voice Mail, Interactive Voice Response (IVR), and Call Center.
These DNs are assigned within the applications that they apply to. You do
not need to do anything to any of these DNs, other than to note they are
not available for application to your telephones.
Note: Call DNs (CDN) and IP telephones get their DNs from a common
pool. If you set your IP telephony to auto assign DNs, check the DN
listings for new telephones to ensure that the DNs are not assigned to
CDNs.
Warning: Changing the settings on these DNs could cause
malfunctions in the applications to which they apply.

Inactive DNs

The DNs listed in this section do not yet have telephones assigned to
them.
This list contains all possible DNs in the digital and Companion ranges.
However, you can only assign a digital, BST T7406 or Companion
telephone to a DN that is connected to an installed station module. IP
telephones and NetVision telephones can use any available DN in the
digital range. If IP telephones are set to auto-assign DNs, the system will
select DNs that are not likely to be required by installed station modules.
Warning: Changing the settings on these DNs could cause
malfunctions in the applications to which they apply.

Business Communications Manager 3.6 Programming Operations Guide

362

Defining the System DN headings

Set DNs

This list displays the digital (M-series and BST T-series telephones),
BST T7406 cordless, IP telephone, and NetVision DNs that are not
assigned or are not active. Use this list to set up new telephones before
they are installed in the field.
Note: If IP telephones are set to auto-assign DNs, the system will select
DNs that are not likely to be required by installed station modules. You
cannot pre-configure the records since you cannot know which DNs the
system will assign to which IP telephone. Once the IP telephone is
configured, the DN record moves to the active list, and you can access it
from this list to perform the required configurations.

Companion DNs This list displays the Companion DNs that do not have registered

handsets. Use this list to define new handset records.

All Inactive DNs

This list displays all digital, IP, and Companion DNs that are not assigned
or are not active.
Note: Companion DNs can also be used for DECT system that require
more than the default number of ISDN and DECT DNs. In this case, when
you define the Companion DN as ISDN/DECT, the record disappears off
this list and appears on the All ISDN/DECT DNs list.

All ISDN/DECT DNs This list displays all the DNs that default to ISDN or DECT applications,

plus any DNs from the Companion range that have been changed to
ISDN/DECT.
Note: ISDN/DECT DNs can also be used for Companion handsets that
require more than the default number of Companion DNs. In this case,
when you define the ISDN/DECT DN as Companion, the record
disappears off this list and appears on the Active Companion DNs list.

All System DNs

This list displays all possible DNs, regardless of whether a station module
is configured to activate them or not. This list begins with the Start DN
that was defined when the system was initialized.

All System B2s

This list displays DNs only if your system is set to PDD (partial double
density). If the system is set to FDD, these are the second-level (B2) DNs
that assign to DS30 bus 06 and 07. This is a read-only list and includes B2
DNs assigned to devices such as Companion handsets. B2 DNs are also
used in some call center applications.

P0609326 1.1

Defining the System DN headings

363

DN Registration headings
The DN records found under this heading indicate whether a device is registered to the system,
and, if it is, whether it is active.
Figure 110 Registration DNs, main headings

All System B2s

DN Registration ...

.....

DN Registration

Voice Port DNs reg’d
Active
Inactive
IP Wireless DNs reg’d
Active
Inactive
CTE mediaDNs reg’d
Active
Inactive
OAM DN reg’d
DN XXX-XXX

Active DNs reg’d
DN XXX-XXX
Inactive DNs reg’d
DN XXX-XXX
All DNs reg’d
DN XXX-XXX
DNs avail for reg’n
DN XXX-XXX
IP set DNs reg’d
Active
Inactive

All registered devices display a Registration type field when the DN is selected. This field
indicates the type of device.

These are the types that display under the various headings:
Device type

Registration type

i2004

i2004

i2002

i2002

i2050

i2050

i2001

i2001

IP wireless (NetVision)

IP wireless

Voice Port

Voice Port

Unified Manager

Remote admin

Call Center

not used

Voice CTE

CTE media

The devices listed under this heading are registered with the system, but are not necessarily active.
This would explain why an application DN, for example, for voice mail, shows up under both the
Application DNs and the DN Registration/Active DNs reg’d headings. If the service were to
stop, however, the heading under Application DNs would disappear and under DN Registration,
the heading would appear under Inactive DNs reg’d.
Business Communications Manager 3.6 Programming Operations Guide

364

Defining the System DN headings

Following is a brief description of the type of devices found under each heading.
Active DNs reg’d

This is a list of registered DNs that are currently in contact with the
Business Communications Manager.

Inactive DNs reg’d

This is a list of DNs that are registered but which are inactive. For
example, in the case of a NetVision handset, this might mean that
the user has the handset turned off.

All DNs reg’d

This list has all the DNs that are currently registered with the
system.

DNs avail for reg’n

This list identifies the DNs that are not yet registered to a device but
which could be assigned to a device. Keep in mind, this list may
include digital DNs that do not yet have a telephone attached. Check
your system DN record to ensure that you do not assign DNs that
you might want to assign to a wired telephone.

IP set DNs reg’d

This list has both an active and inactive list. The active list indicates
the IP telephones (i-series) that are registered and active on the
system. The inactive list indicates the IP telephones that are
registered but which are not yet active on the system.

Voice Port DNs reg’d

This list has both an active and inactive list. The active list indicates
the voice ports that are registered and active on the system. The
inactive list indicates the voice ports that are registered but which
are not yet active on the system. Refer to your voice mail
documentation for information about setting up voice port DNs.

IP wireless DNS reg’d

This list has both an active and inactive list. The active list indicates
the NetVision telephones that are registered and active on the
system. The inactive list indicates the NetVision telephones that
have registered with the system but which are not active.

CTE media DNs reg’d

If you have any applications that use LAN CTE, the DNs are listed
here. This list has both an active and inactive list. The active list
indicates the devices using CTE that are registered and active on the
system. The inactive list indicates the devices using CTE that are
registered with the system but which are not active. Refer to the
CTE documentation for information about assigning these DNs.

OAM DN reg’d

This is the DN that is used for remote administration. Refer to the
remote administration guides for details about assigning this DN.

P0609326 1.1

Defining the System DN headings

365

Moving between the Inactive and Active lists
DNs move between active and inactive lists based on a number of factors which are described in
the two sections below.

From Active list to the Inactive list
A DN record heading will move from the Active list to the Inactive list in the following
circumstances:
• A digital or analog hard-wired telephone (M-series or T-series telephones) remains unplugged
from a port for more than two minutes.
• An IP telephone is disconnected from the system for more than 30 seconds and the Keep DN
alive setting for that telephone is set to No. If Keep DN alive is set to Yes for the telephone, that
DN remains active until the field is set to No, or the system administrator removes the DN.
• An active IP telephone or wireless IP telephone (NetVision) DN is deregistered through the
Unified Manager.
• A Companion handset is deregistered, or a DECT handset is unsubscribed.
• An application such as voice-mail, IVR, or the Unified Manager no longer requires DN(s) and
stops communicating on them.
• In the case of a registered DN, if the device or service is turned off.

From Inactive list to Active list
A DN will move from the Inactive list to the Active list in the following circumstances:
• A digital telephone (M-series or T-series) is plugged into the port assigned to the DN.
• An IP telephone (2001, 2002, 2004, 2050) registers to the system and gets assigned a requested
or automatically-selected DN. IP telephones also assign to one of the IP keycoded positions,
which is indicated in the Device port field.
• An IP cordless telephone (NetVision) registers to the system and gets assigned a
pre-programmed DN. The handsets also assign to one of the IP keycoded positions, which is
indicated in the Device port field.
• An application such as voice-mail, IVR, or the Unified Manager allocates and starts using
DN(s)
• A Companion or a DECT handset is registered to the system.
• In the case of a registered device, if the device or service is started or turned on.

Business Communications Manager 3.6 Programming Operations Guide

366

Renumbering DNs

Deregistering IP and wireless IP devices
If you select the DN for an IP telephone or a wireless IP handset (NetVision), which is listed under
Active DNs reg’d, Inactive DNs reg’d, All DNs reg’d, IP set DNs reg’d, or IP wireless DN’s
reg’d you can deregister that device using the Deregister heading under Configuration on the top
menu. In this case the record will return to the DNs available for reg’n list.
• If you run Deregister on an active device, you will be prompted to confirm that you understand
that the device will be terminated. If you click OK, the device is deregistered immediately.
• If you run Deregister on an inactive device, there will be no prompts, and the action will occur
immediately.
Refer to the IP Telephony Configuration Guide for detailed instructions about installing IP
telephones.

Feature DNs
The system also uses DNs to define remote access features and Hunt groups. These DNs do not
show up on the System DNs list.
• System Access DNs: For remote access to direct-dial lines, the system requires an Auto DN or
a DISA DN. These two settings are found under the Access codes heading. Refer to the remote
access information in “Understanding access codes” on page 309.
• Hunt Group DNs: Hunt Groups are identified by a unique DN for each defined Hunt group.
Refer to Chapter 23, “Configuring Hunt groups,” on page 573 for more information.

Renumbering DNs
Your system auto assigns DNs based on the hardware for digital telephones, or, in the case of IP
telephones, you choose to auto assign DNs when the telephones register to the system. If you need
to change the DN numbers for any reason, there are two ways to do this.
• “Using a wizard to renumber telephone DNs”
• “Change telephone DNs using the Unified Manager”
When you change a DN, the DN record retains the same port number, since the telephone is not
being physically moved. The original DN then assigns to the port vacated by the DN that you
assign as the new DN. If you filled out the DN/Port record in the Programming Records, remember
to change the entries.

P0609326 1.1

Renumbering DNs

367

Using a wizard to renumber telephone DNs
If you need to renumber any DNs, you can use the DN Renumber Wizard, which allows you to
renumber a range of DNs.
Follow these steps to use the DN Renumber Wizard to renumber DNs on your system:
1

From the first page of the Unified Manager, click the Wizards button.

2

Enter your system user ID and password, then click Login.

3

Click the DN Renumber button.

4

On the first screen, enter the range of DNs to change, and the DN with which to start
re-numbering.

5

The Summary page displays the information you entered. Review and revise, if necessary.

6

Click the Apply button.
Warning: DECT DNs
Do not change DECT DNs after the DECT Configuration wizard has run. Doing so will
make the DECT handsets inoperable until you reconfigure the DECT module with the
DECT Wizard and resubscribe the handsets.

Change telephone DNs using the Unified Manager
The General Settings heading also provides access to a screen where you can change the DN
setting.
1

Click on the keys beside Services, Telephony Services.

2

Click on General settings.

3

On the top menu, click on Configuration and choose Change DN.
The Change DN screen appears.

4

Click beside Old DN and enter the DN or group of DNs you want to change.

5

Click beside New DN and enter the DN or group of DNs you want to change to.

6

Click OK to start the change process.
Warning: DECT DNs
Do not change DECT DNs after the DECT Configuration wizard has run. Doing so will
make the DECT handsets inoperable until you reconfigure the DECT module with the
DECT Wizard and resubscribe the handsets.

Business Communications Manager 3.6 Programming Operations Guide

368

Renumbering DNs

P0609326 1.1

369

Chapter 14
Configuring DNs using the Wizards
Wizards are used to make telephone configuration faster and more convenient, especially for sites
where most of the telephones have the same programming. Each record still may require some
adjustments for individual users, but most of the tedious programming can be done using the
Wizards.
The wizards used for the task of configuring telephones are accessed through the Wizards button
on the first page of the Unified Manager. Refer to “Accessing the Wizards” on page 92.
This section describes these wizards and functions:
•
•
•
•
•

“Editing DN Record Templates” on page 369
“Creating telephone records with the Add Users Wizard” on page 375
“Using remote templates” on page 384
“Changing button programming in the wizard” on page 382
“Saving wizard pages on your computer” on page 385

Even when you use a wizard, there may be unique settings that need to be added to DN records.
For details about each DN heading, refer to the information under “Configuring DNs for system
devices” on page 387.
For a general discussion about programming DNs, the DN headings under Telephony Services,
System DNs, and how to work with the DN records, refer to the information under “Configuring
DN records, an overview” on page 353

Editing DN Record Templates
The Edit DN Record Template Wizard allows you to edit templates to define the user settings that
can be used repeatedly to add terminals with the same characteristics. These templates are stored
in a file for use with the Add Users Wizard.
This template assumes you have already set up your lines and line pools, performed any DN
renumbering that may be required, configured your CallPilot Messaging, and added any required
CallPilot Mailbox keycodes that may be applicable. Check your Programming Records for these
settings. If this is not the case, refer to “Configuring lines” on page 227 for lines information and
“DN mapping for digital telephones” on page 355 for information about which DN records are
available for your system. Refer to “Renumbering DNs” on page 366 for details about how to
renumber a group of DNS. Refer to the CallPilot documentation for any CallPilot configuration
that you require.

Business Communications Manager 3.6 Programming Operations Guide

370

Editing DN Record Templates

Refer to “What you need to know to fill out a template” on page 371 for a description of the
information required by this Wizard. You can print out this list and insert the data you want to
enter. If you filled out the telephony programming forms in the Programming Records, use the
information in those forms to configure the templates. After you fill out the information, follow
these steps to run the wizard:
1

From the first page of the Unified Manager, click the Wizards button.

2

When prompted, enter your system user ID and password.

3

Click the Login button.

4

Click the Edit DN Record Template button.

5

Enter the information on these pages. Use the form in What you need to know to fill out a
template on page 371 to ensure you have all the information.
• Page 1: Choose the template you want to edit
• Page 2: Enter the Name of template and the type of telephone
• Page 3: Indicate CallPilot Mailbox information
• Page 4: Define Line access
• Page 5: Determine Capabilities
• Page 6: Determine Call Forward and Hotline settings
• Page 7: Set up User Preferences and determine button configurations

6

The last page, Page 8, provides a summary of the information you entered.
If you need to make changes, use the Back button to return to the pages where the information
was entered and make the corrections, then use the Next button to return to the Summary page.

7

Click the Apply button.

8

To use a template, refer to “Creating telephone records with the Add Users Wizard” on page
375.

P0609326 1.1

Editing DN Record Templates

371

What you need to know to fill out a template
Before you fill out a template, look at the following list and determine what entries you want to
include in the template. Photocopy the list and fill it out for each template you want to create.
Detailed explanations of the fields can be found elsewhere in this chapter.

Remember that some telephones do not allow some of these features or may have specific
configuration requirements. Refer to the relevant sections under “Configuring DNs for
system devices” on page 387.
Table 81 Edit DN Record Template information

Screen 1, Edit Template
•

Do you want to edit an existing template?

(Template  - )

Screen 2, Template Name
•

Find a name that provides a descriptive clue as to what the
template contains.

(Template Name)

•

Do you want this template to be used for a specific model of (Set model)
telephone?
Use the Multiple listing (default) if the template is meant to
apply to more than one type of telephone.

Screen 3, CallPilot Voice Messaging*
*These settings are only for those systems actually running the CallPilot application. Connection to
remote voice mail systems is set under Telco Features and Target lines. Refer also to “Configuring
centralized voice mail” on page 559.
•

Do you want to add a new voicemail mailbox for the set?

No, Yes

If yes . . .
•

Do you want this telephone in the Auto Attendant
directory?

(In directory?): No, Yes

•

How do you want the telephone to dial out to voicemail?
If Pool, you will be prompted to choose a Line pool.
If Line, you will be prompted to choose a line.

Pool, Line, Route, None

Screen 4, Line Assignment
Refer to “Configuring line access” on page 393.
•

Do you want the Prime line for your telephones to be the
intercom button?

(Prime line)
None, Pool (A to O), I/C (intercom),
Line: 

•

How many intercom buttons do you want to assign to the
telephone.

(Intercom Keys)
0 to 8

•

Which line pools do you want this telephone to have access (Pool)
to for outgoing calls?
(enter line pool name) Add

•

Which lines do you want this telephone to have access to?

(Line)
(enter line number)

Add

Business Communications Manager 3.6 Programming Operations Guide

372

Editing DN Record Templates

Table 81 Edit DN Record Template information (Continued)

Screen 5, Capabilities
Refer to “Defining device capabilities” on page 405.
•

Do you want a second call to ring if the telephone is busy?

(DND on busy): No/Yes

•

How do you want the handsfree feature to be activated?

(Handsfree) None/Auto/Standard

•

Do you want to be able to answer a voice call without lifting (HF Answerback) No/Yes
the receiver or pressing the handsfree button on the
telephone?

•

Do you want to include this telephone into a pickup group? (Pickup group) None or Group: 1-9

•

Which Page zone do you want this telephone to be in?

•

Do you want to allow the user of this telephone to access the (Paging) No/Yes
Paging feature?

•

Which telephone, if any, do you want the telephone to dial
when the direct dial number is entered on this telephone?

(Direct dial)
None or Set: 1, 2, 3, 4, 5

•

Do you want the user to be able to use the Priority call
feature?

(Priority Call) No/Yes

•

Do you want an active call to automatically be put on hold
when another call comes in and is picked up?

(Auto hold) No/Yes

•

Do you want lines to this telephone to use an auxiliary
ringer?

(Aux ringer) No/Yes

•

Do you want to allow the line to be redirected?

(Allow redirect) No/Yes

•

Do want redirected lines to ring at this telephone?

(Redirect ring) No/Yes

•

Are you programming an analog telephone or a telephone
attached through an ATA2 device?

(Receive short tones)
No/Yes

(Page zone) None or Zone: 1-6

Screen 6, Call Forward
Refer to “Assigning Call Forward” on page 409.
•

If the call is not answered, where do you want to forward it (Forward no answer to)
to? (i.e. voicemail DN)

•

How long do you want forward to delay on a call that is not (Forward no answer delay)
answered?
2, 3, 4, 6, 10
Note: This field appears after you enter a Forward no
answer to DN.

•

If the telephone is busy, where do you want to forward the
call? (i.e. voicemail DN)

(Forward on busy to)

•

CallPilot Messaging DN (F985)

 (read-only)

P0609326 1.1

Editing DN Record Templates

373

Table 81 Edit DN Record Template information (Continued)

•

Do you want the telephone to have access to a Hotline
number?
Refer to “Assigning a Hotline” on page 411.

(Type) None, Internal/External

If internal . . .
What is the internal number for the hotline?

(Internal #)

If external . . .
What route do you want the telephone to use to access the
external number?

(Facility)
Use prime line, Use routing table
Use 


What is the external number for the hotline?

External #

Screen 7, User Preferences
Note: Not all of these preferences appear for all models of telephones.
Refer to “Defining user preferences” on page 415.
•

What model of telephone are you going to assign using this (Set Model)
template?
Choose Multiple if you want to use the template for
different types of telephones, and you do not plan to
perform any button programming.

•

When do you want calls to be logged at the telephone?
(Call Log Options)
WARNING: Do not choose Log all calls, as this will affect No autologging/No one answered
system speed and function. This setting is used on
Unanswered by me/Log all calls
individual or small groups of telephones for testing
purposes.
If you allow any logging, ensure that the user activates
autobumping (F815) to prevent the log files from filling up
and locking.

•

How do you want the users to be able to dial?

•

Choose the language in which you want the telephone to
(Language)
display the prompts.
These choices depending on which region profile your
system is running. Refer to “Languages” on page 846 for a
list that cross-references regions and supported languages.

•

Choose the level of contrast for your telephone display.
Note: Does not work for portable handsets.

•

Choose how you want your telephone to ring.
(Ring Type)
Note: This ring can be overridden by ring types assigned to 1, 2, 3, 4
lines or hunt groups if the values for lines or hunt groups is
higher than the ring type, or if the ring type for a line was
chosen after you assigned the ring type to the telephone.

(Dialing Options) Automatic dial,
Standard dial, Pre-dial

(Contrast) (1-9)

Business Communications Manager 3.6 Programming Operations Guide

374

Editing DN Record Templates

Table 81 Edit DN Record Template information (Continued)

•

Do you want to determine button settings for the
telephones?
Refer to “Programming telephone buttons” on page 419.

(Perform Button Programming)
No/Yes

If No,
— If Set model is set to Multiple, the button programming for the selected DNs does not
change.
— If Set model on both the Wizard and the system telephone records (DNs) you selected in the
Wizard are the same, there will be no change to existing button programming.
— If Set model on the Wizard and Set model in the DNs on the system are different, the Wizard
will overwrite the button programming for the telephone record with the default settings for
the model specified in the Wizard. The exception to this is if a telephone with a different
model identity is already plugged into the system, in which case the wizard will not change
the button settings for that telephone.
If Yes,
— The button display for the telephone appears. Lines
and intercom buttons will be indicated as read-only
and cannot be changed. Refer to “Changing button
programming in the wizard” on page 382 and
“Default button assignments” on page 422.
— When you apply this template, all current settings
for the specified DNs are overwritten by the wizard
entries.
— For External Autodial numbers and features that
use a dial-out, you will need to know which line,
line pool, route, or prime line the telephone will use
when the number is dialed.

P0609326 1.1

(Button XX)
Blank
Internal Autodial
External Autodial
Feature

Creating telephone records with the Add Users Wizard

375

Creating telephone records with the Add Users Wizard
Use the Add Users Wizard to change the telephony settings for DN records. You can change a
single DN or a group of DNs that require the same settings.
All the DN feature information can be entered when you run this Wizard, or you can indicate a
pre-defined template that automatically sets up the DN features. Refer to “Editing DN Record
Templates” on page 369. If you filled out the telephony forms from the Programming Records,
you can use this information in the wizard if you did not create templates.
If you have a number of Business Communications Manager systems and you want to use the
same templates for all your systems, you can define Edit DN Record templates on one system, and
then use the remote template setting on the first page to access these templates from your remote
systems. Refer to “Using remote templates” on page 384.
To determine what you need to enter for the DNs, refer to “What you need to know about the user”
on page 376. Follow these steps to run the wizard:
1

From the first page of the Unified Manager, click the Wizards button.

2

When prompted, enter your system user ID and password.

3

Click the Add Users button.

4

Proceed through the Wizard and add or change the information, based on what you entered in
“What you need to know about the user” on page 376.
• Page 1: Choose DNs and a local or remote template, of no template.
• Page 2: Enter Name (maximum seven characters). Choose target line assignment.
— Target lines: either enter specific target line numbers for all the DNs, or use Auto
Assign to allow the system to automatically assign sequential target line numbers
• The following pages appear if you do not choose a template name on page 1.
— Page 3: Indicate CallPilot Mailbox information (host system only)
— Page 4: Line access
— Page 5: Determine Capabilities
— Page 6: Determine Call Forward and Hotline settings
— Page 7: Set up User Preferences and determine button configurations

5

The last page provides a summary of the information you chose.
If you need to make changes, use the Back button to navigate to the page where you need to
make changes. Use the Next button to return to the Summary page when you have completed
all your revisions. If you used a template name, you will need to make any changes you
require for the telephone settings on the original template.

6

Click the Apply button.

Business Communications Manager 3.6 Programming Operations Guide

376

Creating telephone records with the Add Users Wizard

7

After you configure the DNs, review each DN record and determine if you need to change any
of the other settings. Refer to the detailed programming sections to identify each field under
each heading.
Note: Not all DN records have the same programming options. For example, ISDN sets do not
have a Button Programming option

What you need to know about the user
Before you fill out the Add Users Wizard, photocopy this list and fill out the information for each
telephone or group of telephones. If you filled out the telephony forms in the Programming
Records, use the information in these forms to answer the questions.
Table 82 Add Users wizard information

Screen 1, Add Users
Refer to “Identifying the telephone (General heading)” on page 391.
•

What type of telephone records are you programming:
Note: Companion and ISDN/DECT DNs have more
limited functionality than Set DNs, therefore, not all the
following pages will appear for these settings.

(DN type)
Set DNs
ISDN and DECT DNs
Companion DNs

•

What type of telephones are you configuring?

(Set model)

•

(Choose one or more DNs)
How many telephones do you want to configure?
Select:
— a single DN
— a range of DNs (hold down  key)
— several DNs scattered across the list
(hold down  key.
Warning: When configuring M7324 telephones, ensure
that you do not choose any DNs that are assigned to BTS
Doorphones, unless the template you choose is for
doorphone configuration.

•

Do you want to use this wizard to define settings or use a (Use settings)
preconfigured template?
Defined in this wizard
From a Local DN Record Template
From a Remote DN Record Template

If from Local DN Record Template . . .
•

Which template do you want to choose?

P0609326 1.1

(Local DN Record Template)
Template  -