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

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

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

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

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

hello: thanks for Tzafrir Cohen for dahdi testing. I installed dahdi-2.1-r3c svn code and asterisk1-6 for testing OpenVox B400P and junghans card. i fund that there is bug (i think) to dectect NT or TE mode. actually on the board, i set it as TE mode, but after start wcb4xxp, but it show the port is NT mode. to detect the TE mode, I modefy the code in base.c

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

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 all! I'm new with telephony cards and DAHDI drivers. I have installed Asterisk NOW 3.0.0 and update to Asterisk 11.7.0, modules are update too. I'm following the installation guide of Atcom [1] for AX1600P analogic card, modules are loaded [root at pbx ~]# lsmod | grep -E "hisax|netjet|dahdi" netjet 14618 0 isdnhdlc 4523 1 netjet mISDNipac

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 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, 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, After an upgrade, I discovered yesterday strange things I would like to share here. Basically, I'me comparing platforms: The first one is a 2.6.26 (Debian Lenny) platform, with Asterisk 1.6.1.18, Libpri 1.4.10.2, Dahdi revision 8853 (must be between 2.3 and 2.5, I think). The second one is a 2.6.32 (Debian Squeeze) platform, with Asterisk 10.5.1, Libpri 1.4.12, Dahdi 2.6.1. Both are

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

Hello I'm trying to install Dahdi through source code on a Fedora 13 host to use an OpenVox PCI card with a single FXO port, but dahdi_cfg -vv isn't happy. 1. After successfully running "make all; make install; make config", I edited /etc/dahdi/system.conf thusly: loadzone=fr defaultzone=fr fxsks=1 2. Then ran "dahdi_cfg -vv" which says: ------------- DAHDI Tools