Avaya B5800 Configuration manual

Implementing Avaya B5800 Branch
Gateway for a Communication Server 1000
Configuration

Release 6.2

03-604053

Issue 3

October 2012

©

2012 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
websites 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 website:
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. “Software” means computer
programs in object code, provided by Avaya or an Avaya Channel
Partner, whether as stand-alone products or pre-installed on hardware
products, and any upgrades, updates, bug fixes, or modified versions
thereto.

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”).

HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE

http://support.avaya.com. Please note that if

Avaya grants you a license within the scope of the license types
described below, with the exception of Heritage Nortel Software, for
which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
applicable license will be a Designated System License. The applicable
number of licenses and units of capacity for which the license is granted
will be one (1), unless a different number of licenses or units of capacity
is specified in the documentation or other materials available to you.
“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.

License types

Designated System(s) License (DS). End User may install and use
each copy of the Software only on a number of Designated Processors
up to the number indicated in the order. Avaya may require the
Designated Processor(s) to be identified in the order 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 Software
may contain software (including open source software) distributed
under third party agreements (“Third Party Components”), which may
contain terms that expand or limit rights to use certain portions of the
Software (“Third Party Terms”). Information regarding distributed Linux
OS source code (for those product that have distributed Linux OS
source code) and identifying the copyright holders of the Third Party
Components and the Third Party Terms that apply is available in the
Documentation or on Avaya’s website at:

Copyright. Y ou agree to the Third Party Terms for any such Third Party

Components.

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 [phone] for the United States
and Canada. For additional support telephone numbers, see the Avaya
Support website:
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to: [e-mail].

Trademarks

Avaya is a registered trademark of Avaya Inc.
Aura is a registered trademark of Avaya Inc.

http://support.avaya.com. Suspected security

http://support.avaya.com/

2 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

All non-Avaya trademarks are the property of their respective owners,
and “Linux” is a registered trademark of Linus Torvalds.

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 website:

Contact Avaya Support

See the Avaya Support website:
notices and articles, or to report a problem with your Avaya product.
For a list of support telephone numbers and contact addresses, go to
the Avaya Support website:
bottom of the page, and select Contact Avaya Support.

http://support.avaya.com.

http://support.avaya.com for product

http://support.avaya.com, scroll to the

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 3

4 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

Contents

Chapter 1: B5800 Branch Gateway overview...................................................................

PSTN trunking configurations...................................................................................................................

Voicemail support options.........................................................................................................................

Management.............................................................................................................................................

About upgrading B5800 Branch Gateways...............................................................................................

Licensing...................................................................................................................................................

B5800 Branch Gateway licenses..............................................................................................................

License modes..........................................................................................................................................

System components..................................................................................................................................

Supported telephones...............................................................................................................................

Software applications................................................................................................................................

Supported country locales........................................................................................................................

Related resources.....................................................................................................................................

Related documents..........................................................................................................................

Avaya Mentor videos........................................................................................................................

Training.............................................................................................................................................

Web sites..........................................................................................................................................

Revision history.........................................................................................................................................

Chapter 2: CS 1000 and B5800 Branch Gateway deployments......................................

Option 1.....................................................................................................................................................

Option 2.....................................................................................................................................................

Configuration considerations....................................................................................................................

Chapter 3: Planning............................................................................................................

Prerequisites.............................................................................................................................................

Dial plan considerations............................................................................................................................

Dial plan example......................................................................................................................................

Voicemail considerations...........................................................................................................................

Branch PSTN call routing considerations.................................................................................................

Network assessment for VoIP requirements.............................................................................................

Unified Communications Management and System Manager integration................................................

Chapter 4: 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 5: Hardware and software installation................................................................

13
13
14
14
16
16
18
19
20
23
26
27
29
29
30
30
30
31

33
34
35
35

37
37
38
38
39
40
41
42

43
43
44
46
46
46
48
49
50
50
51
52
52

55

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 5

Installation checklist..................................................................................................................................

Tools and equipment required...................................................................................................................

Unpacking equipment...............................................................................................................................

SD card preparation..................................................................................................................................

Upgrading the card firmware............................................................................................................

Creating a configuration file..............................................................................................................

Adding a configuration file................................................................................................................

Adding music-on-hold files...............................................................................................................

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................................................................................................................................

Default configuration.................................................................................................................................

Connecting the control unit to the network................................................................................................

Connecting phones...................................................................................................................................

Chapter 6: About preserving staged button programming for BST phones.................

Configuring a short code to preserve the user extension configuration....................................................

Remotely forcing a BST phone to return to default settings.....................................................................

Other DCP short codes.............................................................................................................................

Chapter 7: Upgrading an R6.2 system with an R6.2 service pack..................................

R6.2 service pack installation checklist.....................................................................................................

Remote Software Library for B5800 Branch Gateway upgrades..............................................................

System requirements for the external server...................................................................................

Setting up the external server to work as a remote software library for B5800 upgrades................

Getting inventory.......................................................................................................................................

Setting B5800 Branch Gateway SNMP attributes............................................................................

Configuring user PLDS access.................................................................................................................

Creating a software library........................................................................................................................

Upgrading the B5800 Branch Gateway using System Manager...............................................................

Chapter 8: Administration software suite.........................................................................

55
56
57
58
58
59
60
60
61
61
63
65
67
69
71
72
73
74
76
77
78
79
80
81
81
82
83
84
85
87
88
89

91
91
92
93

95
95
96
96
97
98
98
99
100
101

103

6 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Starting System Status..............................................................................................................................

Starting System Monitor............................................................................................................................

Chapter 9: Initial branch configuration.............................................................................

Configuration checklist..............................................................................................................................

Setting up System Manager to launch IP Office Manager........................................................................

Installing IP Office Manager from the System Manager server to a PC...........................................

Activating license files...............................................................................................................................

Installing the shared PLDS license file on the System Manager WebLM server..............................

Using Manager to deliver license files to the branches....................................................................

Using Embedded File Management to install a PLDS license.........................................................

Performing a certificate exchange between CS 1000 and Session Manager...........................................

Exporting the System Manager certificate........................................................................................

Exporting the CS 1000 security certificate.......................................................................................

Adding System Manager as a certificate authority...........................................................................

Generating a certificate on System Manager............................................................................................

Using the Initial Installation Utility..............................................................................................................

Additional features configured by the Initial Installation Utility..........................................................

Configuring the B5800 Branch Gateway for certificates...........................................................................

About adding B5800 Branch Gateways to System Manager....................................................................

Discovering B5800 Branch Gateways..............................................................................................

Bulk importing of devices.................................................................................................................

Adding the B5800 Branch Gateways to System Manager...............................................................

Enabling WebLM licensing for the branch.................................................................................................

Creating a system template......................................................................................................................

Uploading an auto attendant audio file.....................................................................................................

Applying the system template...................................................................................................................

Creating an endpoint template..................................................................................................................

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....................................

Enabling branch SIP extension support....................................................................................................

SIP Registrar tab field descriptions..................................................................................................

Chapter 10: Managing B5800 Branch Gateways from System Manager.......................

Editing a B5800 Branch Gateway system configuration from System Manager.......................................

Restrictions when editing a B5800 Branch Gateway system configuration from System Manager.

About disabling the System Manager administration feature for a B5800 Branch Gateway....................

103
104

107
107
111
113
114
115
115
116
117
118
118
118
119
121
123
124
126
126
128
130
131
131
132
133
133
135
136
137
138
138
140
140
141
144
145
146
152
153
155
156
157

159
159
160
161

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 7

Disabling the System Manager administration feature for the branch from System Manager.........

Disabling the System Manager administration feature for the branch from IP Office Manager........

Enabling the Security Settings option for the branch.......................................................................

Synchronizing B5800 Branch Gateway with System Manager.................................................................

Configuration changes performed through Manager that cannot be synced with System Manager

Chapter 11: Session Manager Configuration...................................................................

Viewing the SIP domains..........................................................................................................................

Creating locations.....................................................................................................................................

Creating adaptations.................................................................................................................................

Creating SIP entities.................................................................................................................................

Creating entity links...................................................................................................................................

Creating time ranges.................................................................................................................................

Creating routing policies............................................................................................................................

Creating dial patterns................................................................................................................................

Chapter 12: Voicemail configuration.................................................................................

Voicemail options......................................................................................................................................

Configuring Embedded Voicemail.............................................................................................................

Configuring Standalone Voice Mail...........................................................................................................

Configuring B5800 Branch Gateway to use Avaya Aura Messaging for voicemail...................................

Configuring B5800 Branch Gateway to use CallPilot for voicemail..........................................................

Configuring CallPilot and CS 1000 to send MWI in a SIP NOTIFY message to the user................

Modular Messaging and Avaya Aura Messaging PSTN Fallback.............................................................

Adding an overriding short code...............................................................................................................

Uploading an auto attendant audio file.....................................................................................................

Chapter 13: User administration........................................................................................

Adding distributed users to System Manager...........................................................................................

Editing the B5800 Branch Gateway Endpoint Profile for a user...............................................................

Chapter 14: Managing license files with PLDS................................................................

PLDS Overview.........................................................................................................................................

Registering for PLDS................................................................................................................................

About license activation............................................................................................................................

Activating license entitlements.........................................................................................................

Searching for license entitlements............................................................................................................

Moving activated license entitlements......................................................................................................

Regenerate License files..........................................................................................................................

Regenerating a license file...............................................................................................................

Chapter 15: Standalone SAL Gateway for remote service..............................................

Use of SAL to access the B5800 Branch Gateway administration tools and System Manager...............

SAL Gateway installation and registration................................................................................................

B5800 Branch Gateway registration and SAL Gateway on-boarding.......................................................

B5800 Branch Gateway SAL-based alarming..........................................................................................

Universal Install/SAL Registration Request Form.....................................................................................

Chapter 16: Additional system procedures......................................................................

Changing the IP address settings.............................................................................................................

Default passwords.....................................................................................................................................

Changing the security settings.........................................................................................................

Changing the remote user password...............................................................................................

162
162
163
164
164

167
168
168
169
169
170
171
171
172

173
173
174
175
177
179
181
182
182
184

187
187
189

191
191
192
192
193
195
197
199
199

201
201
202
203
203
204

205
205
206
206
207

8 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

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...............................................................................................

Creating a backup of the system configuration using IP Office Manager.................................................

Creating a backup of the system configuration using System Manager...................................................

Upgrades using IP Office Manager...........................................................................................................

Using the upgrade wizard.................................................................................................................

Restoring the system configuration using System Manager.....................................................................

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.....................................................................................................................................

Creating a WAN link.........................................................................................................................

Chapter 17: SD card management.....................................................................................

Booting from the SD cards........................................................................................................................

About creating a B5800 Branch Gateway SD card...................................................................................

Formatting an SD card.....................................................................................................................

Formatting a System SD card using the System Status application................................................

Recreating an SD card.....................................................................................................................

Viewing the card contents.........................................................................................................................

About backing up the System SD card.....................................................................................................

208
208
209
209
209
210
211
211
212
212
213
213
214
214
215
215
216
217
217
218
219
220
221
222
223
223
224
226
227
230
231
232
232
233
236
236
237
240
241

243
246
248
248
249
249
250
250

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 9

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........................................................................

Memory card startup.................................................................................................................................

Starting up a memory card using Manager......................................................................................

Starting up a memory card using System Status.............................................................................

Starting up a card using a system phone.........................................................................................

Chapter 18: 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: Avaya port matrix for B5800 Branch Gateway and SIP phones...............

What are ports and how are they used?...................................................................................................

Port type ranges........................................................................................................................................

251
251
252
252
252
253
253
254
254
254
255
255
256
256
257
257
258
259
259
260
261
261
262
262
263
263
263
264

265
265
265
266
266
267
267
268
269
269
270
271
272
272
272
274

277
277
277

10 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

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 B: B5800 Branch Gateway call flows...............................................................

Appendix C: Branch PSTN call routing examples...........................................................

Centralized call control..............................................................................................................................

Routing B5800 Branch Gateway calls — example...........................................................................

Branch PSTN override..............................................................................................................................

Adding an overriding short code.......................................................................................................

PSTN trunk fallback..................................................................................................................................

Configuring PSTN trunk fallback......................................................................................................

Appendix D: Authorization codes.....................................................................................

Enabling authorization codes in Manager.................................................................................................

Force authorization codes.........................................................................................................................

About entering an authorization code.......................................................................................................

Authorization code configuration settings.................................................................................................

Appendix E: Recommended courses for Avaya B5800 Branch Gateway training.......

Recommended courses............................................................................................................................

Appendix F: T7000 and M7000 Series Digital Deskphones.............................................

Features available on the T7000 and M7000 Series Digital Deskphones................................................

Appendix G: 1100 Series and 1200 Series IP Deskphones.............................................

Features available on the 1100 Series and 1200 Series SIP 4.3 phones.................................................

Glossary...............................................................................................................................

Index.....................................................................................................................................

278
279
280
280
281
283
285
287

289
291

291
292
294
294
296
297

301
302
303
303
304

305
305

309
310

313
314
317

319

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 11

12 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Chapter 1: B5800 Branch Gateway

overview

The Avaya B5800 Branch Gateway is a flexible, cost-effective communications platform for enterprise
branch offices. It enables access via SIP to Avaya Aura® Session Manager in the enterprise center,
optional access to centralized PSTN trunking, and access to centralized applications, such as
conferencing, messaging, and more. The B5800 Branch Gateway solution provides centralized
management by Avaya Aura® System Manager and centralized licensing by WebLM.

B5800 Branch Gateways are deployed in the distributed branch user model. In the distributed branch user
model, call processing for the branch phones is provided locally. Non-IP phones are connected to the
B5800 Branch Gateway and IP and certain SIP endpoints (not including the A vaya 9600 SIP phones) can
be administered with B5800 Branch Gateway as their controller (see
for more information). Access to and from the rest of the Avaya 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 PSTN trunking, and to
centralized applications such as conferencing and A vaya Aura® Messaging. The centralization capability
is based primarily on the infrastructure at the enterprise core. 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.

Supported telephones on page 23

Beginning in R6.2, B5800 Branch Gateway is supported in an Avaya Communication Server 1000 (CS

1000) configuration. B5800 Branch Gateway can be deployed as a new branch in an existing CS 1000
configuration or as a replacement for Business Communications Manager (BCM) as a branch office in a
CS 1000 branch office model. In these deployments, B5800 Branch Gateway operates as a distributed
branch.

Note:

Integration of B5800 Branch Gateway in an Avaya Aura® configuration is provided in a separate
document. See Implementing the Avaya B5800 Branch Gateway for an Avaya Aura® Configuration,
document number 18-603853.

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
it can be configured to make and receive external calls via the central Avaya Aura®Session
Manager or NRS. A combination of these methods can be used for PSTN calls based on the

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 13

B5800 Branch Gateway overview

call type (local, national, international), time of day or even individual user. See Branch PSTN

call routing examples on page 291 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 to
service local PSTN trunks. Standalone Voice Mail is also available for B5800 Branch Gateway
systems when additional port capacity is required. A centralized voicemail system, either CS
1000 CallPilot or Avaya Aura Messaging connected via Session Manager, can also be
configured. When using CallPilot or A vaya Aura Messaging, you are still able to use Embedded
Voicemail or Standalone Voice Mail at each branch to provide auto-attendant operation and
announcements for waiting calls. For more information, see

Voicemail options on page 173.

Management

The primary method for configuring and managing the branches in a B5800 Branch Gateway
system is centrally using Avaya Aura® System Manager R6.2. Avaya Aura® System Manager
is a central management system that delivers a set of shared management services and a
common console for different components of the Avaya Aura® solution. System Manager
provides a single access interface to administer multiple branch locations and multiple
distributed B5800 Branch Gateway users. System Manager also launches IP Office Manager
in the appropriate mode where you can remotely administer individual B5800 Branch
Gateways.

As an alternative to System Manager, you can use IP Office Manager that is directly connected
to the B5800 Branch Gateway to configure a branch locally when you need to administer an
isolated branch or System Manager is not available. IP Office Manager is an application for
viewing and editing a B5800 Branch Gateway system's configuration. It is included in the
B5800 Branch Gateway administration software suite. Manager is an off-line editor . It receives
a copy of the system's current configuration settings. After changes are made to that copy and
the file is saved, Manager automatically sends the file back to the system for those changes
to become active.

Avaya Aura® System Manager

Using Avaya Aura® System Manager R6.2, you are able to:

• Upgrade B5800 Branch Gateway systems.

• Add B5800 Branch Gateway devices from the network to System Manager.

• Create B5800 Branch Gateway endpoint templates that are used to create B5800 Branch
Gateway users. These templates can be edited, duplicated, or deleted.

14 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

Management

• Create B5800 Branch Gateway system configuration templates that can be applied to
selected B5800 Branch Gateway systems. These templates are used for initial device
provisioning. These templates can be edited, duplicated, or deleted.

• Upload and convert audio files to System Manager to be used in the B5800 Branch
Gateway System Configuration Auto Attendant feature.

• Manage B5800 Branch Gateway system configurations. From System Manager, you are
able to launch IP Office Manager to view or edit a system configuration. With this feature,
you make changes to the B5800 Branch Gateway device through System Manager. You
are able to apply the changes immediately or schedule the changes to run at a specified
time.

• Manage B5800 Branch Gateway security configuration. From System Manager, you are
able to launch IP Office Manager to view or edit a system security configuration. With this
feature, you make changes directly to the B5800 Branch Gateway device.

• Create B5800 Branch Gateway user templates. These templates can be edited or
deleted.

• Perform a B5800 Branch Gateway backup with the option of storing the backup output in
System Manager or creating a local backup where the system stores the backup output
on the local storage attached to the B5800 Branch Gateway device.

• Perform a B5800 Branch Gateway restore. This feature allows you to restore:

- a saved B5800 Branch Gateway system configuration onto a B5800 Branch
Gateway from System Manager.

- a backup of a B5800 Branch Gateway system configuration onto a B5800 Branch
Gateway from the device SD card.

- users from System Manager to the B5800 Branch Gateway.

- a saved B5800 Branch Gateway system configuration and user from System
Manager onto a B5800 Branch Gateway.

• View events and alarms regarding various operations that occur on the B5800 Branch
Gateway.

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 15

B5800 Branch Gateway overview

About upgrading B5800 Branch Gateways

With the introduction of centralized management provided by Avaya Aura® System Manager,
you are able to upgrade B5800 Branch Gateway firmware and software from System Manager.
You are also able to upgrade an individual B5800 Branch Gateway system from IP Office
Manager installed on an administration PC that is connected directly to the system. You can
perform an upgrade from IP Office Manager using the upgrade wizard or the System SD
card.

For more information about these upgrade methods, see the following topics:

•

Upgrading the B5800 Branch Gateway using System Manager on page 101

• Using the upgrade wizard on page 219

• System upgrade using the System SD card on page 258

Licensing

B5800 Branch Gateway supports centralized licensing by WebLM where a single license file
is generated in Avaya Product Licensing and Delivery System (PLDS) for multiple branches.

16 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

Licensing

Support for individual PLDS license files for each branch (the licensing method provided in
B5800 Branch Gateway R6.1) is also an option. WebLM licensing is the recommended method
for B5800 Branch Gateway R6.2 and higher. Both licensing methods are described below.

WebLM license management

B5800 Branch Gateway R6.2 supports WebLM licensing in which a single license file is
generated in PLDS for multiple branches. This license file contains the host ID of the WebLM
server and is managed by the WebLM server. Each B5800 Branch Gateway communicates
with the WebLM server to request the required license entitlements. B5800 Branch Gateway
uses the Avaya Aura System Manager WebLM server.

Two configuration models are supported:

• WebLM standard licensing model — in this model, one WebLM server is used. This model
is used for enterprises where the System Manager WebLM server is able to manage all
B5800 Branch Gateway licenses required for the enterprise.

• WebLM enterprise licensing model — in this model, multiple WebLM servers are used.
This model is used for enterprises where the licenses required for all branches in the
enterprise exceed the System Manager WebLM server capacity . One WebLM server acts
as a master WebLM server and hosts the license file from PLDS. The other WebLM
servers(s) act as a local WebLM server and host allocation license files from the master
WebLM server. Each B5800 Branch Gateway must be configured with the IP address of
one of the WebLM servers.

Note:

The expected System Manager WebLM server capacity is about 400 branches on a loaded
System Manager. The capacity would be higher on a lightly loaded System Manager. The
expected WebLM capacity on a standalone Linux server is about 1,100 branches. Large
deployments that exceed the System Manager WebLM capacity require additional
standalone WebLM server(s) and configuration of the WebLM servers as master and local
in the WebLM enterprise licensing model.

Note:

The correct expiration time of licenses for a B5800 Branch Gateway that uses a local WebLM
server is provided on the corresponding master WebLM server. The local WebLM server
shows the licenses as having an expiration time of 30 days or less. However, periodically
the license expiration time on the local WebLM server is automatically refreshed and
extended when the master WebLM server pushes a refreshed Allocation License File to the
local WebLM.

For more information about WebLM licensing, see Administering Avaya WebLM (standalone)
and Avaya WebLM Administration Guide.

Separate PLDS license for each branch

In B5800 Branch Gateway R6.1, an individual PLDS license file was required for each branch
and installed on each branch directly . A WebLM server was not required. This licensing method
is supported in B5800 Branch Gateway R6.2 for branches that cannot be connected via an
enterprise WAN to a central WebLM server or for migration of installed B5800 Branch Gateway
R6.1 systems. Using the WebLM licensing method is recommended, but does not have to be
done as part of an R6.1 to R6.2 upgrade.

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 17

B5800 Branch Gateway overview

For the separate PLDS licensing method, branch licenses are issued and validated against
the Feature Key serial number of the System SD card used by that B5800 Branch Gateway.
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 IP Office Manager application, this number
appears in the PLDS Host ID field on the System page when you select System > System.

B5800 Branch Gateway licenses

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. One Avaya Branch Gateway
System Software license is required.

Native Station licenses

All users on a B5800 Branch Gateway system must be licensed by the addition of Native
Station licenses. Native Station licenses are required for all configured users with analog,
digital, H.323 or DECT extensions; for users without any extension; and for all users with SIP
extensions set as native (or local) (that is, extensions operating in the distributed branch user
model).

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 options,
Embedded Voicemail or Standalone Voice Mail. The Embedded Messaging Ports license is
also used to control the number of ports on systems where Call Pilot is configured as the central
voicemail system and the local Embedded Voicemail provides auto attendant operation. For
Embedded Voicemail, up to 6 ports can be licensed. For Standalone Voice Mail, up to 40 ports
can be licensed. At least one Embedded Messaging Port license must be purchased to enable
this service.

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
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

18 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

License modes

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 120­day 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, except for
administration that fixes the licensing errors.

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 IP Office Manager.

License Normal Mode

No license errors are present. The B5800 Branch Gateway can access the WebLM server and
obtain the required license entitlements. If the licensing method is used where an individual
PLDS license file is required for each branch, a valid license file is installed on the B5800
Branch Gateway with sufficient entitlements.

License Error Mode

One or more license errors are present. The B5800 Branch Gateway initiates a 30–day license
grace period during which time the system issues errors and alarms, but continues to provide
normal operation as in License Normal Mode. Calls are allowed and/or blocked based on
current configuration parameters and configured users can register, regardless of licensing
status. The 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 license
capacities.

License Restricted Mode

One or more license errors are present and the 30–day license grace period has expired.
B5800 Branch Gateway prevents any administrative changes except those that fix the licensing
errors. While administration is restricted, dynamic system operation (such as making calls)
continues based on the current configuration parameters, regardless of licensing status.

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 19

B5800 Branch Gateway overview

System components

The B5800 Branch Gateway system is comprised of the following hardware components.

• B5800 Branch Gateway control unit — B5800 Branch Gateway is supported on the
IP500v2 platform or on the B5800 Branch Gateway hardware platform which is based on
IP500v2. The B5800 Branch Gateway 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 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.

• B5800 Branch Gateway System SD card — The B5800 Branch Gateway System SD
card is a specific Avaya SD card that is required. It determines the system operation as
B5800 Branch Gateway. It is uniquely numbered and has a serial number that must be
used as the Host ID in the PLDS license file if the B5800 Branch Gateway is operating
with an individual license file and not with WebLM licensing. The B5800 Branch Gateway
System SD card 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

20 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

System components

expansion modules on page 22 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.

- TCM 8 card — This card provides 8 digital station ports (1-8).

• 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 B­channels, 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

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 21

B5800 Branch Gateway overview

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.

• 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).

22 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

Supported telephones

Telephone Native extensions (local extensions operating

Analog
1120E SIP
1140E SIP
1220 SIP
1230 SIP
1403 digital
1408 digital
1416 digital

Supported telephones

in the distributed branch user model)

1603
1603SW
1608
1616
1603SW-I
1608-I
1616-I
BM32 (DSS)
2402D
2410D
2420
3616 wireless
3620 wireless
3626 wireless
3641 wireless
3645 wireless

1

3720 DECT R4
3725 DECT R4

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 23

B5800 Branch Gateway overview

Telephone Native extensions (local extensions operating

3740 DECT R4
3749 DECT R4
3810 digital wireless
4601
4602IP
4602SW
4610IP
4610SW
4621
4625
5402
5410

in the distributed branch user model)

5420
EU24 (DSS)
5601
5602IP
5602SW
5610IP
5610SW
5620
5621
EU24 BL (DSS)
9504 digital
9508 digital
9608
9611G
9621G
9641G
9620L
9620C

1

1

2

2

2

2

2

2

24 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

Telephone Native extensions (local extensions operating

9630G
9640
9640G
9650
9650C
SBM24
Avaya 1010/1020/1030/1040 video

conferencing units
B149 conference phone
B159 conference phone
B179 conference phone
BM12

Supported telephones

in the distributed branch user model)

2

2

2

2

2

1

1

BCM TDM sets:

• DECT handsets 4xxx/7xxx series

• T7316E

• T7316

• T7406E

• T7406

• T7208

• T7100

• T7000

• M7310

• M7310N

• M7310+BLF

• M7324

• M7324N

• M7208

• M7208N

• M7100

• M7100N

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 25

B5800 Branch Gateway overview

Telephone Native extensions (local extensions operating

• Audio conference unit

• T24 KIM (Key Indicator Module for
T7316)

DevConnect–approved 3rd-party SIP
audio and video endpoints

1

When connected to their respective telephones.

2

Supported when running H.323 firmware; not supported when running SIP firmware.

Software applications

The B5800 Branch Gateway software applications are provided on DVDs.

in the distributed branch user model)

• User applications — The following applications are supported for use by native users
on a 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.
Embedded Voicemail on a B5800 Branch Gateway system provides 6 ports. This
voicemail option requires a license. See

Licensing on page 16 for more

information.

- Standalone Voicemail: provides additional port capacity (40 ports) on a Linux
server. You must have a Linux server installed to use this option. This voicemail
option requires a license. See

Licensing on page 16 for more information.

- 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 a 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 a B5800 Branch Gateway system.

26 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

- System Status: 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 3rd­party 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.

Supported country locales

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

Australia UK English
Belgium Dutch
Belgium French
Brazil Brazilian
Canada Canadian

Chile Latin

China Mandarin - ­Colombia Latin

Language Telephony Phone

Display

Spanish

French

Spanish

Spanish

Applications EVM and

Manager Soft

Console

- -

SVM

*

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 27

B5800 Branch Gateway overview

Locale Language Telephony Phone

Display

Denmark Danish ­Finland Suomi ­France French
Germany German
Greece Greek - - - SVM only
Hong Kong Cantonese - - - ­Hungary Hungarian - - - SVM only
Iceland Icelandic - - - ­India UK English ­Italy Italian
Korea Korean - ­Mexico Latin

Spanish

Netherlands Dutch

Applications EVM and

Manager Soft

Console

SVM

*

New Zealand UK English
Norway Norwegian ­Peru Latin

Spanish

Poland Polish - SVM only

*

EVM is Embedded Voicemail. SVM is Standalone Voice Mail.

Note:

Hungarian, Polish, and Greek are not supported by Embedded Voicemail, but they are
supported by Standalone Voice Mail.

• 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.

28 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

Comments? [e-mail]

• Manager: Indicates that the IP Office Manager application can run in the specific locale
language. Manager uses the best match it has (French, German, Brazilian, Dutch, Italian,
Mexican Spanish, Russian, 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.

• 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. The system locale can be overridden by setting a different user locale.

• Standalone V oice Mail: Indicates that the locale is recognized by Standalone V oice Mail
and appropriate language prompts are then used. If an unsupported locale is used,
Standalone Voice Mail will attempt the best match using the first two characters of the
locale. The system locale can be overridden by setting a different user locale.

Related resources

Related resources

Related documents

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.

Documents you may need to consult are as follows:

• Administering Avaya Aura® System Manager

• Administering Avaya Aura® Session Manager, document number 03-603324

• Avaya IP Office Manager Release 6.2, document number 15-601011

• Unified Communications Management, Common Services Fundamentals, Avaya
Communication Server 1000, document number NN43001-116

• Security Management Fundamentals, Avaya Communication Server 1000, document
number NN43001-604

• Network Routing Service Fundamentals, A vaya Communication Server 1000, document
number NN43001-130

• Avaya CallPilot Administrator Guide, document number NN44200-601

• CS 1000 System and CallPilot Server Configuration, document number NN44200-312

• CallPilot Telephone Administration Guide, document number NN40090-500

• IP Peer Networking Installation and Commissioning – Avaya Communication Server
1000, document number NN43001-313

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 29

B5800 Branch Gateway overview

• SIP Line Fundamentals – Avaya Communication Server 1000, document number
NN43001-508

• Element Manager System Reference – Administration, document number NN43001-632

• Software Input Output Reference – Administration, document number NN43001-611

• SIP Software for Avaya 1100 Series IP Deskphones–Administration, document number
NN43170–600

• SIP Software for Avaya 1200 Series IP Deskphones–Administration, document number
NN43170–601

Avaya Mentor videos

Avaya Mentor is an Avaya-run channel on YouTube that includes technical content on how to
install, configure, and troubleshoot Avaya products.

Visit http://www.youtube.com/AvayaMentor and do one of the following:

• Enter a key word or key words in the Search channel to search for a specific product
or topic.

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.

Details of courses can be found on the Avaya University web site (

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 305.

Web sites

Information to support B5800 Branch Gateway can be found on a number of web sites.

• Click the name of a playlist to scroll through the posted videos.

http://www.avaya-

• Avaya (

30 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012

http://www.avaya.com)

Comments? [e-mail]