similar to: dahdi/DTMF problem

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)

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?

The card you installed has FXO or FXS modules in it ????? are you getting your lines directly from the telco co??? Doug D On Mon 23/08/10 8:37 AM , Cassius Smith cassius at cassius.org sent: * -----Original Message----- * From: Todd Reese * Reply-to: Asterisk Users Mailing List - Non-Commercial Discussion * To: asterisk-users at lists.digium.com [3] * Subject: [asterisk-users] Dahdi

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 all, As i tested with Asterisk+dahdi+libpri with openvox BRI with NT mode, the ISDN phone does not work. There is the setting and error. ***********************Enviroment***************************** Asterisk-1.6.1.18 dahdi-linux-2.3.0.1 dahdi-tool-2.30. libpri-1.4.11.2 CentOS-5.5 OpenVox B400P ****************************************************************** In my case , I set prot 1 and

Hi all, Last night I went to replace an Asterisk 1.4 + mISDN + b410p box with Asterisk 1.6.2 and DAHDI BRI - to no avail. I had two servers so copied network setting etc from the working one, moved the card across, ran dahdi_genconf etc and it didn't work. Here's the console output with notices disabled: lucas*CLI> pri intense debug span 1 Enabled debugging on span 1 [Dec 16

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

Hi all, As i tested with Asterisk+dahdi+libpri with openvox BRI with NT mode, the ISDN phone does not work. There is the setting and error. ***********************Enviroment********************************** Asterisk-1.6.1.18 dahdi-linux-2.3.0.1 dahdi-tool-2.30. libpri-1.4.11.2 CentOS-5.5 OpenVox B400P ******************************************************************** In my case , I set prot 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

What is dahdi.auto_assign_spans and why should you care? In later versions the kernel module dahdi[Q] includes a new parameter: auto_assign_spans. It defaults to 1, and if you set it to 0, DAHDI can start behaving in strange and completely expected ways. Chances are the default will be set to 1 in a future version. Here is why you'll want to set it yourself. Up until DAHDI 2.5, hardware

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

Hello gang, We just got MaBell to turn on our callerid. I tested the capability with a southwest bell box and a plain phone, so I know the line is sending the signal. I'm running Asterisk SVN-branch-1.4-r204834 using a TDM400P card. Here is my dahdi_cfg -vv output: dahdi_cfg -vv DAHDI Tools Version - 2.1.0.2 DAHDI Version: 2.1.0.3 Echo Canceller(s): MG2

Hello everybody, I try to install -Ubuntu 8.04 server- a B410P and a TDM2400P together with Asterisk 1.4.26-2, dahdi-linux-2.2.0.2 and dahdi-tools-2.2.0. Problem I face is the following one: CLI> module load chan_dahdi.so == Registered application 'DAHDISendKeypadFacility' == Registered application 'ZapSendKeypadFacility' == Parsing

Hi All This may be a silly question but... I have this dahdi_genconf generated file: ; Autogenerated by /usr/sbin/dahdi_genconf on Fri Jul 4 22:05:29 2014 ; If you edit this file and execute /usr/sbin/dahdi_genconf again, ; your manual changes will be LOST. ; Dahdi Channels Configurations (chan_dahdi.conf) ; ; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended ; to

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:

Hello Team I have installed the new DL580 and used the new TE420B to add capacity on our ivr. Before I put new E1?s I decided to first move the old e1 from the old system to this new one but it has errors which not only affect the audio quality, but also cause the asterisk to refuse any call after sometime even though the channels seems up and active {seems d-channel fails}.. When processing

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

Hi fellow asterisk users, I am running Asterisk 1.4.29 with an Digium TE121 card (wcte12xp kernel module) an approx. 100 snom320. The whole installation is running without issues since 5 months. Without having changed anything on the asterisk server for at least 2 months, i noticed "clicking sounds" at external calls over the PRI. Asterisk constantly throws the following messages: ...

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

Hi, I tried again getting DTMF detection on my ISDN devices with dahdi going again. I used the channel debug to see whether asterisk sees the frames and detects them as DTMF. Interestingly here's what works: 1. GSM phone -> chan_dahdi g1 -> asterisk -> can_sip -> SIP phone Both the GSM phone and the SIP phone can issue DTMF that will be detected as features (transfer) 2.