similar to: chan_zap "Cannot handle frames in 2 format"

I've just finished updating my Asterisk to the CVS version. Unfortunately, chan_zap won't load anymore. The hardware has not changed and the config files have not changed. I can re-install the two packages back and forth. The old one will still work. The new one won't. I tried updating to a brand-new zaptel and wcfxo modules, with no difference. This has got to be the most

Any ideas on this? This has always worked in the past until we got this new customer and his new fax machine. Faxing from my machine works fine. But faxing from his gives this error. I can't imagine why his fax machine would be causing frame errors. -- Redirecting Zap/4-1 to fax extension -- Executing Macro("Zap/4-1", "fax-handle|7133950500|2815692740|Y") in

Hi friends, Where can I get some information to understand messages like the following ones? *NOTICE[6455] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1* *NOTICE[6455] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1* * ERROR[6455] chan_zap.c: !! Got S-frame while link down* *ERROR[6458] chan_zap.c: !! Got reject for frame 27, retransmitting

Suddenly after recompiling my 2.4.22 kernel I can no longer load chan_zap: Sep 22 21:25:08 ERROR[16384]: File chan_zap.c, Line 5145 (mkintf): Unable to get span status: Inappropriate ioctl for device Sep 22 21:25:08 ERROR[16384]: File chan_zap.c, Line 6638 (load_module): Unable to register channel '1' Sep 22 21:25:08 WARNING[16384]: File loader.c, Line 301 (ast_load_resource):

Hi, I've a little problem with my asterisk server. I have managed an asterisk server for a few months one. Today, I wanted to restart it and when I did it, my asterisk server didn't want to start again. I looked at the various messages in /var/log and the same thing appears. " [chan_zap.so] => (Zapata Telephony) == Parsing '/etc/asterisk/zapata.conf': Found Sep 30

What am I doing wrong here? Why is this happening? libpri is version 1.0.7-1 (debian package) asterisk is version 1.0.7.dfsg.1-2 (debian package) zaptel is version 1.0.9.2 -- Executing Dial("SIP/739-5935", "Zap/g1/0916000739") in new stack -- Called g1/0916000739 -- Channel 0/1, span 1 got hangup Oct 10 13:14:45 WARNING[7544]: app_dial.c:412 wait_for_answer:

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

The Panasonic KX-TA624 series PBXes (and similar models) support a DTMF integration feature that can be enabled for dedicated voice mail ports. What I want to do is connect an X100P FXO port to a jack on the Panasonic and make use of the Panasonic's DTMF call progress tones that it provides in DTMF integration mode. The integration works well when a Panasonic extension is forwarding into

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 have Asterisk 1.4.0 using Queue App. I use PRI connecting my Asterisk with Siemens EWSD This was working OK but since two days I have this error: [Jun 22 10:53:09] WARNING[8050] chan_zap.c: Ring requested on channel 0/3 already in use on span 1. Hanging up owner. [Jun 22 10:53:09] WARNING[8050] chan_zap.c: Ring requested on channel 0/3 already in use on span 1. Hanging up owner. [Jun 22

We use an IPcortex PABX running Asterisk 1.2.39-BRIstuffed-0.3.0-PRE-1y-y. We have recently implemented Call Queuing for our main incoming line with hold music. The call queue type is: Ring all - One call at a time (no position announcement). Since implementing this feature we've been receiving the below error daily in the mornings and lunchtime when the queue will jump to the next available

Hi all, I am running asterisk 1.2.18, zaptel 1.2.18, libpri 1.2.4. on a suse 10.2, running kernel 2.6.18.2-34-default. The zaptel drivers are loaded on boot via /etc/init.d/zaptel, but Asterisk is unable to start. It ends with the following message: [chan_zap.so] => (Zapata Telephony w/PRI) Jun 13 13:05:41 VERBOSE[3356] logger.c: == Parsing '/etc/asterisk/zapata.conf': Found

Any ideas on this warning? If I call this number, sometimes I get this error and sometimes the call goes thru fine. Why would it work sometimes? -- Executing Goto("SIP/3044-8d49", "cytel-outgoing|915124512424|1") in new stack -- Goto (cytel-outgoing,915124512424,1) -- Executing SetCIDNum("SIP/3044-8d49", "2814494000") in new stack --

Hi all, so what does these messages that i get once in a while mean? (Im running with a TE410P) WARNING[1167306032]: File chan_zap.c, Line 5436 (pri_fixup): Can't fix up channel from 15 to 17 because 17 is already in use WARNING[1167306032]: File chan_zap.c, Line 6064 (pri_dchannel): Hangup on bad channel 17 WARNING[1167306032]: File chan_zap.c, Line 5436 (pri_fixup): Can't fix up

Now I have this errors When I lunch this command I got modprobe wcte11xp This error: Notice: Configuration file is /etc/zaptel.conf line 0: Unable to open master device '/dev/zap/ctl' 1 error(s) detected FATAL: Error running install command for wcte11xp And when I lunch this command ztcfg -vv I got these: Zaptel Configuration ====================== SPAN 1: CCS/HDB3 Build-out: 0 db

Hello everyone! I installed Asterisk following the instructions of the book "Asterisk: The Future of Telephony". (very nice book) However, I failed. I installed zaptel, libpri and asterisk (in this order). The Installation of Zaptel is successful and my TDM400P is correctly detected: # zttool Alarms Span OK Wildcard S400P

I just updated to the new CVS and now I am getting the following error from chan_zap (modprobe wcfxo works fine): WARNING[16384]: File chan_zap.c, Line 577 (zt_open): Unable to specify channel 1: Device or resource busy ERROR[16384]: File chan_zap.c, Line 4781 (mkintf): Unable to open channel 1: Device or resource busy here = 0, tmp->channel = 0, channel = 1 ERROR[16384]: File

Hi!I've a problem with asterisk,it doesn't start..it's stopped..I used the amportal start command and this is the result: SETTING FILE PERMISSIONS Permissions OK STARTING ASTERISK Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk.

Update: I can reproduce the error by putting the reception phone (call queue 0) in Do Not Disturb mode, then call in from outside using a mobile, then pick up the call from the 2nd phone in the queue. It will cause the error only if I hang up _before_ the mobile hangs up. The error doesn't seem to happen if the external call hangs up, or if the call is answered by the reception phone (first