Troubleshooting Logging 

The following information will guide you to enable debugging on your Vega Gateway for troubleshooting issues.  

We are trying to divide the logging in multiple use-cases so we could try to capture more useful/relevant information as per the issue type.


Before starting any troubleshooting step, please make sure your unit is running the latest general available firmware.
The firmware upgrade procedure is described here: Firmware Update



Always make sure you are collecting "show support" command output from Vega and providing this to Sangoma Technical support team along with other logs while reporting an issue.



  1.  To enable debugging in your Vega Gateway, insert the following commands, one-by-one:

Vega 100G - 200G - 400G - Vega 50 BRI - Vega 60 BRI
debug enable router rs
debug enable _isdn 89
debug enable _logger i
log display v
sip monitor on
log display off
debug on
If you are using ENP run this command as well.
debug enable _sip 1efw


Vega 50 FXO/FXS - Vega 5000 - Vega 3000 - Vega 3050 - Vega 60 FXO/FXS
debug enable router rs
debug enable _pots 12346
debug enable _logger i
log display v
sip monitor on
log display off
debug on
If you are using ENP run this command as well.
debug enable _sip 1efw
CAS R2
     debug enable router rs
debug enable isdn rs
debug enable _cas 4567
debug enable _logger i
sip monitor on
log display off
debug on
If you are using ENP run this command as well.
debug enable _sip 1efw


         

        2. If possible try to collect PCAP of the issue call as well. Refer to https://wiki.sangoma.com/display/VG/Packet+Capture 

       3. Reproduce your issue now

       4. Type the following two commands which will dump diagnostic information. Send the output of both of the following commands along with pcap (if possible) in two separate text files (each file for each command) to technical support          

               -> debug dump

              -> show support  


  1. Please look if there is core file present in the system - Refer to https://wiki.sangoma.com/display/VG/Vega-XXXG+Debugging#Vega-XXXGDebugging-Vegarebootingorcrashing
    If yes then scp the core file from Vega gateway to your local system and share with Sangoma Technical Support team. 

    Please note that  We will loose the core file If there is hard reboot or complete Vega gateway box reboot will occur. 

  2. Enable Syslog in Vega to make sure we have syslog output/logging during Vega crash time. This will help us to identify scenario during which crash could happen

  3. "show support " output from Vega box.

    For Old Vega Gateways (Vega 50 , 5000 , 100, 200 , 400 GW)  - 

                    Refer to https://wiki.sangoma.com/display/VG/Capturing+Software+Reboots 


How to Run These Commands in WebGUI

 

1) Log into the webui http://<IP of Vega>/ 
    (i.e. http://192.168.2.12/

 

2) As shown in the picture below click on Expert Config -> Advanced, then type the command "show support" in the CLI Command window. Once done click Submit. This will popup a new window with the output of the command. Copy all text "ctrl->A" (select all) and paste this into a txt file and send this to support@sangoma.com

 

 

 

 

 

 How to Run Commands via SSH/Telnet

 

1) You can use many telnet clients but if you do not have one already download PuTTY from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

 

2) Open PuTTY and put the address of your system in the "Host Name" field, then select "Telnet" from the connection type. Once done click "Open" at the bottom. 

 

 

3) Log into the Vega using username/password.

 

 

 

 

4) Run the "show support" command then right click on the PuTTY title bar and click "Copy All to Clipboard" then paste this into a text file and send this to support@sangoma.com