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
Voicemail considerations
• 6-digit survivable extension numbers of which the first 3 digits are equal to the branch
prefix e.g. 811250.
• Dial 9 prefix for outgoing PSTN calls.
• National and international calls allowed but routed via the headquarters site's PSTN
trunks.
• Where a national call matches a branch location, it should be routed to the PSTN via that
branch.
• Local calls allowed from each branch using its own PSTN trunks.
• Modular Messaging at the headquarters site provides voicemail services to all
employees.
• The LAN on each branch has a unique IP address, 192.168.42.1, 192.168.44.1 and so
on.
• A number of survivability features are required:
• National calls via the branch's PSTN trunks when the branch data connection to the
headquarters site is not available or at maximum capacity.
• Modular Messaging fallback via PSTN.
This example assumes that all the branches were initially setup with the default North American
locale. For B5800 Branch Gateway that means that a dial 9 prefix is used for external calls.
For calls in other locales or between branches in different locals, the example will need to be
adjusted to ensure that the resulting number received at the remote branch will be routed to
an external PSTN trunk and is suitable for external dialing.
Voicemail considerations
The B5800 Branch Gateway system uses its Embedded Voicemail by default. However, a
number of other voicemail options are supported.
• Embedded Voicemail — Embedded Voicemail uses the system SD card in the B5800
Branch Gateway system control unit for storage of prompts and messages. Embedded
Voicemail supports mailboxes for all local extension numbers, announcements to waiting
callers, and auto attendants (up to 40) for external calls. Its capacity is limited to 15 hours
of recorded messages, prompts and announcements. At least one Embedded Messaging
Port license must be purchased to enable this service.
• Voicemail Pro — Voicemail Pro runs on a server PC connected to the B5800 Branch
Gateway system and provides a wide range of features. Voicemail Pro is the only option
that supports manual call recording for the B5800 Branch Gateway system users. It also
supports automatic call recording for the B5800 Branch Gateway system. At least one
Voicemail Pro license must be purchased to enable this service.
• Modular Messaging — The B5800 Branch Gateway system can be configured to use
Modular Messaging as its voicemail server. When Modular Messaging is used as the
Implementing the Avaya B5800 Branch Gateway November 2011 31
Planning
central voicemail system, at each branch you have the option to still use the local
Embedded Voicemail for auto attendant operation and for announcements to waiting
calls. See Configuring Modular Messaging on page 164 for more information. Note that
for this configuration, Embedded Voicemail licenses are required.
For more information about licensing, see Licensing on page 16.
Branch PSTN call routing considerations
Each B5800 Branch Gateway system can support its own external PSTN trunks. When
deployed in an Avaya Aura® network, you have considerable flexibility over where outgoing
PSTN calls should emerge from the network and similarly where incoming calls should be
routed.
For examples of some of the options available, see
page 325. The examples demonstrate the following options:
• Centralized call control on page 325 — External calls at a branch site can be rerouted to
be dialed out at another site. This can be done for reasons of call cost and call control.
For example, the central site may have a bulk call tariff for national and international calls
that would benefit all branches.
•
Branch PSTN Override on page 328 — Having configured the branch to send outgoing
external calls to the Avaya Aura® Session Manager for onward routing, there may be
cases where a specific number should still be routed via the branches own PSTN
trunks.
•
PSTN Fallback on page 330 — The B5800 Branch Gateway can be configured to allow
some calls that would normally use the Avaya Aura® Session Manager line to be routed
via the PSTN when the Avaya Aura® Session Manager line is not available.
The various methods used in the these examples can be combined to match the customer's
needs. However the main aim should be as follows:
• To keep the branch configuration as generic as possible, i.e. to use the same PSTN call
control in all branch configurations. This simplifies maintenance of multiple branches.
• To centralize as much of the PSTN call control in the Avaya Aura® Session Manager as
possible. Again this simplifies maintenance and control.
Branch PSTN call routing examples on
B5800 Branch Gateway configuration methods
There are two ways to configure and manage the branches in your B5800 Branch Gateway
system – locally using Manager or centrally using Network Management.
32 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
B5800 Branch Gateway configuration methods
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.
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.
Implementing the Avaya B5800 Branch Gateway November 2011 33
Planning
Network assessment for VoIP requirements
B5800 Branch Gateway is a converged telephony system, that is it combines aspects of
traditional P ABX telephone systems and IP data and telephony systems. This works at various
levels.
• Individual phone users can control the operation of their phone through applications
running on their PC.
• Data traffic can be routed from the LAN interface to a telephony trunk interface, for
example a dial-up ISP connection.
• Voice traffic can be routed across internal and external data links. This option is referred
to as voice over IP (VoIP).
The VoIP mode of operation can include IP trunks between customer systems and or H.323
IP telephones for users. In either case the following factors must be considered:
• The B5800 Branch Gateway control unit must be fitted with voice compression channels
(see
Voice compression channels on page 38). These channels are used whenever an
IP device (trunk or extension) needs to communicate with a non-IP device (trunk or
extension) or a device that uses a different codec.
• A network assessment is a mandatory requirement for all systems using V oIP. For support
issues with VoIP, A vaya may request access to the network assessment results and may
refuse support if those are not available or satisfactory.
A network assessment includes a determination of the following:
• A network audit to review existing equipment and evaluate its capabilities, including its
ability to meet both current and planned voice and data needs.
• A determination of network objectives, including the dominant traffic type, choice of
technologies, and setting voice quality objectives.
• The assessment should leave you confident that the implemented network will have the
capacity for the foreseen data and voice traffic, and can support H.323, DHCP, TFTP and
jitter buffers in H.323 applications.
• An outline of the expected network assessment targets is:
Test Minimum Assessment Target
Latency Less than 150ms
Packet Loss Less than 3%
Duration Monitor statistics once every minute for a full
week
34 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Chapter 3: Installation requirements
This chapter provides information about power supplies, cables, grounding and environmental and space
requirements for installing the B5800 Branch Gateway control unit and external expansion modules. The
B5800 Branch Gateway control unit can be mounted on the wall if no external expansion units are included
in the installation. If the installation includes external expansion modules, the control unit and external
expansion modules can be mounted into a standard 19-inch rack system.
Power supply backup (UPS)
The use of an Uninterrupted Power Supply (UPS) with any telephone system is strongly
recommended. Even at sites that rarely lose electrical power, that power may occasionally
have to be switched off for maintenance of other equipment. In addition, most UPSs also
provide an element of power conditioning, reducing spikes and surges.
The capacity of UPS systems and the total equipment load the UPS is expected to support are
usually quoted in VA. Where equipment load is quoted in Watts, multiply by 1.4 to get the VA
load.
The calculation of how much UPS capacity is required depends on several choices.
• What equipment to place on the UPS? Remember to include server PCs such as the
voicemail. It is recommended that the total load on a new UPS is never greater than 75%
capacity, thus allowing for future equipment.
• How many minutes of UPS support is required? Actual UPS runtime is variable, it
depends on what percentage of the UPSs capacity the total equipment load represents.
For example, a 1000VA capacity UPS may only support a 1000VA (100%) load for 5
minutes. This relationship is not linear , the same UPS would support a 500V A (50%) load
for 16 minutes. Therefore the lower the percentage of capacity used, the increasingly
longer the UPS runtime, typically up to 8 hours maximum. Remember also that for most
UPS's the ratio of discharge to full recharge time is 1:10.
• How many output sockets does the UPS provide? Multiple UPS units may be required
to ensure that every item of supported equipment has its own supply socket.
The web site
equipment you want supported on a UPS. It will then display various UPS options. The site
uses VA values for typical B5800 Branch Gateway systems. However, if more specific values
are required for a particular system, the table below can be used to enter values.
http://www.avayaups.com provides a calculator into which you can enter the
Implementing the Avaya B5800 Branch Gateway November 2011 35
Installation requirements
Typical B5800 Branch Gateway System VA
B5800 Branch Gateway system 230
Individual Equipment VA
Analog 16 module 88
Digital Station 16 module 34
Digital Station 30 module 42
WAN3 module 17
So8 module 34
The 1151D2 power supply unit for Avaya H.323 IP phones includes a backup battery. This
typically provides 15 minutes backup at maximum load (20 Watts) and up to 8 hours at light
load (2 Watts).
Cables
The B5800 Branch Gateway system is designed primarily for use within an RJ45 structured
cabling system using CAT3 unshielded twisted-pair (UTP) cabling and RJ45 sockets.
A structured cabling system is one where cables are run from a central RJ45 patch panel in
the communications/data room to individual RJ45 sockets at user locations. All wires in each
cable between the patch panel and the desk socket are connected straight through. This
arrangement allows devices connected at the patch panel to be swapped to match the type of
device that needs to be connected at the user socket. For example, making one user socket
a phone port and another user socket a computer LAN port, without requiring any rewiring of
the cables between the patch panel and the user location.
• Traditional IDC punchdown wiring installations — Where necessary , the far end RJ45
plug can be stripped from B5800 Branch Gateway cables and wired into traditional wiring
36 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Cables
systems using punch-block connectors. This type of installation should be performed by
an experienced wiring technician.
• Trunk connections — The majority of B5800 Branch Gateway trunk ports use RJ45
connectors for acceptance of an RJ45-to-RJ45 cable. However, connection at the line
provider's end may require use of a different plug type in order to match the line providers
equipment.
• RJ11 phone connectors — Many phones use RJ11 sockets and are supplied with RJ11-
to-RJ11 cables. RJ11 plugs can be inserted into RJ45 sockets and in many case the
connection will work. However this is not recommended or supported as the connection
lock is not truly positive and may become disconnected. An RJ45-to-RJ11 cable is
available for these connections.
Standard B5800 Branch Gateway cables
The following are Avaya standard cables available for use with B5800 Branch Gateway
systems. The maximum length is applicable if the standard Avaya cable is replaced with an
alternate cable.
Cable Description Standard
9-way DTE cable Connects to control unit RS232 DTE
port. 9-way D-type plug to 9-way Dtype socket.
Structured cabling
DS line cable
BRI/PRI trunk cable Connects BRI/PRI trunk ports to the
Expansion
interconnect cable
LAN cable Connects from B5800 Branch
V.24 WAN cable 37-way D-type plug to 25-way D-type
V.35 WAN cable 37-way D-type plug to 34-way MRAC
Connects from RJ45 sockets to RJ11
socketed DS and analog phones.
line provider's network termination
point. RJ45 to RJ45. Red.
Connects the control unit to expansion
modules (except WAN3 modules).
RJ45 to RJ45. Blue.
Gateway LAN ports toB5800 Branch
Gateway devices. RJ45 to RJ45.
Grey.
plug.
plug.
Maximum
Length
2m/6'6'' 2m/6'6''
4m/13'2'' –
3m/9'10'' –
1m/3'3'' 1m/3'3''
3m/9'10'' 100m/328'
3m/9'10'' 5m/16'5''
3m/9'10'' 5m/16'5''
Length
X.21 WAN cable 37-way D-type plug to 15-way D-type
plug.
Implementing the Avaya B5800 Branch Gateway November 2011 37
3m/9'10'' 5m/16'5''
Installation requirements
Grounding
Use of ground connections reduces the likelihood of problems in most telephony and data
systems. This is especially important in buildings where multiple items of equipment are
interconnected using long cable runs, for example phone and data networks.
All control units and external expansion modules must be connected to a functional ground.
Where the unit is connected to a power outlet using a power cord with an earth lead, the power
outlet must be connected to a protective earth.
In some cases, such as ground start trunks, in addition to being a protective measure this is a
functional requirement for the equipment to operate. In other cases it may be a locale regulatory
requirement and or a necessary protective step, for example areas of high lightning risk.
For more information about grounding including the location of the ground points on the control
unit and external expansion modules, see Grounding on page 65.
Wall and rack mounting
The B5800 Branch Gateway control unit is designed to be freestanding. When external
expansion modules are used, the control unit and expansion modules are intended to be
stacked. With optional mounting kits, the system can be wall or rack mounted. See
mounting on page 59 and Rack mounting on page 61 for more information.
Voice compression channels
Calls to and from IP devices can require conversion to the audio codec format being used by
the IP device. For B5800 Branch Gateway systems this conversion is done by voice
compression channels. These support the common IP audio codecs G711, G723 and
G729a.
For the B5800 Branch Gateway control unit, channels can be added using VCM base cards,
BRI combination cards, and ATM combination cards. See
more information about these cards.
The voice compression channels are used as follows:
Wall
System components on page 18 for
38 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Voice compression channels
Call type Voice compression channel usage
IP device to non-IP device These calls require a voice compression channel for the
duration of the call. If no channel is available, busy indication
is returned to the caller.
IP device to IP device Call progress tones (for example dial tone, secondary dial
tone, etc) do not require voice compression channels with
the following exceptions:
• Short code confirmation, ARS camp on and account code
entry tones require a voice compression channel.
• Devices using G723 require a voice compression channel
for all tones except call waiting.
When a call is connected:
• If the IP devices use the same audio codec no voice
compression channel is used.
• If the devices use differing audio codecs, a voice
compression channel is required for each.
Non-IP device to non-IP
device
Music on Hold This is provided from the B5800 Branch Gateway TDM bus
Conference resources and IP
devices
Page calls to IP dDevice B5800 Branch Gateway only uses G729a for page calls,
Voicemail services and IP
devices
T38 fax calls In order to use T38 fax connection, B5800 Branch Gateway
No voice compression channels are required.
and therefore requires a voice compression channel when
played to an IP device.
Conferencing resources are managed by the conference
chip which is on the B5800 Branch Gateway TDM bus.
Therefore, a voice compression channel is required for each
IP device involved in a conference. This includes services
that use conference resources such as call listen, intrusion,
call recording and silent monitoring.
therefore only requiring one channel but also only
supporting pages to G729a capable devices.
Calls to the B5800 Branch Gateway voicemail servers are
treated as data calls from the TDM bus. Therefore calls from
an IP device to voicemail require a voice compression
channel.
performs fax tone detection if the analog extension
connected to the fax machine is set as “Standard
telephone.” If the fax machine does not include an attached
handset that is used to make/receive voice calls, then the
Equipment Classification of an analog extension connected
to the fax machine can be set to Fax Machine, which will
result in T38 fax connection without fax tone detection and
respective signaling renegotiation. Additionally, a new short
code feature, Dial Fax, is available.
Implementing the Avaya B5800 Branch Gateway November 2011 39
Installation requirements
Measuring channel usage
The B5800 Branch Gateway System Status Application can be used to display voice
compression channel usage. Within the Resources section it displays the number of channels
in use. It also displays how often there have been insufficient channels available and the last
time such an event occurred.
For the VCM cards, the level of channel usage is also indicated by the LEDs (1 to 8) on the
front of the VCM card.
Emergency and power failure ports
B5800 Branch Gateway systems can provide 2 types of analog extension power failure ports
as described in the following table.
Type Description Provided By:
Switching power failure
ports
Emergency only power
failure ports
During normal B5800 Branch
Gateway operation these ports
can be used for normal analog
phone connection.
During power failure the port is
directly connected to an analog
trunk port.
During normal B5800 Branch
Gateway operation these ports
cannot be used.
During power failure the port is
directly connected to an analog
trunk port.
• Analog phone 8 card
When an analog phone 8
base card is fitted with an
analog trunk daughter card,
during power failure
extension port 8 is connected
to analog trunk port 12.
• ATM combination card
On this card, during power
failure, extension port 8 is
connected to analog trunk
port 12.
• Analog trunk daughter
card
Regardless of the card
hosting it, during power
failure pins 4 and 5 of port 12
are connected to pins 7 and
8.
In all cases these only work with loop-start analog trunks. Any phones connected to these ports
should be clearly labeled as power fail extensions in accordance with the appropriate national
and local regulatory requirements.
40 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Environmental requirements
The planned location must meet the following requirements. If being installed into a rack
system, these are requirements for within the rack:
• Temperature: 0°C to 40°C / 32°F to 104°F.
• Humidity: 10% to 95% non-condensing.
• Check there are no flammable materials in the area.
• Check there is no possibility of flooding.
• Check that no other machinery or equipment needs to be moved first.
• Check that it is not an excessively dusty atmosphere.
• Check that the area is unlikely to suffer rapid changes in temperature and humidity.
• Check for the proximity of strong magnetic fields, sources of radio frequency and other
electrical interference.
Environmental requirements
• Check there are no corrosive chemicals or gasses.
• Check there is no excessive vibration or potential of excessive vibration, especially of any
mounting surface.
• Check that where telephones are installed in another building, that the appropriate
protectors and protective grounds are fitted (see
page 66).
• Check there is suitable lighting for installation, system programming and future
maintenance.
• Check that there is sufficient working space for installation and future maintenance.
• Ensure that likely activities near the system will not cause any problems, e.g. access to
and maintenance of any other equipment in the area.
• Where ventilation holes are present on any of the B5800 Branch Gateway units, those
holes should not be covered or blocked.
• The surface must be flat horizontal for free-standing or rack mounted installations.
Wall mounting: In additional to the requirements above, the following are applicable to control
units that are mounted on the wall.
• Units must only be mounted onto permanent wall surfaces.
• The surface must be vertical and flat.
• Orientation of the unit must be as shown in the section on
page 59.
Out of Building Telephone Installation on
IP500 Wall Mounting on
• The appropriate Avaya wall mounting kits must be used.
Implementing the Avaya B5800 Branch Gateway November 2011 41
Installation requirements
Note:
See Important safety instructions when using your telephone equipment on page 275 for
basic safety precautions to follow when using your telephone equipment.
Space requirements
The B5800 Branch Gateway control unit and external expansion modules are designed to be
installed either in a free-standing stack or into a 19-inch rack system. Rack installation requires
a rack mounting kit for each control unit and expansion module. See
page 61 for more information. If there are no external expansion modules used in the
installation, the control unit can be wall mounted using a wall mounting kit. See
mounting on page 59 for more information.
• Cable clearance
Clearance must be provided at the front and rear of all modules for cable access and
feature key dongle connection. Allow a minimum clearance of 90mm (3.5 inches).
Rack mounting on
Wall
• Additional clearance
Care should be taken to ensure that the positioning of the modules does not interrupt air
flow and other environmental requirements. The control unit has ventilation slots at the
side that must not be blocked. See
space requirements on page 44 for more information.
• Cable access
Power cords must not be attached to the building surface or run through walls, ceilings,
floors and similar openings. Installation measures must be taken to prevent physical
damage to the power supply cord, including proper routing of the power supply cord and
provision of a socket outlet near the fixed equipment or positioning of the equipment near
a socket outlet.
Control unit
When wall mounted, a clearance of 500mm is required on all sides. The ventilation slots on
the rear and sides should not be covered or blocked.
Environmental requirements on page 41 and Rack
42 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Space requirements
External expansion modules
The dimensions below are applicable to all external expansion modules.
Implementing the Avaya B5800 Branch Gateway November 2011 43
Installation requirements
Wall mounting space requirements
The control unit can be wall mounted if not using any external expansion modules. A wall
mounting kit is required in addition to 4.5mm fixings suitable for the wall type. A clearance of
500mm around the control unit is required. See
information.
Rack space requirements
The B5800 Branch Gateway control unit and external expansion modules can be rack mounted
into standard 19-inch rack systems. Each unit requires a 2U slot space within the rack. Rack
mounting requires a rack mounting kit for each control unit and external expansion module.
Rack mounting on page 61 for more information about the rack mounting kit.
See
Where B5800 Branch Gateway systems are being rack mounted, the effect of conditions within
the rack cabinet must be considered. For example the rack temperature may be above the
room temperature and airflow within the rack will be restricted. The environmental
requirements for the individual control unit and expansion modules are still applicable inside
the rack cabinet.
Wall mounting on page 59 for more
Barrier box rack mounting kit
The barrier box rack mounting kit must be used for out-of-building analog phone extensions.
This bracket allows up to 8 barrier boxes to be rack mounted and simplifies the number of
connections to the protective ground point in the rack. This kit must be used when more than
3 barrier boxes are in use and supports a maximum of 16 barrier boxes for a single external
expansion module.
44 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Rack module positioning
The integral expansion ports on a control unit are located on the rear of the unit. An additional
4 expansion ports can be added to the front of the control unit by installing a 4-port expansion
card.
• Each external expansion module is supplied with a blue 1 meter (3'3'') expansion
interconnect cable. This cable must be used when connecting to expansion ports on the
rear of a control unit.
• When connecting to expansion ports on a 4-port expansion card, a yellow 2-meter (6'6")
expansion interconnect cable can be used in place of the standard blue cable. Four yellow
cables are supplied with the 4-port expansion card.
Space requirements
Implementing the Avaya B5800 Branch Gateway November 2011 45
Installation requirements
46 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Chapter 4: Hardware and software
installation
All hardware components should be turned off while they are installed and connected. Once the installation
is complete, the system is turned on. The control unit will then upgrade all of the connected components,
including phones, to the appropriate level of firmware. In addition, when the system is turned on, it should
not be connected to the customer's data network. This ensures that the control unit will default to known
default IP address settings (unless you have pre-loaded the System SD card with a configuration file with
different settings).
Installation checklist
Use this checklist to monitor your progress as you install a B5800 Branch Gateway system.
#
1 Review the prerequisites. See Prerequisites on page 29.
2 Review the Installation
requirements.
3 Review the required tools and
equipment.
4 Unpack the equipment. See Unpacking equipment on page 49.
5 If you want to pre-configure the
system, there are several tasks
you can perform to configure the
SD card before it is installed in the
control unit.
6 Prepare the base and trunk cards
and install them in the control
unit.
7 Do one of the following:
• Install the control unit on the
wall.
• Install the control unit in a rack.
Description Section
See Installation requirements on page 35.
See Tools and equipment required on
page 48.
See SD card preparation on page 50.
See Base and trunk card installation on
page 53.
See one of the following:
• Wall mounting on page 59.
• Rack mounting on page 61.
Implementing the Avaya B5800 Branch Gateway November 2011 47
Hardware and software installation
# Description Section
8 Connect the external expansion
modules.
9 Connect the control unit and
external expansion modules to a
functional ground.
10 Install the B5800 Branch Gateway
administration applications on the
installer PC.
11 Connect the PC to the control
unit.
12 Apply power to the system. See Applying power to the system on
13 Start the Manager application. See Starting Manager on page 78.
14 Change the default IP address
settings to match the customer
requirements.
15 Connect the control unit to the
network.
16 Change the system's security
settings.
See External expansion modules on
page 63.
See Grounding on page 65.
See Installing the administration
applications on page 72.
See Installer PC connection on page 73.
page 75.
See Changing the IP address settings on
page 81.
See Connecting the control unit to the
network on page 82.
See Changing the security settings on
page 82.
17 Change the remote user
password.
18 Connect the phones. See Connecting phones on page 84.
19 Download the SIP firmware for the
96x1 SIP phones.
See Changing the remote user password on
page 83.
See 96x1 phones SIP firmware download in
B5800 Branch Gateway centralized branch
deployments on page 84.
Tools and equipment required
Following is a general summary of the tools required. Additional tools and equipment are
required for wall and/or rack mounting and to fashion ground cable connections suitable to
local requirements.
• Tools required
• 5mm Flat-blade screwdriver
• Crosshead screwdriver
• Anti-static wrist strap and ground point
48 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Unpacking equipment
• RJ45-RJ45 ethernet LAN cable
• M4 cross-head screwdriver
• Tools suitable for crimping a cable spade
• If wall mounting, drills and tools for wall mounting fixtures
• Additional parts required
In addition to orderable system equipment, the following items are required.
• 14AWG solid copper wire for ground connection of control units and expansion
modules
• Cable sleeve matching local regulator requirements for ground wires. T ypically green
for a functional ground and green/yellow for a protective ground.
• If wall mounting, additional 4.5mm diameter fixtures and fittings suitable for the wall
type
• Cable ties and labels for tidying and identifying cables
• PC requirements
• Windows PC with the administration software installed. See
page 72.
• SD card reader
Unpacking equipment
About this task
Use the following procedure when unpacking any equipment supplied by Avaya or an Avaya
reseller or distributor. Have the equipment order checklist available as you unpack the
equipment to ensure you have all parts and equipment ordered.
Procedure
1. Check for package damage
Before unpacking any equipment, check for any signs of damage that may have
occurred during transit. If any damage exists bring it to the attention of the carrier.
2. Check the correct parts have been delivered
Check all cartons against the packing slip and ensure that you have the correct
items. Report any errors or omissions to the equipment supplier.
PC requirements on
3. Retain all packaging and documentation
While unpacking the equipment, retain all the packaging material. Fault returns are
accepted only if repackaged in the original packaging. If performing a staged
installation, the original packaging will also assist when repacking equipment to be
moved to the final install site.
Implementing the Avaya B5800 Branch Gateway November 2011 49
Hardware and software installation
4. Ensure that anti-static protection measures areobserved
Ensure that anti-static protection measures are observed at all times when handling
equipment with exposed electrical circuit boards.
5. Check all parts
Visually inspect each item and check that all the necessary documentation and
accessory items have been included. Report any errors or omissions to the dealer
who supplied the equipment.
6. Check all documentation
Ensure that you read and retain any documentation included with the equipment.
SD card preparation
B5800 Branch Gateway control units are supplied with no installed firmware or configuration.
When first powered up, the control unit loads and installs the necessary firmware from the
B5800 Branch Gateway System SD card that has been installed in the control unit. A default
configuration is then created that matches the cards installed in the control unit and external
expansion modules attached.
You can perform the following tasks prior to installing the B5800 Branch Gateway System SD
card in order to pre-configure the system.
• See
Upgrade the Card Firmware on page 50
• See Creating a configuration file on page 51.
• See Adding a configuration file on page 52.
• See Adding music-on-hold files on page 52.
• See
Add a 9600 Screen Saver Image File on page 53.
For more information about SD cards, see SD Card Management on page 253.
Upgrading the card firmware
About this task
This process creates the folder structure on the SD card and copies the firmware files from
those installed with Manager onto the SD card. This includes the binary files for the B5800
Branch Gateway system and any external expansion modules and phones. It also includes
the prompt files for embedded voicemail operation.
This process can be used to upgrade an existing SD card to match the file set installed with
Manager. The card installed in the System SD slot must be an Avaya SD Feature Key card.
The card must be correctly formatted.
50 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
SD card preparation
If the card contains any dynamic system files, for example SMDR records, they are temporarily
backed up by Manager and then restored after the card is recreated.
Procedure
1. Insert the SD card into a card reader on the Manager PC.
Note:
Do not remove the SD card. Removing the SD card will interrupt the upgrade.
2. Using Manager, select File > Advanced > Recreate IP Office SD Card.
3. Select Avaya Branch Gateway.
4. Browse to the card location and click OK.
Manager starts creating folders on the SD card and copying the required files into
those folders. This process takes approximately 15 minutes. Do not remove the SD
card until the Manager status bar at the bottom shows a Ready message.
Creating a configuration file
About this task
Manager can be used to create a new configuration file without connecting to a B5800 Branch
Gateway system. This allows the creation of a configuration prior to installing the system. The
configuration file can be loaded on the System SD card before the card is installed. The
configuration file specifies the system's location, trunk cards, control unit, and expansion
modules.
• The configuration created must match the physical equipment in the B5800 Branch
Gateway system for which the configuration will be loaded. If they do not match, the
system may reset and experience other problems.
• The configuration creation tool includes all control units, external expansion modules and
trunk cards supported by B5800 Branch Gateway. It is your responsibility to confirm the
B5800 Branch Gateway equipment that is supported in your location.
Procedure
1. Start Manager with no configuration loaded into Manager.
2. Click on Create an Offline Configuration in the simplified view.
3. Select the type of configuration that you want to create.
4. When completed, click OK.
Manager will create and load the configuration.
5. Edit the configuration to match the customer requirements.
This can include importing information from prepared CSV files.
Implementing the Avaya B5800 Branch Gateway November 2011 51
Hardware and software installation
Note:
For information about CSV files, see the Help available in the Manager
application. From Manager, select Help > Contents. In the Manager Help
window, in the left navigation pane, expand IP Office Configuration Mode and
then expand Editing Configuration Settings. Then click Importing and
Exporting Settings.
6. When completed, select File > Save Configuration As.
Adding a configuration file
About this task
Use this procedure to add a configuration file on the System SD card. That configuration file
will then be used when the B5800 Branch Gateway system is started.
Procedure
1. Create an offline configuration that matches the customer requirements and the
equipment that will be installed in the B5800 Branch Gateway system. See Creating
a configuration file on page 51.
2. Rename the configuration file config.cfg.
3. Using a card reader, copy the file into the /system/primary folder on the System
SD memory card.
Adding music-on-hold files
About this task
By default B5800 Branch Gateway uses internal music-on-hold by uploading a music file. You
can load a file onto the System SD card prior to installing it in the control unit
The file must be of the following format and must be called holdmusic.wav.
Property
File Type WAV
Bit Rate 128kbps
Value
Audio sample size 16 bit
Channels 1 (mono)
Audio Sample Rate 8 kHz
52 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Property Value
Audio Format PCM
Length Up to 90 seconds.
Procedure
1. Rename the music file holdmusic.wav.
2. Using a card reader, copy the file into the /system/primary folder on the System
SD memory card.
3. If the B5800 Branch Gateway system is configured for additional music-on-hold files
(up to 3 additional files), copy those files to the same location.
The name of the additional files must match those specified in the B5800 Branch
Gateway system configuration.
Base and trunk card installation
9600 series phones screen saver file
When idle, 9600 Series phones can timeout and display a screen saver image. A file,
96xxiposs.jpg, is present on the cards by default.
Y ou can replace this file with your own branded file. The file should be smaller than the screen
size on 9600 Series phones in order for the image to move around the screen.
Base and trunk card installation
The base cards and trunk daughter cards should be fitted before power is applied to the control
unit. Ensure that cards are inserted in the order that matches the planned or pre-built
configuration. In general, the following applies to card installation:
• Cards can be fitted in any order into any available slots. The only exception is the 4-port
expansion card which can only be installed in right-hand slot 4.
• It is recommended that cards are fitted from left to right.
• There are restrictions to the number of supported cards of some types. When a limit is
exceed, the right-most card of that type will not function.
• Ensure that you use the labels supplied to identify the card fitted into the control unit.
Implementing the Avaya B5800 Branch Gateway November 2011 53
Hardware and software installation
Warning:
• Correct anti-static protection steps should be taken before handling circuit boards.
• Cards must never be added or removed from the control unit while it has power
connected.
Trunk daughter card preparation
Trunk daughter cards can be fitted to any base card except the legacy card carrier. For
combination cards, the trunk daughter card is pre-installed and cannot be changed.
Warning:
Correct anti-static protection steps should be taken while handling circuit boards.
54 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Parts and equipment required
• Base card (except the legacy card carrier)
• Trunk daughter card
• 3 stand-off pillars (these are supplied with the trunk daughter card)
Tools required
• 5mm Flat-blade screwdriver
• Anti-static wrist strap and ground point
Installing a trunk daughter card
Procedure
1. Check that correct cards have been supplied.
2. Ensure that you are wearing an anti-static wrist strap connected to a suitable ground
point.
Base and trunk card installation
3. On the base card, identify the position of the 3 holes for the plastic pillars for the
trunk daughter card.
These are along the same edge as the card connector.
4. Fit the stand-off pillars to the base card.
5. If there is a clip-on metal shield over the connector block on the base card, remove
it.
6. Using minimal force and checking that the pins are correctly located, push the trunk
card onto its connector block and the stand-off pillars.
7. Check that the card connector has snapped into position.
8. Using the washers and screws provided, secure the metal stand-off pillars to the
base card.
9. From the set of labels that are supplied with the trunk daughter card, fit the
appropriate label to the front of the base card.
Legacy carrier card preparation
A legacy carrier card can be used to fit VCM cards into the B5800 Branch Gateway control
unit. Up to 2 legacy carrier cards can be inserted. The following trunk and VCM cards are
supported. Cards not listed are not supported.
Implementing the Avaya B5800 Branch Gateway November 2011 55
Hardware and software installation
• PRI T1
• Dual PRI T1
• PRI 30 E1 (1.4)
• Dual PRI E1
• PRI 30 E1R2 RJ45
• Dual PRI E1R2 RJ45
• BRI-8 (UNI)
• ANLG 4 UNI (US only)
• VCM 4
• VCM 8
• VCM 16
• VCM 24
• VCM 30
Warning:
Correct anti-static protection steps should be taken while handling circuit boards.
Parts and equipment required
• Legacy carrier card
• VCM card
56 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
• 2 plastic stand-off pillars per card
• Trunk cards are supplied with a replacement blanking plate which is not required.
Tools required
• 5mm Flat-blade screwdriver
• Anti-static wrist strap and ground point
Installing a legacy carrier card
Procedure
1. Check that correct cards have been supplied.
2. Ensure that you are wearing an anti-static wrist strap connected to a suitable ground
point.
3. On the carrier card identify the position of the jumper block and stand-off pillar holes
for the IP400 card.
The peg holes are labeled as VCM or TRUNK.
Base and trunk card installation
4. If fitting an IP400 trunk card, identify which of the plastic snap-off panels on the front
of the carrier card need to be removed to allow the trunk cable connections.
5. Carefully remove those panels.
6. Fit the stand-off pillars to the legacy carrier card.
7. Using minimal force and checking that the pins are correctly located, push the IP400
card onto its jumper and the stand-off pillars.
Base card insertion
Having prepared each base card by adding the trunk daughter cards or legacy carrier cards,
the base card can be inserted into the control unit.
Implementing the Avaya B5800 Branch Gateway November 2011 57
Hardware and software installation
Warning:
• Correct anti-static protection steps should be taken before handling circuit boards.
• Cards must never be added or removed from the control unit while it has power
connected.
• Tools required
• 5mm Flat-blade screwdriver
• Anti-static wrist strap and ground point
Installing a base card
Procedure
1. Check that there is no power to the control unit.
2. Using a flat-bladed screwdriver, remove the cover from the slot on the front of the
control unit that will be used for each card being installed.
This cover is no longer required but should be retained until installation has been
completed.
3. Allowing the card to rest against the bottom of the slot, begin sliding it into the control
unit.
4. When half inserted, check that the card rails have engaged with the slot edges by
trying to gently rotate it. If the card rotates, remove it and begin inserting it again.
The card should slide in freely until almost fully inserted.
58 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
5. At this point apply pressure at the base of the front of the card to complete
insertion.
6. Using a flat-bladed screwdriver secure the card.
Wall mounting
B5800 Branch Gateway control units can be wall mounted. This requires a wall mounting kit
plus additional 4.5mm fixtures and fittings suitable for the wall type. The wall mounting kit
includes two brackets, one top and one bottom.
Wall mounting
In addition to the existing
apply when wall mounting a unit:
• The wall surface must be vertical, flat and vibration free.
• The brackets must be used as shown, with the deeper tray-like bracket used at the bottom
of the wall mounted control unit.
• Only the screws (M3 x 6mm) provided with the mounting kit should be used to attach the
brackets to the control unit.
environmental requirements on page 41, the following requirements
Implementing the Avaya B5800 Branch Gateway November 2011 59
Hardware and software installation
60 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Rack mounting
The B5800 Branch Gateway control unit and external expansion units can be rack mounted
into 19-inch rack systems. This requires a rack mounting kit for each unit.
The rack mounting kit includes:
• A rack mounting bracket and screws for attachment of the bracket to the unit
• Nuts and bolts for rack attachment
• Brackets and cable ties for cable tidying
Environmental requirements
In addition to the environmental requirements on page 41, the following factors must be
considered when rack mounting a unit:
• Rack positioning — Ensure compliance with the rack manufacturers safety instructions.
For example check that the rack legs have been lowered and fixing brackets have been
used to stop toppling.
Rack mounting
• Elevated operating ambient — If installed in a closed or multi-unit rack assembly, the
operating ambient temperature of the rack environment may be greater than room
ambient. Therefore, consideration should be given to installing the equipment in an
environment compatible with the maximum ambient temperature (Tma) specified by the
manufacturer.
• Operating temperature: 0°C (32°F) to 40°C (104°F).
• Operating humidity: 10% to 95% non-condensing.
• Reduced air flow — Installation of the equipment in a rack should be such that the amount
of air flow required for safe operation of the equipment is not compromised. Proper
ventilation must be maintained. The side ventilation slots on the control unit should not
be covered or blocked.
• Mechanical loading — Mounting of the equipment in the rack should be such that a
hazardous condition is not achieved due to uneven mechanical loading.
• Circuit overloading — Consideration should be given to the connection of the equipment
to the supply circuit and the effect that overloading of the circuits might have on
overcurrent protection and supply wiring. Appropriate consideration of equipment
nameplate ratings should be used when addressing this concern.
• Reliable earthing — Reliable earthing of rack-mounted equipment should be maintained.
Particular attention should be given to supply connections other than direct connections
to the branch circuit (e.g. use of power strips).
Implementing the Avaya B5800 Branch Gateway November 2011 61
Hardware and software installation
•
Important:
Only the screws (M3 x 6mm) provided with the mounting kit should used to attach the
62 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
brackets to the control unit. As indicated in the diagram, the rack mounting bracket can
be used in several positions on the unit.
External expansion modules
External expansion modules should be connected to the control unit before power is applied
to the control unit. Ensure that modules are attached in the order that matches the planned or
pre-built configuration.
External expansion modules connect to the control unit using an expansion interconnect cable.
Each module is supplied with an expansion interconnect cable and a power supply unit. An
appropriate local specific power cord for the power supply unit must be ordered separately.
• Each external expansion module is supplied with a blue 1 meter (3'3'') expansion
interconnect cable. This cable must be used when connecting to expansion ports on the
rear of a control unit.
• When connecting to expansion ports on a 4-port expansion card, a yellow 2-meter (6'6")
expansion interconnect cable can be used in place of the standard blue cable. Four yellow
cables are supplied with the 4-port expansion card.
External expansion modules
Installation requirements
• Installation space either on or under the control unit
• Switched power outlet socket
• Available EXPANSION port on the control unit
• Functional grounding requirements — connection of a functional ground is:
• recommend for all modules
• mandatory for analog trunk modules
• Protective grounding requirements — connection of a protective ground via surge
protection equipment is:
• mandatory for analog trunk modules in the Republic of South Africa
• mandatory for digital station and phone modules connected to out-of-building
extensions
• mandatory for digital station V2 and phone V2 modules
Tools required
• Manager PC
• Tools for rack mounting (optional)
Implementing the Avaya B5800 Branch Gateway November 2011 63
Hardware and software installation
Parts and equipment required
• External expansion module — each module is supplied with a suitable external power
supply unit and a 1m blue interconnect cable. 2m yellow interconnect cables are supplied
with the 4-Port expansion card and should only be used with that card.
• Power cord for the power supply unit
• Rack mounting kit (optional)
• Cable labeling tags
Connecting external expansion modules
About this task
Note:
External expansion modules should not be attached to a control unit that has power.
Procedure
1. If the system is being installed in a rack, attach the rack mounting kit to the
expansion module. See Rack mounting on page 61.
2. Attach the external expansion module's power supply but do not switch power on.
3. Connect the expansion interconnect cable from the module's EXPANSION port to
the EXPANSION port on the control unit. Make careful note of the port used and
include this detail on the cable label and any other system records.
64 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Grounding
Use of ground connections reduces the likelihood of problems in most telephony and data
systems. This is especially important in buildings where multiple items of equipment are
interconnected using long cable runs, for example phone and data networks.
All control units and external expansion modules must be connected to a functional ground.
Where the unit is connected to a power outlet using a power cord with an earth lead, the power
outlet must be connected to a protective earth.
In some cases, such as ground start trunks, in addition to being a protective measure this is a
functional requirement for the equipment to operate. In other cases it may be a locale regulatory
requirement and or a necessary protective step, for example areas of high lightning risk.
Warning:
During installation do not assume that ground points are correctly connected to ground. Test
ground points before relying on them to ground connected equipment.
Grounding
Additional protective equipment
In addition to grounding, additional protective equipment is required in the following
situations.
• On any digital station or phones external expansion module connected to an extension
located in another building. See
• In the Republic of South Africa, on all analog trunk external expansion modules (ATM16)
and on any control units containing an analog trunk cards (ATM4/ATM4U).
Tools required
• M4 cross-head screwdriver
• Tools suitable for crimping a cable spade
Parts and equipment required
• 14AWG solid copper wire for ground connection
• Cable sleeve matching local regulator requirements. Typically green for a functional
ground and green/yellow for a protective ground.
The ground point on control units and expansion modules are marked with a
Ground connections to these points should use a 14 A WG solid wire with either a green sleeve
for a functional ground or green and yellow sleeve for a protective ground.
Out of Building Telephone Installations on page 66.
or symbol.
B5800 Branch Gateway control unit
On control units the ground point is located above the RS232 DTE port.
Implementing the Avaya B5800 Branch Gateway November 2011 65
Hardware and software installation
External expansion modules
On expansion modules, the ground point is a 4mm screw located towards the right on the rear
of the module.
On some older modules, the dedicated ground point screw is not present. In those cases, the
top-center cover fixing screw (3mm) can be used as an alternative ground connection point.
A toothed washer should be added to ensure good contact.
Out-of-building connections/lightning protection
The following are the only supported scenarios in which wired extensions and devices outside
the main building can be connected to the B5800 Branch Gateway system. In these scenarios,
additional protection in the form of protective grounding and surge protectors must be fitted.
Warning:
The fitting of additional protection does not remove the risk of damage. It merely reduces
the chances of damage.
66 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Out-of-building connections/lightning protection
• Cables of different types, for example trunk lines, phone extensions, ground and power
connections, should be kept separate.
• All cabling between buildings should be enclosed in grounded ducting. Ideally this ducting
should be buried.
• A Primary Protection Box must be provided at the point where the cables enter the
building. This should be three point protection (tip, ring and ground). Typically this would
be gas tube protection provided by the local telephone company. The ground wire must
be thick enough to handle all the lines being affected by indirect strike at the same
time.
Connection type Protection device type Requirement
DS phone extensions
External expansion module
DS ports only.
Analog phone extensions
Phones external expansion
module (POT or Phone)
ports only.
Analog trunks ITWLinx towerMAX CO/4x4
ITWLinx towerMAX DS/2
Supports up to 4 connections.
(This device was previously
referred to as the Avaya
146E.)
Barrier box
Supports a single connection.
Maximum of 16 on any
expansion module.
Supports up to 4 two-wire
lines. (This device was
previously referred to as the
Avaya 146C.)
• Connection from the
expansion module to the
phone must be via a surge
protector at each end and
via the primary protection
point in each building.
• The expansion module,
control unit, and IROB
devices must be connected
to the protective ground
point in their building.
• The between building
connection must be via
earthed ducting, preferable
underground. The cable
must not be exposed
externally at any point.
For installations in the
Republic of South Africa, the
fitting of surge protection on
analog trunks is a
requirement.
For other locations where the
risk of lightning strikes is felt to
be high, additional protection
of incoming analog trunks is
recommended.
Implementing the Avaya B5800 Branch Gateway November 2011 67
Hardware and software installation
Connection type Protection device type Requirement
External output switch ITWLinx towerMAX SCL/8
(This device was previously
referred to as the Avaya
146G.)
The towerMAX range of devices are supplied by ITWLinx (http://www.itwlinx.com).
DS phone IROB installation
When digital phone extensions are required in another building, additional In-Range Out-OfBuilding (IROB) protective equipment must be used. For phones connected to B5800 Branch
Gateway DS ports, the supported device supplied by ITWLinx is a towerMAX DS/2 module.
This IROB device was previously referred to by Avaya as the 146E IROB.
The protection device should be installed as per the instructions supplied with the device. The
ground points on the control unit and the DS modules must be connected to a protective ground
using 18AWG wire with a green and yellow sleeve.
Typically the IROBs 2 RJ45 EQUIPMENT ports are straight through connected to the 2 RJ45
LINE ports. This allows existing RJ45 structured cabling, using pins 4 and 5, to be used without
rewiring for up to two DS connections. However each of these ports can be used to connect a
second extension using pins 3 and 6.
Connections from an Ext O/P
port to an external relay
device must be via a surge
protector.
LINE Signal EQUIPMENT
1 Not used 1
2 Not used 2
3 Ring II
(Optional)
4 Ring I 4
5 Tip I 5
6 Tip II
(Optional)
7 Not used 7
8 Not used 8
68 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
3
6
Analog phone barrier boxes
Where analog phone extensions are required in another building, phone barrier boxes and
protective earth connections must be used .
Warning:
PHONE (POT) ports on the front of control units must not be used for extensions that are
external to the main building.
• The correct B5800 Branch Gateway barrier boxes must be used. These modules have been
designed specifically for the signalling voltages used by the B5800 Branch Gateway system:
• Only the B5800 Branch Gateway phone barrier box should be used with phone V1
modules.
• Only the B5800 Branch Gateway phone barrier box V2 should be used with phone V2
modules.
• No other type of analog phone barrier box should be used.
Out-of-building connections/lightning protection
• Where more than 3 barrier boxes are required in a building, they must be rack mounted
using a barrier box rack mounting kit. See
Rack mounting barrier boxes on page 70.
• A maximum of 16 barrier boxes can be used with any phone module.
• The phone barrier box does not connect the ringing capacitor in phone V1 modules.
Main Building Barrier Box Secondary Building
• RJ11 — Connect to PHONE
(POT) port on the Phone
module using cable supplied
with the barrier box.
• RJ45 — Connect to the
secondary building barrier
box via primary protection in
both buildings.
• RJ11 — Connect to analog
phone. Cable not supplied.
• RJ45 — From main building
via primary protection in
both buildings.
Implementing the Avaya B5800 Branch Gateway November 2011 69
Hardware and software installation
Main Building Barrier Box Secondary Building
• Center screw — Connect to
main building protective
ground (or ground terminal of
Barrier Box Rack Mounting
Kit). Use 18AWG (minimum)
wire with a green and yellow
sleeve.
• Right-hand screw —
Connect to ground point on
Phone module using ground
cable supplied with barrier
box.
The following wires must be kept apart, that is, the wires cannot be routed in the same bundle:
• Earth leads from the barrier box to the phone modules.
• Internal wires, for example extension leads going directly to the phone modules.
• Wires from external telephone going directly to the barrier boxes.
Rack mounting barrier boxes
• Center screw — Connect
to main building protective
ground. Use 18AWG
(minimum) wire with a green
and yellow sleeve.
• Right-hand screw — Not
used.
About this task
Where more than 3 phone barrier boxes are used they must be rack mounted. The Barrier Box
Rack Mounting Kit (SAP Code 700293905) supports up to 8 phone barrier boxes.
Procedure
1. Unscrew the two screws arranged diagonally at the front of each barrier box and
use these same screws to reattach the barrier box to the rack mounting strip.
2. Each barrier box is supplied with a solid green ground wire connected to its
functional ground screw. Remove and discard this wire.
3. Connect a green/yellow ground wire to the protective earth screw in the center of
the point on the back of the barrier box.
4. The rack mounting strip has threaded M4 earthing pillars. Connect the other end of
the barrier box ground wire, using M4 washers and nuts, to the earthing pillar on
that side of the rack mounting strip.
70 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Administration software suite
5. Using 14AWG wire with green and yellow sleeve, connect one of the earthing pillars
to the buildings protective earth.
6. Using 14AWG wire with green and yellow sleeve, connect the other earthing pillar
to the phone module.
7. Ensure that the following wires are not routed together in the same bundle:
• Earth lead from the barrier box to the phone module.
• Internal wires, e.g. wires going directly to the phone module.
• Wires from external telephone going directly to the barrier boxes.
Administration software suite
The B5800 Branch Gateway administration software applications are installed on the
installation PC. They are used by installers and maintainers to configure, manage, and monitor
the B5800 Branch Gateway system.
The B5800 Branch Gateway administration applications are:
• Manager
B5800 Branch Gateway Manager is 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 system software files.
• System Status
The B5800 Branch Gateway System Status application is a monitoring and reporting tool
that provides a wide range of information about the current status of the system. It can
report the available resources and components within the system and details of calls in
Implementing the Avaya B5800 Branch Gateway November 2011 71
Hardware and software installation
progress. Details of the number of alarms are recorded and the time and date of the most
recent alarms.
• System Monitor
The B5800 Branch Gateway System Monitor application is a tool that shows details of all
activity on the B5800 Branch Gateway system. Because of the level of detail,
interpretation of System Monitor traces requires a high-level of data and telephony
protocol knowledge. Installers and maintainers must understand how to run System
Monitor when necessary as Avaya may request copies of System Monitor traces to
resolve support issues.
PC requirements
The minimum Microsoft® Windows® PC requirements for the B5800 Branch Gateway system
tools are provided in the following table. If other applications are to be installed on the PC then
those individual requirements should also be met.
Requirement Minimum Recommended
Processor 600MHz Pentium or AMD
Opteron, AMD Athlon64,
AMD Athlon XP.
RAM 128MB 256MB
HD Space 1GB - 800MB for .NET2,
200MB for Manager.
Display 800 x 600 - 256 Colors 1024 x 768 - 16-bit High
Operating System Supported on Windows® XP Pro, Windows® Vista, Windows
7, Windows® 2003 and Windows® 2008.
• 32-bit and 64-bit versions are supported.
• Vista support is only on Business, Enterprise and Ultimate
versions.
• Windows 7 support is only on Professional, Enterprise and
Ultimate versions.
800MHz Pentium or AMD
Opteron, AMD Athlon64,
AMD Athlon XP.
1.4GB - 800MB for .NET2,
600MB for the full B5800
Branch Gateway Admin
suite.
Color
®
Installing the administration applications
Procedure
1. Insert the B5800 Branch Gateway Administrator Applications DVD.
72 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Installer PC connection
2. Select B5800 Branch Gateway Administration Suite.
3. Double-click on setup.exe.
4. Select the language you want to use for the installation process.
This does not affect the language used by Manager when running.
5. Click Next.
6. Select who should be able to run the Administration Suite applications.
7. Click Next.
8. If required, select the destination to which the applications should be installed.
It is recommended that you accept the default destination.
9. Click Next.
The Custom Setup window appears.
10. Select the applications that you want to install. At a minimum select System
Monitor and Manager.
When you select an application, a description of the application appears. Click on
the next to each application to change the installation selection.
11. Click Next.
12. Click Install.
Installation of Windows .Net2 components may be required. If dialogs for this
appear, follow the prompts to install .Net.
13. If requested, reboot the PC.
Installer PC connection
During installation it is recommended that the B5800 Branch Gateway control unit be started
without it being connected to any network. That ensures that the B5800 Branch Gateway
defaults to a known set of IP address settings.
The B5800 Branch Gateway control unit is connected to the PC with a standard RJ45–RJ45
LAN cable.
Implementing the Avaya B5800 Branch Gateway November 2011 73
Hardware and software installation
Connecting the PC directly to the control unit
About this task
The default address for a B5800 Branch Gateway control unit LAN port is
192.168.42.1/255.255.255.0. Use this procedure to change the TCP/IP properties for the LAN
port on the PC and directly connect the PC to the control unit.
Procedure
1. Change the TCP/IP properties of the LAN port on the PC to the following:
2. Connect the LAN cable from the PC LAN port to the LAN or LAN1 port on the control
3. Check that the orange LED lamp on the control unit LAN port is on.
4. To test the connection before running Manager or the System Status application,
• Fixed IP address: 192.168.42.203
• Subnet mask: 255.255.255.0
• Default gateway: 192.168.42.1
Note:
While setting the PC to be a DHCP client could be used, this is not recommended
for performing more advanced functions such as firmware upgrades.
unit.
The green LED may also be flickering. This indicates traffic across the LAN
connection.
do the following:
a) Select Start > Run.
b) Enter cmd.
c) In the command window that appears, enter ping 192.168.42.1.
The results should show a number of ping replies from the B5800 Branch
Gateway . This confirms basic communication between the Manager PC and
the B5800 Branch Gateway .
74 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
d) If there are no ping replies, enter ipconfig.
The results should list the IP address settings of the Manager PC as required
above.
e) If the IP address settings of the Manager PC are displayed, enter exit and
check the cable connection.
Applying power to the system
Procedure
1. With the power off on the control unit, insert the B5800 Branch Gateway System
SD card into the System SD slot on the rear of the control unit.
Ensure that you have the correct card. The B5800 Branch Gateway System SD
card is required for branch operation. The card is labeled System SD BRANCH
GW.
Applying power to the system
2. Apply power to the external expansion modules.
The power outlet used must include a switch and in cases where the power cord
includes an earth lead, that outlet must have a protective earth connection.
3. Apply power to the control unit.
The power outlet used must include a switch and the power outlet must have a
protective earth connection.
When power is applied to the control unit, the following occurs:
• The control unit begins loading firmware from the System SD card with which
it will upgrade itself and the components installed in the control unit. This
process takes approximately a minute. The end of this process is indicated by
LED1 on each base card flashing every 5 seconds and LED9 on each base
card fitted with a trunk daughter card flashing every 5 seconds.
• The control unit will then begin upgrading the external expansion modules.
This is indicated by the red center LED on each module flashing red. The
process is completed when the LED changes to steady green.
Implementing the Avaya B5800 Branch Gateway November 2011 75
Hardware and software installation
• If a configuration file is already present on the System SD card, it is loaded by
the B5800 Branch Gateway. If not, the B5800 Branch Gateway creates a
default configuration based on the components of the system and copies that
configuration onto the System SD card.
You are now able to use Manager to access the B5800 Branch Gateway
configuration.
Control unit LEDs startup sequence
The LEDs on the rear of the control unit go through the following sequence during a normal
start up. Note that the times are approximate only.
LED 4s 4s 12s 5s 2s 5s 5s 10s 10s Finished
CPU Orng Grn Grn Grn Grn Grn Grn Grn Grn Grn
Red
SystemSDOrng Off Grn Grn Grn Off Grn Grn Grn Grn
Optional
SD
(if
present)
Orng = Orange Grn = Green
Orng Off Grn Grn Grn Off Off Grn Grn Grn
On the front of the control unit, LED1 on any IP500 base cards fitted is used as follows. LED9
is also used for any trunk daughter cards fitted.
LED 30s 30s Finished
Optional SD Red Red Red
About the LEDs
Flash
Fast Flash Flash every 5
seconds
Control unit LEDs
LED
Optional SD
76 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
• Off = card shutdown
Description
Applying power to the system
LED Description
System SD
CPU
• Green on = card present
• Green flashing = card in use
• Orange steady = reset imminent
• Red flashing = card initializing or shutting
down
• Red fast flashing = card full
• Red steady = card failure/wrong type
• Alternate red/green = starting up
• Green on = okay
• Red on = no software
• Flashing Red = error/shutdown
Base card LEDs
Base Card LEDs 1 to 8 Usage
All cards LED1 is used for base card status:
• Red on = error
• Red slow flash = initializing
• Red flash every 5 seconds = card okay
• Red fast flash = system shutdown
Analog phone No status LEDs are used for analog phone
extensions.
Digital station Green on = phone detected
VCM LEDs 1 to 8 are unlabelled. They are used to
indicate voice compression channel usage.
Each LED lit represents 12.5% of the
available voice compression channel
capacity in use (total card capacity rather
than licensed capacity).
4-port expansion LEDs 1 to 8 are used for the expansion ports
on the rear of the control unit. LEDs 9 to 12
are used for the card's own expansion
ports.
• Green on = expansion module present
• Red flashing = initializing
• Red on = error
• Orange regular flash = base card okay
Combination LEDs 1 to 6
Green on = phone detected
Implementing the Avaya B5800 Branch Gateway November 2011 77
Hardware and software installation
Trunk daughter card LEDs
Trunk Daughter Card LEDs 9 to 12 Usage
All cards LED 9 is used for daughter card status:
• Red on = error
• Red slow flash = initializing
• Red flash every 5 seconds = card okay
• Red fast flash = system shutdown
Analog trunk
BRI trunk
PRI trunk
External expansion module LEDs
External expansion module
• Green on =card fitted
• Green flashing = trunk in use
• Off = no trunk present
• Green on = trunk present
• Green flashing = trunk in use
• Off = no trunk present
• Green on = trunk present
• Green flashing = trunk in use
• Red/green fast flash (port 9) or greenfast
flash (port 10) = alarm indication signal
(AIS) from the trunk remote end
• Red with green blink (port 9) or green blink
(port 10): port in loopback mode (set
through System Monitor)
All modules
• Green on = module okay
• Red flashing = module starting up
• Red on = error
Starting Manager
About this task
B5800 Branch Gateway Manager is used to access all parts of the B5800 Branch Gateway
configuration. Different levels of access can be defined to control which parts of the
78 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Default configuration
configuration the Manager user can view and alter. Manager is also used to upgrade the system
software files.
Procedure
1. Select Start > Programs > IP Office > Manager.
If the PC has firewall software installed, you may be prompted as to whether you
want to allow this program to access the network.
2. If a prompt appears requesting permission to allow this program to access the
network, select Yes or OK.
3. From the menu bar, select File > Open Configuration.
The Select IP Office window appears. After a few seconds, the control unit should
be listed. The default name used for a newly installed control unit is its MAC address.
If the control unit is not found, the address used for the search can be changed.
4. If the control unit is not found, change the address for which to search as follows:
a) In the Unit/Broadcast Address field, enter or select the required address.
b) Click Refresh to perform a new search.
5. Click the check box next to the system and then click OK.
The name and password request is displayed.
6. Enter the name and password.
The name and password must match one of those setup through the security
settings. The default name and password for full configuration settings access is
Administrator and Administrator.
Default configuration
Unless you loaded a configuration file onto the System SD card, the B5800 Branch Gateway
system will be configured with default settings when the system is started.
Following are the basic default configuration settings for a B5800 Branch Gateway system.
Network Settings LAN1 LAN2/WAN
IP address 192.168.42.1 192.168.43.1
IP mask 255.255.255.0 255.255.255.0
DHCP mode server server
Number of DHCP IP
addresses
200 200
Implementing the Avaya B5800 Branch Gateway November 2011 79
Hardware and software installation
• Extensions and users — A user is automatically created for each physical extension
port detected in the system. Users are assigned extension numbers starting from 201.
User names take the form Extn201, Extn202, etc.
• Hunt group — A single hunt group 200 called Main is created and the first 10 users are
placed into that hunt group as members.
• Incoming call routes — Two default incoming call routes are created. Voice calls are
routed to the hunt group Main. Data calls are routed to the RAS user DialIn.
• Default short codes — A-Law or U-Law variant operation is determined by the Feature
Key installed in the control unit. Depending on the variant, different short codes and trunk
settings are added to the default configuration.
• A-Law or Mu-Law — Pulse Code Modulation (PCM) is a method for encoding voice as
data. In telephony, two methods of PCM encoding are widely used, A-law and Mu-law
(also called U-law). Typically Mu-law is used in North America and a few other locations
while A-law is used by the rest of the world. As well as setting the correct PCM encoding
for the region, the A-Law or Mu-Law setting of a B5800 Branch Gateway system when it
is first started affects a wide range of regional defaults relating to line settings and other
values. The encoding default is set by the type of Feature Key installed when the system
is first started.
Default DHCP/IP address settings
When a defaulted or new B5800 Branch Gateway control unit is switched on, it requests IP
address information from a DHCP server on the network. This operation will occur whether the
LAN cable is plugged in or not. The process below is done separately for both the LAN port
(LAN1 in the configuration) and the WAN port (LAN2 in the configuration) on the back of the
control unit.
• The B5800 Branch Gateway makes a DHCP request for what IP address information it
should use.
• If a DHCP server responds within approximately 10 seconds, the control unit defaults to
being a DHCP client and uses the IP address information supplied by the DHCP server.
Note:
For this installation, we have not yet connected the control unit to the network so a
DHCP server will not respond.
• If a DHCP server does not respond, the control unit defaults to being the DHCP server
for the LAN using the following settings:
• For its LAN1 it allocates the IP address 192.168.42.1 and IP Mask 255.255.255.0.
It supports 200 DHCP clients using the addresses range 192.168.42.2 and
192.168.42.201, the IP Mask 255.255.255.0 and default gateway address
192.168.42.1 (the control unit LAN1 address).
• For its LAN2 if supported, it allocates the IP address 192.168.43.1 and IP Mask
255.255.255.0.
• Note that the B5800 Branch Gateway does not check that these addresses are valid
and or available on the network.
80 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Important:
Once the control unit has obtained IP address and DHCP mode settings, it retains those
settings even if rebooted without a configuration file present on the System SD card. To fully
remove the existing IP address and DHCP mode setting the B5800 Branch Gateway must
be defaulted using Manager.
Changing the IP address settings
About this task
Use this procedure to change the system name, IP address, IP mask, or DHCP settings of the
B5800 Branch Gateway system. By default the B5800 Branch Gateway system name is set to
match its MAC address. The system name can be changed to something more distinctive. For
more information about the system default settings, see
that if you change the IP address settings, you must restart the system.
Procedure
Changing the IP address settings
Default configuration on page 79. Note
1. Start Manager and connect to the B5800 Branch Gateway system.
2. In the left navigation pane, click System.
3. On the System tab, in the Name field, enter a distinctive name for this B5800 Branch
Gateway system.
4. Click OK.
5. Click the LAN1 tab.
6. On the LAN Settings sub-tab, do the following:
a) Change the IP Address to match the customer requirements.
b) Change IP Mask to match the customer requirements.
c) Change DHCP Mode setting to match the customer requirements.
These settings are used for the LAN port on the back of the control unit.
7. Click OK.
8. Click the LAN2 tab.
9. On the LAN Settings sub-tab, do the following:
a) Change the IP Address to match the customer requirements.
b) Change IP Mask to match the customer requirements.
c) Change DHCP Mode setting to match the customer requirements.
These settings are used for the WAN port on the back of the control unit.
10. Click OK.
11. Select File > Save Configuration.
Implementing the Avaya B5800 Branch Gateway November 2011 81
Hardware and software installation
12. Reboot the system.
Connecting the control unit to the network
About this task
Once you have changed the B5800 Branch Gateway system default settings to those that
match the customer requirements, you can connect the B5800 Branch Gateway control unit
to the customer's network.
Procedure
1. Disconnect the LAN cable from the installer PC.
2. Connect the LAN cable to the customer network.
3. If you want to use the administration PC for on-going administration, connect the
PC to the customer network.
Default passwords
Do not change any other settings than those described below until you have read and
understood the Security Mode section of the IP Office Manager document. See Section 3.3
“The Security Mode Interface” in the IP Office Manager document for more information.
A B5800 Branch Gateway system's security settings can be set back to default if necessary.
See “Resetting an IP Office's Security Settings” in Section 3.5 “Editing Security Settings” in
the IP Office Manager document for more information.
Changing the security settings
Procedure
1. Start Manager and connect to the B5800 Branch Gateway system.
2. Select File > Advanced > Security Settings.
3. In the Select IP Office window, click the check box for the appropriate system.
4. Click OK.
82 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Default passwords
5. In the Security Service User Login window, enter a user name and password of an
account that has security configuration access to the B5800 Branch Gateway
system.
The defaults are security and securitypwd.
6. In the left navigation pane, click System.
7. Click the Unsecured Interfaces tab.
The password in the System Password field is used by Manager for remote
software upgrade of the B5800 Branch Gateway system. The default password is
password.
8. Next to the System Password field, click the Change button.
9. Enter a new password and click OK.
10. Click OK.
11. Click on Service Users.
The list shows the service user accounts that can access the system configuration.
The default service users Administrator, Manager and Operator each use the same
value (Administrator, Manager and Operator) as their password.
12. For each of these service users:
a) Click on the service user name.
b) In the Service User Details tab, click on Change and enter a new password.
c) Click OK.
d) Click OK.
13. Click on General.
The general security settings are displayed in the main display area.
14. Next to the Password field, click on Change and enter a new password for the
security administrator.
15. Click on File > Configuration to exit security configuration mode and return to the
B5800 Branch Gateway configuration.
Changing the remote user password
About this task
The B5800 Branch Gateway configuration contains a user whose password is used as the
default for remote dial-in access to the B5800 Branch Gateway network. Use this procedure
to change this user's password.
Procedure
1. Start Manager and connect to the B5800 Branch Gateway system.
Implementing the Avaya B5800 Branch Gateway November 2011 83
Hardware and software installation
2. In the left navigation pane, click User.
3. In the user list, click RemoteManager.
4. On the User tab, do the following:
a) In the Password field, enter a new password for the user.
b) In the Confirm Password field, enter the new password again.
5. Click OK.
6. Select File > Save Configuration.
Connecting phones
Procedure
1. Connect the analog phones to the phone ports.
2. Ensure that the analog phones that are connected to power failure ports are clearly
labeled as such.
3. Connect the Avaya digital phones to the appropriate DS ports.
When the control unit is started, after loading its own firmware and the firmware for
its external expansion modules, it will upload the appropriate firmware to the digital
phones.
Avaya H323 phones do not need to be connected at this stage. They will go through
a firmware upgrade process when connected to an B5800 Branch Gateway system
that is already running. Refer to the H323 IP Phone Installation Manual.
96x1 phones SIP firmware download in B5800 Branch Gateway centralized branch deployments
When Avaya SIP phones are deployed in the centralized branch deployment model, the
primary method for phone firmware download is centralized as well. In this mode the phones
get their settings file and firmware file from a central HTTP server.
However, if this method cannot be used, for example, due to WAN bandwidth concerns, an
alternative method may be used leveraging the B5800 Branch Gateway located in the branch
where the phones are located.
84 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
96x1 phones SIP firmware download in B5800 Branch Gateway centralized branch deployments
This section describes the process for 96x1 Series Phone SIP firmware download using the
B5800 Branch Gateway . The procedure required to replace the H.323 version of the firmware
to the SIP version is not covered here.
B5800 Branch Gateway support for SIP phone firmware download
This capability is made available in the B5800 Branch Gateway Release 6.1 SP2. Note that a
hidden B5800 system configuration parameter (the B5800 NoUser Source Number
‘ENABLE_SIP_FIRMWARE_DOWNLOAD’) needs to be configured.
Enabling the DHCP server on the B5800 Branch Gateway
About this task
Before upgrading the phones, a DHCP server has to be set up to provide the correct HTTP
server address to the phones. The preferred approach is for the DHCP server to be enabled
on each B5800 Branch Gateway. Perform this procedure on each B5800 Branch Gateway.
Procedure
1. Start Manager and connect to the B5800 Branch Gateway.
2. In the left navigation pane, click System.
3. Click the LAN tab.
4. In the LAN Settings tab, under DHCP Mode, click Server.
5. Click the Advanced button.
6. Click the Apply to Avaya IP Phones only check box to select this option.
About using external DHCP servers
As an alternative to enabling the DHCP server on each B5800 Branch Gateway , external DHCP
servers can be used if preferred. In this case, the DHCP server must be configured to provide
the IP address of each B5800 Branch Gateway as the HTTP server address in the Site-Specific
Option of the DHCP response to the phone.
The SIP phone configuration file 46xxsettings.txt has to be edited and then loaded to the B5800
Branch Gateway . This should be done as part of installation and does not have to be repeated
when upgrading to a new phone SIP firmware.
Implementing the Avaya B5800 Branch Gateway November 2011 85
Hardware and software installation
• SIP_CONTROLLER_LIST has to have the appropriate Avaya Aura® Session Manager IP
address as a primary SIP server.
• See Survivability settings on page 198 for the settings file parameters that are relevant
to B5800 Branch Gateway centralized branch deployment.
• HTTPSRVR IP address may have to be set to point to the B5800 Branch Gateway (if this
is not what is already provided to the phone via DHCP).
The SIP phone firmware load of the required version has to be obtained. It comes as a zip file
containing multiple files (tar, xml, txt).
Loading the SIP phone firmware to the B5800 Branch Gateway SD card
About this task
The SIP phone firmware must be loaded onto the B5800 Branch Gateway SD card. The entire
content of the zip file should be copied to the B5800 Branch Gateway . In particular, be sure to
load the phone upgrade file 96x1Supgrade.txt containing the correct name of the new firmware
files.
Loading the files to the B5800 Branch Gateway can be done using B5800 Branch Gateway
Manager, either locally in the branch or remotely where B5800 Branch Gateway Manager
connects from the NOC to the different branches and loads the files to each branch at a time.
The unzipped files have to be on the machine running B5800 Branch Gateway Manager.
Procedure
1. Start Manager and connect to the B5800 Branch Gateway.
2. Select File > Advanced > Embedded File Management.
3. Copy the files onto the B5800 Branch Gateway SD card in the System/Primary
folder.
Loading the SIP phone configuration file to the B5800 Branch Gateway SD card
About this task
The SIP phone configuration file (46xxsettings.txt) must be loaded onto the B5800 Branch
Gateway SD card. Loading the files to the B5800 Branch Gateway can be done using B5800
Branch Gateway Manager. Note that this file does not have to be modified and loaded to the
B5800 Branch Gateway again each time a new firmware for the SIP phone is available.
86 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
96x1 phones SIP firmware download in B5800 Branch Gateway centralized branch deployments
Procedure
1. Start Manager and connect to the B5800 Branch Gateway.
2. Select File > Advanced > Embedded File Management.
3. Copy the configuration file onto the B5800 Branch Gateway SD card.
About rebooting the phones
The phones must be rebooted to start the firmware download from the B5800 Branch Gateway .
Y ou can reboot the phones remotely from the Avaya Aura® System Manager in the NOC or by
power cycling the phones.
Rebooting the phones from Avaya Aura® System Manager
About this task
When upgrading from phones running firmware versions prior to R6.0 SP2, upgrade up to 10
phones in each branch at once. Once these phones finish, another set of up to 10 phones can
be rebooted to start the upgrade. If more than 10 phones try to download their firmware from
B5800 Branch Gateway at once, there is a risk that the download will not be successful on
some of phones. If this occurs, the phones that failed to download successfully should be
rebooted to try again.
When upgrading from phones running firmware versions R6.0 SP2 and later, simultaneous
upgrade of groups of up to 50 phones is supported.
Note:
This procedure must be performed in sunny day conditions when the phones are registered
to Session Manager.
Procedure
1. On the System Manager console, under Elements, click Session Manager.
2. Select System Status > User Registrations.
3. Use the Advanced Search Criteria option to find the phones to be upgraded.
Using the Location search criteria and specifying the branch location may provide
a convenient way to display all phones in a given branch, assuming Location is
administered in System Manager for all users. Alternatively, other criteria can be
used, including choosing the Address search criteria and specifying the leading
digits that are common to and unique to the users in that branch, or choosing the
IP Address search criteria and specifying the subnet IP address of the branch
Implementing the Avaya B5800 Branch Gateway November 2011 87
Hardware and software installation
4. In the list of users that is displayed, select the check box (on the left of each row)
for the users to be rebooted.
Note:
Multiple users can be selected by checking the boxes of multiple entries on the
list. For best results of the firmware download process, check multiple (up to 10)
users from the list to reboot them together in one action.
5. Click the Reboot button (located next to AST Devices Notification above the list
of users).
System Manager will notify Session Manager that will instruct each of the selected
phones to reboot. After the reboot, the phone will get in DHCP the address of the
local B5800 Branch Gateway in its branch as HTTP server, and will get its
configuration files (upgrade and settings files) and then download its firmware file
from the B5800 Branch Gateway. After the download completes successfully, the
phone will automatically restart using the new firmware.
6. Confirm that the firmware upgraded correctly by choosing one of the following
methods:
• From the phone craft menu, do the following:
1. Press the Mute button.
2. Enter the password, CRAFT# (27238#)
3. Scroll to the View option.
• From the phone user menu, do the following:
1. Select Home > Network Information > IP Parameters.
2. Scroll right 4 pages.
• Use a MIB browser to read the following two MIB items from the Avaya 96x1
SIP Phone MIB:
• endptAPPINUSE
• endptRFSINUSE
The MIB items from the A vaya 96x1 SIP Phone MIB are on the Avaya support
site at
https://support.avaya.com/css/appmanager/css/support/Downloads/
P0553/SIP%206.0.x/C2010 111895427550_1#files).
7. If the firmware download was not successful on a given phone, reboot the phone
again.
88 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
96x1 phones SIP firmware download in B5800 Branch Gateway centralized branch deployments
Rebooting the phones by power cycling the phones
About this task
This procedure can be performed in sunny day or rainy day conditions. The phones do not
need to be registered to Session Manager.
Procedure
To power cycle the phone, remove power to the phone, wait about one minute, then
reapply power.
Implementing the Avaya B5800 Branch Gateway November 2011 89
Hardware and software installation
90 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Chapter 5: Administration software suite
The B5800 Branch Gateway administration software applications are installed on the installation PC. They
are used by installers and maintainers to configure, manage, and monitor the B5800 Branch Gateway
system.
The B5800 Branch Gateway administration applications are:
• Manager
B5800 Branch Gateway Manager is 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 system software files.
• System Status
The B5800 Branch Gateway System Status application is a monitoring and reporting tool that
provides a wide range of information about the current status of the system. It can report the available
resources and components within the system and details of calls in progress. Details of the number
of alarms are recorded and the time and date of the most recent alarms.
• System Monitor
The B5800 Branch Gateway System Monitor application is a tool that shows details of all activity on
the B5800 Branch Gateway system. Because of the level of detail, interpretation of System Monitor
traces requires a high-level of data and telephony protocol knowledge. Installers and maintainers
must understand how to run System Monitor when necessary as Avaya may request copies of
System Monitor traces to resolve support issues.
Starting System Status
About this task
The B5800 Branch Gateway System Status application is a monitoring and reporting tool that
provides a wide range of information about the current status of the system. It can report the
available resources and components within the system and details of calls in progress. Details
of the number of alarms are recorded and the time and date of the most recent alarms.
Procedure
1. To start the System Status application, choose one of the following:
• On the PC where System Status has been installed, select Start > Programs
> IP Office > System Status.
Implementing the Avaya B5800 Branch Gateway November 2011 91
Administration software suite
The Logon window appears.
2. In the Logon window, enter the details of the B5800 Branch Gateway system to
which you want it to connect as follows:
a) In the Control Unit IP Address drop-down box, select the appropriate address,
b) In the Services Base TCP Port field, enter the Services Base TCP Port setting
c) In the Local IP Address field, enter the appropriate local IP address. If the PC
d) In the User Name field, enter a user name that has been configured for System
e) In the Password field, enter the appropriate password.
f) Check the Auto Reconnect check box if you want System Status to attempt to
• If Manager is also installed and is running, select File > Advanced > System
Status.
• Start a web browser and enter the IP address of the control unit. Then select
the System Status Application link.
or enter the IP address of the control unit.
that was set in the system's security settings. The default is 50804
has more than one IP address assigned to its network card or multiple network
cards, the address to use can be selected if necessary.
Status access in the B5800 Branch Gateway security settings.
reconnect using the same settings if connection to the B5800 Branch Gateway
is lost.
3. Click Logon.
Starting System Monitor
About this task
The B5800 Branch Gateway System Monitor application is a tool that shows details of all
activity on the B5800 Branch Gateway system. Because of the level of detail, interpretation of
System Monitor traces requires a high-level of data and telephony protocol knowledge.
Installers and maintainers must understand how to run System Monitor when necessary as
Avaya may request copies of System Monitor traces to resolve support issues.
Procedure
1. Select Start > Programs > IP Office > Monitor.
If System Monitor has been run before it will attempt to connect with the system
which it monitored previously.
2. To monitor a different system, select File > Select Unit.
The Select System to Monitor window appears.
92 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Starting System Monitor
3. In the Control Unit IP Address drop-down box, select the IP address of the control
unit you want to monitor.
4. In the Password field, enter the appropriate password.
Note:
You are able to set a System Monitor password using Manager. If the B5800
Branch Gateway does not have a System Monitor password set, System Monitor
uses the B5800 Branch Gateway System password. The System Monitor
password and System password are both set within the B5800 Branch Gateway
system security settings.
5. For Control Unit Type, select IP Office.
6. Click OK.
Implementing the Avaya B5800 Branch Gateway November 2011 93
Administration software suite
94 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Chapter 6: Initial configuration for a
Centralized Branch
This chapter provides initial configuration tasks required for each B5800 Branch Gateway branch deployed
in the Centralized Branch user model.
In the scenario where no survivable extensions are present and the same hardware is used at each
branch, the branches can use the same configuration except for branch prefix and IP address.
Communication Manager vs Communication Manager Feature Server
When an B5800 Branch Gateway is not hosting any survivable extensions, the Communication Manager
at the headquarters location is acting just as a trunk gateway for the branches and not also as a
Communication Manager Feature Server for survivable extensions.
Implementing the Avaya B5800 Branch Gateway November 2011 95
Initial configuration for a Centralized Branch
Centralized Branch configuration checklist
Use this checklist to monitor your progress as you configure a B5800 Branch Gateway system
deployed as Centralized Branch.
# Description Section
1 Launch Network Management and
start Network Management Console
to discover devices in your network.
Note:
This step applies only if you are
using Network Management to
configure the system.
2 Activate license files and deliver the
license files to the branches.
3 If you are not going to use Network
Management to configure the
branch, disable the Network
Management administration feature
for the branch.
4 Disable unused trunks. See Disabling unused trunks on
5 Set a trunk clock quality setting. See Setting a trunk clock quality setting on
6 Set trunk prefixes. See Setting the trunk prefixes on
See “Chapter 3: Discovering the Voice
Network” in Avaya Integrated Management
Release 6.0 Network Management
Configuration.
See Activating license files on page 98.
See Disabling the Network Management
administration feature for the branch on
page 103.
page 104.
page 106.
page 106.
7 Enable SIP trunk support. See Enabling SIP trunk support on
page 109.
8 Set the branch prefix and local
number length for the extension
numbering.
9 Change the default codec selection. See Changing the default codec
10 Change the maximum SIP sessions. See Changing the maximum SIP
11 Add a Session Manager line. See Adding an Avaya Aura Session
96 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
See Setting the branch prefix and local
number length for extension numbering on
page 110.
selection on page 112.
sessions on page 113.
Manager line on page 114.
Centralized Branch configuration checklist
# Description Section
12 Add a second Session Manager line
for redundancy.
13 Set up outgoing call routing.
14 Configure Modular Messaging as the
voicemail system the branch will use.
Survivable extensions cannot use
Embedded Voicemail or Voicemail
Pro.
Note:
Numbers 15 through 23 are performed from Avaya Aura®Session Manager.
B5800 Branch Gateway supports Session Manager 6.1 and 6.0 and procedures
for both versions are provided.
15 View a list of the SIP domains.
See Avaya Aura Session Manager line
redundancy on page 118.
• See Setting up outgoing call routing on
page 120.
• For information on routing back to the
branch for fallback alternate routes, see
Branch PSTN call routing examples on
page 325.
See Voicemail operation on page 163.
• For Session Manager 6.1, see Viewing
the SIP domains on page 150.
• For Session Manager 6.0, see Viewing
the SIP domains on page 156.
16 Create a location.
17 Create a digit adaptation.
18 Create a SIP entity.
19 Create an entity link.
• For Session Manager 6.1, see Creating
locations on page 150.
• For Session Manager 6.0, see Creating
locations on page 156.
• For Session Manager 6.1, see Creating
adaptations on page 151.
• For Session Manager 6.0, see Creating
adaptations on page 157.
• For Session Manager 6.1, see Creating
SIP entities on page 151.
• For Session Manager 6.0, see Creating
SIP entities on page 157.
• For Session Manager 6.1, see Creating
entity links on page 152.
• For Session Manager 6.0, see Creating
entity links on page 158
Implementing the Avaya B5800 Branch Gateway November 2011 97
Initial configuration for a Centralized Branch
# Description Section
20 Create a time range. For Session Manager 6.1 or 6.0, see
Creating time ranges on page 153.
21 Create a routing policy.
22 Create a dial pattern.
23 If you are going to use Network
Management to configure the
branch, you can create a System
Manager cut-through link to Network
Management.
24 Administer extensions See Extension administration on
Activating license files
• For Session Manager 6.1, see Creating
routing policies on page 153.
• For Session Manager 6.0, see Creating
routing policies on page 159
• For Session Manager 6.1, see Creating
dial patterns on page 154.
• For Session Manager 6.0, see Creating
dial patterns on page 160
For Session Manager 6.1 or 6.0, see
Creating a System Manager link to Network
Management on page 161.
page 173.
About this task
B5800 Branch Gateway uses the Avaya Product Licensing and Delivery System (PLDS) to
manage license entitlements. When you access PLDS and activate a license file, you are given
the opportunity to save the license file to the local PC. Once saved on the local PC, you can
send the license file to the branch in two ways — either through Provisioning and Installation
Manager (PIM) or Manager. If using PIM, you load the license file to PIM and then create a job
to send the license file to the B5800 Branch Gateway device. If using Manager, you select a
locally saved license file and then upload the license file to the B5800 Branch Gateway
device.
PIM provides a bulk provisioning feature where you can use a mapping file that contains a list
of comma separated key value pairs of B5800 Branch Gateway IP addresses and license file
names, one pair for each branch, to send licenses to multiple branches simultaneously. The
license file names are based on the Feature Key (FK) serial number on the SD cards. See
Creating a mapping file on page 102 for more information.
Note:
B5800 Branch Gateway supports a 30-day grace period during which time the system is
fully functional if a license error is detected or if a license file cannot be obtained, for example
due to loss of WAN connectivity.
98 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Procedure
Activating license files
1. See
2. Depending upon which method you want to use to deliver the activated license files
Activating license entitlements on page 209 to generate the licenses.
to each branch, see one of the following:
Using Manager to deliver license files to the branches on page 99.
• See
Using Provisioning and Installation Manager to deliver license files to the
• See
branches on page 100.
Using Manager to deliver license files to the branches
Before you begin
License files have been activated. See Activating license entitlements on page 209.
About this task
Y ou can use Manager to distribute activated license files to B5800 Branch Gateway sites. This
procedure explains how to distribute the license files to a single branch at a time.
Procedure
1. Start Manager and connect to the B5800 Branch Gateway system.
2. In the left navigation pane, select PLDS License.
3. Right-click PLDS License and select Send license file to IP Office.
4. In the Upload Files window, select the PLDS license xml file.
Manager copies the license file to the B5800 Branch Gateway SD card where it is
validated and stored for persistent use.
5. Select File > Close Configuration.
6. To view the license, select File > Open Configuration.
Deleting the PLDS license file from the branch
Procedure
1. Start Manager and connect to the B5800 Branch Gateway system.
2. In the left navigation pane, select PLDS License.
3. Right-click PLDS License and select Delete PLDS License file from Avaya
Branch Gateway.
Implementing the Avaya B5800 Branch Gateway November 2011 99
Initial configuration for a Centralized Branch
4. Select File > Close Configuration.
Using Provisioning and Installation Manager to deliver license files to the branches
Before you begin
License files have been activated. See Activating license entitlements on page 209.
About this task
Use this procedure to load the license files to Provisioning and Installation Manager (PIM) and
then create a job to send the license files to the B5800 Branch Gateway branches. You can
send license files to a single branch or to multiple branches simultaneously. You can also
schedule when you want the job to run.
Procedure
1. From the A vaya Integrated Management Launch Products page, click Provisioning
and Installation Manager for IP Office.
2. From the Provisioning and Installation Manager main window, select
Administration > Licenses in the left panel.
3. Click Add.
4. In the PIM – Upload License file window, click the Browse button and select the .xml
license file.
5. Click the Upload file button.
The license file is uploaded to PIM and appears in the License Files List.
Note:
The license file is now stored in the Network Management server file system
under \Program Files\Avaya\Network Management\CSV\IPOLicenses. PIM
renamed the license file name to the format <host ID of the SD card>_HID.xml,
for example 111306312781_HID.xml. The host ID is the Feature Key (FK) serial
number printed on the SD card. PIM renames the license file to one that identifies
the respective device. If you have multiple license files, once you upload all the
license files, you can create a mapping file for bulk distribution. See Creating a
mapping file on page 102 for more information.
6. T o send the license file to the branch, from the Provisioning and Installation Manager
main window, click Import Licenses at the top of the window.
The Import Licenses Job Wizard appears.
7. On the General page, do the following:
a) In the Job Name field, enter a name for this job.
b) In the Notes field, enter notes about this job.
100 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com
Loading...