similar to: "dahdi show channels" no such command

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

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

Hello out there, I'm running an Asterisk 1.8.15-cert1 with DAHDI. Today I noticed that Asterisk is signalling to the calling party the current internal CallerID whenever I put a call to another internal phone. Example: Customer calls 020212345-555 -> IVR answers and puts caller to the chosen queue -> Someone picks up the phone (Internal ext. 321) -> CallerID shown on customers

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,

Hi, Most people using iaxmodem + HylaFAX or spandsp from an Asterisk application get satisfactory results for both transmitting and receiving FAXes. However, quite a few people find FAX receive is reliable, but FAX transmit can be flaky. Its box dependent. The cause of this has been known since the early days of spandsp. Asterisk + zaptel/dahdi is unable to produce a consistent audio stream

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

Hello, I have Asterisk version: Asterisk SVN-branch-11-r420435 I have the following code: exten => 303,1,NoOp(Dialing ${EXTEN}) ? ? ? ? same => n,NoOp(DBKey = ${DBKey}) ? ? ? ? same => n,DB_DELETE(office/${DBKey}) ? ? ? ? ? same => n,Playback(auth-thankyou) ? ? ? ? same => n,Hangup() And I get the following error: [2014-08-09 18:00:30] WARNING[4338][C-00000067]: pbx.c:4869

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

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, 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,

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.

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 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

Hi I took a UEFI image of CentOS 7.7, (dahdi runs on the image). copied that to a physical disk with dd, booted the image and dahdi does not start. doing service dahdi restart says "could not insert dahdi module - the required key is not found." How do I get dahdi to be happy ? it is "NOT" possible to disable UEFI on my hardware. Kernel is 3.10.0-1062.12.el7 I saw

Some recent issues I had with hardware seem to come back to not understanding two very similarly named files: /etc/asterisk/dahdi-channels.conf /etc/asterisk/chan_dahdi.conf I've modified the chan_dahdi.conf to work now, but it would appear all I needed to do was include dahdi-channels.conf in chan_dahdi.conf and the problem would not have persisted? Is it me or is that a bit Monty Python?

after installing asterisk 1.4.23.1 and dahdi-linux-2.1.0.4 and at CLI> module load chan_dahdi.so receive the following: signalling must be specified before any channels are. CLI> Warning [4663]: chan_dahdi.c:11627 process_dahdi: Ignoring signalling Error[4663]: chan_dahdi.c:10946 build_channels: Unable to reconfigure channel '1' Error[4663]:

Hey, all. Just added an analog card to our dual-T1 system... and clearly I'm doing something wrong. Less interested in having the specifics pointed out than in finding out how/why certain things work. So, really, three things: * What the bloody Hell is the difference between dahdi-channels.conf and chan_dahdi.conf? (And who thought it was a good idea to have two files with,

Hi, I've always used dahdi-genconf to just create the dahdi-channels.conf and since our PRI is fairly simple (just dump all the channels into one group) it works with dialing with dahdi/g1/(number). I'm trying to understand the file though for my own reference. It seems the file looks like this: group=0,11 context=from-pstn switchtype = national signalling = pri_cpe channel => 1-23

Hi, After an upgrade, I discovered yesterday strange things I would like to share here. Basically, I'me comparing platforms: The first one is a 2.6.26 (Debian Lenny) platform, with Asterisk 1.6.1.18, Libpri 1.4.10.2, Dahdi revision 8853 (must be between 2.3 and 2.5, I think). The second one is a 2.6.32 (Debian Squeeze) platform, with Asterisk 10.5.1, Libpri 1.4.12, Dahdi 2.6.1. Both are

I own a TDM2400 board, with three FXO modules and one FXS. I'am having trouble with analog sip phones, from two different equipment. (Grandstream GXW-4024 192.168.0.105, and Audiocodes MP202), sometimes when I am calling someone, then I press flash, and then call someone else, both calls stay connected after I hang up. [Sep 29 07:18:06] VERBOSE[3218] logger.c: -- Called g2/16 [Sep 29