Avaya Media Gateway G250, Administration Manual

Page: 208 / 840

Configuring Standard Local Survivability (SLS)
208 Administration for the Avaya G250 and Avaya G350 Media Gateways
Up-converting SLS data to Release 4.x
In order to re-use an SLS administration data set from an earlier release, you must convert it to
Release 4.x compatibility.
1. Enter
copy ftp startup-config
to restore the Release 3.x translation file on the
gateway.
2. Reset the gateway.
The gateway copies translations from startup-config to running-config and converts them
to Release 4.x command contexts.
3. Enter
copy running-config startup-config
.
The gateway saves the Release 4.x converted translations in startup-config.
4. Enter
reset
.
This command makes sure that the new translation file command set is being executed
and prevents spurious error messages from occasionally being displayed.
set send-name Define whether or not the calling,
connected, called, or busy party’s
administered name is sent to the
network on outgoing or incoming
calls in SLS
set send-number Define whether or not the calling,
connected, called, or busy party’s
administered number is sent to the
network on outgoing or incoming
calls in SLS
set supervision Define the incoming signaling
supervision mode for analog DID
trunks or DS1 tie trunks only in SLS
set tac Administer the trunk-access codes
for SLS
set trunk-hunt Specify the trunk-hunting search
within a facility in an ISDN trunk
group or through a non-ISDN digital
trunk group in SLS
show List all trunk-group SLS parameters
for this trunk-group
Table 58: SLS CLI command hierarchy (continued)
Root Level
Commands First Level Context
Commands Second Level Context
Commands Description
9 of 9