Maximum number of members in a trunk group on page 182
SLS group type assignments on page 182
Module-port values in SLS trunk-group context for analog trunks on page 183
Trunk port values in SLS trunk-group context for digital trunks on page 183
Administering signaling-group parameters on page 183
Administering dial-pattern parameters on page 185
Administering incoming-routing parameters on page 186
Summary of SLS configuration commands on page 187
SLS configuration rules
SLS is included as part of the resident firmware package that is installed as part of the Branch
Gateway firmware upgrade. However, for SLS to function correctly, the following conditions
must be met:
•
Avaya Aura
®
Communication Manager must be configured for SLS and Auto Fallback.
For instructions on configuring SLS in Avaya Aura
®
Communication Manager, see
Configuring Communication Manager for SLS on page 120.
•
Provisioning data from the PIM tool must be gathered from Avaya Aura
®
Communication
Manager and delivered to the Branch Gateway using PIM. For instructions on gathering
and delivering the provisioning data, see
Using PIM to manage SLS administration on the
gateway on page 133.
If PIM is not available, the Branch Gateway can be manually configured for SLS and Auto
Fallback using the CLI. See Using the CLI to manually configure SLS administration on
the gateway on page 139.
• SLS must be enabled on the Branch Gateway. See Enabling SLS on page 138.
• To activate any saved changes within SLS, the disable and enable SLS commands must
be used together. See Activating changes in SLS on page 138.
Configuring Communication Manager for SLS
About this task
You must configure the Avaya Aura
®
Communication Manager for SLS whether you will be
using PIM provisioning or manual CLI entry of SLS administration. Perform the configuration
during the initial administration of the host Communication Manager server.
Procedure
1. Access theCommunication Manager administrative SAT interface.
Standard Local Survivability (SLS)
120 Administering Avaya G430 Branch Gateway October 2013
Comments? infodev@avaya.com
To Next Page
Loading...
