similar to: Problems with udev on FC3

I am using Fedora Core 3 distribution with tinc-1.0.3-1.1.fc3.rf. These are the contents of my configuration files: /etc/tinc/saaotun/tinc.conf: Name = suth DEvice = /dev/net/tun /etc/tinc/saaotun: /sbin/ifconfig eth0 192.168.1.1 netmask 255.0.0.0 /etc/tinc/saaotun/hosts/suth: -----BEGIN RSA PUBLIC KEY----- MIGJAoGBAMNiy1zXS6k3s+ocIdFWKU6MbpW3rQXGp7yIL+baY7GMxhOmsgZdyc1B

Hello, I can''t seem to get the network going. I found this message in the log of Domain0: ----------------------------------------------------------------------- Dec 1 15:39:18 zms wait_for_sysfs[4180]: either wait_for_sysfs (udev 039) needs an update to handle the device ''/class/net/br0'' properly (no device symlink) or the sysfs-support of your device''s

Hi, again. I've spent a week trying to get asterisk to work on FreeBSD unix, with some success. Everything works until I plug the box into the TELCO line and then the line goes off-hook and stays that way. So I bit the bullet and decided to install the application on a fresh linux install. Not to start an OS war, here, but linux is ... difficult ... for an old unix hand to get his mind

Hello everybody, After going through multiple posts on Internet and trying different things I can't seems get zaptel wcfxo loaded on the server correctly. I run dual P3 500 Mhz box. After reading README.udev I put a file 60-zaptel.rules /etc/udev/rules.d # Section for zaptel device KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer",

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greets all sorry for the posting but this one has me confused. I compiled Zaptel and am experiencing something strange. I followed the instructions on README.udevs to the tee, set permissions, etc. and I'm confused as to what gives. Zaptel compiled without a problem but no device was made.... [beta@staging ]# uname -a Linux xxx.xxx

I have decided to move on from Asterisk@Home and start compiling asterisk myself now. I got a dedicated box and put my X100P in it. I installed the server version of CentOS 4.2 (2.6.9-22.EL kernel) barebones. The box is a dell GX270 workstation with 1GB of RAM. I got a fresh copy of O'Reilly's Asterisk the future of technology and begun. I downloaded the zaptel-1.2.4.tar.gz, libpri-1.0.9,

Of course I am not a kernel expert, so .. please be patient. I am investigating on my zaptel/zapata problem. As the main error message asterisk quits on mentions <'/dev/zap/channel': No such file or directory> I went peeking over there. [Asterisk Verbose Error Mar 13 20:43:35 WARNING[5779]: chan_zap.c:763 zt_open: Unable to open '/ dev/zap/channel': No such file or

When I try to start up zaptel, whilst running ztcfg, I get the following error: Jan 1 10:48:18 bu ztcfg: ZT_CHANCONFIG failed on channel 2: No such device or address (6) My /etc/zaptel.conf is: fxsks=1 fxoks=2 loadzone = au defaultzone=au Channel 1 is a X101P card connected to the PSTN and channel 2 is a S100U box driving an analogue phone. The zaptel kernel module gets loaded OK as does the

Trying to setup asterisk and zaptel on a Fedora Core 3. Its all working after reading up on udev but I still get errors. [root@redhat ~]# ztcfg -vvvvv Zaptel Configuration ====================== Channel map: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 04: FXS Kewlstart (Default) (Slaves: 04) 2 channels configured. Notice: Configuration file is /etc/zaptel.conf line 4: Unable to

Just as an FYI.... I have a configuration suppestion to pass along... If you have: Fedora Core 3 Asterisk 1.0.x Digium Wildcard T100P PCI Card -------------------------------- In order to get the card to work you MUST edit /etc/udev/rules.d/50-udev.rules Goto the end of the file and add....... KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer",

> -----Original Message----- > From: Tzafrir Cohen [mailto:tzafrir.cohen@xorcom.com] > Sent: Wednesday, October 25, 2006 10:18 AM > To: asterisk-users@lists.digium.com > Subject: Re: [asterisk-users] Re: Meetme... No channel type registered > for'zap' > > > On Wed, Oct 25, 2006 at 10:06:02AM -0600, Douglas Garstang wrote: > > > -----Original

I have had a TDM400 with 2 FXO and 2 FXS working for ages (>12 months). It has stopped working. All four green lights are still lit. I have rebuilt zaptel and asterisk and restarted but the problem persists. /sbin/ztcfg -vvvv Zaptel Configuration ====================== Channel map: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 02: FXO Kewlstart (Default) (Slaves: 02) Channel 03:

Hi, I am sorry if this message has been reposted, but for some reason I am having problems with posting it. I configured asterisk and zaptel modules with fedora2. I want to be able to load the zaptel wcfxo and wcfxs modules. For now I will use only the Wildcard TDM400P card. I am able to load the modules but I cant configure them using ztcfg or zttool because the tools are compiled to use the

hi there I'm trying to get asterisk going on gentoo 2005.1 I'm just getting my feet wet so I thought I would just stick with the stable portage packages. Right now that's asterisk 1.0.8 I emerge asterisk with the following make.conf file: CFLAGS="-O2 -mcpu=i686" CHOST="i386-pc-linux-gnu" CXXFLAGS="${CFLAGS}" USE="-gtk -gnome -qt -kde -dvd alsa

Hi, I'm using zaptel-1.2.22.1 with asterisk-1.2.10 and following steps to make zaptel working... OS is gentoo linux 2006.1 Hardware: --------- 0000:05:01.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Unknown device 8085:0003 Flags: bus master, medium devsel, latency 32, IRQ 22 I/O ports at b400 Memory at ff900000

>rom: "Jose Hernandez" <jfhernandez_01@verizon.net> >Subject: RE: [Asterisk-Users] Unable to open master device > '/dev/zap/ctl' > >If you are using udev you will get a message during compile suggesting to >read README.udev, I did not pay attention to this message. > >Anyways.. I did not get the error after creating a udev rules file in

Hi, I had problems described in another thread so went from a start, but now have problems when loading qozap module. I get : # insmod qozap.ko ports=9 insmod: error inserting 'qozap.ko': -1 Unknown symbol in module and in /var/log/messages: module qozap unsupported by SUSE/Novell, tainting kernel. qozap: disagrees about version of symbol zt_receive qozap: Unknown symbol zt_receive

On 14/09/2018 at 09:30, Jean-Francois Dockes wrote: > Hi, > > You may be interested by how Recoll does it: > > https://www.lesbonscomptes.com/recoll/idxthreads/threadingRecoll.html > > A few things in the document are slightly obsolete (esp. the last > paragraph: recollindex now does use vfork()), but it's overall quite close > to how the current indexer works.

It's a udev configuration. Read UDEV.txt, or, read the AMP wiki http://aussievoip.com for a step-by-step. --Rob -----Original Message----- From: asterisk-users-bounces@lists.digium.com on behalf of Jachin Rupe Sent: Wed 7/09/2005 9:16 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] /dev/zap* is not showing up (gentoo, portage,asterisk 1.0.8 hi

Hi guys, I'm hoping I've made a silly mistake here, but I've been staring at the screen for the past few hours and I can't work it out. I upgraded to 1.2.16 recently, and am having problems with zaptel. The card is detected, I get a reasonable output from ztcfg -vv, and zttool shows the installed module (TDM400) with one FXS module. But when I start asterisk, I get