similar to: DAHDI aaaaaaaaaaaaaaarrrrrrrrrghhhhhhhhh :((((

Hi, How to properly re-configure dahdi, when for instance I want to change from TE to NT mode ? I'm planning the following operations : /etc/init.d/asterisk stop /etc/init.d/dahdi stop rmmod dahdi rm /etc/asterisk/dahdi-channels.conf rm /etc/dahdi/system.conf rm /etc/dahdi/modules nano /etc/dahdi/genconf_parameters dahdi_genconf -v modules dahdi_genconf -v system dahdi_genconf -v chandahdi

Hello, 1. How can specify in /etc/dahdi/genconf_parameters file that a port from a B410P board is to be "disabled". Playing with comments (see bellow) doesn't help : file /etc/asterisk/dahdi-channels.conf is filled with 4 ports data. pri_termtype SPAN/1 TE SPAN/2 TE SPAN/3 TE # SPAN/4 TE 2. How can specify groups in

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, On a Lenny system, with dahdi 2.4.0, libpri 1.4.11.5 and asterisk 1.6.1.18, I inserted a new Digium HA8 + B400M card. My usual installation fails. I can see it listed : # lspci -n | grep d161 01:0b.0 0200: d161:8007 (rev 11) # lspci -vn 01:0b.0 0200: d161:8007 (rev 11) Subsystem: d161:8007 Flags: medium devsel, IRQ 22 I/O ports at d400 [size=256] Memory at

Hi, I'm using Asterisk 1.6.1.18 with latest Dahdi Linux and Tools (rev 8854) and libpri 1.4.10.2. During installation, I'm facing this : # dahdi_genconf -v system Default parameters from /etc/dahdi/genconf_parameters Empty configuration -- no spans Of course, I've got span descriptions in /etc/dahdi/genconf_parameters : .... pri_termtype SPAN/1 TE SPAN/2

Hi, I've just discovered that dahdi_genconf could create configuration files reading a single genconf_parameter file. 1. Is using dahdi_genconf recommended to configure dahdi or is it a helpful tool for specific devices or installation processes ? 2. If not, is there a custom mecanism that would prevent hand-edited files to be written over by dahdi_genconf (you can obviously remove

Hi, I'm using revision 6822 of Dahdi Tools. # dahdi_hardware pci:0000:05:06.0 wcb4xxp+ d161:b410 Digium Wildcard B410P # asterisk -rx "dahdi show version" DAHDI Version: 2.2.0.2 Echo Canceller: OSLEC # cat /etc/dahdi/genconf_parameters ... pri_termtype SPAN/1 TE SPAN/2 TE SPAN/3 NT SPAN/4 NT #

Hi I have a TDM400 and 4 channels of HPEC. I don't use the POTs lines much so I didn't realize it wasn't working. This morning I was watching the console and noticed that the echo canceller didn't load when a call came in. /etc/dahdi/system.conf showed mg2 for all 4 channels. I changed them all to hpec and then restarted dahdi and Asterisk and suddenly HPEC was working. Is

On Sat, Jan 17, 2015 at 09:31:33AM +0100, Bertrand LUPART - Linkeo.com wrote: > >>> However, dahdi_genconf keeps finding no span: > >>> What am i missing? > >> > >> It looks like your driver is loaded correctly. My guess would be maybe > >> the dahdi-tools is packaged as an older version that doesn't know > >> about the newer te435

Hello, On a very new system, I've got : # cat /etc/dahdi/genconf_parameters | grep -v "^#" lc_country fr context_lines remote group_lines 1 bri_sig_style bri_ptmp echo_can oslec pri_termtype SPAN/1 TE SPAN/2 TE SPAN/3 TE SPAN/4 TE # dahdi_genconf Empty

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

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

At the top of my /etc/dahdi/system.conf file is this line: # Autogenerated by /usr/sbin/dahdi_genconf on Wed Feb 25 18:25:10 2009 -- do not hand edit OK, so how do I adjust the timing source and LBO numbers, and echo cancellers if I'm not supposed to edit this file? Brandon. -------------- next part -------------- An HTML attachment was scrubbed... URL:

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?

Hi, My genconf_parameter is : # grep -v "^#" genconf_parameters lc_country fr context_lines remote group_lines 1 bri_sig_style bri echo_can oslec pri_termtype SPAN/* NT (I also tried various identations and syntax for pri_termtype line such as bri_termtype but I still get the same output file). But still, generated system.conf contains

I have a CentOS release 4.7 box running asterisk-1.4.26.1 with dahdi-linux-2.2.0.2 and dahdi-tools-2.2.0 I regularly get these messages, is this something i should be worried about? [Aug 21 01:05:07] VERBOSE[4343] logger.c: codec_g726.so => (ITU G.726-32kbps G726 Transcoder) [Aug 21 01:05:07] ERROR[4343] codec_dahdi.c: Failed to open /dev/dahdi/transcode: No such file or directory [Aug

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

Hello, I just installed a Debian Jessie box from scratch which sports a Digium TE435 digital card. I installed the software, built and loaded the kernel modules: # dpkg -l|grep dahdi ii asterisk-dahdi 1:11.13.1~dfsg-2+b1 amd64 DAHDI devices support for the Asterisk PBX ii dahdi 1:2.10.0.1-1 amd64

Because of a kernel upgrade i needed to recompile DAHDI. Dahdi 2.0.0 with 2.0.1 was working ok, after the reboot and compile it doesn't start anymore. Firstly it tells me it is using /etc/zaptel.conf which is deprecated, if i remove that file it complains that this file is missing..... Secondly i get an error about a missing dev file which refers to zap (which seems strange to me because

Hello, I just made a asterisk / dahdi fresh install on Debian 8.4, and ended up with the following packages : $ sudo dpkg -l|grep -Ei 'dahdi|asterisk|libpri' ii asterisk 1:11.13.1~dfsg-2+b1 amd64 Open Source Private Branch Exchange (PBX) ii asterisk-config 1:11.13.1~dfsg-2 all Configuration