Versions Compared

Version Old Version 3 New Version Current
Changes made by

Kelli Higdon

Kelli Higdon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Wireshark trace (Step #5) 

  • Show Support (Step #7)

  • Debug Dump (Step #7)

Advanced Logging

  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

  1. If possible try to collect PCAP of the issue call as well. Refer to Packet Capture 

  • Please note that we can collect at max 5 MB size of pcap so not recommended to use for Load/Traffic time.

  • Applicable only for next gen vega gateways.

  • If issue is reproducible in single call then highly recommended to collect pcap.

  1. Reproduce your issue now

  2. 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          

...

              -> show support  

Audio issue Logging  - 

Refer to Diagnostics for audio issues 

Vega Gateway Reboot - 

For Next Generation Vega Gateways - 

If you observe Vega gateway is crashing randomly then try to collect following information - 

  1. Please look if there is core file present in the system
    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

    1. "show support " output from Vega box.

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

                    Refer to Capturing Software Reboots 

SNMP Issues - 

...

Refer to SNMP Configuration and Troubleshooting 

DSP Failure  - 

  • GUI is displaying DSP failure after an upgrade of Vega SW to 11.1 or 12.0. 

  • Refer to DSP Failure Issue

Private Wire (PW) Issues - 

  • Collect Show Support

    • Setup configuration

    • If its audio related issue then please collect the pcap as mentioned above.

      • To enable debugging in  Vega Gateway, insert the following commands one-by-one:

...

sip monitor on

log display off

debug on

SNMP Issue

Please refer to SNMP Troubleshooting in order to get how to troubleshoot SNMP related issues.

How to Run Commands in the WebGUI

 

1) Go to Configuration → Expert Config → CLI and then type in the command. Click SEND to execute the command. 

...

   

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) Now run the command you would like to run. To copy all output from commands like show support, you can right click on the title bar and then click Copy All to Clipboard as shown below. 

...