chan_dahdi: Unable to open channel: Invalid Argument

Asterisk Asterisk Support
1

I just installed Asterisk 11.8.0 with Dahdi 2.11.0.
I’m actually trying to use a amfeltec USB-FXO adapter with my PBX.
I find that chan_dahdi.so doesn’t load on system startup. When I tried to load it from the Asterisk cli, I get the following errors:

micro*CLI> module load chan_dahdi.so
Unable to load module chan_dahdi.so
Command 'module load chan_dahdi.so' failed.
[2016-01-04 14:38:02] WARNING[3744]: chan_dahdi.c:4488 dahdi_open: Unable to specify channel 1: Invalid argument
[2016-01-04 14:38:02] ERROR[3744]: chan_dahdi.c:12665 mkintf: Unable to open channel 1: Invalid argument
here = 0, tmp->channel = 1, channel = 1
[2016-01-04 14:38:02] ERROR[3744]: chan_dahdi.c:17274 build_channels: Unable to register channel '1'

I figured this has something to do with my settings in /etc/asterisk/chan_dahdi.conf or nano /etc/dahdi/system.conf. Here’s what I have in these files:

/etc/asterisk/chan_dahdi.conf:

[trunkgroups]

; No trunk groups are needed in this configuration.

[channels]
#include /etc/asterisk/dahdi-channels.conf
; The channels context is used when defining channels using the
; older deprecated method.  Don't use this as a section name.

/etc/asterisk/dahdi-channels.conf:

context=from-internal
group=0
echocancel=yes
signaling=fxo_ks
channel => 1

/etc/dahdi/system.conf:

loadzone        = us
defaultzone     = us

fxsks=1
echocanceller=mg2,1

I don’t understand what is wrong here, but when I remove these settings, I am able to load the chan_dahdi module.
I’m a newbie to asterisk and dahdi. I’d appreciate if someone could help me here.

2

You need to contact the supplier of the third party hardware for support.

3

Thanks for the prompt reply David. I’m trying to contact the vendor.
Meanwhile, could you please confirm that the syntax of settings is correct?

4

I’m not particularly familiar with DAHDI, but the error appears to be a semantic error, i.e. the device driver has rejected a parameter that was successfully parsed, rather than a syntax error. I suspect the device driver doesn’t believe there is a channel 1.