DAHDI not working after upgrade

Asterisk Asterisk Hardware
1

Hello. Just upgraded to Debian 10, Asterisk 13.28.1 and dahdi 3.0.0. The problem I have is with dahdi, which has stopped working.

root@pbx:/etc# dahdi_hardware
pci:0000:02:00.0     wctdm24xxp-  d161:8005 Wildcard TDM410P

root@pbx:/etc# dahdi_cfg -vv
DAHDI Tools Version - 3.0.0

DAHDI Version: 3.0.0
Echo Canceller(s):
Configuration
======================


Channel map:

Channel 01: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 02)

2 channels to configure.

DAHDI_CHANCONFIG failed on channel 1: Invalid argument (22)
Selected signaling not supported
Possible causes:
        FXS signaling is being used on a FXS interface (use a FXO signaling variant)
        RBS signaling is being used on a E1 CCS span
        Signaling is being assigned to channel 16 of an E1 CAS span

I know it’s old, but for the few occasions that it’s used, it was just fine.
Here is chan-dahdi.conf, which hasn’t changed for years:

[trunkgroups]
; define any trunk groups
[channels]
; hardware channels
usecallerid=yes
hidecallerid=no
callwaiting=no
cidsignalling=bell
threewaycalling=no
transfer=yes
echocancel=yes
busydetect=yes
busycount=5
faxdetect=both
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
context=from-pstn
channel => 2
context=default

From lspci -v the system seems to think it’s an Ethernet controller:

02:00.0 Ethernet controller: Digium, Inc. Wildcard TDM410 4-port analog card (rev 11)
        Subsystem: Digium, Inc. Wildcard TDM410 4-port analog card
        Flags: bus master, medium devsel, latency 64, IRQ 3
        I/O ports at cc00 [size=256]
        Memory at fdeff000 (32-bit, non-prefetchable) [size=1K]
        [virtual] Expansion ROM at fde00000 [disabled] [size=128K]
        Capabilities: [c0] Power Management version 2

Any thoughts?
Regards,
Ian

2

In this case downgrade dahdi should fix the problem, assuming new version is not recognizing the card

3

The previous version will not compile:

/home/asterisk/dahdi/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/wctc4xxp/base.c: In function ‘wctc4xxp_init_one’:
/home/asterisk/dahdi/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/wctc4xxp/base.c:4092:2: error: implicit declaration of function ‘setup_timer’; did you mean ‘sk_stop_timer’? [-Werror=implicit-function-declaration]
  setup_timer(&wc->watchdog, wctc4xxp_watchdog, (unsigned long)wc);
  ^~~~~~~~~~~
  sk_stop_timer
cc1: some warnings being treated as errors
make[6]: *** [/usr/src/linux-headers-4.19.0-6-common/scripts/Makefile.build:309: /home/asterisk/dahdi/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/wctc4xxp/base.o] Error 1
make[5]: *** [/usr/src/linux-headers-4.19.0-6-common/scripts/Makefile.build:549: /home/asterisk/dahdi/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/wctc4xxp] Error 2
make[4]: *** [/usr/src/linux-headers-4.19.0-6-common/Makefile:1534: _module_/home/asterisk/dahdi/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi] Error 2
make[3]: *** [Makefile:146: sub-make] Error 2
make[2]: *** [Makefile:8: all] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-4.19.0-6-686-pae'
make[1]: *** [Makefile:74: modules] Error 2
make[1]: Leaving directory '/home/asterisk/dahdi/dahdi-linux-complete-2.11.1+2.11.1/linux'
make: *** [Makefile:9: all] Error 2

Regards

4

I have a while without use dahdi but try first dahdi_genconf and then dahdi_cfg -vvv

5 
# dahdi_genconf
Empty configuration -- no spans
Empty configuration -- no spans
Empty configuration -- no spans
# dahdi_cfg -vvv
DAHDI Tools Version - 3.0.0

DAHDI Version: 3.0.0
Echo Canceller(s):
Configuration
======================


Channel map:


0 channels to configure
6

It seems I’m not alone: https://serverfault.com/questions/978738/dahdi-3-0-0-not-assign-spans-and-cannot-generate-configuration?newreg=087dcf4ff9db40a9a48c8263c63c3ae3

7

The TDM410 is not supported in DAHDI past the 2.x releases. The README file in the dahdi-linux package (or the “linux” subdirectory if you downloaded the complete tarball) provides a list of the supported hardware.

1 Like
8

Unfortunately, 2.11 no longer compiles. I guess I will have to buy another card…:confused:

9

You could download an old version of FreePBX Distro which have also supported version of dahdi for this type of card

10

DAHDI is kernel version dependent. You would need to install an end of life OS as part of doing this.

11

In order to get my card to work the Debian 10 and the newest drivers and the standard configuration I used to use I had to do:

# cat /etc/modprobe.d/dahdi.conf
# You should place any module parameters for your DAHDI modules here
# Example:
#
# options wctdm24xxp latency=6
options dahdi auto_assign_spans=1

Then in /etc/rc.local

# start digium card
/sbin/modprobe wct4xxp
/etc/init.d/dahdi start

Then

# cat /etc/dahdi/system.conf
# pri config
span=1,0,0,esf,b8zs
e&m=1-24
loadzone = us
defaultzone=us
echocanceller=none
#echocanceller=mg2,1-23

Hopefully this is useful.

1 Like
12

assigned-spans.conf is empty, and dahdi_genconf fails:

 dahdi_genconf -v
Default parameters from /etc/dahdi/genconf_parameters
Empty configuration -- no spans
Generating /etc/dahdi/assigned-spans.conf
Empty configuration -- no spans
Generating /etc/dahdi/system.conf
Empty configuration -- no spans
Generating /etc/asterisk/dahdi-channels.conf
13

I dont use either of those things. Hence the:

options dahdi auto_assign_spans=1

in /etc/modprobe.d/dahdi.conf

Then try /sbin/modprobe wctdm24xxp & /etc/init.d/dahdi start

14

No go:

root@pbx:~# cat /etc/modprobe.d/dahdi.conf
# You should place any module parameters for your DAHDI modules here
# Example:
#
# options wctdm24xxp latency=6
options dahdi auto_assign_spans=1
root@pbx:~# /sbin/modprobe wct4xxp
root@pbx:~# /etc/init.d/dahdi start
Loading DAHDI hardware modules:
   wctdm24xxp: done
using '/etc/dahdi/assigned-spans.conf'
Running dahdi_cfg: done.

Then, after restarting Asterisk:

pbx*CLI> dahdi show channels
   Chan Extension       Context         Language   MOH Interpret        Blocked    In Service Description
 pseudo                 default                    default                         Yes

Thanks anyway.

15

Try rebooting as well.

16

Rebooting doesn’t help.

17

Do you see it in dmesg?

18

Alas, what’s been posted after @david551 's posting is only leading the original poster astray. I’m confident in the accuracy of my posting w.r.t. DAHDI versioning and hardware support.