similar to: /dev/zap/channel ownership

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

Hi, In the 2nd edition of the Asterisk book, there is a section recommending running asterisk as non-root - tried this and it works. However, asterisk does not have permissions to view certain files relating to zaptel as in the following 'zap show status' command in the * CLI What would be the best way to get round this, in terms of reliability and security? Is there a way to allow the

Well, I'm experiencing a similar problem with my setup... debian etch, asterisk 1.4.2, zaptel 1.4.1, ... I cannot find the chan_zap.so module file anywhere, tried recompiling with zaptel 1.4.0... no change... I tried 'make menuselect', and going to the channels-part, chan_zap is marked XXX -> dependencies missing: and this is the message for it, as an explanation. Zapata Telephony

I have spent some time this morning trying to add an Astribank to our current Asterisk, but it failed, so I just removed the hardware, restore the config files to the original setup and started asterisk.; I could see that no Zap channels are started so I did load chan_zap.so: pbx*CLI> module load chan_zap.so [Feb 26 10:32:18] WARNING[3809]: pbx.c:2968 ast_register_application: Already have an

Hi, I've noticed that a small but meaningful quota of calls from my Alcatel PBX to Asterisk are failing. This does not always happen and it is not easily reproducible but on high traffic I do get a large number of cases. Example: Alcatel PBX extension 7085 calls Asterisk PBX extension 6145 over a PRI E1 link. I see this in the Asterisk log: Dec 14 14:10:31 VERBOSE[11378] logger.c: --

Hi list, Attempting to get an ISDN-BRI line connected using an HFC-S PCI card together with Asterisk v1.4.14 and Zaptel 1.4.7 on a Debian etch system, I find that I can't access the card's resources because the channels are always be busy. An attempt to call out results in the following CLI output: == Primary D-Channel on span 1 down == Primary D-Channel on span 2 down

Hi All I had asterisk running on a xercom install, I upgraded the box to a full debian install and now asterisk is not starting from on boot. I can start asterisk from the command line fine no problems, but when i type /etc/init.d/asterisk start it says asterisk PBX started. It doesn't start it though, when I look at the log file it has this. May 16 10:19:05 WARNING[3711]: Unable to open

Hi all. chan_zap not compiling, yes yes I know this sounds trivial but here me out... This morning I decided to upgrade to Asterisk 1.4.2 and Zaptel 1.4.1. I successfully installed zaptel 1.4.1 and the card is picked up and correctly configured. ztcfg shows the following: [root@zion root]# ztcfg -vv Zaptel Version: 1.4.1 Echo Canceller: MG2 Configuration ====================== Channel

Evening, My latest asterisk box is having a difficult problem. It is configured with one TE210P and TDM400P with four FXO modules. I'm running FC6. The TE210P only has a single PRI. When the system boots, it is completely random what order the zaptel modules will get loaded in. Sometimes zttool shows the FXO as the last span, sometimes as the first. When it does load as the first, which

Hi All; Suddenly the zaptel channel look like stop working and it is giving me this error when I do zap restart: [May 24 19:30:21] ERROR[2772]: chan_zap.c:7219 mkintf: Unable to open channel 1: Device or resource busy here = 0, tmp->channel = 1, channel = 1 [May 24 19:30:21] ERROR[2772]: chan_zap.c:10582 build_channels: Unable to register channel '1,2' To what it could be related?

Hi all, I am seeing on my logs this message: Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 on channel 3 Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 on channel 3 (repeated much more then what I will show here). I see that it comes from static void* do_monitor(void *data) in chan_zap.c, but I do not understand what does it

I am having trouble with chan_zap.so not loading. When I load it from modules.conf, Asterisk bails out without any error message. When I load it from the console, it just says "Unable to load module chan_zap.so" no matter what verbose level I am using. dmesg says: Zaptel Version: 1.4.4 Zaptel Echo Canceller: MG2 Freshmaker version: 73 Freshmaker passed register test Module 0:

Hi list, I've just compiled and installed Asterisk 1.4.16 and when I try to run "zap show" I get the message "*No such command 'zap show'*". I have a Sangoma Remora A400D with 2 FXS / 10 FXO ports, I've installed the latest wanpipe too. zaptel-1.4.7.1 was compiled from the wanpipe installation, so I don't know what's happening here!!! Any ideas???

Sorry I should have stated that I've tried +x, -x, x.y and x and I still get the same. Regards Lee -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Eric "ManxPower" Wieling Sent: 05 January 2007 08:10 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users]

Hi, Has anyone information about BRI hardware supported by 1.6 libpri ? In another thread, I was told a basic BRI card with HFC chipset (Bewan Gazel 128) was supported but I would delighted to lear about other harwarde (and specifically about Digium B410P). Regards -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

Hello I've been googling for this message, but can't find why Asterisk sends a warning. The configuration files look similar to http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf.sample It's a TDM card with just one FXO module on it, and I connected an RJ11 cable to it from the wall plug: # cat /etc/zaptel.conf fxsks=1 loadzone=fr defaultzone=fr # ztcfg -vv

Hi, I have debian etch 4.0 machine (2.6.18) with two TW-ISDN PCI (Hfc) cards. I use bristuff-0.3.0-PRE-1y-e (asterisk-1.2.17,libpri-1.2.4,zaptel-1.2.16). I also have patched zaphfc with zaphfc_0.4.0-test1_florz-13.diff.gz (I load module: insmod /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko modes=1 debug=1). So i want to test two cards and make loop between them. So one card would be NT,

Hi, after a few of upgrades, I noticed these messages in full debug log: Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring switchtype Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring pridialplan Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring prilocaldialplan Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring overlapdial Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring

I have the following dialplan (segment) that isn't working as I expected it to: exten => s,n,Dial(Zap/1&SIP/202&SIP/203,18) exten => s,n,Dial(Zap/1&SIP/201&SIP/202&SIP/203,42) The plan was to have SIP/201 added to the group of ringing phones after 3 or so rings. What ends up happening, though, is the Zap/1 phone STOPs ringing when the dialplan falls through to