Problem with DAHDI when using Fonebridge RedFone2

Asterisk Asterisk Support
1

Hello, I’m having a very stressing problem, whenever I try to start Asterisk (using Trixbox 2.8.0.4 CE) with DAHDI modules started, I get this error:

[Sep 21 13:33:24] ERROR[601] asterisk.c: Asterisk has detected a problem with your DAHDI configuration and will shutdown for your protection.  You have options:
        1. You only have to compile DAHDI support into Asterisk if you need it.  One option is to recompile without DAHDI support.
        2. You only have to load DAHDI drivers if you want to take advantage of DAHDI services.  One option is to unload DAHDI modules if you don't need them.
        3. If you need DAHDI services, you must correctly configure DAHDI.

Of course, if it says that my configuration is wrong, than there has to be somthing with it, however I really can’t find the error, here’s the config for /etc/dahdi/system.conf:

loadzone        = us
defaultzone     = us

dynamic=ethmf,eth2/00:50:c2:65:dc:1f/0,31,0
dynamic=ethmf,eth2/00:50:c2:65:dc:20/1,31,1

alaw=1-60

bchan=1-30
bchan=31-60

Here’s /etc/dahdi/modules (just the end where I actually added some modules):

#Fonebridge
dahdi_dynamic_ethmf
dahdi_dynamic

And here’s /etc/asterisk/chan_dahdi.conf:

;
; DAHDI telephony
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300              ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes

usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
;echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no

;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

;Include setup-pstn configs
#include dahdi-channels.conf

group=1
channel => 1-60

;Include PBXconfig configs
#include chan_dahdi_additional.conf

Now, what I really find odd is that if I run dahdi_scan, I can find the E1 spans from RedFone:

# dahdi_scan
[1]
active=yes
alarms=YEL
description=Dynamic 'ethmf' span at 'eth2/00:50:c2:
name=DYN/ethmf/eth2/00:5
manufacturer=
devicetype=
location=
basechan=1
totchans=31
irq=0
type=digital-
syncsrc=0
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=
framing_opts=
coding=
framing=
[2]
active=yes
alarms=RED
description=Dynamic 'ethmf' span at 'eth2/00:50:c2:
name=DYN/ethmf/eth2/00:5
manufacturer=
devicetype=
location=
basechan=32
totchans=31
irq=0
type=digital-
syncsrc=0
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=
framing_opts=
coding=
framing=

They are alarming because there’s no E1 connected to it, yet.
If however, I unload dahdi modules, asterisk comes up just fine (without dahdi of course).
Can anyone help me out on what may be wrong? I’m going nuts here.

Thank you very much.

2

Hi

What are you connecting these to ? as tou have no d channel asigned and signally set to fxs_ks

Ian

3

Actually I’m not connecting anything yet, I’m just making some tests to see if the FoneBridge works like it should…
I got the configuration sample from the FoneBridge installation guide, and tried with dchan as well, but no luck.

4

Thank you, I’ve found the solution by configuring the dahdi the first time with an E1 connect to it (otherwise it kernel panicked at my face every time), and by adding the correct loadzone.

Thanks for your help.