similar to: chan_zap.c: Failed to read gains: Invalidargument

I am running Asterisk 1.2.14 and Zaptel 1.2.12 and using a Digium TE110P card in E1 mode. I've recently noticed in my logs the following Jan 5 01:27:11 VERBOSE[22490] logger.c: [chan_zap.so]Jan 5 01:27:11 VERBOSE[22490] logger.c: [chan_zap.so] => (Zapata Telephony w/PRI) Jan 5 01:27:11 VERBOSE[22490] logger.c: == Parsing '/etc/asterisk/zapata.conf': Jan 5 01:27:11

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

Hi, I' ve just connected a carte X100M to my asterisk server running zaptel-1.2.5, libpri-1.2.2 and asterisk-1.2.6 on SUSE 10.0. When I make modprobe wcfxo and modprobe zaptel I haven't any error, I have also chan_zap.so module existing in /usr/lib/asterisk/modules. But, when i run ztcfg, it shows me this: Zaptel Configuration ====================== Channel map: 0 channels configured.

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

Hello, When I start Asterisk, I get the following in my log (/var/log/asterisk/full): Mar 15 17:16:55 VERBOSE[4242] logger.c: == Parsing '/etc/asterisk/zapata.conf': Mar 15 17:16:55 VERBOSE[4242] logger.c: == Parsing '/etc/asterisk/zapata.conf': Found Mar 15 17:16:55 DEBUG[4242] chan_zap.c: Failed to read gains: Invalid argument Mar 15 17:16:55 DEBUG[4242]

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:

Hello, I'm trying to set the 3rd span of a new digium quad card as a E&M T1 for Faxes to a Hylafax server. The 1st and 2nd spans are working as PRIs. When I start asterisk, the logs show a signaling error and chan_zap.c dies. I also get an error that it can't read the gains but they are the standard shown below. 2.6 kernel, Debian Stable, * 1.2 svn from feb 2007 my procedure: make

Hello. I'm trying to setup MFC/R2 signaling, but chan_unicall fails at loading with this message: --- Unable to load module chan_unicall.so Loaded /usr/lib/asterisk/modules/chan_unicall.so => (Unified call processing (UniCall)) == Parsing '/etc/asterisk/unicall.conf': Found 061213-075938 ERROR[11454]: chan_unicall.c:3361 mkintf: Unable to open channel 1: Success here = 0,

Situation such. There is an asterisk working as office pbx. 6 fxo - 18 fxs ports. All works perfectly, but some times in a week something occurs. Could not catch what exactly yet. But symptoms such. The asterisk infinitely writes the message of a type to broad gullies: WARNING [20757] chan_zap.c: We're Zap/8-1, not ... <ZOMBIE>. Numbers of channels can change. Because of that that broad

I've been looking through the logs of a system trying to figure out why it sometimes starts extra asterisk processes. In the logs I keep seeing Apr 4 15:22:18 WARNING[5054] chan_zap.c: Can't fix up channel from 1 to 2 because 2 is already in use Apr 4 15:22:18 WARNING[5054] chan_zap.c: Unable to move channel 2! Apr 4 15:22:55 WARNING[5054] chan_zap.c: Can't fix up channel from 1

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

Hi, For a significant time now (since about 0.2.0-rc8n) the qozap driver has become very verbose if an ISDN line is not connected... I get the messages below every couple of seconds in the asterisk logs. The "flaw" in the messages is the "Alarm cleared" message - The alarm cannot possibly be cleared because there is no physical media connected into that port!!! (BTW - All

Trying to use: Asterisk 1.4.2 Zaptel 1.4.0 chan_zap won't compile in asterisk 1.4.2 when used with zaptel 1.4.0. The changelog has this entry: * channels/chan_zap.c, configure, configure.ac: If we receive ZT_EVENT_REMOVED, destroy the specified channel. (issue #7256, tzafrir) Also, update the configure script to make sure that we don't try to build chan_zap

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

install asterisk with x100p clone; the problem is that call me and hangup but the interface zap not detect the hangup and the line open. the error is : The 'reload' command is deprecated and will be removed in a future release. Please use 'module reload' instead. -- Reloading module 'chan_zap.so' (Zapata Telephony) == Parsing '/etc/asterisk/zapata.conf':

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 there! Trying to originate and dial a number using Zap-8, used to work, but now it just fails. I enabled all debug I found in the source-code and this is the output from asterisk. Can someone understand something from the debug-output what is wrong and direct me to what the problem might be? The setup is correct, trust me, it worked some hours ago, haven't changed anything. Just dialing

I have a Digium TDM400b11, 1FXO [port2] & 1FXS [port 1] When I reload the chan_zap I get: [chan_zap.so] => (Zapata Telephony w/PRI) == Parsing '/etc/asterisk/zapata.conf': Found Apr 9 22:39:36 ERROR[3541]: chan_zap.c:10388 setup_zap: Signalling must be specified before any channels are. Apr 9 22:39:36 WARNING[3541]: loader.c:414 __load_resource: chan_zap.so: load_module

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