similar to: Dahdi causes panic on server restart

Hi Steve; Currently with Dahdi, for the below configuration that we were using it in the rc.local, how it will be? I think there should be something new to be used instead of ztcfg, what it is? And what about other lines? They need to be changed? touch /var/lock/subsys/local /sbin/modprobe wctdm /sbin/ztcfg -vv /usr/sbin/fxotune -s /usr/sbin/safe_asterisk Regards Bilal --- On Thu, 5/1/08,

Hello, I have just installed an Asterisk server with a Digium TDM410P card with 3 FXO modules (no module in the 4th slot). It's lived on two different machines (a test machine, which had Linux kernel 2.6.28, and a new dedicated machine which has Linux kernel 2.6.32). On the test machine (2.6.28), I used the Zaptel drivers. Once the kernel modules were loaded, the lights on the TDM410P came

Hi Eric, > On 12 avr. 2016, at 17:48, Eric Cooper <ecc at cmu.edu> wrote: > > On Tue, Apr 12, 2016 at 04:36:58PM +0200, Bertrand LUPART - Linkeo.com wrote: >> I just made a asterisk / dahdi fresh install on Debian 8.4, and ended up with the following packages : >> [...] >> However, i can't find any dahdi startup script, neither init.d neither systemd

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

" Hello, Strangely i purchase a TDM440E with the echo canceller onboard and I still receive a horrible echo and i'm only using bridged connections between DAHDI/4 and DAHDI/1. I turned of echo cancellation on bridged connections which seemed to help alittle bit. I ran fxotune -i5 and setup fxotune -s to apply settings on startup, which has helpped but there is still echo on the

Greetings, This may be a dumb question, but here goes. When I was on 1.4.21.2 using Zaptel, I had (at least as far as I could tell) access to line supervision on my POTS lines using a TDM400P/TDM410P. Since upgrading to the DAHDI branches of 1.4 (SVN and 1.4.26.1), I've only been able to duplicate the success of the 1.4.21 functionality once. To test what I'm talking

Hi gang, We are moving our computers from a cluster of physical machines to a VMWARE server with virtual machines. We investigated and are looking to replace our TDM400P/TDM410P with AEX410P cards. Can we run asterisk with the DAHDI drivers from one of the Virtual machines or is DAHDI going to have to be a native process on the "REAL" machine? Thanks Danny Nicholas

Greeting list, I hope this isn't a "lazy" question. I have been running TDM400P and TDM410P cards in Dell PowerEdge Servers for a few years now. We are moving from physical servers to VMWARE servers. What opportunities should I expect moving these cards into the new machines? Or should I leave the existing machines intact and use IAX to get to the DAHDI lines

Hi Listers, I'm running 1.4.25-rc1 on opensuse 11.0 with dahdi-linux-2.1.0.3, dahdi-tools-2.1.0.2, libpri-1.4.7 and snapdsp.0.0.2. Incoming calls work fine. Outgoing calls made directly (exten => s,1,Dial(DAHDI/G1) then number work fine. The problem I have is trying to let Asterisk make the call (exten => s,1,Dial(DAHDI/G1/5551212,,r). If I use "m" (moh) the

Good day , I have configured TDM410P (asterisk 1.6.x) on Cent OS 5, but dahdi take some time to hangup the call when playing the IVR..(it will send the hangup signal after finishing the IVR promt..) is there any specific setting to avoid such incidents ? iam using busycount as 3, signalling=fxs_ks ;toneduration=100 callwaiting=yes threewaycalling=yes callreturn=yes

Hi, Trying to configure my tdm410p card, my dahdi in asterisk cli was missing. ! ael agent agi cdr channel cli config console core database devstate dialplan dnsmgr dundi features file group hangup help http iax2 indication keys

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've got a Digium Wildcard TDM410P with one POTS line and three extensions. One of the extensions is connected to a fax modem. This kind of works, but there's a gotcha. If I set faxdetect=incoming in chan_dahdi.conf, then incoming faxes do get routed to the modem and this all works, but outbound faxes fail, with a message like this: [Oct 29 21:57:09] WARNING[16732][C-00000000] app_dial.c:

This may be commonly known but I haven't come across it so here goes, maybe it'll help someone: I have terrible echo with asterisk 1.2, zaptel 1.2.12, and a TDM400P with 1 FXS and two FXO modules. The Mark2 echo canceller with Aggressive turned on was the only setting that would make it acceptable. I found fxotune with this zaptel version to be broken. I pulled the latest fxotune.c

I noticed the following came into cvs head yesterday: > Update of /usr/cvsroot/zaptel > In directory mongoose.digium.com:/tmp/cvs-serv2118 > > Modified Files: > fxotune.c wctdm.c wctdm.h > Log Message: > More TDM card echo API modifications. Making the fxotune program automatically > find the correct coefficients for the module. Lots of neat stuff. I did a complete

Hey all, First of all, some background: Fxotune is a utility that is used to tune the hybrid on FXO modules For all of you with FXO modules out there, fxotune can help you adjust the analog and digital hybrid that is on the FXO interface and tune it so that it maximizes echo return loss. This means that it will reduce your default echo which is received, and will help any echo cancellers

Hi Steve; Currently with Dahdi, for the below configuration that we were using it in the rc.local, how it will be? I think there should be something new to be used instead of ztcfg, what it is? And what about other lines? They need to be changed? touch /var/lock/subsys/local /sbin/modprobe wctdm /sbin/ztcfg -vv /usr/sbin/fxotune -s /usr/sbin/safe_asterisk Regards Bilal --- On Thu, 5/1/08,

System details: Digium Wildcard TDM410P with three extensions and one POTS line. Dual core Pentium 4 (32-bit) processor Fedora 18 Asterisk 11.2.1 DAHDI Version: 2.6.2 Echo Canceller: HWEC I recently upgraded from Asterisk 1.4, and made as few changes to the configuration files as possible. I regenerated the dahdi-channels.conf file, then I believe I had to edit this to set the contexts

Hello, I am currently trying to configure an Asterisk (current 1.4) box with a TDM410P and 2 FXS as well as 2FXO modules. An analog modem is directly connected to the TDM (port 4) which itself is directly connected to the PSTN (port 1). [V.34 Modem]-----[TDM on Ast. 1.4 TDM]---PSTN When I try to establish an analog modem connection with this setup, the modem is unable to connect to the remote

My SM56 (Motorola X100P clone) has echo as hight as 38%, according to fxotune -d. But when trying to take action, it fxotune simply says it can't. ./fxotune -i3 -vvvv Running with parameters: doset=0 docalibrate=1 dodump=0 startdev=1 stopdev=252 calibtype=2 waveformtype=-1 delaytosilence=0 silencegoodfor=18