User's Manual
# 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.
• For Session Manager 6.1, see Creating
routing policies on page 153.
• For Session Manager 6.0, see Creating
routing policies on page 159
22 Create a dial pattern.
• For Session Manager 6.1, see Creating
dial patterns on page 154.
• For Session Manager 6.0, see Creating
dial patterns on page 160
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.
For Session Manager 6.1 or 6.0, see
Creating a System Manager link to Network
Management on page 161.
24 Administer extensions See Extension administration on
page 173.
Activating license files
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.
Initial configuration for a Centralized Branch
98 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com