similar to: Dahdi & Congestion status

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

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:

In 1.4.43 I would see things from "core show channels" like DAHDI/18/xxxxx for line 18 in Asterisk 11 its DAHDI/i4/xxxx How do I get the line number back? Jerry

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,

I finally decided it's been long enough using my ancient HP junker and I built a Atom 330 based machine to replace it. I've installed Centos 5, Dahdi and Asterisk 1.6.2. After a bit of struggles getting the 1.2 version files converted to 1.6 almost everything seems to be working. All my SIP lines seem to work and calls come in as expected and all my DAHDI lines work with incoming

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

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

Hello I have upgraded our asterisk box from zaptel to dhadi two weeks ago... Since, there has been quite a significant amount of echo when making a call. Only for the local outgoing call, the person on the other side doesn't hear any echo. This is with a TE-110P ISDN PRI card .. I've pretty much took the original zaptel configuration and used it as-is with the dahdi one ; to no

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 have a tdm22b (2 fxs / 2 fxo) When Asterisk is just started, outbound calls routing to fxo port, do not working with error: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) Inbound calls to fxo port work fine. After first inbound call, the outbound calls starts working. CentOS 5.4 asterisk 1.6.0.21-1 dahdi 2.2.1.-1 Can anybody help me to identify what is the

I'm trying to add an emergency dial to my context. However, when I try to dial it, I get caught in an endless loop. For debugging, I have pared out nearly all the control flow and just have ChanIsAvail() and Dial() called. Using two different extensions to call teh same number, I get two different actions by *. Here is the vvverbose output: -- Starting simple switch on

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

Hy guys i am having so much hard time to setup asterisk on a virtual machine that i got , i just want to know if i really need to use Dahdi and libpri on a complete Digital PBX i just gonna use sip and iax. I will never use any kind of analog line on this machine. Wait for a feed back. Daniel Abreu.

Hi, I'm running Asterisk SVN-trunk-r226890 and whenever I restart asterisk and try to make a call I get the following error message: ======================================================================================== -- Executing [6781948 at default:1] Dial("IAX2/iaxy-7477", "DAHDI/g1/96781948") in new stack [Apr 25 13:00:10] WARNING[3772]: app_dial.c:1806

Hi all, I'm getting compilation error as trying to install latest version of dahdi on CentOS box 5.9 which I now updated from 5.6. I also installed the dependencies but still not getting the clue to get install the driver. Listing down the errors below; CC [M]

Yo he conseguido que los chunks y el texto tengan la misma anchura instalando ?tinytex?. Un saludo, Patricio Patricio Suárez Gil Unidad de Investigación Área V-Gijón Planta 5ª Impar Hospital Universitario de Cabueñes C/Prado, 395 33203 Gijón (Asturias) Tfno: 985 185 000 (Ext. 85715) @uinvest_psg ESPAÑA [[alternative HTML version deleted]]

Instalado ?tinytex? > install.packages(?tinytex?) y cargándolo > library(tinytex) Fue una causalidad: cuando instalé este paquete los PDFs comenzaron a salir correctamente de anchura. Tampoco puede darte una explicación :( Saludos, Patricio Patricio Suárez Gil Unidad de Investigación Área V-Gijón Planta 5ª Impar Hospital Universitario de Cabueñes C/Prado, 395 33203 Gijón (Asturias)

On Thu, Aug 1, 2019 at 6:09 PM JF Bastien <jfbastien at apple.com> wrote: > > Hi Alexander, > > The code doesn’t compile. Could you send a godbolt.org link that shows the issue? Sorry about that, here's the link: https://godbolt.org/z/-PinQP Lines 4 to 8 are initializing |acpar|. If I'm understanding correctly, the store to 8(%rsp) at line 7 can be removed because of the