Sangoma Vega 3000G - 24 FXS

Introduction

The Sangoma Vega 3000G is intended to be used to connect analog telephones to a SOP. Each analog line, will be registered on the sop.
It is delivered with a patch panel with 24 RJ45 ports. Adapters for RJ11 ports are also available.
See more details in Product Description: Sangoma Vega3000 ATA 24 RJ45-FXS ports.

SOP Configuration via the SMP

Modules

Mandatory to configuring resources, install first the Sangoma Vega Gateway Support Module to your sop.

Resources

ALERT! Warning : make sure the server is on time
For each line, configure a SangomaVega3000FXS phone resource (SDV2). You can configure up to 24 resources for each Sangoma Vega 3000.

Do not forget to apply change on the sop.

Configuration of Sangoma Vega 3000

Cabling

  • Connect the sangoma Vega 3000 to the patch panel for analog FXS using the RJ21 FXS-1-24 port.
  • Connect the sangoma Vega 3000 to your network using the LAN port.

Discover Vega IP address

To find the Vega 3000 address, please check your DHCP logs and look for the gateway MAC Address or use the software provided by Sangoma here http://wiki.sangoma.com/files/vega-net-discovery/vs_scanner_v5.zip.
ALERT! Warning : This tool will only scan 255 addresses as it has been developed only for /24 networks.

First Installation

ALERT! Warning : This step is only required if the option DHCP option 66 is not available or Sangoma Vega gateway has firmware version <= VEGAARM_R110S010 installed due to an issue in the auto provisioning system. To check the firmware version connect by telnet and run 
show version
--[ System Status ] --
 [Overview]:
    Hardware Platform : Vega High Density FXS
    Serial Number     : 00505820381a
    Boot Loader       : Version 5.00 (supports firmware 11.00 upwards)

 [ACTIVE]:
    Binary File Name  : VEGAARM_R110S010
    Release Date      : Dec  4 2015 16:15:37
    Versioning Info   : SIP Firmware Rev 11.00 for H/W Type 16
    Boot Requirements : Boot Loader 05.00

 [IMAGE1]: *ACTIVE NEXT BOOT*
    Physical Data     : v-file LINUX:/dev/mtd4
    Binary File Name  : VEGAARM_R110S010
    Release Date      : Fri Dec  4 21:17:57 2015
    Versioning Info   : SIP Firmware Rev 11.00 for H/W Type 16
    Boot Requirements : Boot Loader 05.00

 [IMAGE2]:
    Physical Data     : v-file LINUX:/dev/mtd5
    Binary File Name  : VEGAARM_R110S005
    Release Date      : Mon Jul 13 12:07:05 2015
    Versioning Info   : SIP Firmware Rev 11.00 for H/W Type 16
    Boot Requirements : Boot Loader 05.00
Now connect yourself to the Sangoma Vega 3000 via telnet. 
telnet <vegaipaddress>

Once logged in using admin as username and admin as password. Run the following code in the Sangoma Vega 3000 CLI to set the tftp server address where the vega will look for its own configuration.
  • If the module version is 1.1.0 
set .lan.if.1.dhcp.get_tftp=0
  • For all modules versions (1.0.0 to 1.1.0) 
set .tftp.ip="<SOP IP>"
save
apply change
reboot system

If you have some issues with tftp file transfer, check that the parameter 'lan.file_transfer_method' is set to 'TFTP'.
  • To check you can use the following command 
show lan.file_transfer_method
  • To reconfigure it to TFTP you can use the following command: 
  set lan.file_transfer_method=TFTP
  save
  apply
  reboot system
The Vega 3000 will reboot, and fetch the configuration from the tftp server. This process will take up to 5 minutes the first time the Vega 3000 is installed. 
Now connect yourself using the web ui http://<vegaipaddress> and verify on the status page if all configured peers have been registered.

Upgrade and update

To update the configuration file and/or upgrade the Firmware it's just required to reboot the Vega Gateway by using the following command : 
  reboot system
See the First Installation section to connect via telnet to the Sangoma Vega Gateway.

Upgrading from Sangoma Vega Gateway Support 1.0.0 to 1.1.0

The firmware provided by Sangoma include a bug related to DHCP option 66. Indeed if you have configured an IP address for the TFTP server to be used, it the option 66 is an IP address, this one will be replaced by bad. To prevent this, before rebooting Vega Gateway you have to execute the following line before rebooting the appliance. 
set .lan.if.1.dhcp.get_tftp=0

Once the Vega3000 has been rebooted, it will be upgraded (status led will switch to orange then to green). The upgrade process lasts up to 5 minutes.

To check if the upgrade is well ongoing, try to connect to the Vega3000 via telnet: 
$ telnet 172.16.35.15
Trying 172.16.35.15...
Connected to 172.16.35.15.
Escape character is '^]'.
Upgrade in progress, please try again later
Connection closed by foreign host.
Once the upgrade is done, the Vega3000 will reboot a second time. You will see the led switched off, then switch to orange and finally switch to green when the device is ready.

Debugging

If you want to debug, connect to the Vega using telnet and execute the command debug on to activate debugging in the current session. 
debug on

These command are useful for debugging

  • sip monitor <on|off>: enable or disable the sip traffic debugging
  • debug <on|off>: enable or disable debugging
  • show ports: show state of all ports, allows to see status of FXS ports
  • show calls: show call summary table.
  • show log : display the logs since the Vega has started.
  • disc all: disconnect all calls. (This is necessary if some lines are busy even there's no calls).

To provide full debugging information, execute the following commands before reproducing the issue: 
debug enable router rs
debug enable _ports 12345
debug enable _logger i
log display v
sip monitor on
log display off
debug on

Once done, execute the following to get the dump: 
debug dump
show support

Analyze the output of both commands.

Copyright © Escaux SA