On Sun, 30 May 2010 02:45:51 +0300, Tzafrir Cohen
tzafrir.co...@xorcom.com wrote:
This is a bug of the netjet module. It should not try to handle those
devices. While they use the netjet chipset, they are not the ISDN BRI
devices drivven by it.
[Snip details]
If nobody beats me to it, I'll
On Thu, May 27, 2010 at 12:29:05PM +0300, Tzafrir Cohen wrote:
On Wed, May 26, 2010 at 09:52:52PM +0200, Vincent wrote:
On Wed, 26 May 2010 17:30:08 +0200, Vincent codecompl...@free.fr
wrote:
More information, as I investigate:
For those having the same issue, here's what I learned:
On Wed, May 26, 2010 at 09:52:52PM +0200, Vincent wrote:
On Wed, 26 May 2010 17:30:08 +0200, Vincent codecompl...@free.fr
wrote:
More information, as I investigate:
For those having the same issue, here's what I learned:
1. In /etc/modprobe.d/dahdi.blacklist.conf, blacklist the netjet
DON'T RUN dahdi_genconf, as it overwrites system.conf.
Yes. dahdi_genconf reads /etc/dahdi/genconf_parameters and writes
/etc/dahdi/system.conf and /etc/asterisk/dahdi_channels.conf. You can
set the country as
lc_country fr
in /etc/dahdi/genconf_parameters.
1. When I run dahdi_genconf:
On Thu, 27 May 2010 12:29:05 +0300, Tzafrir Cohen
tzafrir.co...@xorcom.com wrote:
This is a bug of the netjet module. It should not try to handle those
devices. While they use the netjet chipset, they are not the ISDN BRI
devices drivven by it.
Thanks for the explanation. On this exact same
On Thu, 27 May 2010 11:41:09 +0200, Leonardo Pistone
l.pist...@sispac.it wrote:
Yes. dahdi_genconf reads /etc/dahdi/genconf_parameters and writes
/etc/dahdi/system.conf and /etc/asterisk/dahdi_channels.conf.
Thanks for the tip.
Do you have asterisk installed? You neet at least to mkdir
On Thu, May 27, 2010 at 03:03:21PM +0200, Vincent wrote:
On Thu, 27 May 2010 12:29:05 +0300, Tzafrir Cohen
tzafrir.co...@xorcom.com wrote:
This is a bug of the netjet module. It should not try to handle those
devices. While they use the netjet chipset, they are not the ISDN BRI
devices
On Thu, 27 May 2010 16:12:57 +0300, Tzafrir Cohen
tzafrir.co...@xorcom.com wrote:
Thanks for the explanation. On this exact same hardware, I didn't have
this problem with Dahdi/Zaptel 1.4.
Older kernel did not have the netjet module?
Yup, that could be the reason. Anyway, problem solved :-)
On Thu, 27 May 2010 15:09:45 +0200, Vincent codecompl...@free.fr
wrote:
/usr/share/dahdi/waitfor_xpds: Missing astribank_is_starting
Running dahdi_cfg: [ OK ]
it's harmless. but it's a symtom of building dahdi-tools without
libusb
https://issues.asterisk.org/view.php?id=17189
--
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
On Wed, 26 May 2010 17:17:08 +0200, Vincent codecompl...@free.fr
wrote:
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.
More information, as I investigate:
# vi
On Wed, 26 May 2010 17:30:08 +0200, Vincent codecompl...@free.fr
wrote:
More information, as I investigate:
For those having the same issue, here's what I learned:
1. In /etc/modprobe.d/dahdi.blacklist.conf, blacklist the netjet
driver:
blacklist netjet
2. To configure Dahdi, edit
12 matches
Mail list logo
