Update to DAHDI drivers

General Help
1

Hello,

I have a Asterisk PBX with Asterisk 1.4.22, freepbx 2.5.1 and recently I have updated zaptel 1.4.12.1 to dahdi 2.0.0. I have 4 zap trunk (dahdi trunk now!) defined, From the moment that I updated to dahdi the outbound routes don’t funtion. The dahdi configuration files are:

system.conf:

Autogenerated by /usr/sbin/dahdi_genconf on Sat Nov 22 16:14:08 2008 – do not hand edit

Dahdi Configuration File

This file is parsed by the Dahdi Configurator, dahdi_cfg

Span 1: WCTDM/4 “Wildcard TDM400P REV I Board 5” (MASTER)

fxsks=1
echocanceller=mg2,1
fxsks=2
echocanceller=mg2,2
fxsks=3
echocanceller=mg2,3
fxsks=4
echocanceller=mg2,4

Global data

loadzone = es
defaultzone = es

chan_dahdi.conf:

;# Flash Operator Panel will parse this file for Dahdi trunk buttons
;# AMPLABEL will be used for the display labels on the buttons

;# %c Dahdi Channel number
;# %n Line number
;# %N Line number, but restart counter
;# Example:
;# ;AMPLABEL:Channel %c - Button %n

;# For Dahdi/* buttons use the following
;# (where x=number of buttons to dislpay)
;# ;AMPWILDCARDLABEL(x):MyLabel

[channels]
language=es

;# Configuracion para ganacia
relaxdtmf=yes
rxgain=1.0
txgain=0.0

; include zap extensions defined in AMP
#include chan_dahdi_additional.conf

; XTDM20B Port #1,2 plugged into PSTN
;AMPLABEL:Channel %c - Button %n
context=from-pstn
signalling=fxs_ks
faxdetect=incoming
busydetect=yes
busycount=6
answeronpolarityswitch=yes
hanguponpolarityswitch=yes
usecallerid=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=800
group=0
channel=3

group=1
channel=1-2

group=2
channel=4

When I see on asterisk with dahdi show channels the results is:
internal*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret
pseudo from-pstn es default
1 from-pstn es default
2 from-pstn es default
3 from-pstn es default
4 from-pstn es default

Where is the problem?, Why doesn’t FOP show the trunk?.
Can anybody help me?.

Thanks

2

see http://freepbx.org/forum/freepbx/installation/dahdi-no-jokes-version-with-freepbx

3

Thanks,
but this article does not refer to the variable ZAP2DADHICOMPAT in file amportal.conf, or FOP, etc … only speaks of the new files to configure to DADHI.

4

Basically, you want to set ZAP2DADHICOMPAT to yes or true ( I forget which, but there is an example in the amportal.conf.)

5

I think it’s dahdichanname = no

in the /etc/asterisk/asterisk.conf options section.

Don’t forget to remove the semicolon in front of the [options] line.

6
  1. In /etc/asterisk/asterisk.conf add:

[options]
dahdichanname = no

This will ensure full compatibility with /etc/asterisk/extensions*.

  1. In /etc/asterisk/ link chan_dahdi.conf with zapata.conf:

ln -s chan_dahdi.conf zapata.conf

This will ensure all the zap channels will show up in the FOP. If you find anything else please let me know!!!

7

Nope it doesnt work for me, still cant see any Dadhi in FOP