In some of the newer Sangoma Vega firmware, it seems like there was a default setting for the DTMF signalling which had changed from previous firmware builds.

Enter the following commands in the Vega console:

set .media.pkt_profile.1.voice.out-of-band-dtmf=on
apply
save

It is possible to upgrade the firmware on a Sangoma Vega gateway from the command line.

You can connect to it using telnet, ssh or a serial console cable. Note – the console cable is the same as a Cisco console cable.

To upgrade firmware you will need a tftp server running on the network local to the Vega gateway.

A free tftp server for a Windows PC is Pumpkin.

In Linux/Unix(/OSx??) install tftpd.

Place the firmware file into the root folder of the tftp server. Get the firmware from the Sangoma wiki.

The filename will be something like “VEGA_R100S043.bin” depending on which gateway it’s for and what the version of firmware is. Note that Vega 100/200/400 gateways use different firmware than Vega 100G/200G/400G.

Connect to the command line of the Vega gateway.

You need to tell the Vega where your tftp server is. They will usually look at DHCP Option 66 but in many cases you’ll need to manually tell it using this command:

    set .tftp.ip="xxx.xxx.xxx.xxx"

With the correct IP address! Then:

    apply

and if you want the setting to survive a reboot:

    save

To do the actual firmware upgrade:

    upgrade

    download enable

    download firmware _filename_

    reboot system

Where _filename_ is the entire file name of the firmware file in the tftp server root folder. E.G. VEGA_R100S043.bin

I’ve come across this issue a few times, it seems very confusing but is an easy fix.

The scenario is:

– ISDN PBX connected to a Vega 100/200/400 gateway using a SIP provider for inbound & outbound calls.

– When ringing an inbound number that comes in over SIP, through the gateway and to the ISDN PBX, the call works fine but no ring-back is heard.

The reason:

The ISDN system is sending a progress indicator message to the gateway tell it that it will send in-band media. The Vega gateway translates this into a “183 Session Progress” message which would be the SIP equivalent.

However, the PBX then clearly isn’t actually sending any audio so the caller just hears silence till the call is answered by someone.

I suspect that the reason this problem doesn’t occur on a real ISDN line is that BT et al. just ignore these messages and generate ringing whether the PBX said it was going to send it’s own or not.

So the fix is to force the Vega gateway to always send a “180 Ringing” message no matter what the ISDN side says. This tells the SIP server upstream to generate it’s own Ringing rather than expect to get some audio from the gateway.

In the Vega web interface:

• go to Expert Config
• click on SIP
• scroll right to the bottom and click Advanced SIP
• find the setting called “183 Session Progress if media present. If =2, send 183 instead of 180 with sdp”
• change it to 1 (a number one) instead of the default value of 2

Apply the changes and save the config.

That should work around the issue.

My preferred method for installing Asterisk on Debian is by using standard Debian packages. I don’t want the hassle of re-compiling packages whenever there is an updated version or some security hole gets closed.

Step one is getting Asterisk & Dahdi installed and working.

Do this:

apt-get install asterisk libpri1.4 asterisk-dahdi

The country code for the UK is 44.

Now to get the dahdi kernel modules built, install dahdi-source and use module assistant to install the modules:

apt-get install dahdi-source

m-a a-i dahdi

Now you should have Asterisk & Dahdi installed.

Before installing the Sangoma Wanpipe drivers, you need to compile the Dahdi source (module assistant just compiles the kernel module parts):

cd /usr/src/modules/dahdi

make

The rest is the same as the standard installation instructions for Wanpipe which are here (scroll down to Sangoma Driver Installation):

http://wiki.sangoma.com/wanpipe-linux-asterisk-dahdi

In summary:

apt-get install automake autoconf libtool libncurses5-dev bison libxml2-dev cmake flex

wget ftp://ftp.sangoma.com/linux/current_wanpipe/wanpipe-current.tgz

tar xzf wanpipe-current.tgz

cd wanpipe-{version}/

./Setup install

and just follow the instructions.

Paul Hayes.

Sangoma has launched a new web tool for ITSPs that allows for quick and easy provisioning of Vega gateways. The tool allows ITSPs to generate configuration files for any Vega gateway without having to manually configure each setting on the web GUI. SNAP walks through a series of screens and spits out a final configuration file which can be uploaded to the Vega.

To benefit from the tool, the ITSP will have to provide a test account and general install scenario such as whether the box will be on DHCP or static IP address, what codec types to use, etc. Sangoma will then test those scenarios with provided test account and make the final template available for users to download. There is no limit on the number of templates. Multiple templates can be created for the same product according to the scenario.

Have a look at the link below to get a general idea of how it works.

http://vegaconfig.com