User's Manual

Administering a Session Manager line for each branch
This section provides the procedures required to configure a Session Manager line between
each branch site and the headquarters site.
This section also describes how the B5800 Branch Gateway uses a configured Session
Manager line to handle incoming and outgoing calls to and from the branch and explains how
a second Session Manager line can be configured for Session Manager line redundancy.
• See
Enabling SIP trunk support on page 136. Use this procedure to configure the IP
Office LAN interface which will be used for the Session Manager line connection to the
Avaya Aura
®
Session Manager.
• See
Setting the branch prefix and local number length for extension numbering on
page 137. Use this procedure to set the prefix number for the B5800 Branch Gateway
and the required extension length.
• See Changing the default codec selection on page 139. Use this procedure to set the
preferred order for codec negotiation. This can be done as a system default and also for
each individual SIP and Avaya Aura
®
Session Manager line.
• See
Adding an Avaya Aura Session Manager line on page 141. Use this procedure to
create a Session Manager line for calls to the Avaya Aura
®
Session Manager.
• See
Setting up outgoing call routing on page 145. Use this procedure to create short
codes for routing calls to the Avaya Aura
®
Session Manager line when the required
destination or resource is on another branch of the Avaya Aura
®
network.
• See How the B5800 Branch Gateway uses a configured Session Manager line on
page 147.
Enabling SIP trunk support
About this task
Before adding any SIP trunks, includingAvaya Aura
®
Session Manager lines, the B5800 Branch
Gateway system must be configured for SIP trunk operation. The system has 2 LAN interfaces,
LAN1 and LAN2 (the physical ports are labeled LAN and WAN respectively). Either can be
used for the Avaya Aura
®
Session Manager line operation.
Important:
The configuration changes in the following procedure will require the B5800 Branch
Gateway system to be rebooted.
Initial configuration for a Distributed Branch
136 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com