similar to: How to properly re-configure dahdi

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

The information (or lack of it) on upgrading from zaptel to that @&*^QW%&^%!!! dahdi is very frustrating. I cannot find anything on how to uninstall zaptel, i found an earlier post to this list which suggested make uninstall and make remove in the zaptel directory which just generates errors and does nothing (on zaptel 12.1). Then i install dahdi-linux and dahdi-tools and i want to

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'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, 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'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 #

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

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

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

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

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

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

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

Hi, On lenny, when I'm adding a "blacklist hfc4s8s_l1" statement in a /etc/modprobe.d/myfile.conf file, this change seems ineffective until I reboot : # dahdi_genconf -v system Default parameters from /etc/dahdi/genconf_parameters Empty configuration -- no spans Generating /etc/dahdi/system.conf I tried this : /etc/init.d/module-init-tools then this : /etc/init.d/udev restart but

2010/8/24 Olivier <oza_4h07 at yahoo.fr> > Hi, > > On lenny, when I'm adding a "blacklist hfc4s8s_l1" statement in a > /etc/modprobe.d/myfile.conf file, this change seems ineffective until I > reboot : > # dahdi_genconf -v system > Default parameters from /etc/dahdi/genconf_parameters > Empty configuration -- no spans > Generating

The Asterisk Development Team is pleased to announce the first release of DAHDI-Linux 2.6.0 and DAHDI-Tools 2.6.0. 2.6.0 is a feature release which: - Adds support for the TE820 8-span card to the wct4xxp driver. - Decrease load time of analog cards supported by the wctdm24xxp driver. - Adds sysfs object model to facilitate persistent span numbering and early loading of modules

The Asterisk Development Team is pleased to announce the first release of DAHDI-Linux 2.6.0 and DAHDI-Tools 2.6.0. 2.6.0 is a feature release which: - Adds support for the TE820 8-span card to the wct4xxp driver. - Decrease load time of analog cards supported by the wctdm24xxp driver. - Adds sysfs object model to facilitate persistent span numbering and early loading of modules

Greetings, I have a quad port Tormenta 2 PCI card (uses the tor2 driver), which I have been successfully using for some time on an older, power-hungry Intel machine. I recently moved it to a newer machine with an Intel Atom D510 CPU in an effort to save on energy costs, but I cannot seem to get it to work there. Both machines are running Ubuntu 13.10 x64, with DAHDI support coming from the