PIAF 1.6 - Incredible PBX Dahdi Config

[briankelly63]

Raising discussion as to whether we should change the chan_dahdi.conf file as part of the PIAF install... Comments?

I did a fresh install of PIAF today (added Incredible piece) just to test ksalt16alt with Dahdi and an AEX800 Digium type card. 4 FXS - 4 FXO.

I had come across and issue in the past and had trouble getting this card to function in PIAF with Dahdi drivers but this time decided to run down the issue.

Despite going through all the appropriate Dahdi configuration steps the one file that is left in generic form on PIAF is chan_dahdi.conf . Unless this is configured its not going to work. The default version of this file is 12 plus pages in length with virtually everything commented out.

A more effective initial configuration and starting point is shown in the following link...

freepbx.org/forum/freepbx/installation/freepbx-and-dahdi-configuration

chan_dahdi.conf:




[trunkgroups]
[channels]
context=from-pstn
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
echotraining=800
rxgain=0.0
txgain=0.0
callgroup=1
pickupgroup=1
;Uncomment these lines if you have problems with the disconection of your analog lines
busydetect=yes
busycount=3
hanguponpolarityswitch=yes
immediate=no
#include chan_dahdi_additional.conf
#include dahdi-channels.conf

This allowed my AEX800 Digium card to function immediately after setting up a Dahdi Extension and Trunk.

An almost identical version of the chan_dahdi.conf file is included as part of a base Elastix install.

I'm suggesting we may need to look at how we set up this file during installation so we have a better chance of a card functioning right off the bat. I would like new users to have the best initial experience with our distro...

 

[dswartz]

seconded. i had to diddle around with various dahdi named files after googling b4 i got my rhino card working.

 

[dstroot]

I'm going to get flamed/banned but I ... just...can't...stop...myself.

Ward & Co. got upset several years ago by the direction the Asterisk project took that "broke" existing code and as a result the project has not fully embraced Asterisk 1.6, DAHDI and all the latest and greatest "stuff".

The flip side is that Ward & co have integrated a lot of other functionality into the distro so if they tried to keep current I suppose it would be be headache.

But this distro just got a working "update-source" script for 1.6 in 2010 and they still say "stay away from DAHDI..."

I'm hoping they change their minds and fully embrace 1.6 and DAHDI but I get the sense they are just biding time until maybe something like FreeSwitch is baked enough...

 

[wardmundy]

Brian,
Great suggestion. I've already added it to Incredible PBX and passed along to Tom for new build.

Part of my problem with Dahdi and Zaptel is that I personally don't use them and don't have no stinkin' Ma Bell lines to test this stuff. If there are missing pieces, by all means let us know. Thanks!!

 

[darmock]

I'm going to get flamed/banned but I ... just...can't...stop...myself.

Ward & Co. got upset several years ago by the direction the Asterisk project took that "broke" existing code and as a result the project has not fully embraced Asterisk 1.6, DAHDI and all the latest and greatest "stuff".

Yep basically because when dahdi first came out it DID NOT WORK with all cards period. It has take a while to get it stable and so it works with almost all cards.



The flip side is that Ward & co have integrated a lot of other functionality into the distro so if they tried to keep current I suppose it would be be headache.

But this distro just got a working "update-source" script for 1.6 in 2010 and they still say "stay away from DAHDI..."


That will be changing in the 1.7.5.5 release. While we still like zaptel for rock solid pbx's you will have the choice of using dahdi with asterisk 1.4-current version or asterisk 1.6 current version. As for the "just got a working update-source" all I can say is why don't you pay my mortgage and I will gladly put things out faster.

Also unlike many distros of fine pbx systems we change things fairly slowly and only once they actually work. While this pisses the bleeding edgers off we take the long view of reliable systems for the long term much like historical hardware based PBX systems.

Now you will have the option of going to hell in your own way.




I'm hoping they change their minds and fully embrace 1.6 and DAHDI but I get the sense they are just biding time until maybe something like FreeSwitch is baked enough...

Anything is possible..... I am not happy with our internal build of freeswitch yet as it is not fully baked....


Tom

 

[dstroot]

Now you will have the option of going to hell in your own way.



Tom

I guess I deserved that one. Although I can't cover your mortgage I do appreciate your major contribution to PAIF. Thanks.

 

[blanchae]

I have been using dahdi with 1.6 since Jan 2009 and have gone through all the bells and whistles to figure it out. The config files should follow the same format/standard as the other protocols like sip and iax. Here's the breakdown as far as I see it:

chan_dahdi.conf - contains links (includes) to the following files:
chan_dahdi_general.conf - this is where the global settings should be that freepbx sets
chan_dahdi_general_custom.conf - this is where the global settings that joe user can modify
chan_dahdi_additional.conf - this is where FreePBX configures extensions
chan_dahdi_additional_custom.conf - this is for unique extensions
chan_dahdi_trunks.conf - this would be new and used for configuring fxo and PRI trunks, normally FreePBX would configure this but this is one area missing out of FreePBX, if a module were built then a _custom.conf file would be added.

I've updated my website this past week, specifically to re-organize the zaptel and dahdi configuration and troubleshooting sections.

The biggest issue with dahdi/zaptel that is a major difference from all the other protocols, is that dahdi/zaptel has a hardware component that must be configured first before asterisk runs AND the asterisk software configuration MUST agree otherwise nothing happens which is extremely frustrating because it just doesn't work with little indication of why.

Another issue is that if you are adding a new zaptel or dahdi device to the system, as you configure, you must stop asterisk, restart zaptel/dahdi then start asterisk again. This makes it way more complicated than creating a sip or iax trunk.

There is extremely good error reporting buried in the asterisk full log file and the error messages should really be made more visible. That alone would help greatly.

One config file that is created if you use dahdi_genconf is /etc/asterisk/dahdi_channels.conf, which for some reason or other creates "example" extensions and trunks which don't match what is generated by FreePBX. These extensions and trunks can fail asterisk because if there is one error in any of the config files (hardware or software) then dahdi will fail to load. I don't recommend including this file in chan_dahdi.conf.

Dadhi/zaptel is extremely unforgiving, for example, I have 9 T1 lines (about 200 extensions), if there is 1 typo then asterisk chokes and won't load dahdi. This makes it very difficult for new users to configure.

 

[Alex728]

But this distro just got a working "update-source" script for 1.6 in 2010 and they still say "stay away from DAHDI..."

I'm hoping they change their minds and fully embrace 1.6 and DAHDI but I get the sense they are just biding time until maybe something like FreeSwitch is baked enough...

There is a world outside North America. PIAF appears to attract more users from the UK and Europe than other distros.

Its still unclear whether DAHDI works reliably with UK telephone lines due to the line testing signals - and if it doesn't the results are unpleasant as all the lines will be shown as disconnected - this line test happens in the middle of the night so a business won't realise what is going on until they try to dial out (and to inbound callers it would seem that no-one is bothering to pick up the phone!)

Even some versions of zaptel segfault on these tests on certain boxes (although thankfully asterisk just restarts)

There is a fix but it took a year to go through Digium's process and its still not clear if its made it into the current Asterisk/DAHDI combination.

the UK's telecoms pricing system also still (bizzarely) makes having 3-4 analogue copper pairs work out cheaper than a fractional E1 so many businesses depend a lot on PABXs which can reliably interface with analogue lines..

so for Brits (and perhaps other nations too) Zaptel "just works"..

 

[wardmundy]

so for Brits (and perhaps other nations too) Zaptel "just works"..

Funny. That's all but become the mantra of PBX in a Flash... It Just Works!

 

[womble1]

There is a world outside North America. PIAF appears to attract more users from the UK and Europe than other distros.

Its still unclear whether DAHDI works reliably with UK telephone lines due to the line testing signals - and if it doesn't the results are unpleasant as all the lines will be shown as disconnected - this line test happens in the middle of the night so a business won't realise what is going on until they try to dial out (and to inbound callers it would seem that no-one is bothering to pick up the phone!)

Even some versions of zaptel segfault on these tests on certain boxes (although thankfully asterisk just restarts)

There is a fix but it took a year to go through Digium's process and its still not clear if its made it into the current Asterisk/DAHDI combination.

the UK's telecoms pricing system also still (bizzarely) makes having 3-4 analogue copper pairs work out cheaper than a fractional E1 so many businesses depend a lot on PABXs which can reliably interface with analogue lines..

so for Brits (and perhaps other nations too) Zaptel "just works"..

Where are we with this ?

 

[blanchae]

FreePBX 2.8 has a Dahdi configuration module. We would have to test it to see what files it creates and follow their lead.