similar to: DAHDI not loading

Hi, I'm using a revision 6822-enabled Dahdi-Tools (see https://issues.asterisk.org/view.php?id=13897) with a Junghanns QuadBRI. 1. Do I still need qozap driver ? If positive, how is it recommended to get it ? 2. Which line should be included in /etc/dahdi/modules to have the appropriate driver loaded ? 3. The process I'm planning to use is : A- Hand edit /etc/dadhi/modules,

I have followed the instructions in Asterisk The Definitive Guide 4th edition. ?Once I load DAHDI I run the dahdi show channels command and get no such command. ?I have setup all the conf files. ?I compiled DADHI prior to Asterisk. Any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Here's a call coming in over PSTN to dahdi/4, connected to a local extension dahdi/1: -- Executing [s at incoming-pstn-line:1] Answer("DAHDI/4-1", "") in new stack .......... -- Executing [s at incoming-pstn-line:6] Dial("DAHDI/4-1", "DAHDI/g0,36") in new stack -- Called g0 -- DAHDI/1-1 is ringing -- DAHDI/1-1 is ringing

Hi, I need to run ztdummy for Paging, but now that this is all become dahdi I don`t really know where to start. I did build dahdi before building asterisk, but that`s it. I find it hard to find any documentation referring to dadhi instead of zaptel. I have no Digium hardware, but I still need the ztdummy timer (or whatever it`s called now). How do I get myself going? Regards,

HI All, I tried removing the dahdi directory - re-extracting from source and recompile. Did not help. Still getting the error. I am installing from source. Thoughts ? Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200316/30cb7b29/attachment.html>

Hi List. I've bought a new server for my home asterisk installation and I'm trying to install asterisk with dahdi drivers and OSLEC. To do that I've got the svn dahdi-linux trunk revision 5366 and the echo subproject from the 2.6.28-rc6 Linux kernel sources. As reported in the dadhi README file I've uncommented out the two OSLEC related lines at Kbuild file in the

Looking for some help from the UK please. I backed up all my Asterisk configuration before re-installing the server from 32 -> 64 bit. Unfortunately I did not transfer the backup to another machine!!!!! I now have a TDM400P that is not picking up the line. Can you see what I have done wrong when I have rebuilt the config please: dahdi_scan ---------- [1] active=yes alarms=OK

Hi I am in the process of installing a new box and using dahdi. I have a tdm410 + hardware echo canceller. I have just read in the read me for dadhi that VPMADT032 support has been removed and unlike with the zaptel stuff i could just download and install the firmware I can't with dahdi what is the best way forward to recompile with hardware echo canceller support. Thanks Alex

Hi, I'm using an half T1 line on a asterisk (obviously :)) 1.6.2.4 system, up to recently everything was fine but we are starting to experience the call limitation of the line (15). So as to warn user of the problem i attached a vocal notification to the CONGESTION status after a Dial(), but it looks like it also catch other congestion case (maybe on the receiver side). Should i / Could i

Hi, After upgrading to DAHDI 2.4.0 from Zaptel, I noticed a lot of HDLC errors on my console: [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 These errors prevented calls from being made and received on my PRI spans. This seems

I've seen this consistently on three systems, with three different cards, and multiple versions of DAHDI. At first I thought the issue only occurred on newer, Nehalem-based, systems, but I reproduced it on a Core 2 Duo box as well. I've tested with dahdi-linux 2.2.0.2, dadhi- linux-complete 2.0.0+2.0.0, 2.1.0.2+2.1.0.2, and 2.2.0.2+2.2.0. The card is a Digium TE220B which uses the

Hi All, I have installed asteriskNow with Asterisk 1.6.2.11 and FreePBX 2.7.0.10. I have configured x100p fxo card in my asterisk box. But in my cli mode i am not getting the command *"dahdi show status"* Output of CLI : astrisks*CLI> *dahdi show status* No such command 'dahdi show status' (type 'core show help dahdi show' for other possible commands) I

Has anyone experimented with increasing the DAHDI chunk size in improve fax reliability? If so, did it help, hurt, or not make any difference?

Hi, Sometimes calls on Asterisk fail to connect to DAHDI channels and giving below error: Unable to create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion) There are 8 E1 connected on server and only 15-20 simultaneous calls. All channels and E1 are showing in service without any alarms. Could anyone please let me know why this is happening? Thanks

> Just a guess, > Recompile Dadhi. I'd rather not have to do that step. I "desire" to make the image and copy to the physical disk with dd and have everything set to go. Not take further time and "recompile" things. How do I do that? Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL:

From asterisk -cvvvvv == Parsing '/etc/asterisk/chan_dahdi.conf': == Found == Parsing '/etc/asterisk/users.conf': == Found -- Automatically generated pseudo channel [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23. [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! I'm using Asterisk 1.4.24.1 with dahdi-linux-2.1.0.4 and dahdi-tools-2.1.0.2 compiled by myself with the source code of the official site of the project. I would like to update to one more newer version. I suppose that the recommendable thing is to maintain me in branch 1.4, reason why in this case it would be 1.4.30 that I suppose that

Dear Customer Support, i connected the asterisk to a e1 interface of our hipath4000. outgoing calls from a sip peer of my asterisk to an up0 telephone which iss connected to the hipath4000 are working. If you want to dial from an up0 device to the e1 interface where asterisk is connected to, you have to use the prefix 83. But when you enter the 3rd cipher this error appears at the cli

Hi, This is the output from queue show 28: 47 (DAHDI/g0/12345678) (realtime) (Ringing) has taken no calls yet Why is the devicestate "Ringing" when no channels is calling this number, and the queue says "has taken no calls yet"? Is it picking up the general state of a random channel on g0 in dahdi? Or what is happening? It only seems to happen with this particular

Using asterisk 1.6.2.1 and dahdi 2.2.0.2. dadhi-linux installed just fine. Using dahdi_dummy as there is no card in system. Did not install libpri, again, no card. When compiling asterisk, I include -with-dahdi and everything ./configure's fine but when I do 'make', everything goes fine but chan_dahdi doesn't get compiled. No errors. No warnings. It just skips it for some reason.