Avaya Configuration - Telephony Configuration manual
Avaya Business Communications Manager 6.0
Configuration —Telephony
NN40170-502
Document status: Standard
Document issue:
Document date: October 2010
Product release: 6.0
Job function: Installation
Type: Document
Language type: English
03.03
Copyright © 2010 Avaya Inc.
All Rights Reserved.
Notices
While reasonable efforts have been made to ensure that the information in this documen t is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the informatio n
in this document without the obligation to notify any person or organization of such changes.
Documentation disclaimer
A vaya shall not be responsible for any modifications, additions, or deletions to the original published version of this
documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and
hold harmless Avaya, Avaya’s agents, servants and employees against all claims, lawsuits, demands and judgments arising out
of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End
User.
Link disclaimer
A vaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s)
provided by Avaya. Avaya is not responsible for the accuracy of any information, s tatement or content provided on these sites
and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not
guarantee that these links will work all the time and has no control over the availability of the linked pages.
Warranty
A vaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty.
In addition, A vaya’s standard warranty language, as well as information regarding support for this product, while under warranty,
is available to A vaya customers and other parties through the Avaya Support Web site:
Please note that if you acquired the product from an authorized reseller, the warranty is provided to you by said reseller and not
by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE,
LICENSEINFO/
SOFTWARE, PURCHASED FROM AV AYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AV AY A OR AN AUTHORIZED AVAYA RESELLER.
UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE
SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA
AUTHORIZED RESELLER, AND AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND
ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING
OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE
ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER
REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER"), AGREE TO THESE TERMS AND CONDITIONS
AND CREATE A BINDING CONTRACT BETWEEN YOU AND AV AY A INC. OR THE APPLICABLE AVAYA AFFILIATE
("AVAYA").
Copyright
Except where expressly stated otherwise, no use should be made of the Documentation(s) and Product(s) provided by Avaya. All
content in this documentation(s) and the product(s) provided by A vaya including the selection, arrangement and design of the
content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the
sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit
or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction,
transmission, dissemination, storage, and or use without the express written consent of A vaya ca n be a criminal, as well as a civil
offense under the applicable law.
Third Party Components
Certain software programs or portions thereof included in the Product may contain software distributed under third party
agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the
Product ("Third Party Terms"). Information regarding distributed Linux OS source code (f or those Prod ucts that have distributed
the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that
apply to them is available on the Avaya Support Web site: http://support.avaya.com/Copyright.
Trademarks
The trademarks, logos and service marks ("Marks") displayed in this site, the documentation(s) and product(s) provided by
Avaya ar e the registered or unr egistered Marks of A vaya, its affiliates, or other third parties. Users are not permitted to use such
Marks without prior written consent from Avaya or such third party which may own the M ark. Nothing contained in this site, the
documentation(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in
and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark
of A vaya Inc. All non-Avay a trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support. Web site: http://www.avaya.com/support
Contact Avaya Support
A vaya provides a telephone number for you to use to report problems or to ask questions about your product. The support
telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site:
http://www.avaya.com/support
ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA
http://www.avaya.com/support
HTTP://SUPPORT.AVAYA.COM/
Contents
New in this release 15
Public SIP trunks for VoIP 15
Network Name Display elements 15
Introduction 17
Purpose 17
About Avaya BCM 17
Audience 17
Prerequisites 18
System telephony networking overview 19
Basic system configurations 19
Private network parameters 26
Understanding Avaya Voice Networking (MCDN) network features 35
Networking with ETSI QSIG (international systems only) 40
Private networking with DPNSS (international only) 50
Telephony programming 55
Dialing plan configuration overview 55
Contents
Two basic system telephony configurations 19
DID system 21
Basic telephony routing 23
Tandem calling to a remote PSTN 23
Callers using Avaya BCM 25
Callers in the public network 25
Callers in the private network node 26
Private networking protocols 26
Keycode requirements 27
Remote access to the network 27
Lines used for networking 27
Types of private networks 28
Routing-based networks using T1 E&M lines 29
PRI networking using Call-by-Call services 31
PRI SL-1/Q.Sig/DPNSS and VoIP trunk networking 32
System dialing plans 33
Creating tandem private networks 33
Routing for tandem networks 34
Network Call Redirection Information 36
ISDN Call Connection Limitation 37
Trunk Route Optimization 38
ETSI Euro network services 42
DPNSS 1 services 43
DPNSS 1 capabilities 43
DPNSS 1 features 44
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 3
Contents
Configuration for incoming calls 55
Configuration for incoming call controls 59
Configuration for out-going call traffic 59
Applications Resources overview 61
Applications Resources panel 61
Total Resources 61
Reserved Resources 61
Application Resource Reservations 61
Details for application 61
Types of resources 65
Total and Reserved Resources 65
Setting values for application resources 66
Changes pending 66
IP set resources 67
IP trunk resources 67
Media gateway resources 67
Voice mail and Contact Center resources 67
Fax 67
Conf. Parties 67
Conf. Mixers 67
SIP Trunks 68
Digital Trunks 68
Lines overview 69
Line configuration prerequisites overview 69
System-level line identification 70
Line types 70
Active physical lines 70
Active VoIP lines (requires keycode) 70
Target lines 71
CO trunks as physical lines 72
BRI loops 72
BRI loops configuration 72
Line records 72
Line characteristics 73
Line restrictions 73
Remote restrictions 73
Voice message center 73
Line job aids 73
Line pool configuration 73
Loss packages 74
Privacy on/off by call 75
Line access 75
Line availability and assignment 75
Incoming calls 76
4 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Outgoing calls 76
Telephony resources configuration 77
Telephony Resources table 78
Telephony Resources table 78
Media bay module panels 81
Trunk Module Parameters 81
Call-by-Call Service Selection 86
Port details 88
Provisioning module lines and loops 90
IP telephones 91
IP Terminal Global Settings 91
IP telephone set details 94
IP (VoIP) trunk configuration 97
Introduction to IP trunk configuration 97
Local gateway 98
Remote gateway 98
Options common to all IP trunks 99
Call Routing Summary 99
Call Routing Summary table 99
H323 Routing Mode 99
Private SIP Routing Mode 100
IP trunk settings 100
SIP trunks – options common to public and private SIP trunks 101
Global settings 102
DTMF handling using RFC2833 103
SIP media parameters 104
SIP trunks – public trunk configuration 106
ITSP accounts 106
Account parameters — Basic tab 107
Account parameters — Advanced tab 107
ITSP Association Method 110
User account parameters 112
ITSP templates 114
ITSP Templates — Basic tab 115
ITSP Templates — Advanced tab 115
ITSP Templates — Comments tab 115
Local NAT compensation 116
SIP public route configuration 118
SIP trunks – private trunk configuration 118
SIP private trunk routing table 118
SIP private trunk settings 120
SIP proxy 120
SIP URI map 123
SIP authentication 124
Contents
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 5
Contents
H.323 trunks 127
H.323 routing table 127
H.323 settings 128
H.323 media parameters 132
Line configuration overview 135
Trunk/Line data, main panel 135
Properties 138
Preferences (lines) 141
Restrictions (Line and Remote) 144
Assigned DNs 145
BRI ISDN loop properties overview 147
Loop type and general parameters 148
T-loop gener al settings 149
T-loop SPIDS and network DNs 150
T-loop s D-packet service 151
S-loops assigned DNs 153
BRI T-loops overview 155
Process overview 155
T-loop gener al settings 156
T-loop SPIDS and network DNs 157
T-loop s D-packet service 159
S-loops assigned DNs 160
Router overview 163
ADSL and Ethernet configurations 163
Router features 163
VLAN overview 165
LAN Interfaces 166
Choosing DHCP for VLAN 166
Specifying the site-specific o ptions for VLAN 166
Professional call recording 169
Overview 169
Autonomous recording 169
Call Details 170
Adding a Professional Call Recording Rule 170
Feature dependencies and restrictions 173
Limitations 173
Remote modem 175
Overview 175
Remote modem modules 175
Voice mail modem access 175
CTI server enhancements 176
ModemCC enhancements 176
LAN packet IP capture 177
Output modes 177
6 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Rules for capture 177
Business Element Manager interface options 178
BCM DHCP overview 179
DHCP context for the BCM platform 179
DHCP on BCM 179
Main module DHCP client 180
Main module DHCP server 180
DHCP default configuration 180
BCM50 models without the router 180
BCM50 with integrated router 181
DHCP network scenarios 181
BCM configured as DHCP client is unable to reach external DHCP server 182
BCM using a dynamic address is changed to a static address 182
Changing the default router DHCP configuration 182
DHCP server on BCM50a and BCM50e 182
Main DHCP Server tabs 183
General Settings tab 183
IP Terminal DHCP Options tab 185
Primary Terminal Proxy Server options 185
Secondary Terminal Proxy Server options 185
VLAN options 185
Address Ranges tab 188
Lease Info tab 189
Call security and remote access overview 191
Defining restriction filters 191
Notes about restriction filters 191
Default filters (North America) 193
Default filters (other) 194
Restriction filter examples 194
Remote call-in programming 195
Direct Inward System Access (DISA) creation 196
Remote access line settings 196
Remote access on loop start trunks 197
Remote access on T1 DID and PRI trunks 197
Remote access on DPNSS lines 197
Remote access on a private network 198
Defining remote access packages 198
Defining CoS passwords 198
Notes about CoS passwords 199
External access tones 199
Module management 201
Disabling or enabling a bus or module 201
Disabling or enabling a port channel setting 202
Contents
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 7
Contents
Lines configuration 203
DN addition to a line record 204
Adding a DN to a line record 204
Target lines configuration 204
Configuring target lines 208
PRI lines configuration 210
Configuring PRI lines 212
Configuring call-by-call services and PRI lines 214
T1 E and M lines configuration 215
Configuring T1 E and M lines 219
T1/E1 loop start lines configuration 222
Configuring T1/E1 loop start lines 226
T1-digital ground start configuration 229
Configuring T1-digital ground start lines 232
T1-DID lines configuration 234
Configuring T1-DID lines 237
DASS2 lines configuration 239
Configuring DASS2 lines 242
DPNSS lines configuration 244
Configuring DPNSS lines 247
BRI T-loops configuration 251
Configuring BRI T-loop parameters 251
Configuring provisioned BRI line features 253
BRI S-loops, lines, and ISDN devices programming 257
Setting BRI properties for ISDN device connections 257
Configuring an ISDN telephone DN record 258
Calling line identification configuration 261
CLID configuration for incoming calls 261
Allowing CLID for telephones 261
Setting up alpha-tagging for name display 264
Configuring Network Name Display elements 264
Configuring Business Names 265
Configuring Business Names to telephones 265
Configuring Long Names to telephones 266
CLID configuration for outgoing calls 266
Configuring a business name for outgoing CLID display 267
Displaying the internal name and extension 267
Setting internal CLID display on calling set 267
Configuring Outgoing Call Identification 267
Blocking outgoing name display at the trunk level 268
Blocking outgoing name display at the telephone level 268
Dialing plan configuration: general 271
Carrier codes management 271
Direct dial set configuration 271
8 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Contents
Defining a direct dial set 272
Dialing plan: routing configuration 275
Configuring a route to allow local calls 275
Configuring a route through dedicated trunk 276
Configuring a route for a secondary carrier 277
Configuring multiple routing overflow feature 277
Programming the PRI routing table 279
Configuring a long distance carrier access code into a destination code 279
Private networking 281
Private networking: Fallback configuration over a VoIP MCDN network283
Configuring the Meridian 1 in a BCM network 283
Configuring MCDN functionality for PRI fallback line 285
Private networking: MCDN and ETSI network features configuration287
MCDN network feature configuration 287
Configuring network call redirection information 287
Configuring ISDN call connection limitation 287
Configuring trunk route optimization 288
Configuring trunk anti-tromboning 288
ETSI European network services configuration 288
Configuring MCID and network diversion 289
Silent Record-a-Call configuration 291
Centralized voice mail configuration 293
Host system configuration 293
Configuring the host system to receive central voice mail 293
Satellite system configuration 295
Configuring a satellite system for voice mail 295
Configuring call forward to voice mail 297
Configuring a PRI connection 297
System setup configuration for centralized voice mail 299
Configuring the PRI connection for voice mail 299
Configuring IP trunks 301
Configuration procedures for all IP trunks 301
Configuring IP trunk settings 301
Configuring VoIP line features 301
Configuration procedures for SIP trunks 303
Configuring SIP settings 303
Configuring SIP media parameters 304
Importing an ITSP template 305
Configuring an ITSP account 305
Configuring local NAT compensation 306
Configuring a public SIP route 307
Configuring a private SIP route 308
Configuring a SIP proxy 309
Configuring private SIP settings 310
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 9
Contents
Configuring the SIP URI map 310
Configuring SIP authentication 310
Configuring SIP authentication for a SIP user account 311
Configuration procedures for H.323 trunks 314
Configuring an H.323 route 314
Configuring H.323 settings 315
Configuring H.323 media parameters 316
IP trunk fallback configuration 319
Fallback traffic routes addition 319
Adding a PSTN route to a far-end system 319
Adding a PSTN route to a local PSTN lines 320
Adding the IP route 320
Line pools to routes assignment 321
Assigning PSTN line pools to routes for a far-end system 321
Assigning PSTN line pool to local PSTN lines 321
Assigning the IP line pool 321
Destination code for a fallback route configuration 322
Creating unique destination codes for fallback routes 322
T.38 fax configuration 323
T.38 fax configuration 323
Verifying codecs in Busine ss Element Manager 324
Enabling a T.38 fax 324
T.38 fax restrictions 325
SIP fax over G.711 configuration 327
SIP fax over G.711 configuration 327
Verifying codecs in Busine ss Element Manager 327
Enabling fax on an analog set port 328
Enabling SIP G.711 fax 328
Restriction filters configuration 331
Configuring restriction filters and exceptions 331
Meet Me Conferencing configuration 335
Conference bridges management 336
Viewing the conference bridges table 336
Configuring CoS in the conference bridges table 336
Class of service and system settings for Meet Me Conferencing configuration 337
Configuring COS for Meet Me Conferencing 337
Chairperson settings configuration 340
Setting up a conference bridge for a chair 341
Configuring the chairperson COS 344
Resetting the chairperson’s PIN 344
Removing conference privileges from a chairperson 344
Port Ranges configuration 347
RTP over UDP port ranges management 348
Adding new RTP over UDP port ranges 348
10 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Modifying RTP over UDP port ranges 349
Deleting RTP over UDP port ranges 349
UDP port ranges management 349
Adding new UDP port ranges 349
Modifying UDP port ranges 350
Deleting UDP port ranges 350
Displaying signalling port ranges 350
Class of service password configuration for remote access 351
Adding or modifying class of service password values 351
IP subsystem configuration 353
Configuring general settings 353
Configuring DNS Settings options 354
Procedure steps 354
Configuring the MTU option 354
Procedure steps 354
Viewing the OAM interface 357
Procedure steps 357
Modifying IP configuration 357
Procedure steps 357
Viewing DHCP lease information 358
Procedure steps 358
Static routes configuration 359
Adding a new IP Static Route 359
Modifying an existing IP Static Route 360
Deleting a static route 360
DHCP server configuration on BCM main module 363
Configuring shared DHCP settings 363
Configuring shared DHCP options 365
Adding a new included IP address range 365
Deleting a new included address range 366
Adding a reserved address 367
Deleting a reserved address 367
Configuring the router 369
Accessing the router 369
Configuring flexible DiffServ Code Point 371
Configuring flexible Diff Serv code point 371
Firewall configuration resources 373
Dial-up resources configuration 375
ISDN interface management 375
Adding an ISDN interface 376
Enabling an ISDN interface 376
Disabling an ISDN interface 376
Deleting an ISDN interface 377
ISDN interface connection or disconnection 377
Contents
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 11
Contents
Connecting an ISDN interface 377
Disconnecting an ISDN interface 378
ISDN channel parameters configuration 378
Configuring parameters for an ISDN channel 378
Configuring the ISDN Link Parameters 379
Global settings panel 380
Allowing network access 380
Assigning a Line Pool for ISDN dial out 381
Modem interface management 381
Adding a modem interface 381
Enabling a modem interface 381
Disabling a modem interface 382
Deleting a modem interface 382
Modem interface connection or disconnection 382
Connecting a modem interface 383
Disconnecting a modem interface 383
Modem dial-out link parameters configuration 383
Configuring modem link parameters 383
Configuring the modem IP address specifications 385
Modem dial-in parameters configuration 386
Configuring modem dial-in parameters 386
ISDN dial-in parameters configuration 389
Configuring ISDN dial-in access 389
Configuring the ISDN dial-out IP address 392
Automatic dial-out interface configuration 392
Adding an automatic dial-out interface 393
Disconnecting an automatic dial-out interface 393
Dial-up interfaces as primary connections 394
Assigning remote access privileges to an account 394
Configuring a dial-up interface 395
Static routes for dial-out configuration 395
WAN failover configuration on BCM50 with a router card 395
Assigning a modem interface for WAN failover 396
Assign an ISDN interface for WAN failover 396
Configuring virtual LANs 399
Configure the default gateway IP address 400
Configuring LAN interfaces 400
Adding a VLAN 401
Deleting a VLAN 402
Modifying a VLAN 403
Adding ports to a VLAN 403
Deleting ports from a VLAN 404
Modifying ports on a VLAN 405
Adding static routes 405
12 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Configuring DSCP Marking for Quality of Service 406
Viewing DSCP to Avaya Service Code mapping 407
Viewing Avaya Service Code to P Bit Mapping 407
Configuring Professional Call Recording 409
Adding the recording rule 409
Modifying the recording rule 410
Deleting the recording rule 411
Configuring LAN packet IP capture 413
Starting a capture 413
Stopping a capture 414
Adding a filter 415
Modifying a filter 416
Deleting a filter 417
Configuring output type 418
Configuring the remote modem 419
Configuring the remote modem 419
Silence suppression reference 421
Silence suppression on full-duplex links 423
Comfort noise 425
ISDN reference 427
Welcome to ISDN 427
Analog versus ISDN 427
Types of ISDN service 428
ISDN layers 428
ISDN bearer capability 429
Services and features for ISDN BRI and PRI 429
PRI services and features 429
BRI services and features 430
Service provider features 430
Network name display 431
Name and number blocking (North America only) 432
Call-by-Call Service Selection for PRI-NI2 (North America only) 432
Emergency 911 dialing (North America only) 432
2-way DID 433
Dialing plan and PRI 433
ISDN hardware 434
PRI hardware 434
BRI hardware 434
S Reference Point 434
T Reference Points 435
Clock source for ISDN 436
ISDN BRI NT1 equipment 437
ISDN standards compatibility 437
Planning your ISDN network 437
Contents
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 13
Contents
Ordering ISDN PRI 438
Ordering ISDN PRI service outside of Canada and the United States 438
Ordering ISDN BRI 438
Ordering ISDN BRI service in Canada 438
Ordering ISDN BRI service in the United States 438
Ordering ISDN BRI service outside Canada or the United States 439
Supported ISDN protocols 439
Codec rates reference 441
14 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
New in this release
The following sections detail what’s new in Avaya Business Communications Manager
6.0 Configuration — Telephony (NN40170-502) for Release 6.0.
Navigation
• Public SIP trunks for VoIP (page 15)
• Network Name Display elements (page 15)
Public SIP trunks for VoIP
This feature introduces BCM SIP trunking enhancements to provide interoperability with
public Internet Telephony Service Providers. As part of this enhancement, the Business
Element Manager panels for VoIP have been reorganized to increase ease of use.
This feature impacts the following sections:
• Telephony resources configuration (page 77)
• IP (VoIP) trunk configuration (page 97)
• Configuring IP trunks (page 301)
• IP trunk fallback configuration (page 319)
Network Name Display elements
You can configure the components of the Network Name Display to show both a
Business Name and an associated phone number in the LCD of the IP pho ne. You can
configure a maximum of five Business Names for calling line identification (CLID). A
Business Name can be a maximum of 15 characters in length.
For more information about configuring Network Name Display elements, see
Configuring Network Name Display elements (page 264). For more information about
multiple Business Names and Long Names, see Avaya Business Communications
Manager 6.0 Planning and Engineering (NN40170-200).
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 15
New in this release
16 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Introduction
The information in this chapter applies to both the BCM50 and the BCM450 platforms
running Avaya Business Communications Manager 6.0 (Avaya BCM 6.0).
This guide describes how to configure and assign features, and provide basic
programming for the Avaya BCM. The flowchart below identifies the steps required to
configure your system for inbound and outbound traffic. For more information about
network planning information, planning and configuration prerequisites, and planning
checklists, see Avaya Business Communications Manager 6.0 Planning and
Engineering (NN40170-200).
Purpose
The concepts, operations, and tasks described in this guide relate to the Avaya BCM
software. This guide provides task-based information about how to assign features and
provide basic programming for the Avaya BCM.
Use Business Element Manager , S t artup Profile, and Telset Administration to configure
various Avaya BCM parameters.
In brief, the information in this guide explains:
• global telephony settings
• steps to configure DNs
• product features and how to assign them
About Avaya BCM
The Avaya BCM system provides private network and telephony management
capability to small and medium-sized businesses.
The Avaya BCM system enables you to create and provide telephony applications for
use in a business environment.
Audience
This guide is directed to installers who install, configure, and maintain Avaya BCM
systems. To use this guide, you must
• be an authorized Avaya BCM installer or administrator within your organization
• know basic Avaya BCM terminology
• be knowledgeable about telephony and IP networking technology
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 17
Introduction
Prerequisites
Before you complete the following procedures, review the following prerequisites.
• Ensure all applicable keycodes are purchased and applied.
• Ensure all required MBMs are installed.
• Ensure market profile is selected.
18 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
System telephony networking overview
The information in this chapter applies to both the BCM50 and the BCM450 platforms
running Avaya Business Communications Manager 6.0 (Avaya BCM 6.0).
The system supports both public and private networking for telephony traffic.
• The public network is created by PSTN trunk connections from a Central Office
terminating on a telephone system such as the Avaya BCM 6.0.
• A private network is created when the system is connected through dedicated PSTN
lines or VoIP trunks to other systems. This system can take several forms. At the
simplest level, your system may be behind a private PBX, which connects directly to
the Central Office. A more complicated system may be a node in a network of
systems of various types, where calls not only terminate at t he system, but calls can
need to be passed through the system to oth er nodes unconnected to the originating
node.
Refer to the following information:
• Basic system configurations (page 19)
• Private network parameters (page 26)
Basic system configurations
In the most basic application, your system can provide support for system telephones
to make and receive calls over public network (PSTN) lines.
Two basic system telephony configurations
The following provides a broad overview of the telephony setup for two of the most
common office-telephone configurations.
PBX system
This setup is for larger offices which have fewer CO lines than telephones. In this case
the lines are pooled, and the line pool access is assigned to all DNs. There may also be
a designated attendant with a telephone that has all lines individually assigned.
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 19
System telephony networking overview
PBX system for BCM450
The following figure shows a PBX system for the BCM50.
20 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
PBX system for BCM50
System telephony networking overview
BCM 50
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 DN 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 telephone number.
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, and you use t arget lines to match each
number with a DN.
The following figure shows a DID system for the BCM450.
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 21
System telephony networking overview
DID system for BCM 450
Target line mapped to
DN (4005)
Target line mapped to
DN (4006)
The following figure shows a DID system for BCM50.
DID system for BCM 50
Target line mapped to
DN (4007)
Target line mapped to
DN (4005)
Target line mapped to
DN (4006)
Target line mapped to
DN (4008)
CO DID line
i.e. 769
with range of call
numbers (4005 to
4020)
Target line mapped to
DN (4007)
Target line mapped to
DN (4008)
22 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Incoming calls
1 DID trunks are assigned to be auto-answer.
Attention: PRI lines are automatically set to auto-answer.
2 All DNs 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 maps the call on the target line
assigned to the matching received digits.
5 The DN assigned to that target line rings.
Y ou can assign unanswered or busy telephones to Call Forward to another DN, such as
a designated attendant or a voice-mail system.
Basic telephony routing
In a basic configuration, simple access codes (for example Line Pool Codes) are used
to access the PSTN network.
In a more complex configuration, more advanced destination codes are required to
access multiple PSTNs, private network resources, and remote nodes. Access to these
resources enables advanced features, such as tandem routing.
System telephony networking overview
Tandem calling to a remote PSTN
A system connected to a private network that uses dedicated circuits or VoIP circuits
can allow a user to dial directly to many other users, on different nodes, using a
coordinating dialing plan.
Using a private network saves on toll charges, and local charges, as fewer PSTN
accesses are required for internal and external calling. Several nodes located on one
site initiate their external local calls to a centralized Avaya BCM having a T1 or E1
termination to the PSTN. This type of configuration avoids multiple PSTN terminations
at other local nodes.
The same tandeming concepts can be applied to inbound calls. DID numbers dialed
from the PSTN can be processed and tandem routed out of the centralized system to
the localized remote nodes. For more information see, Creating tandem private
networks (page 33).
The following figure shows three types of callers. Each type of caller has a specific
method of accessing the other two BCM450 systems.
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 23
System telephony networking overview
Tandem dialing through a BCM450 to/from a private network
T1 E&M
PRI SL1
VoIP
T1/E1 lines
Analog lines
PRI/BRI lines
The following figure shows three types of callers. Each type of caller has a specific
method of accessing the other two BCM50 systems.
24 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Tandem dialing through a BCM50 to/from a private network
System telephony networking overview
Callers using Avaya BCM
These callers can
• call directly to a specific telephone
• select an outgoing line to access a private network
T1 E&M
PRI SL1
VoIP
T1/E1 lines
Analog lines
PRI/BRI lines
• select an outgoing line to access features that are available on the private network
• select an outgoing central office line to access the public network
• use all of the Avaya BCM features
Callers in the public network
These callers use the public lines to
• call directly to one or more Avaya BCM DNs
• call into Avaya BCM and select an outgoing TIE line to access a private network
• call into Avaya BCM and select an outgoing central office line to access the public
network
• call into Avaya BCM and use remote features
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 25
System telephony networking overview
Callers in the private network node
These callers use the private lines to
• call directly to one or more Avaya BCM DNs
• call into Avaya BCM and select an outgoing TIE line to access other nodes in a
private network
• call into Avaya BCM and select an outgoing central office line to access the public
network
• call into Avaya BCM and use remote features
System numbering and dialing plans
All systems on a private network must coordinate dialing plans, to ensure that calls get
directed to the correct network node. As well, routing becomes more complex,
especially if the system is not an end node and must be configured to relay calls to
nodes not directly connected to the system. The type of dialing plan supported by the
network determines whether each node also requires unique DNs.
Private network parameters
The following sections provide an overview of the system values that affect private
networking.
• Private networking protocols (page 26)
• Keycode requirements (page 27)
• Remote access to the network (page 27)
• Lines used for networking (page 27)
• Types of private networks (page 28)
Private networking protocols
The Avaya BCM supports the following protocols for private networking:
• PRI: ETSI QSIG, Avaya Voice Networking (MCDN)
•DPNSS
• BRI: ETSI QSIG
• T1: E&M
• VoIP trunks (with optional MDCN)
Attention: For the DTM-PRI configuration protocol, MCDN is referred to as SL-1 in
Business Element Manager.
26 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
BCM systems can be networked together using T -1, PRI or V oIP trunks. PRI SL-1 lines
and VoIP trunks also offer the opportunity to use the MCDN protocol, which provides
enhanced trunking features and end-to-end user identification. If a Meridian 1 is part of
the MCDN network, the network can also provide centralized voice mail and auto
attendant off the Meridian.
Attention: MCDN networking requires all nodes on the network to use a common
Universal Dialing Plan (UDP) or a Coordinated Dialing Plan (CDP).
Keycode requirements
Keycodes are required to activate the protocols that are used to create private
networking, includi ng:
• VoIP Gateway keycodes
• an MCDN, DPNSS, or Q. Sig keycode, if you want to use a networking protocol
between the systems
You must purchase and install these keycodes before you can create any of the
networks described in this chapter. Consult with your Avaya distributor to ensure you
order the correct keycodes for the type of network you want to create.
System telephony networking overview
Remote access to the network
Authorized users can access TIE lines, central office lines, and features from outside
the system. Remote users accessing a private network configured over a large
geographical area can avoid toll charges.
Attention: You cannot program a DISA DN or Auto DN to a VoIP trunk, as they act as
auto-answer trunks from one private network to the n ext. Howe ver, you can configure
VoIP line pools with remo te access packages so that callers can access telepho nes or
the local PSTN on remote nodes on a tandemed network that use V oIP trunks between
systems.
Lines used for networking
External (trunk) lines provide the physical connection between Avaya BCM and other
systems in a private or public network.
The BCM50 numbers physical lines from 061 to 124. Default numbering depends on the
type and connection to the BCM50 (EXP1 - EXP2)
VoIP trunks: Although a VoIP gateway does not use physical lines, it is easier to think
of them that way . BCM450 support s a dynamically configurable number of IP trunk line
numbers, from 0 to 130. In the BCM50, lines 001 to 012 are used for VoIP trunk
functionality.
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 27
System telephony networking overview
Avaya BCM networking configurations that use PRI and T1 lines, requ ire specific DTM
modules.
• DTMs configured for PRI are used for incoming and outgoing calls (two-way DID).
Incoming calls are routed directly to a BCM DN that has a properly configured and
assigned target line. All outgoing calls made through PRI, are initiated using the
destination codes.
• DTMs configured for T1/E1 can have digital lines configured as Groundstart, E&M,
Loop, or DID.
Target lines are virtual communication paths between trunks and telephones on the
BCM system. They are incoming lines only , and cannot be selected for outgoing calls or
networking applications. With target lines, you can concentrate incoming calls on fewer
trunks. This type of concentration is an advant age of DID lines. Avaya BCM t arget lines
allow you to direct each DID number to one or more telephones. VoIP trunks also
require target lines to direct incoming traffic.
In BCM450, there is a maximum of 639 target lines. In BCM 50, there is a maximu m of
208 target lines.
Telephones can be configured to have an appearance of analog lines or multiple
appearances of target lines.
Attention: PRI B-channels cannot be assigned as line appearances. PRI B-channels,
or “trunks”, can only be configured into PRI line pools for inbound routing through target
lines with receive digits or outbound routing through destination codes.
Types of private networks
There are several ways you can create private networks. Configuration can be based
on such things as cost of trunks, proximity of network nodes, size of the private network,
and business requirements for communications.
VoIP-based networking also requires an understanding of IP features such as codecs,
jitter buffers, Quality of Service (QoS) function, and silence compression.
The services provided within networks is based on the type of trunks and the protocols
assigned to the trunks. All trunks within the network should be running the same
protocols, to provide a technically sound and stable network.
The following links are procedures to set up basic networks to advanced networks, using
the support protocols within Avaya BCM:
• Routing-based networks using T1 E&M lines (page 29)
• PRI networking using Call-by-Call services (page 31)
• PRI SL-1/Q.Sig/DPNSS and VoIP trunk networking (page 32)
28 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Routing-based networks using T1 E&M lines
By properly planning and programming routing tables and destination codes, an installer
can create a dialing plan where T1 E&M lines between BCM systems are available to
other systems in the network.
The following figure shows a network of three Avaya BCM450 systems. Two remote
systems connect to a central system.
Dialing plan for T1 E&M routing network of BCM450s
System telephony networking overview
The following figure shows a network of three BCM50 systems. Two remote systems
connect to a central system.
NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010 29
System telephony networking overview
Dialing plan for T1 E&M routing network of BCM50s
Each system must be running Avaya BCM software. Each system must be equipped
with target lines and a DTM with at least one T1 E&M line.
The call appears on the auto answer line on the Avaya BCM in Santa Clara as 6-221.
Because 6 is programmed as a destination code for Toronto on the Santa Clara system,
another call is placed using route 002 from Santa Clara to Toronto. At the Toronto
system, the digits 6-221 are interpreted as a target line Private received number. The
call now alerts at DN 6221 in Toronto.
Attention: Network calls that use routes are subject to any restriction filters in effect.
If the telephone used to make a network call has an a ppearance of a line used by the
route, the call will move from the intercom button to the Line button. The telephone
used to make a network call must have access to the line pool used by the route.
Network calls are external calls, even though they are dialed as if they were internal
calls. Only the features and capabilities available to external calls can be used.When
programming a button to dial a Network number automatically (autodial), network calls
must be treated as external numbers, even though they resemble internal telephone
numbers. Routes generally define the path between your Avaya BCM switch and
another switch in your network, not other individual telephones on that switch.
30 NN40170-502 Avaya Business Communications Manager 6.0 Configuration —Telephony May 2010
Loading...