Sangoma W400 GSM NOT Work

Hello to everyone,
Does Sangoma W400 GSM digital card works with latest freePBX distro (Asterisk 16)?
I found some response to this question that it is not supported?
How it is even possible? And why? (Please give some technical reasons not commercial or “it is just the fact”).
At my custom VoIP server i have one OpenVox A800P analog card, and one Sangoma W400 GSM card. The first one are older and it is working well thus second one don’t work.
Please, if someone have solution to make this card to work and can share solution i will be very tankful.

Here some technical info about deployment
Linux freepbx.local 3.10.0-1127.19.1.el7.x86_64 #1 SMP Tue Aug 25 17:23:54 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

[root@freepbx ~]# lspci | grep Tiger
06:02.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface

[root@freepbx ~]# lspci | grep Sangoma
05:04.0 Network controller: Sangoma Technologies Corp. Device 0025

[root@freepbx ~]# wanrouter hwprobe

Wanpipe Hardware Probe Info

1 . AFT-W400-SH : SLOT=4 : BUS=5 : IRQ=11 : PORT=1 : V=20
Sangoma Card Count: W400=1

[root@freepbx ~]# dahdi_hardware
pci:0000:06:02.0 opvxa1200+ e159:0001 OpenVox A800P

[root@freepbx ~]# yum info libwat
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
Installed Packages
Name : libwat
Arch : x86_64
Version : 2.1.0
Release : 1.2.sng
Size : 153 k
Repo : installed
From repo : anaconda
Summary : LibWAT is an open source library that encapsulates the protocols used to communicate with Wireless GSM modules.
URL :
License : GPL
Description : LibWAT is an open source library that encapsulates the protocols used to communicate with Wireless GSM modules.
: LibWAT is a dependency for Asterisk and DAHDI if GSM signaling is used.
: LibWAT is still in beta phase.

yum info autoconf
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
Installed Packages
Name : autoconf
Arch : noarch
Version : 2.69
Release : 11.el7
Size : 2.2 M
Repo : installed
From repo : sng-base
Summary : A GNU tool for automatically configuring source code
URL :
License : GPLv2+ and GFDL
Description : GNU’s Autoconf is a tool for configuring source code and Makefiles.
: Using Autoconf, programmers can create portable and configurable
: packages, since the person building the package is allowed to
: specify various configuration options.
:
: You should install Autoconf if you are developing software and
: would like to create shell scripts that configure your source code
: packages. If you are installing Autoconf, you will also need to
: install the GNU m4 package.
:
: Note that the Autoconf package is not required for the end-user who
: may be configuring software with an Autoconf-generated script;
: Autoconf is only required for the generation of the scripts, not
: their use.

Connected to Asterisk 16.26.1 currently running on freepbx (pid = 3213)
freepbx*CLI>

freepbx*CLI> dahdi show version
DAHDI Version: 2.11.1 Echo Canceller: OSLEC

freepbx*CLI> dahdi show status
Description Alarms IRQ bpviol CRC Fra Codi Options LBO
Wanpipe GSM Board 1 OK 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)
OpenVox A1200P/A800P Board 13 OK 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)

freepbx*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked In Service Description
pseudo default default Yes
3 from-analog en default Yes
4 from-analog en default Yes
5 from-analog en default Yes
6 from-analog en default Yes
7 from-analog en default Yes
8 from-analog en default Yes
9 from-analog en default Yes
10 from-internal en default Yes

freepbx*CLI> wat
No such command 'wat ’ (type ‘core show help wat’ for other possible commands)

I would imagine the drivers are no longer being maintained for that card. It went EOL in 2017 and support in 2018.

OpenVox A800P is much older than Sangoma W400 and it is also EOL EOS etc.
Despite that, OpenVox support make it work with dahdi 2.11.1 !!!
It is very disappointing that Sangoma and community also make decisions based on profit and not by technics. Sangoma’s hardware should be supported and platform backward compatible!
In my opinion only acceptable reason can be that kernel on newest version of freepbx don’t support this card. And my technical question is why? What is that on newest kernel that is not supported?

I think you are a little confused, there is a difference between backwards compatibility and ongoing support. The reality is there is probably nobody left in engineering at Sangoma that has any idea on this card and the reason it went EOL is because the uptake of these cards was minimal (I’m ex-Sangoma so I remember the discussions) whilst there are a lot of decisions I don’t agree with, trying to provide engineering support for a card that is at least 5yrs old minimum and probably a handful of these cards that are still in use doesn’t make sense in any way.

Ok. if i understand you well, nobody works on to support this card?!
That doesn’t mean that it is not possible that this card works on SNG7 and Asterisk 16 !?
If that is the case, maybe someone from community is capable to provide answers and solutions.

Libwat would have to be updated for newer kernel and dahdi requirements and that open source project has not been touched in 7 plus years. This is not a FreePBX problem. Get someone to update that package to be compatible and the card should work.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.