similar to: No subject

On Thu, Jun 6, 2019 at 12:17 PM Malcolm Davenport <malcolmd at sangoma.com> wrote: > Howdy, > > There's a dahdi-linux-complete-3.1.0-rc1+3.1.0-rc1.tar.gz. > > Try that. > I noticed that was there, but I didn't try it originally because it's obviously a beta version. However, I did download it and try it. It does compile, but doesn't work correctly. For one

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

Running Asterisk 1.6.2.9, DAHDI 2.3.0.1, CentOS 5.5 (update to date as of a week ago), I've installed a Digium AEX800P with 2 X400M FXO Modules and 1 VPMADT032 Module, hooked up to 5 analog lines. I get the error message referenced in the subject in my dmesg output everytime I load / reload DAHDI using the command "system dahdi start/restart". When I make an outbound call over

I'm having a problem receiving incoming faxes and I'm hoping someone here can help me out. My system is a PBX in a Flash with one dahdi card for my incoming analog lines and another dahdi card for my analog devices (fax and modem). My dahdi-channels.conf file looks like: ; Autogenerated by /usr/sbin/dahdi_genconf on Tue Jun 23 14:56:24 2009 ; If you edit this file and execute

I have Asterisk 1.4.24 en a Digium TDM410 with EC and with 3 FXO modules. When I plug one PSTN-line into a FXO-port I am able to receive calls on this line and I can also make calls from an internal SIP-phone to the external PSTN-network. Still I am bothered about something that appears on the CLI when I do a reload chan_dahdi.so : asterisk*CLI> reload chan_dahdi.so -- Reloading module

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

Hi, I know it sounds weird, and this is part of the reason I have not reported that sooner. As I upgraded from 1.6.2.x to 1.8.x several months ago I am experiencing this problem. If a call is initiated from a DAHDI extension after no DAHDI extensions were used for some time, arbitrary DTMF digits are skipped and the call fails. If the call is redialed it goes through. Normally just one (1)

I am having problems getting a Nicherons TDM400P wildcard clone to dial out. Everything appears to be configured correctly, but although I see call progress, it never seems to actually pick up the phone. (The following is a test of 911 emergency, where I substitute 811 [repair service] as the actual number dialed.) *CLI> -- Executing [911 at from-internal:1]

[18884732963 at from-fax-machine:... - your call is hitting the from-fax-machine context - yet your 'fax' exten is in the from-pstn-4 context. See the "[2011-03-17 13:40:29.6] NOTICE[8825] chan_dahdi.c: Fax detected, but no fax extension" line. When Asterisk detects an incoming fax tone - it tries to automagically route the call to the 'fax' extension in the SAME

Hello, I am installing dahdi on a machine lspci 00:00.0 Host bridge: Intel Corporation 3200/3210 Chipset DRAM Controller (rev 01) 00:01.0 PCI bridge: Intel Corporation 3200/3210 Chipset Host-Primary PCI Express Bridge (rev 01) 00:06.0 PCI bridge: Intel Corporation 3210 Chipset Host-Secondary PCI Express Bridge (rev 01) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI

I've set up an outbound .call system for customer callbacks and the like. Calls are going out over analog lines and I'm trying to use the WaitForSilence routine to make sure the phone has stopped ringing before starting message playback. The problem is that if I set the first argument of WaitForSilence to anything other than 1, WaitForSilence never exits. Some general info on my setup:

Aloha, I'm not sure why I'm getting this error, but I can't seem to get chan_dahdi to load. SIP & IAX2 are working fine. Debian 4 w/ 2.6.28 kernel. Asterisk 1.6.1.5, dahdi-linux 2.2.0.2, dahdi-tools-2.2.0 CLI> module load chan_dahdi.so Unable to load module chan_dahdi.so Command 'module load chan_dahdi.so' failed. [Sep 1 10:57:51] WARNING[31696]: pbx.c:4550

I am running Asterisk 1.6.2.17.2 with a Openvox A400 card with 2FXO/2FXS modules. I'm trying to set-up things to route analog fax calls from a FXO port to an analog fax machine on a FXS port on the same card. Outgoing faxes work just fine. But incoming faces are routed to the right DAHDI extension, but the call dropped right as the fax machine rings for the first time. The fax machine

I am unable to dial out over a Wildcard TDM400P. This was working previously, so must have messed up the config somehow. I'm running Asterisk 1.6.0.15, with FreePBX 2.5.2.2. When I dial, I see: -- Executing [s at macro-dialout-trunk:19] Dial("DAHDI/1-1", "DAHDI/g0/9239220,300,") in new stack == Everyone is busy/congested at this time (1:0/1/0) It looks like the

My DAHDI phones were broken since a recent power outage (which required a reboot). For some reason the Asterisk or DAHDI configuration is messed up somewhere (probably from an update that was applied before the reboot?). I am using a Digium TDM410 card. At first, nothing worked at all, but I discovered that if I loaded things manually (e.g. modprobe dahdi; modprobe wctdm24xxp, then go into

Hi, Continuing with the saga of Digium vs MTNL Mumbai, looking for suggestions on handling incoming Caller-ID issues. The card manages to grab a couple of (random) digits of the incoming CID, but they're more or less useless. Is there any way to fix this? Asterisk 1.8.13, Dahdi 2.5.0.1 on Debian Testing (Wheezy), MTNL Mumbai. Digium, Inc. Wildcard AEX410 4-port analog card (PCI-Express)

Hi, Odd problem have just noticed in that when I call into the PBX DAHDI detects the call and hands it off to the extension, if I then hang up it still continues to process through the dialplan. This is what I have in chan_dahdi.conf: [channels] language=en echocancel=yes usecallerid=yes cidsignalling=v23 sendcalleridafter = 2 hanguponpolarityswitch=yes rxgain=2.0 txgain=3.0 progzone=uk

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

Hi I am having some problem forcing my tdm410 to alaw over ulaw, I have 1.6.1.0 asterisk (debian i486) dahdi 1:2.2.0 built with the hardware echo canceller firmware /etc/asterisk/chan_dahdi.conf alaw=1-4 but I have this in the general section, before any channel definition dahdi show channel 1 Default law: ulaw even when i have a call going it is still ulaw Thanks Alex