Note:
The “*” and “#” characters are not available on rotary-dial, analog phones.
18. Enter set pim-lockout no to allow Provisioning and Installation Manager (PIM)
updates, since you finished SLS administration of the Branch Gateway.
19. At the Branch Gateway command prompt, enter exit to leave the sls context.
The Branch Gateway command prompt reverts to that of the original login.
20. After all of the SLS features are administered, at the Branch Gateway command
prompt enter set sls enable to enable SLS on the Branch Gateway.
Note:
If you enabled SLS and then entered additional administration, you must first
disable SLS by entering set sls disable, and then re-enable it by entering
set sls enable. This will cause the SLS application to resynchronize its
administrative database with the Branch Gateway's CLI command database.
21. At the Branch Gateway command prompt, enter copy running-config
startup-config to save the changes.
Administering station parameters
Procedure
1. At the Branch Gateway command prompt, enter station extension class to
enter a second-level sub-context to administer each phone that you want covered
by SLS.
In this command, extension is a 1 to 13 digit numeric string that may begin with
0, and class is analog, dcp, or ip.
For example, station 1234567 ip administers an IP phone with the extension
“1234567”.
The command line prompt changes to sls-station <extension> to indicate
that you are in the station context for SLS administration. Entering exit ends the
station configuration mode, and the command line prompt returns to its original
state. If you want to remove the station from the SLS administration, enter clear
station extension at the command line interface. Enter exit to leave the
second-level station context to return to the (super-sls)# context.
2. Depending on the class (analog, dcp, or ip, set in Step
1 on page 0 ), enter set
type model, where model is a value from Class values in SLS station context on
page 168.
Standard Local Survivability (SLS)
166 Administering Avaya G430 Branch Gateway October 2013
Comments? infodev@avaya.com
To Next Page
Loading...
