similar to: OT - How to blacklist a driver in /etc/modprobe.d without reboot [SOLVED]

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

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

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

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 #

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,

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

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

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

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

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

dahdi_cfg -vvv error `cut: '/sys/bus/dahdi_devices/devices/pci:0000:01:00.0/spantype': No such file or directory` PRI show spans --command not found test call not working. -- dahdi_genconf -vvv Default parameters from /etc/dahdi/genconf_parameters Generating /etc/dahdi/assigned-spans.conf cut: '/sys/bus/dahdi_devices/devices/pci:0000:01:00.0/spantype': No such file or

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

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 all, So, we reverted the LibPRI version and tested it, and then tried with the latest version of everything. Still no changes. The BRI line is in PTMP. If we set the configs to PTMP in the genconf_parameters and try it, we get the following: [Jan 21 17:32:20] ERROR[20341]: chan_dahdi.c:12645 dahdi_pri_error: Unable to receive TEI from network! If we set it to PTP (which it is not) we

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

Hi All, This is my first post. I searched the archives and found something similar and I tried some of those suggestions. I changed the file permissions on the scripts directory to 777 (which doesn't seem secure), I also manually ran the detectdahdi.sh script. The response is "None". I am running Mac OS X 10.5.7 with Asterisk 1.4.26.1 which I compiled from source. The Asterisk Gui