Sls Logging Activities - Avaya G250 Administration

Configuring Standard Local Survivability (SLS) on the G250
There is no means to disable the ETR feature when the G250 is powered-down. Therefore, on
the G250, certain ports should not be used as DID ports to avoid having the ETR "loop-start"
trunk connected directly to the tip and ring circuit of the DID trunk and having two battery feed
circuits driving one another. For the following models, Avaya discourages using the associated
Integrated port as DID:
G250 — Integrated port V305
●
G250-BRI — Integrated port V302
●
Note:
SLS is not supported on the G250-BRI.
Note:

SLS logging activities

SLS exports two important types of data:
Trace output provides valuable informational messages about its state and state
●
transitions, allowing Services Tier III/IV to better understand how and/or if it is functioning.
These messages can be displayed on any computer accessible through the gateway's
UDP/IP network connection. Tracing must be manually enabled from the tshell, and the
trace data sent out through the UDP port, not logged.
Call Detail Record (CDR) log: contains detailed information about each call that uses a
●
trunk. This information can be stored in flash NVRAM or directed to an external server for
later processing and includes data for:
- Merged outgoing Trunk Access Codes (TACs), indicating successfully completed dialing
- Successfully completed ARS calls
Figure 5
82 Administration for the Avaya G250 and Avaya G350 Media Gateways
shows an example of CDR log entries and format.