Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

If you require assistance from a Sangoma Support Engineer please open a support ticket at https://support.sangoma.com
Verify that you have a valid Support Contract or Credits in order to open a ticket and receive priority support. Log into your portal account to verify at https://portal.sangoma.com

  1. The PBX Vega Gateway Module dashboard page has a "Warning" section which will display warnings (if available) at any point of time. 

  2. Make sure TFTP Server is running fine. To check whether TFTP server is running or not, execute below commands and compare output.

cat /etc/xinetd.d/tftp |grep disable
disable         = no
 
#service xinetd status |grep Active
Active: active (running) since Mon 2017-11-27 05:13:43 UTC; 4h 12min ago

  1. Vega bridge process not running warning. 

 In this case. need to check if vega_bridge process is running or not using below command.

/usr/bin/systemctl status vega_bridge 

If not running then try to run 

/usr/bin/systemctl start vega_bridge 

you can monitor logs to see if vega_bridge failed to start by below command - 

journalctl -u vega_bridge -f    Or look in /var/log/syslog log file.

  1. Vega gateway module log is handy tool to see live interaction of the PBX Vega Gateway Module with Vega gateways. Always look for debug logs if you face any issue in communication with Vega gateways.

We can view the Vega logs from "Reports→Asterisk Log file → Select "Vega module" log file "

  • No labels