similar to: dahdi and linux-2.6.38

Hi. I am having problems with dahdi using kernel 2.6.32. I am using 2.6.30 kernel and it works fine -- here is the output of dahdi_cfg -vv ++ dahdi_cfg -vv DAHDI Tools Version - SVN-trunk-r8670 DAHDI Version: SVN-trunk-r7445M Echo Canceller(s): Configuration ====================== Channel map: Channel 01: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01) Channel 04: FXS Kewlstart

I have 2 separate Asterisk servers that are both exibiting this problem. 1 has a 4 port FXO digium card, the other an 8 port. For some reason when the machine reboots, the dahdi drivers are not properly loaded. Then asterisk ends up starting without dahdi support. I've tried everything that I can think of, even to the point of running dahdi_cfg in the asterisk startup script before

Hello, Getting this error on dahdi_cfg. Reverting to 2.8 the error goes away: *line 15: Unable to create 'dahdi_cfg' mutex.* Is this a problem? Thanks in advance. Full detail: [ebox]> dahdi_cfg -vvvvvvv DAHDI Tools Version - 2.9.0.1 DAHDI Version: 2.9.0 Echo Canceller(s): HWEC Configuration ====================== SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 2:

Hello all, Ok it is Sunday afternoon and I am going crazy. I have been running in circles so long that I can't think straight. As an example, I sent this message to the wrong address the first try, AAARRRRGGGGGGHHHHH. I have Asterisk 1.6.0.6 and DAHDI Tools Version - 2.1.0.2, DAHDI Version: 2.1.0.4, OpenSuSE 10.3 x86_64, tdm422 at the end of installing dahdi-linux and dahdi-tools I get:

Hi. I have a Debian Leni system with asterisk-1.8. I was trying to get meetme to work and it depends on dahdi, so I compiled dahdi-trunk and dahdi-tools-trunk, however, when trying to insert dahdi_dummy, it complained about symbol crc_ccitt_table, although the module was actually there in the kernel tree. So, I took the Debian source, and I had the config and I did make Bzimage, make modules

Hi. I have been using asterisk-1.6.2 and if I update the version -- using svn -- to around May 19 or after, when I dial a digit on my fxs port which is on an X400p card, asterisk seg faults. If I go back before about this date, this problem does not occur. The dahdi version is svn 7445. Any ideas would be appreciated. -- Your life is like a penny. You're going to lose it. The question

Hello group, I am installing Asterisk on a new pc running Ubuntu 12.04.3 Server. ?I have dahdi-complete-2.7.0.1+2.7.0.1, and have tried 2.6.1 and 2.8.0-rc1 and 2.8.0-rc2. ?I am following along in the ASTERISK The Definitive Guide 4th Edition and on page 116 when I issue the command $ sudo /etc/init.d/dahdi start I get the following error: Loading DAHDI hardware modules: ? ?wctdm24xxp: done

Hi. When I dial a Dahdi extension using asterisk 1.6.0, and there is no answer, the extension hangs up, but the dial status is busy instead of no answer. How do I get this to work -- do I need to update dahdi? The card is an X400p using its FXS module. Thanks in advance for any ideas on this. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it?

Hello I was editing files manually, and noticed that if I include the familiar "fxsks=1" in /etc/dahdi/system.conf, Dahdi fails loading: ===================== # cat /etc/dahdi/system.conf loadzone = fr defaultzone = fr fxsks=1 ===================== # /etc/init.d/dahdi start Loading DAHDI hardware modules: wctdm: [ OK ] /usr/share/dahdi/waitfor_xpds: Missing

Hello I'm trying to install Dahdi through source code on a Fedora 13 host to use an OpenVox PCI card with a single FXO port, but dahdi_cfg -vv isn't happy. 1. After successfully running "make all; make install; make config", I edited /etc/dahdi/system.conf thusly: loadzone=fr defaultzone=fr fxsks=1 2. Then ran "dahdi_cfg -vv" which says: ------------- DAHDI Tools

Hi. I have run into a problem compiling dahdi-linux in kernel 6.1.0-10. Apparently there was a change, so I found a patch to fix stdbool.h but now I have an implicit declaration of pci_alloc_consistent in drivers/dahdi/wct4xxp/base.c I don't see any other references to that name anywhere. I am using version from git 5c840cf43838e0690873e73409491c392333b3b8 . So, the question, how to fix,

Hi. I am using gentoo kernel 2.6.27-r2 and dahdi trunk svn 5211 and it will not compile with this kernel whereas it does compile with 2.6.25. Here is the relevant portion of the build: VERIFY /usr/src/dahdi-trunk/drivers/dahdi/xpp/init_card_1_30 VERIFY /usr/src/dahdi-trunk/drivers/dahdi/xpp/init_card_2_30 VERIFY /usr/src/dahdi-trunk/drivers/dahdi/xpp/init_card_3_30 VERIFY

Hi. I am using asterisk 1.4 (latest as of today) and zaptel 1.4 (latest as of today) and I cannot dial out using my 400P card with one fxs module and one fxo module. I am using kernel 2.6.24 and get the following log entries: [Feb 25 17:28:13] VERBOSE[25071] logger.c: -- Executing [s at macro-dialout-trunk:23] Dial("Zap/1-1", "ZAP/4/www411|300|wW") in new stack [Feb 25

Thank you, very interesting! As I understand the Digium card is used as a interrupt source for Asterisk? Is there a diagnostic tool available ? Anybody else experienced a simmialr problem? Thank you! HB > From: > covici at ccs.covici.com > Date: > Sat, 12 Dec 2009 19:04:23 -0500 > To: > Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users at

Dear all, i have a problem with a system running - Ubuntu 10.04 ( all updates done ) - ii asterisk 1:1.8.5.0-1digium1~lucid Open Source Private Branch Exchange (PBX) - ii asterisk-dahdi 1:1.8.5.0-1digium1~lucid DAHDI devices support for the Asterisk PBX I also use freepbx 2.9 for the configuration. Hardware is a Dell R410 and a Digium

Hi all, I am having trouble setting the signalling method for the B410P using DAHDI. Asterisk complains that it has never heard of 'bri_cpe' or 'bri_net' - but it doesn't mind having 'pri_cpe' etc. ERROR[4294]: chan_dahdi.c:11327 process_dahdi: Unknown signalling method 'bri_net' Dahdi - dahdi-linux-complete-2.1.0.4+2.1.0.2 Asterisk - 1.4.23.1 Libpri - 1.4.9

I have a TDM400. Just updated Fedora 12 to kernel 2.6.32. Rebuilt and installed dahdi-2.2.1. kernel modules loaded. lsmod | grep wctdm wctdm 37233 0 dahdi 194985 1 wctdm lsmod | grep dahdi dahdi 194985 1 wctdm crc_ccitt 1549 2 dahdi,isdnhdlc dmesg: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.2.1

Hi Eric, > On 12 avr. 2016, at 17:48, Eric Cooper <ecc at cmu.edu> wrote: > > On Tue, Apr 12, 2016 at 04:36:58PM +0200, Bertrand LUPART - Linkeo.com wrote: >> I just made a asterisk / dahdi fresh install on Debian 8.4, and ended up with the following packages : >> [...] >> However, i can't find any dahdi startup script, neither init.d neither systemd

Oh, I forgot to mention that Asterisk 15 went End-Of-Life last Thursday. :) You should use Asterisk 16. On Mon, Oct 7, 2019 at 5:58 AM George Joseph <gjoseph at digium.com> wrote: > > > On Fri, Oct 4, 2019 at 1:19 PM John Covici <covici at ccs.covici.com> wrote: > >> Hi. I am trying to install asterisk 15.7.4 from git onto a Debian 10 >> system and I am

OK, using zaptel 1.4 and asterisk 1.4 rev 6745, if someone types an asterisk from the other end of a call, I here it forever till the call hangs up. Looks like it starts the vldtmf, but never ends it from the logs. I am using Digium 400P rev I with one fxs and one fxo module. Any way around this one? Thanks. -- Your life is like a penny. You're going to lose it. The question is: How