Using syslog for Vega Debug tracing
Log data and debug information can be sent to an external syslog server for storage and processing. This is useful when trying to find intermittent issues that may take a long to appear. Any standard syslog server can be used.
Enabling debug via syslog
Configure the syslog server IP and set the options to send debug to the server. Under Expert Config->Logging fill in the syslog details. Apply and save the configuration.
Log into the console via SSH or serial and enable the debug as requested by Sangoma Support, for example
DEBUG ENABLE _SIP IWEFT
DEBUG ON
Optionally the syslog can be set to persist after a debug. To do this enter the following on the CLI
DEBUG SAVE
SET _advanced.boot_debug=1
SAVE
Disabling debug syslog
To disable the debug enter the following commands on the CLI
DEBUG OFF
DEBUG SAVE
SET _advanced.boot_debug=0
SAVE
, multiple selections available,
Related content
Vega Gateways - Vega Detailed Logging
Vega Gateways - Vega Detailed Logging
More like this
Vega Gateways - Collecting logs and diagnostic information
Vega Gateways - Collecting logs and diagnostic information
More like this
Vega Gateways - Vega Audio Diagnostics
Vega Gateways - Vega Audio Diagnostics
More like this
Vega Gateways - Capturing a DSP tap trace on 60Gv2
Vega Gateways - Capturing a DSP tap trace on 60Gv2
More like this
Vega Gateways - Capturing Software Reboots
Vega Gateways - Capturing Software Reboots
More like this
Vega Gateways - Diagnostics for audio issues
Vega Gateways - Diagnostics for audio issues
More like this