Avaya Implementing B5800 Branch Gateway User Manual
Implementing the Avaya B5800 Branch
Gateway
Release 6.1
18-603853
November 2011
Issue 5
©
2011 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the
information in this document 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 information in this
document without the obligation to notify any person or organization of
such changes.
Documentation disclaimer
“Documentation” means information published by Avaya in varying
mediums which may include product information, operating instructions
and performance specifications that Avaya generally makes available
to users of its products. Documentation does not include marketing
materials. Avaya shall not be responsible for any modifications,
additions, or deletions to the original published version of
documentation unless such modifications, additions, or deletions were
performed by Avaya. End User agrees 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
Avaya is not responsible for the contents or reliability of any linked Web
sites referenced within this site or documentation provided by Avaya.
Avaya is not responsible for the accuracy of any information, statement
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
Avaya provides a limited warranty on its Hardware and Software
(“Product(s)”). Refer to your sales agreement to establish the terms of
the limited warranty. In addition, Avaya’s standard warranty language,
as well as information regarding support for this Product while under
warranty is available to Avaya customers and other parties through the
Avaya Support Web site:
you acquired the Product(s) from an authorized Avaya reseller outside
of the United States and Canada, the warranty is provided to you by
said Avaya reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE,
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA 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 A V A Y A, AN A V A Y A AFFILIA TE OR AN
AVAYA AUTHORIZED RESELLER; 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 INTERCHANGEABL Y AS “YOU” AND “END USER”),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
Avaya grants End User a license within the scope of the license types
described below. The applicable number of licenses and units of
capacity for which the license is granted will be one (1), unless a
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE
http://support.avaya.com. Please note that if
different number of licenses or units of capacity is specified in the
Documentation or other materials available to End User. “Designated
Processor” means a single stand-alone computing device. “Server”
means a Designated Processor that hosts a software application to be
accessed by multiple users. “Software” means the computer programs
in object code, originally licensed by Avaya and ultimately utilized by
End User, whether as stand-alone Products or pre-installed on
Hardware. “Hardware” means the standard hardware originally sold by
Avaya and ultimately utilized by End User.
License types
Designated System(s) License (DS). End User may install and use
each copy of the Software on only one Designated Processor, unless
a different number of Designated Processors is indicated in the
Documentation or other materials available to End User. Avaya may
require the Designated Processor(s) to be identified by type, serial
number, feature key, location or other specific designation, or to be
provided by End User to Avaya through electronic means established
by Avaya specifically for this purpose.
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, or Hardware
provided by Avaya. All content on this site, the documentation and the
Product provided by Avaya 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 unless expressly authorized by Avaya. Unauthorized
reproduction, transmission, dissemination, storage, and or use without
the express written consent of Avaya can 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 (for those
Products 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 A vaya Support
Web site:
Preventing Toll Fraud
“T oll fraud” is the unauthorized use of your telecommunications system
by an unauthorized party (for example, a person who is not a corporate
employee, agent, subcontractor, or is not working on your company's
behalf). Be aware that there can be a risk of Toll Fraud associated with
your system and that, if Toll Fraud occurs, it can result in substantial
additional charges for your telecommunications services.
Avaya Toll Fraud Intervention
If you suspect that you are being victimized by T oll Fraud and you need
technical assistance or support, call Technical Service Center Toll
Fraud Intervention Hotline at +1-800-643-2353 for the United States
and Canada. For additional support telephone numbers, see the Avaya
Support Web site:
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to: securityalerts@avaya.com.
Trademarks
Avaya is a registered trademark of Avaya Inc.
Aura is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners,
and “Linux” is a registered trademark of Linus Torvalds.
http://support.avaya.com/Copyright.
http://support.avaya.com. Suspected security
2 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation and Product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, 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 Mark.
Nothing contained in this site, the Documentation 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.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support Web site:
Contact Avaya Support
Avaya 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 W eb site:
http://support.avaya.com.
http://support.avaya.com.
Implementing the Avaya B5800 Branch Gateway November 2011 3
4 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Contents
Chapter 1: Overview...........................................................................................................
Branch user deployment models..............................................................................................................
Centralized solution...................................................................................................................................
PSTN trunking configurations...................................................................................................................
Voicemail support options.........................................................................................................................
Centralized management..........................................................................................................................
Licensing...................................................................................................................................................
System components..................................................................................................................................
Supported telephones...............................................................................................................................
Software applications................................................................................................................................
Supported country locales........................................................................................................................
Training.....................................................................................................................................................
Web sites..................................................................................................................................................
Documentation..........................................................................................................................................
Revision history.........................................................................................................................................
Chapter 2: Planning............................................................................................................
Prerequisites.............................................................................................................................................
Dial plan considerations............................................................................................................................
Dial plan example......................................................................................................................................
Voicemail considerations...........................................................................................................................
Branch PSTN call routing considerations.................................................................................................
B5800 Branch Gateway configuration methods........................................................................................
Network assessment for VoIP requirements.............................................................................................
Chapter 3: Installation requirements.................................................................................
Power supply backup (UPS).....................................................................................................................
Cables.......................................................................................................................................................
Grounding.................................................................................................................................................
Wall and rack mounting.............................................................................................................................
Voice compression channels....................................................................................................................
Emergency and power failure ports..........................................................................................................
Environmental requirements.....................................................................................................................
Space requirements..................................................................................................................................
Control unit.......................................................................................................................................
External expansion modules............................................................................................................
Wall mounting space requirements..................................................................................................
Rack space requirements.................................................................................................................
Chapter 4: Hardware and software installation................................................................
Installation checklist..................................................................................................................................
Tools and equipment required...................................................................................................................
Unpacking equipment...............................................................................................................................
SD card preparation..................................................................................................................................
Upgrading the card firmware............................................................................................................
Creating a configuration file..............................................................................................................
Adding a configuration file................................................................................................................
13
13
14
14
15
15
16
18
21
23
24
26
27
27
28
29
29
30
30
31
32
32
34
35
35
36
38
38
38
40
41
42
42
43
44
44
47
47
48
49
50
50
51
52
Implementing the Avaya B5800 Branch Gateway November 2011 5
Adding music-on-hold files...............................................................................................................
9600 series phones screen saver file...............................................................................................
Base and trunk card installation................................................................................................................
Trunk daughter card preparation......................................................................................................
Legacy carrier card preparation.......................................................................................................
Base card insertion...........................................................................................................................
Wall mounting...........................................................................................................................................
Rack mounting..........................................................................................................................................
External expansion modules.....................................................................................................................
Connecting external expansion modules.........................................................................................
Grounding.................................................................................................................................................
Out-of-building connections/lightning protection.......................................................................................
DS phone IROB installation..............................................................................................................
Analog phone barrier boxes.............................................................................................................
Rack mounting barrier boxes...........................................................................................................
Administration software suite....................................................................................................................
PC requirements..............................................................................................................................
Installing the administration applications..........................................................................................
Installer PC connection.............................................................................................................................
Connecting the PC directly to the control unit..................................................................................
Applying power to the system...................................................................................................................
Control unit LEDs startup sequence.................................................................................................
About the LEDs................................................................................................................................
Starting Manager.......................................................................................................................................
Default configuration.................................................................................................................................
Changing the IP address settings.............................................................................................................
Connecting the control unit to the network................................................................................................
Default passwords.....................................................................................................................................
Changing the security settings.........................................................................................................
Changing the remote user password...............................................................................................
Connecting phones...................................................................................................................................
96x1 phones SIP firmware download in B5800 Branch Gateway centralized branch deployments.........
B5800 Branch Gateway support for SIP phone firmware download................................................
Enabling the DHCP server on the B5800 Branch Gateway.............................................................
About using external DHCP servers.................................................................................................
Loading the SIP phone firmware to the B5800 Branch Gateway SD card.......................................
Loading the SIP phone configuration file to the B5800 Branch Gateway SD card...........................
About rebooting the phones.............................................................................................................
Chapter 5: Administration software suite.........................................................................
Starting System Status..............................................................................................................................
Starting System Monitor............................................................................................................................
Chapter 6: Initial configuration for a Centralized Branch...............................................
Centralized Branch configuration checklist...............................................................................................
Activating license files...............................................................................................................................
Using Manager to deliver license files to the branches....................................................................
Using Provisioning and Installation Manager to deliver license files to the branches......................
Creating a mapping file....................................................................................................................
52
53
53
54
55
57
59
61
63
64
65
66
68
69
70
71
72
72
73
74
75
76
76
78
79
81
82
82
82
83
84
84
85
85
85
86
86
87
91
91
92
95
96
98
99
100
102
6 Implementing the Avaya B5800 Branch Gateway November 2011
Disabling the Network Management administration feature for the branch..............................................
Disabling unused trunks............................................................................................................................
Digital trunk clock source..........................................................................................................................
Setting a trunk clock quality setting..................................................................................................
Setting the trunk prefixes..........................................................................................................................
SIP trunk prefixes.............................................................................................................................
Administering a Session Manager line for each branch............................................................................
Enabling SIP trunk support...............................................................................................................
Setting the branch prefix and local number length for extension numbering...................................
Changing the default codec selection..............................................................................................
Changing the maximum SIP sessions..............................................................................................
Adding an Avaya Aura® Session Manager line................................................................................
Avaya Aura® Session Manager line redundancy.............................................................................
Setting up outgoing call routing........................................................................................................
How the B5800 Branch Gateway uses a configured Session Manager line....................................
Chapter 7: Initial configuration for a Distributed Branch................................................
Distributed Branch configuration checklist................................................................................................
Activating license files...............................................................................................................................
Using Manager to deliver license files to the branches....................................................................
Using Provisioning and Installation Manager to deliver license files to the branches......................
Creating a mapping file....................................................................................................................
Disabling the Network Management administration feature for the branch..............................................
Disabling unused trunks............................................................................................................................
Digital trunk clock source..........................................................................................................................
Setting a trunk clock quality setting..................................................................................................
Setting the trunk prefixes..........................................................................................................................
SIP trunk prefixes.............................................................................................................................
Administering a Session Manager line for each branch............................................................................
Enabling SIP trunk support...............................................................................................................
Setting the branch prefix and local number length for extension numbering...................................
Changing the default codec selection..............................................................................................
Changing the maximum SIP sessions..............................................................................................
Adding an Avaya Aura® Session Manager line................................................................................
Setting up outgoing call routing........................................................................................................
How the B5800 Branch Gateway uses a configured Session Manager line....................................
Chapter 8: Session Manager Configuration.....................................................................
Session Manager 6.1................................................................................................................................
Viewing the SIP domains..................................................................................................................
Creating locations.............................................................................................................................
Creating adaptations........................................................................................................................
Creating SIP entities.........................................................................................................................
Creating entity links..........................................................................................................................
Creating time ranges........................................................................................................................
Creating routing policies...................................................................................................................
Creating dial patterns.......................................................................................................................
Session Manager 6.0................................................................................................................................
Viewing the SIP domains..................................................................................................................
103
104
105
106
106
107
108
109
110
112
113
114
118
120
121
123
123
125
126
127
129
130
131
132
133
134
134
136
136
137
139
140
141
145
147
149
149
150
150
151
151
152
153
153
154
155
156
Implementing the Avaya B5800 Branch Gateway November 2011 7
Creating locations.............................................................................................................................
Creating adaptations........................................................................................................................
Creating SIP entities.........................................................................................................................
Creating entity links..........................................................................................................................
Creating time ranges........................................................................................................................
Creating routing policies...................................................................................................................
Creating dial patterns.......................................................................................................................
Creating a System Manager link to Network Management.......................................................................
Chapter 9: Voicemail operation.........................................................................................
Configuring Modular Messaging...............................................................................................................
Modular Messaging PSTN Fallback..........................................................................................................
Adding an overriding short code.......................................................................................................
Embedded Voicemail for auto attendants and announcements................................................................
Creating an auto attendant...............................................................................................................
Recording prompts...........................................................................................................................
Recording announcements..............................................................................................................
Transferring recordings to the system SD card................................................................................
Chapter 10: Extension administration..............................................................................
Native extensions......................................................................................................................................
Native extension configuration checklist..........................................................................................
Enabling branch SIP extension support...........................................................................................
Adding extensions and users to the B5800 Branch Gateway..........................................................
Survivable extensions...............................................................................................................................
Survivable extension configuration checklist....................................................................................
Survivability operation......................................................................................................................
Internal calls.....................................................................................................................................
Session Manager 6.1 configuration required for survivable extension support................................
Session Manager 6.0 configuration required for survivable extension support................................
Enabling branch SIP extension support...........................................................................................
Adding SIP extensions and users to the B5800 Branch Gateway...................................................
Survivability settings.........................................................................................................................
Using the group parameters.............................................................................................................
SIP controller monitoring..................................................................................................................
9600 extension operation.................................................................................................................
Chapter 11: Managing license files with PLDS.................................................................
Overview...................................................................................................................................................
Registering for PLDS................................................................................................................................
About license activation............................................................................................................................
Activating license entitlements.........................................................................................................
Searching for license entitlements............................................................................................................
Regenerate License files..........................................................................................................................
Regenerating a license file...............................................................................................................
Chapter 12: Standalone SAL Gateway for remote service..............................................
Use of SAL to access the B5800 Branch Gateway management tools and Network Management
applications...............................................................................................................................................
SAL Gateway installation and registration................................................................................................
B5800 Branch Gateway registration and SAL Gateway on-boarding.......................................................
156
157
157
158
159
159
160
161
163
164
165
165
167
167
170
170
171
173
173
173
174
176
181
182
182
183
185
188
192
194
198
201
202
204
207
207
208
208
209
210
212
212
215
215
216
217
8 Implementing the Avaya B5800 Branch Gateway November 2011
B5800 Branch Gateway SAL-based alarming..........................................................................................
Universal Install/SAL Registration Request Form.....................................................................................
Chapter 13: Additional installation and system procedures..........................................
System shutdown......................................................................................................................................
Shutting down the system using Manager.......................................................................................
Shutting down the system using the System Status application......................................................
Shutting down the system using a system phone............................................................................
Shutting down the system using the AUX button.............................................................................
Rebooting the system...............................................................................................................................
About changing components....................................................................................................................
Replacing a component with one of the same type..........................................................................
Replacing a component with one of higher capacity........................................................................
Replacing a component with one of lower capacity.........................................................................
Replacing a component with one of a different type.........................................................................
Adding a new component.................................................................................................................
Permanently removing a component................................................................................................
Swapping extension users........................................................................................................................
About changing extension numbers..........................................................................................................
Renumbering all extensions and users............................................................................................
Changing a user's extension number...............................................................................................
B5800 Branch Gateway software upgrade...............................................................................................
Creating a backup of the system configuration................................................................................
Using the upgrade wizard.................................................................................................................
External output port (EXT O/P).................................................................................................................
EXT O/P connections.......................................................................................................................
Example of BRI So8 module configuration...............................................................................................
Example 1: ISDN terminal................................................................................................................
Example 2: video conference...........................................................................................................
SNMP........................................................................................................................................................
Installing the B5800 Branch Gateway MIB files...............................................................................
Enabling SNMP and polling support.................................................................................................
Enabling SNMP trap sending...........................................................................................................
DTE port maintenance..............................................................................................................................
RS232 DTE port settings..................................................................................................................
About erasing the configuration........................................................................................................
Resetting the security settings to the default settings......................................................................
Resetting the configuration and security settings to the default settings via the boot loader...........
About erasing the operational firmware............................................................................................
Reset button..............................................................................................................................................
AUX button................................................................................................................................................
Creating a WAN link..................................................................................................................................
Chapter 14: SD card management.....................................................................................
Booting from the SD cards........................................................................................................................
About creating an B5800 Branch Gateway SD card.................................................................................
Formatting an SD card.....................................................................................................................
Formatting a System SD card using the System Status application................................................
Recreating an SD card.....................................................................................................................
217
218
219
219
220
220
221
221
221
222
222
223
224
224
225
225
226
226
227
227
228
229
230
231
232
233
233
234
236
237
240
241
242
242
243
246
246
247
250
251
251
253
256
257
258
258
259
Implementing the Avaya B5800 Branch Gateway November 2011 9
Viewing the card contents.........................................................................................................................
About backing up the System SD card.....................................................................................................
Backing up the primary folder using Manager..................................................................................
Backing up the primary folder using the System Status application.................................................
Backing up the primary folder using a system phone.......................................................................
About restoring from the backup folder.....................................................................................................
Restoring from the backup folder using Manager............................................................................
Restoring from the backup folder using the System Status application...........................................
Restoring from the backup folder using a system phone.................................................................
About backing up to the Optional SD card................................................................................................
Backing up to the Optional SD card using Manager........................................................................
Backing up to the Optional SD card using the System Status application.......................................
Backing up to the Optional SD card using a system phone.............................................................
About restoring from the Optional SD card...............................................................................................
Restoring a configuration file from the Optional SD card using Manager........................................
Restoring a configuration file from the Optional SD card using a system phone.............................
Restoring software files from the Optional SD card using Manager.................................................
Restoring software files from the Optional SD card using a system phone.....................................
System upgrade using the System SD card.............................................................................................
Upgrading remotely using Manager.................................................................................................
Upgrading the SD card locally..........................................................................................................
Upgrading using an Optional SD card..............................................................................................
Memory card removal...............................................................................................................................
Shutting down a memory card using Manager.................................................................................
Shutting down a memory card using a system phone......................................................................
Shutting down a memory card using System Status........................................................................
Card startup..............................................................................................................................................
Starting up a card using Manager....................................................................................................
Starting up a card using the System Status application...................................................................
Starting up a card using a system phone.........................................................................................
Chapter 15: Safety and regulatory information................................................................
Safety statements.....................................................................................................................................
Important safety instructions when using your telephone equipment...............................................
Lithium batteries...............................................................................................................................
Lightening protection/hazard symbols..............................................................................................
Trunk interface modules...................................................................................................................
Port safety classification...................................................................................................................
EMC cautions...................................................................................................................................
Regulatory Instructions for Use.................................................................................................................
Australia...........................................................................................................................................
Canada.............................................................................................................................................
China................................................................................................................................................
European Union...............................................................................................................................
New Zealand....................................................................................................................................
FCC notification................................................................................................................................
Compliance with FCC rules..............................................................................................................
Appendix A: Centralized deployment example call flows...............................................
260
260
260
261
261
262
262
262
263
263
264
264
264
265
265
266
266
267
267
268
269
269
270
271
271
272
272
272
273
273
275
275
275
276
276
277
277
278
279
279
280
281
282
282
282
284
287
10 Implementing the Avaya B5800 Branch Gateway November 2011
Routing concepts......................................................................................................................................
Call flows...................................................................................................................................................
Sunny day.................................................................................................................................................
Rainy day..................................................................................................................................................
Appendix B: Avaya port matrix for B5800 Branch Gateway and SIP phones...............
What are ports and how are they used?...................................................................................................
Port type ranges........................................................................................................................................
Sockets.....................................................................................................................................................
Firewall types............................................................................................................................................
Firewall policies.........................................................................................................................................
TFTP port usage.......................................................................................................................................
Ingress ports for B5800 Branch Gateway and SIP phones......................................................................
Egress ports for B5800 Branch Gateway and SIP phones.......................................................................
Table column heading definitions..............................................................................................................
Port usage diagram...................................................................................................................................
Appendix C: B5800 Branch Gateway call flows...............................................................
Appendix D: PSTN example call flow................................................................................
Communication Manager configuration required for survivable extension support..................................
Verifying Communication Manager licenses.............................................................................................
Configuring trunk-to-trunk transfer............................................................................................................
Configuring IP node names......................................................................................................................
Configuring IP codec set...........................................................................................................................
Configuring IP network regions.................................................................................................................
SIP signaling group and trunk group.........................................................................................................
Configuring SIP signaling groups..............................................................................................................
Configuring SIP trunk groups....................................................................................................................
Configuring route patterns........................................................................................................................
Configuring private numbering..................................................................................................................
Configuring AAR.......................................................................................................................................
ARS Access Code.....................................................................................................................................
Location specific ARS digit analysis.........................................................................................................
Global ARS Digit Analysis.........................................................................................................................
Appendix E: Branch PSTN call routing examples...........................................................
Centralized call control..............................................................................................................................
Routing B5800 Branch Gateway calls..............................................................................................
Branch PSTN override..............................................................................................................................
Adding an overriding short code.......................................................................................................
PSTN trunk fallback..................................................................................................................................
Configuring PSTN trunk fallback......................................................................................................
Appendix F: Recommended courses for Avaya B5800 Branch Gateway training........
Avaya B5800 Branch Gateway.................................................................................................................
Unified Communications...........................................................................................................................
Glossary...............................................................................................................................
287
287
289
292
297
297
297
298
299
300
300
301
303
305
307
309
313
314
314
315
315
315
316
317
317
319
320
320
321
321
322
322
325
325
326
328
328
330
331
335
335
336
339
Implementing the Avaya B5800 Branch Gateway November 2011 11
12 Implementing the Avaya B5800 Branch Gateway November 2011
Chapter 1: Overview
The Avaya B5800 Branch Gateway is a single-platform solution with multiple deployment options that
enable seamless, user-centric access to Avaya Aura® Messaging, Avaya Aura® Conferencing, Avaya
Aura® Presence services and much more. It's complimentary to any existing networking solution, adding
communications and collaboration functionality in a “thin” device designed for branch use. Supporting
either distributed, centralized, or mixed network deployments, the B5800 Branch Gateway is adaptable
to meet the needs of specific features and applications of individual employees in each branch location.
The result is a smooth migration between architectures. In addition to centralized SIP endpoints, the B5800
Branch Gateway can concurrently support other IP and TDM endpoints for a community of centralized
and distributed users on the same platform. Ideal for customers wanting applications deployed in customer
data centers and/or in the branch itself, the B5800 Branch Gateway enables the branch to cost effectively
deliver the range of communication tools without complex infrastructure and administration.
Branch user deployment models
B5800 Branch Gateway can be deployed in the Distributed, Centralized or Mixed Branch user
models.
• Distributed Branch user model — In this model, call processing for the branch phones
is provided locally. Non-IP phones are connected to B5800 Branch Gateway and IP and
SIP video endpoints are administered with B5800 Branch Gateway as their controller.
Access to and from the rest of the A vaya Aura® network is via the B5800 Branch Gateway
system's A vaya Aura® Session Manager link across the enterprise WAN. This connection
allows for VoIP connectivity to other B5800 Branch Gateway systems, to centralized
trunking and to centralized applications such as conferencing and Modular Messaging.
• Centralized Branch user model — Certain 9600 A vaya SIP phones can use the B5800
Branch Gateway as a survivability gateway (see
more information). In normal operation, these phones register directly to the Avaya
Aura®Session Manager in the enterprise core and get services from core applications
such as the Communication Manager Feature Server. The local B5800 Branch Gateway
can still be accessed as a SIP gateway connected to the core Avaya Aura®Session
Manager to provide access to local PSTN trunks and services when required. If WAN
connectivity to the Avaya Aura®Session Manager is lost, the SIP phones automatically
register with and get services from the B5800 Branch Gateway. When connection to the
Avaya Aura®Session Manager is available again, failback occurs where the SIP phones
return to being controlled by Avaya Aura® Session Manager.
• Mixed Branch user model — Each B5800 Branch Gateway system can support
extensions using the Centralized Branch user model and extensions using the Distributed
Supported telephones on page 21 for
Implementing the Avaya B5800 Branch Gateway November 2011 13
Overview
Branch user model at the same time. The extensions supported in the Centralized Branch
user model are SIP extensions only.
Centralized solution
The B5800 Branch Gateway can be deployed as a Distributed branch, a Centralized branch,
or a Mixed branch. Both Distributed and Centralized branches can benefit from centralization.
In Distributed branch deployments, the option to leverage centralized PSTN trunking and
centralized applications such as voice mail and conferencing is provided. In Centralized branch
deployments, in addition to the above, phone registration and call processing is also
centralized.
The centralized solution is based primarily on the central Avaya Aura® infrastructure at the
enterprise core. During normal operation, the centralized users located in the branches receive
their service from the core, like users in the main office do. The phones register directly to the
Avaya Aura®Session Manager in the enterprise core, get their features from the central
Communication Manager Feature Server (CM-FS) or Communication Manager Evolution
Server (CM-ES), and utilize the Avaya Aura® applications.
The local B5800 Branch Gateway can be accessed as a SIP gateway connected to the core
Avaya Aura®Session Manager to provide access to local PSTN trunks and services when
required. In addition, if WAN connectivity to the Avaya Aura®Session Manager is lost, the
centralized SIP phones automatically failover and register with the B5800 Branch Gateway
which provides them with basic telephony survivability. When connection to the Avaya
Aura®Session Manager is available again, failback occurs where the SIP phones return to
being controlled by Avaya Aura®Session Manager.
In the centralized solution, the users must be administered on the Avaya Aura®Session
Manager and the core Communication Manager, as well as on the local B5800 Branch
Gateway. The centralized users' extension numbers must be defined according to the
enterprise numbering plan of the Avaya Aura® Session Manager. In addition to general
administration of the Avaya Aura®Session Manager and the core Communication Manager,
special consideration must be given to the design and configuration of branch locationdependent functionality in the Session Manager and optionally also in the core Communication
Manager. It is also important to verify the readiness of the underlying IP network since in the
centralized solution, VoIP is transported over the WAN.
PSTN trunking configurations
With the ability to administer call control at both the B5800 Branch Gateway and the Avaya
Aura®Session Manager, there are many ways you can optimize external PSTN trunk usage.
The B5800 Branch Gateway is a full P ABX and by default uses its own PSTN trunks. However
14 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
it can be configured to make and receive external calls via the central Avaya Aura®Session
Manager. A combination of these methods can be used for PSTN calls based on the call type
(local, national, international), time of day or even individual user. See Branch PSTN call routing
examples on page 325 for more information.
Voicemail support options
B5800 Branch Gateway supports a range of options for voicemail services to the branch's
native users. It supports embedded voicemail for native branch users and auto attendants for
external PSTN trunks. This can be changed to using a local V oicemail Pro voicemail server or
to using the central Modular Messaging server. In the later mode the B5800 Branch Gateway
can still use the local Embedded Voicemail for announcements to waiting callers and for auto
attendants.
Voicemail support options
Centralized management
The Network Management offer is a suite of software applications that enable centralized
management of the B5800 Branch Gateway system. It provides a single access interface to
manage multiple branch locations. The suite of applications include:
• Avaya Network Management Console — allows you to view the devices in the network.
• Manager — allows you to view and edit individual branches in the B5800 Branch Gateway
system.
• Avaya Provisioning and Installation Manager — allows you to provision and install large
numbers of B5800 Branch Gateway devices simultaneously through the use of templates
and bulk provisioning to a group of devices.
Note:
• When using Network Management to create a hardware template, Manager provides
the IP500v2 and ABG B5800 control units as options. Be sure to select ABG B5800.
IP500v2 is not supported in branch mode.
• The B5800 Branch Gateway system is referred to as IP Office in the Network
Management applications.
If you do not have the Network Management applications installed on a server in your network,
you can use Manager to administer each branch in the system. Manager is an off-line editor.
This means that it receives a copy of the current branch configuration. Changes are made to
the copy and then sent back to the branch for those changes to become active.
Implementing the Avaya B5800 Branch Gateway November 2011 15
Overview
Note:
If you are going to use Network Management for centralized management of the B5800
Branch Gateway system, Network Management (NM) 6.0, NM 6.0 SP2, plus an additional
B5800 Branch Gateway patch hosted on the Avaya support web site must be installed and
configured.
For more information about Network Management, see the Avaya Integrated Management 6.0
Network Management Configuration guide which is available on the Avaya support web site.
Remote access to Network Management
You are able to use Avaya Aura® Session Manager Release 6.x, cut-through capability to
access Network Management. The System Manager cut-through allows the provisioning of the
Network Management IP address with a unique menu name within the System Manager GUI.
Although System Manager and Network Management must be installed on two separate
servers, there is a single access interface for administration and management of the B5800
Branch Gateway. For more information, see
Management on page 161.
In addition to System Manager cut-through, you are able to remotely access Network
Management using a Secure Access Link (SAL) Gateway. A standalone SAL Gateway is
installed in the enterprise headquarters and allows remote management of individual branches
in the B5800 Branch Gateway system. See
page 215 for more information.
Creating a System Manager link to Network
Standalone SAL Gateway for remote service on
Licensing
B5800 Branch Gateway is a licensed solution. Branch licenses are issued and validated
against the Feature Key serial number of the System SD card used by that branch. That
number is printed after the FK prefix on the System SD card and is also shown in the branch
system configuration. This means that licenses issued for one branch cannot be used in the
configuration of another branch. In the Manager application, this number appears in the PLDS
Host ID field on the System page when you select System > System.
The B5800 Branch Gateway licenses are as follows:
• Avaya Branch Gateway System Software license
• Station licenses
• Embedded Messaging Ports license
• Voicemail Pro Messaging Ports license
• SIP Trunk Sessions license
• Additional channels licenses
• Additional T1 Channels license
16 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Licensing
• Additional E1 Channels license
• 120-day trial license
B5800 Branch Gateway uses the Avaya Product Licensing and Delivery System (PLDS) to
manage license entitlements. See Chapter 11: Managing license files with PLDS for more
information.
The B5800 Branch Gateway licenses are described below.
Avaya Branch Gateway System Software license
This license is required for operation of the B5800 Branch Gateway system. This license does
not include any implicit entitlements and therefore is not sufficient by itself for branch operation
without additional Station and/or SIP Trunk Session licences.
Station licenses
All users on a B5800 Branch Gateway system must be licensed by the addition of Station
licenses. There are two types of Station licenses:
• Native Station licenses — are required for all configured users with analog, digital, H.323
or DECT extensions and for all users with SIP extensions set as native (or local) (that is,
extensions operating in the Distributed Branch user model).
• Survivable Station licenses — are required for all configured users with SIP extensions
set as survivable (or centralized) (that is, extensions operating in the Centralized branch
user model, normally connecting to the Avaya Aura® core and connecting to the B5800
Branch Gateway is survivable mode during rainy-day).
Warning:
Unlicensed extensions will display No License Available but will be able to make
emergency calls, i.e. calls that match B5800 Branch Gateway Dial Emergency short
codes.
Embedded Messaging Ports license
This license is required if you are using the B5800 Branch Gateway voicemail option,
Embedded voicemail or using the B5800 Branch Gateway Embedded Auto-Attendant and
Announcements with a central voicemail option. Up to 6 ports can be licensed. At least one
Embedded Messaging Port license must be purchased to enable this service.
Voicemail Pro Messaging Ports license
This license is required if you are using the B5800 Branch Gateway voicemail option, Voicemail
Pro. Up to 40 ports can be licensed. At least one Voicemail Pro Messaging Port license must
be purchased to enable this service.
Note:
An Embedded Messaging Ports license and a Voicemail Pro Messaging Ports license
cannot be used together on the same system.
SIP Trunk Sessions license
This license refers to the total number of concurrent sessions allowed on all SIP connections
to the B5800 Branch Gateway . The maximum number of SIP trunk sessions is 128. SIP trunks
Implementing the Avaya B5800 Branch Gateway November 2011 17
Overview
provide the SIP connections between Avaya Aura®Session Manager and B5800 Branch
Gateway.
Additional channels licenses
The PRI Universal (PRI-U) trunk card can be used in the B5800 Branch Gateway system. The
PRI-U ports can be configured to support E1, E1R2, or T1 line types. Each port supports 8 B
channels which do not require a license. Additional B channels beyond these 8 require a
license. There are two additional channels licenses that define the number of additional
channels (above the default 8):
• Additional T1 Channels license — This license is for additional T1 trunks.
• Additional E1 Channels license — This license is for additional E1 or E1R2 trunks.
For trunk types on which channels can be set as in service, the licenses are consumed by
those channels which are configured as being in service. Manager will block attempts to
configure PRI channels as in service if they exceed the 8 per port allowed by default on that
card and if there are no Additional T1 Channels or Additional E1 Channels licenses
available.
120-day trial license
This license provides a 120-day trial period during which you have access to the features,
functions, and capabilities available in B5800 Branch Gateway . After the expiration of the 120day trial license, the 30-day grace period is activated. At the end of the 30-day grace period,
if no other license is installed or available, system administration is blocked.
License modes
The B5800 Branch Gateway system can be in one of three license modes — License Normal
Mode, License Error Mode, and License Restricted Mode. The license mode, as well as any
license errors, are displayed in Manager. When the B5800 Branch Gateway system is in
License Error Mode, a 30-day grace period is provided during which time the system is fully
functional. If the B5800 Branch Gateway system is in License Error Mode, all license errors
must be fixed, either by installing a valid license file with the appropriate licenses or by changing
the configuration so that it does not exceed any licensed capacities. If the B5800 Branch
Gateway system is in License Error Mode and not all license errors are fixed within the 30-day
grace period, the system will go into License Restricted Mode in which system administration
is blocked except for fixing the license errors.
System components
The B5800 Branch Gateway system is comprised of the following hardware components.
• Control unit — The control unit stores the system configuration and performs the routing
and switching for telephone calls and data traffic. It includes 4 slots for optional base cards
to support trunk and phone extension ports. The slots are numbered 1 to 4 from left to
18 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
System components
right. They can be used in any order; however , if the capacity for a particular type of card
is exceeded, the card in the right-most slot will be disabled.
• SD card — The B5800 Branch Gateway SD card is a uniquely numbered dongle used to
validate license keys entered into the B5800 Branch Gateway system configuration to
enable features. It also provides embedded voicemail support and storage for system
software files. The card fits into a slot in the rear of the control unit.
• Base cards — The control unit has slots for up to 4 base cards. The base cards are used
to add analog extension ports, digital extension ports, and voice compression channels.
Each base card includes an integral front panel with ports for cable connections. The
following base cards are supported:
• Digital station base card — This card provides 8 digital station (DS) ports for the
connection of A vaya digital phones other than IP phones. The card can be fitted with
a trunk daughter card which uses the base card ports for trunk connection. A
maximum of 3 digital station base cards are allowed per control unit.
• Analog phone base card — This card is available in two variants, supporting either
2 or 8 analog phone ports. The card can be fitted with a trunk daughter card which
uses the base card ports for trunk connection. A maximum of 4 analog phone base
cards are allowed per control unit. The analog phone ports do not include a ringing
capacitor. Where this is a requirement, connection should be via a Master socket
containing ringing capacitors. If fitted with an analog trunk daughter card, during
power failure phone port 8 is connected to analog trunk port 12.
• VCM base card — This card is available in variants supporting either 32 or 64 V oice
Compression Channels (VCM) for use with VoIP calls. A maximum of 2 VCM base
cards are allowed per control unit. The card can be fitted with a trunk daughter card
which uses the base card ports for trunk connection.
• 4–port expansion base card — This card adds an additional 4 expansion ports for
external expansion modules. The card is supplied with four 2m yellow interconnect
cables. This card does not accept any trunk daughter cards. A maximum of 1 4–port
expansion base card is allowed per control unit (right-hand slot 4 only). See
External
expansion modules on page 20 for a list of the supported external expansion
modules.
• BRI combination card — This card provides 6 digital station ports (1-6), 2 analog
extension ports (7-8) and 2 BRI trunk ports (9-10, 4 channels). The card also includes
10 VCM channels. This card has a pre-installed BRI trunk daughter card. A maximum
of 2 BRI combination cards of any type are allowed per control unit.
• ATM combination card — This card provides 6 digital station ports (1-6), 2 analog
extension ports (7-8) and 4 analog trunk ports (9-12). The card also includes 10 VCM
channels. This card has a pre-installed analog trunk daughter card. A maximum of
2 ATM combination cards of any type are allowed per control unit. The analog phone
ports do not include a ringing capacitor. Where this is a requirement, connection
should be via a Master socket containing ringing capacitors. If fitted with an analog
trunk daughter card, during power failure phone port 8 is connected to analog trunk
port 12.
Implementing the Avaya B5800 Branch Gateway November 2011 19
Overview
• Trunk daughter cards — Most base cards can be fitted with a trunk daughter card to
support the connection of trunks to the base card. The following trunk daughter cards are
supported:
• Analog trunk card — This card allows the base card to support 4 analog loop-start
trunks. The analog phone ports do not include a ringing capacitor. Where this is a
requirement, connection should be via a Master socket containing ringing capacitors.
If fitted with an analog trunk daughter card, during power failure phone port 8 is
connected to analog trunk port 12. A maximum of 4 analog trunk cards are allowed
per control unit.
• BRI trunk card — This card allows the base card to support up to 4 BRI trunk
connections, each trunk providing 2B+D digital channels. The card is available in 2
port (4 channels) and 4 port (8 channels) variants. A maximum of 4 BRI trunk cards
are allowed per control unit. For S-Bus connection, the card can be switched from
To trunk mode to So mode. This mode requires additional terminating resistors and
an ISDN crossover cable connection.
• PRI trunk card — This card allows the base card to support up to 2 PRI trunk
connections. The card is available in single and dual port variants. The card can be
configured for E1 PRI, T1 robbed bit, T1 PRI or E1R2 PRI trunks. A maximum of 4
PRI trunk cards are allowed per control unit. The B5800 Branch Gateway system
supports 8 unlicensed B-channels on each IP500 PRI-U port fitted. Additional Bchannels, up to the capacity of ports installed and PRI mode selected require
Universal PRI (Additional Channels) licenses added to the configuration. These
additional channels consume the licenses based on which additional channels are
configured as in-service from port 9 of slot 1 upwards. D-channels are not affected
by licensing.
• Combination cards — Combination cards are pre-paired base and trunk daughter cards.
They provide 6 digital station ports, 2 analog phone ports, 10 VCM channels and either
4 analog trunk ports or 4 BRI channels (2 ports). The trunk daughter card cannot be
removed or replaced with another type of trunk daughter card.
• External expansion modules — External expansion modules are used to add additional
analog and digital ports. If the control unit is fitted with a 4–port expansion base card, then
up to 12 external expansion modules are supported. The following external expansion
modules are supported:
• Analog trunk module — This module rovides an additional 16 analog ports for
connection of analog trunks. It supports both loop-start and ground-start trunks.
• BRI So8 module — This module provides 8 ETSI BRI-So ports for the connection
of ISDN devices. This module is not intended to support BRI trunks.
• Digital station module — This module provides, depending on variant, an
additional 16 or 30 DS ports for supported Avaya digital phones.
• Phone module — This module provides, depending on variant, an additional 16 or
30 phone ports for analog phones.
20 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Supported telephones
• Power supplies — The control unit has an internal power supply unit. Each external
expansion module is supplied with an external power supply unit. Additional power supply
units may also be required for IP phones and some phone add-ons.
• Power cords — Depending on the locale, different power cords need to be ordered for
each control unit, external expansion module, and any phones or devices using external
power supply units.
• Mounting kits — The control unit can be used free-standing, with external expansion
modules stacked above it. With optional rack mounting kits, the control unit and external
expansion modules can also be rack mounted. Alternatively, with an optional wall
mounting kit the control unit can be wall mounted. However, the control unit cannot
support any external expansion modules when wall mounted.
• Surge protectors and barrier boxes — Where the installation includes extensions in
other buildings, additional protective equipment is required. This equipment may also be
required in areas where the lightning risk is high.
• Phones — B5800 Branch Gateway systems support a variety of Avaya digital and IP
phones plus analog phones.
• Application DVDs — The B5800 Branch Gateway applications can be ordered on a
number of DVDs. In addition they can be downloaded from the B5800 Branch Gateway
section of the Avaya support web site (http://support.avaya.com).
Supported telephones
Telephone Native extensions Survivable extensions
Analog
1403
1408
1416
1603
1603SW
1608
1616
1603SW-I
1608-I
1616-I
Implementing the Avaya B5800 Branch Gateway November 2011 21
Overview
Telephone Native extensions Survivable extensions
BM32 (DSS)
2402D
2410D
2420
3641 wireless
3645 wireless
3720 DECT R4
3725 DECT R4
4602IP
4602SW
4610IP
4610SW
4621
1
4625
5402
5410
5420
EU24 (DSS)
5601
5602IP
5602SW
5610IP
5610SW
5620
5621
EU24BL (DSS)
9620L
9620C
9630G
9640
9640G
1
1
2 3
2 3
2 3
2 3
2 3
22 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Telephone Native extensions Survivable extensions
9650
9650C
SMM24
2 3
2 3
1
9608
9611G
9621G
9641G
BM12
1
Avaya
1010/1020/1030/1040
video conferencing units
Standards-compliant 3rdparty SIP audio and video
endpoints
Software applications
4
4
4
4
1
When connected to their respective telephones
2
With H.323 firmware
3
With SIP 2.6 firmware
4
With SIP 6.0 firmware
Software applications
The B5800 Branch Gateway software applications are provided on DVDs. They can also be
downloaded from Network Management.
• User applications — The following applications are supported for use by native users
on an B5800 Branch Gateway system.
• Embedded Voicemail: supports basic voicemail mailbox operation, simple auto-
attendants and hunt group announcements. It is provided on the Avaya SD card.
This voicemail option requires a license. See
information.
Licensing on page 16 for more
• Voicemail Pro: is a complete voicemail solution and provides Interactive Voice
Response (IVR) and call recording capabilities. Voicemail Pro runs on a server PC
connected to the B5800 Branch Gateway system. This voicemail option requires a
license. See
Implementing the Avaya B5800 Branch Gateway November 2011 23
Licensing on page 16 for more information.
Overview
• SoftConsole: is intended for telephone system operators or receptionists. It displays
details of calls and allows them to quickly see the status of the callers required
destination and transfer the call. The SoftConsole user is able to access a range of
details about the status of users and groups on the B5800 Branch Gateway system.
Up to 4 simultaneous SoftConsole users can be configured. This application does
not require a license.
• Installer/maintainer applications — The following B5800 Branch Gateway applications
are used to program and maintain an B5800 Branch Gateway system. These applications
do not require a license.
• Manager: a configuration application used to access all parts of the B5800 Branch
Gateway configuration. Different levels of access can be defined to control which
parts of the configuration the Manager user can view and alter. Manager is also used
to upgrade the software files used by an B5800 Branch Gateway system.
• System Status Application: a monitoring application used to inspect the current
status of B5800 Branch Gateway lines and extensions and to view records of recent
alarms and events. It runs as a Java application.
• System Monitor: shows a trace of all activity on the B5800 Branch Gateway system
in detail. Interpretation of System Monitor traces requires a high-level of data and
telephony protocol knowledge. B5800 Branch Gateway installers and maintainers
must run System Monitor when Avaya requests copies of System Monitor traces to
resolve support issues.
• SNMP MIBs: Not an application as such, the SNMP MIB files can be used by 3rdparty SNMP applications to monitor the B5800 Branch Gateway system.
Supported country locales
When a new or defaulted system's configuration is first opened in Manager, the value set in
the Locale field (System > System > Locale) should always be checked and changed if
necessary. The system's locale sets factors such as the default ringing patterns and caller
display settings. The locale also controls the language that a voicemail server will use for
prompts.
The following table indicates locale settings supported for different functions. Note that this
does not necessarily indicate support, availability or approval for B5800 Branch Gateway within
that country.
Locale
Argentina Latin
Language Telep
hony
Spanish
Phone
Display
Applications Voicemail
Manager Soft
Console
Embedded
Voicemail
Voicemai
l Pro
24 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Supported country locales
Locale Language Telep
hony
Australia UK
English
Belgium Dutch
Belgium French
Brazil Brazilian
Canada Canadian
French
Chile Latin
Spanish
China Mandarin - Colombia Latin
Spanish
Denmark Danish Finland Suomi France French
Phone
Display
Applications Voicemail
Manager Soft
Console
- -
Embedded
Voicemail
Voicemai
l Pro
Germany German
Greece Greek - - - Hong
Kong
Hungary Hungarian- - - - -
Iceland Icelandic - - - - India UK
Italy Italian
Korea Korean - Mexico Latin
NetherlandsDutch
New
Zealand
Norway Norwegia
Cantones
e
English
Spanish
UK
English
n
- - - -
-
-
Implementing the Avaya B5800 Branch Gateway November 2011 25
Overview
Locale Language Telep
hony
Peru Latin
Spanish
Poland Polish -
Phone
Display
Applications Voicemail
Manager Soft
Console
Embedded
Voicemail
Voicemai
l Pro
• Locale: The country represented by the locale.
• Language: The voicemail prompt language used for that locale.
• Telephony: The B5800 Branch Gateway provides default telephony settings matching
the normal expected defaults for the locale.
• Phone Display: Indicates that display messages from the B5800 Branch Gateway to
Avaya phones can be sent using the appropriate language for that locale. Note that the
user locale can be used to override the system locale for these messages. Note also that
some phones support their own language selection options for menus displayed by the
phone's own software.
• Manager: Indicates that the B5800 Branch Gateway Manager application can run in the
specific locale language. Manager uses the best match it has (French, German, Brazilian,
Dutch, Italian, Mexican Spanish or US English) for the regional location setting of the PC
on which it is running, otherwise it defaults to UK English. If required the language used
within the Manager screens can be overridden.
Training
Avaya University provides a wide range of training courses for B5800 Branch Gateway and its
associated applications. This includes courses necessary for B5800 Branch Gateway resellers
to become Avaya Authorized Channel Partners and for individuals to achieve B5800 Branch
Gateway certification.
• V oicemail: These columns indicate for which locales the different B5800 Branch Gateway
voicemail servers can provide the appropriate language prompts. In all cases, the system
locale can be overridden by setting a different user locale.
• Embedded Voicemail: Indicates that the locale is recognized by Embedded
Voicemail and appropriate language prompts are then used. If an unsupported locale
is used, Embedded Voicemail will attempt the best match using the first two
characters of the locale.
• Voicemail Pro: Indicates that the locale is recognized by Voicemail Pro and
appropriate language prompts are then used. For an unsupported locale if used, or
one for which the necessary prompts are not available, Voicemail Pro will attempt
the best match using a sequence of alternate locales. For example French Canadian
falls back to French, then US English and finally UK English. Note that the languages
available are selectable during Voicemail Pro installation.
26 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Details of courses can be found on the Avaya University web site (http://www.avaya-
learning.com). The site can be used to check course availability and to book courses. It also
includes on-line courses and on-line course assessments. The site requires users to setup a
user name and password in order to track their personal training record.
For a list of recommended courses available for the B5800 Branch Gateway, see
Recommended courses for Avaya B5800 Branch Gateway training on page 335.
Web sites
Information to support B5800 Branch Gateway can be found on a number of web sites.
• Avaya (http://www.avaya.com)
Web sites
The official web site for Avaya. The front page also provides access to individual Avaya
web sites for different countries.
• Avaya Enterprise Portal (
This is the official web site for all A vaya Business Partners. The site requires registration
for a user name and password. Once accessed, the site portal can be individually
customized for what products and information types you wish to see and to be notified
about by email.
• Avaya Support (
Contains documentation and other support materials for Avaya products.
• Avaya University (
This site provides access to the full range of Avaya training courses. That includes both
on-line courses, course assessments and access to details of classroom based courses.
The site requires users to register in order to provide the user with access to details of
their training record.
• Avaya Community (
This is the official discussion forum for A vaya product users. However it does not include
any separate area for discussion of B5800 Branch Gateway issues.
http://support.avaya.com)
http://www.avaya-learning.com)
http://partner.avaya.com)
http://www.aucommunity.com)
Documentation
Ensure that you have read this manual before starting the installation. Also read the installation
documentation for any other equipment and applications being installed as part of the B5800
Branch Gateway system.
Implementing the Avaya B5800 Branch Gateway November 2011 27
Overview
Documents you may need to consult are as follows:
• Administering Avaya Aura® Session Manager, document number 03-603324
• Avaya Integrated Management Release 6.0 Network Management Configuration
• Avaya Integrated Management Release 6.0 Network Management Installation and
Upgrade
• Avaya Integrated Management Release 6.0 Network Management Console User Guide
• IP Office Manager, document number 15-601011
• IP Office Release 6.1 Embedded Voicemail Installation, document number 15-601067
• Provisioning and Installation Manager for IP Office help system (available in the
application)
• Avaya B5800 Branch Gateway Solution Overview, document number 18-603903
Revision history
Issue
2, 3,
and 4
5 2/3/2012 Release 6.1 does not support the 9608, 9621G, and 9641G H.323
Date Summary of changes
In issues 2, 3, and 4, the following sections were added:
• Centralized solution
• 96x1 phones SIP firmware download in B5800 Branch Gateway
centralized branch deployments
• Centralized deployment example call flows
• Avaya port matrix for B5800 Branch Gateway and SIP phones
• Additional glossary terms
telephones in the Distributed Branch user model. In the Supported
T elephones table in Chapter 1, the check mark in the Native extensions
column for these telephones has been removed. These telephones are
supported as survivable extensions with SIP 6.0 firmware.
28 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Chapter 2: Planning
Before you begin installing and configuring the B5800 Branch Gateway system, you should already have
determined the implementation issues listed in the table below.
You have determined... See
The branch user model you are
deploying.
The dial plan you are configuring for the
system and each branch.
The B5800 Branch Gateway licenses
required for this installation.
How you are going to route outgoing
PSTN calls.
The voicemail solution you are going to
deploy.
The method you will use to configure and
manage the branches in the system.
Prerequisites
The following applications and servers must be installed and configured before the B5800
Branch Gateway system is installed.
Branch user deployment models on page 13
Dial plan considerations on page 30
Licensing on page 16
Branch PSTN call routing considerations on
page 32
Voicemail considerations on page 31
B5800 Branch Gateway configuration
methods on page 32
• Avaya Aura® Session Manager must be installed and configured at the headquarters
location.
• Avaya Aura® Communication Manager must be installed and configured as a feature
server at the headquarters location.
• If you are going to use Network Management for centralized management of the B5800
Branch Gateway system, Network Management (NM) 6.0, NM 6.0 SP2, plus an additional
B5800 Branch Gateway patch hosted on the Avaya support web site must be installed
and configured.
• A stand-alone Secure Access Link (SAL) gateway must be deployed.
Note:
System Platform's virtual SAL gateway is not supported.
Implementing the Avaya B5800 Branch Gateway November 2011 29
Planning
Dial plan considerations
A uniform dial plan greatly simplifies configuration, management and phone calls within the
network branch sites. For example, if each branch has similar roles such as reception, manager
and warehouse - using the same extension number for each role and a unique prefix for each
branch allows calls between sites with little need for directory lookups. It also means a standard
configuration can be used at branches; simplifying installation, user training and
maintenance.
For our examples we have used the following dial plan for each branch site:
• 3-digit branch prefixes beginning with 8 — A 3-digit branch prefix in the range 800 to
899. This allows us up to 100 branches yet keeps call routing simple. Any dialing at a
branch that being with an 8 can be assumed to be a call to a branch number and can be
routed to the Avaya Aura® Session Manager for routing to the correct branch.
• 3-digit extension numbers beginning with 2 — 3-digit extension numbers for all native
extensions and hunt groups starting from 200. This is the default numbering used by
B5800 Branch Gateway.
Centralized survivable extensions may have very different numbering. However, even here,
adopting elements of the uniform dial plan will simplify management and usage. For the
survivable extensions in our examples we have used a dial plan that has 6-digit extension
numbers of which the first 3 digits are equal to the branch prefix. This allows users that migrate
from the Distributed Branch user model to the Centralized Branch user model to keep their
same numbers. The numbers for the survivable extensions can also be different and don’t
necessarily have to share common first digits.
Dial plan example
T o describe a dial plan example, we have created Acme T ravel, a travel agency with a growing
number of branches. Each branch follows the same pattern, with extensions for a branch
manager and a small team of travel consultants in a sales group.
Given the nature of the business, branch users need to make national and international calls.
The company has taken advantage of a bulk call contracts from it headquarters site so wants
such calls routed via the headquarters site wherever possible. In addition, the branch staff want
to keep their branch phone numbers.
• 3-digit branch numbers beginning with 8, ie. 800 to 899.
• 3-digit native extension numbers beginning with 2, ie. 200 to 299.
30 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Loading...