search for: chan_zap

...reject" even they "see" the channels available. For troubleshooting porpouses, they have enabled the most simple configuration of PBX in the network side of the PRI (no DIDs, 30 B channels and one header). These are the messages that I got in the CLI: 051008-153001 WARNING[27660]: chan_zap.c:7182 zt_pri_error: PRI: Short write: -1/15 (Unknown error 500) 051008-153001 WARNING[27660]: chan_zap.c:3195 zt_handle_event: Detected alarm on channel 1: Yellow Alarm -- Hungup 'Zap/1-1' == No one is available to answer at this time 051008-153001 WARNING[27660]: chan_zap.c:5684 han...

...clock and Asterisk is slave, additionally the Panasonic takes the clock from the PSTN E1. This scheme works and I?m able to make and receive calls the problem is that some times the Asterisk lose the synchronism with the Panasonic and the log shows this error: [Oct 1 16:22:14] WARNING[6130] chan_zap.c: Detected alarm on channel 32: Yellow Alarm[Oct 1 16:22:14] WARNING[6130] chan_zap.c: Unable to disable echo cancellation on channel 32[Oct 1 16:22:14] WARNING[6130] chan_zap.c: Detected alarm on channel 33: Yellow Alarm[Oct 1 16:22:14] WARNING[6130] chan_zap.c: Unable to disable echo cancella...

...Asterisk 1.0.7 and CVS Head. Digium has done the loopbacktests w/o errors. Our question is, is this hardware, software or pri related? What can we do? The PRI is used to an Lucent pbx and is working fine, but when we connect it to asterisk we get this log (CVS HEAD): May 31 20:08:31 NOTICE[1522] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 31 20:08:31 NOTICE[1522] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 31 20:09:17 NOTICE[1522] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 31 20:09:17 NOTICE[1522] ch...

...lplan=national overlapdial=yes immediate=no faxdetect=both overlapdial=no usecallerid=yes usecallingpres=yes callerid=asreceived group=9 channel => 1-15 channel => 17-31 The following are the messages that keep repeating. == Primary D-Channel on span 1 down Mar 31 14:34:05 WARNING[2361]: chan_zap.c:2682 pri_find_dchan: No D-channels available! Using Primary channel 16 as D-channel anyway! Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm cleared on channel 1 Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm cleared on channel 2 Mar 31 14:34:07 N...

..., with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'show license' for details. ========================================================================= Dec 28 21:31:54 NOTICE[5484]: chan_zap.c:8176 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Dec 28 21:31:54 NOTICE[5484]: chan_zap.c:8176 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Dec 28 21:31:54 NOTICE[5484]: chan_zap.c:8176 pri_dchannel: PRI got event: HDLC Bad FCS (8)...

...or twice a day, but today it happened 5 times. Even once is too many. Every call in progress is dropped. Please help! What do I need to do? What can I try? I've googled and searched this list and can't find anything. Here's an example from the logs: Feb 7 13:37:54 WARNING[32451] chan_zap.c: Detected alarm on channel 6: Red Alarm Feb 7 13:37:54 WARNING[32238] chan_zap.c: Detected alarm on channel 1: Red Alarm Feb 7 13:37:54 WARNING[32546] chan_zap.c: Detected alarm on channel 2: Red Alarm Feb 7 13:37:54 WARNING[32477] chan_zap.c: Detected alarm on channel 3: Red Alarm Feb 7 13:3...

...tting yellow alarm Sep 24 12:59:28 asterisk01 kernel: wcte12xp: NMF workaround off! Sep 24 12:59:33 asterisk01 kernel: wcte12xp: Clearing yellow alarm Sep 24 13:16:31 asterisk01 -- MARK -- The siemens see a F5413 Spur error... A more detailed asterisk log shows [Sep 24 12:59:28] WARNING[6374] chan_zap.c: Detected alarm on channel 2: Red Alarm [Sep 24 12:59:28] WARNING[6374] chan_zap.c: Unable to disable echo cancellation on channel 2 [Sep 24 12:59:28] WARNING[6374] chan_zap.c: Detected alarm on channel 3: Red Alarm [Sep 24 12:59:28] WARNING[6374] chan_zap.c: Unable to disable echo cancellati...

...ial,Zap/10|60 ; exten => 3509,2,Hangup When I attempt to call these extensions I get: *CLI> dial 3501 -- Executing Dial("OSS/dsp", "Zap/2|60") in new stack -- Called 2 -- Zap/2-1 is ringing -- Zap/2-1 is ringing Aug 2 12:59:50 WARNING[3397]: chan_zap.c:5684 handle_init_event: Detected alarm on channel 1: Yellow Alarm Aug 2 12:59:50 WARNING[3397]: chan_zap.c:5684 handle_init_event: Detected alarm on channel 3: Yellow Alarm Aug 2 12:59:50 WARNING[3397]: chan_zap.c:5684 handle_init_event: Detected alarm on channel 4: Yellow Alarm Aug 2 12:59...

...eas it would be greatly appreciated. Thanks, Kevin /etc/asterisk/zapata.conf switchtype=national defaultzone=us context=default signalling=pri_cpe group=1 channel => 1-23 dchannel=24 callerid=asreceived /etc/zapata.conf span=1,0,0,esf,b8zs bchan=1-23 dchan=24 Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Mar 29 17:08:18 NOTICE...

Hi, Trying to trace an asterisk hang on a production (it had to be didn't it) system. The last thing before it crashed was [Mar 16 12:32:42] DEBUG[7754] chan_zap.c: Ignore switch to REVERSED Polarity on channel 1, state 4 [Mar 16 12:54:34] DEBUG[7754] chan_zap.c: Ignore switch to REVERSED Polarity on channel 2, state 4 [Mar 16 12:54:35] DEBUG[7754] chan_zap.c: Ignore switch to REVERSED Polarity on channel 2, state 4 [Mar 16 12:55:09] DEBUG[7754] chan_...

...=3.0 immediate=no context=inbound-analog signalling=fxs_ks callerid=asreceived channel=>1 [[extensions.conf]] [inbound-analog] exten => s,1,DISA,1234|voiptel exten => s,2,Hangup And finaly the log ... *CLI> -- Starting simple switch on 'Zap/1-1' DEBUG[1255338944]: File chan_zap.c, Line 1069 (zt_enable_ec): Enabled echo cancellation on channel 1 -- Executing DISA("Zap/1-1", "1234|voiptel") in new stack DEBUG[1255338944]: File chan_zap.c, Line 1961 (zt_answer): Took Zap/1-1 off hook DEBUG[1255338944]: File chan_zap.c, Line 3511 (zt_read): DTMF digit:...

...eks I got the problems. Does anyone have any idea? The last points what is on my todo is to switch the pci slot. The cable which connects card to E1 interface is also switched. Kind regards, Eric I got a snippet from the console, where the problem is occuring. [Nov 16 15:57:09] ERROR[5499]: chan_zap.c:8178 zt_pri_error: Write to 39 failed: Unknown error 500 [Nov 16 15:57:09] ERROR[5499]: chan_zap.c:8178 zt_pri_error: Short write: 0/15 (Unknown error 500) [Nov 16 15:57:09] WARNING[5499]: chan_zap.c:3822 zt_handle_event: Detected alarm on channel 1: Red Alarm [Nov 16 15:57:09] WARNING[2868]: cha...

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 internationalprefix Jun 21...

...channels] signalling=pri_cpe switchtype=euroisdn language=en context=sip channel => 1-15 channel => 17-31 echocancel = yes echocancelwhenbridged = yes echotraining = yes group = 1 usecallingpres = yes console errors: Jan 26 19:39:45 NOTICE[2158]: chan_zap.c:7381 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1 Jan 26 19:39:45 WARNING[2158]: chan_zap.c:1925 pri_find_dchan: No D-channels available! Using Primary on channel anyway 16! Jan 26 19:39:45 WARNING[2159]: chan_zap.c:5642 handle_init_event: Detected alarm on channel 1:...

...ple debug log. This happens only once a day or so, with 100 or so users transfering and three way calling all the time. Anyone having a simular problem. Thanks for you help Mar 7 11:21:29 VERBOSE[8204] logger.c: -- Starting simple switch on 'Zap/99-1' Mar 7 11:21:31 DEBUG[8204] chan_zap.c: DTMF digit: 8 on Zap/99-1 Mar 7 11:21:32 DEBUG[8204] chan_zap.c: DTMF digit: 3 on Zap/99-1 Mar 7 11:21:32 DEBUG[8204] chan_zap.c: DTMF digit: 3 on Zap/99-1 Mar 7 11:21:33 DEBUG[8204] chan_zap.c: DTMF digit: 5 on Zap/99-1 Mar 7 11:21:33 DEBUG[8204] chan_zap.c: DTMF digit: 6 on Zap/99-1 Mar 7...

...rying to connect an RBS T1 with AMI/D4 framing and E&M Wink. Using a Sangoma A102d and asterisk 1.4.22-2 on Centos5 (Trixbox 2.6.2.1). Outbound calls work fine, but inbound calls fail to read the DID information, and with debug set to 10 I get the following: [Feb 2 19:40:23] DEBUG[25184] chan_zap.c: Monitor doohicky got event Wink/Flash on channel 3 [Feb 2 19:40:23] VERBOSE[25273] logger.c: -- Starting simple switch on 'Zap/3-1' [Feb 2 19:40:24] DEBUG[25273] chan_zap.c: Exception on 14, channel 3 [Feb 2 19:40:24] DEBUG[25273] chan_zap.c: Got event Wink/Flash(3) on channel...

...Telco E1 link, but for testing I was trying every combination. If I use span=1,x,0,ccs,hdb3 where x =0,1,2 the sync light appears on the E100P card but when i bring the TDA E1 card in service i get a sync error and a crap load of Red Alerts for every channel and a Mar 11 14:40:35 NOTICE[3910]: chan_zap.c:7395 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 1 Mar 11 14:40:35 WARNING[3910]: chan_zap.c:1931 pri_find_dchan: No D-channels available! Using Primary on channel anyway 16! At this stage I was pulling hair thinking what the.... but since murphy's law rules...

...write: 0/15 (Unknown error 500) What does this mean? Why this occurs? How could I solve that? Someone could tell me if it was a primary error (the primary shows red alert in all its channels) or it could be a driver or config problem? Thanks in advance. VoipCrazy. Mar 27 14:28:00 DEBUG[20313] chan_zap.c: Got event Alarm(4) on channel 1 (index 0) Mar 27 14:28:00 VERBOSE[20313] logger.c: Write to 55 failed: Unknown error 500 Mar 27 14:28:00 VERBOSE[20313] logger.c: Short write: 0/15 (Unknown error 500) Mar 27 14:28:00 WARNING[20313] chan_zap.c: Detected alarm on channel 1: Red Alarm Mar 27 14:28:0...

...from one of these phone calls (I replaced the phone number with some Xs). Somebody calls us from the line that's connected to zap channel 2. Then, our 4 phones ring and I pick up the call on phone connected to zap channel 7. Ten minutes later that event fires up: Jun 7 17:53:09 DEBUG[9015] chan_zap.c: Got event On hook(1) on channel 2 (index 0). After the output I attached my zapata.conf. Anyone has had this problem before? Is there something in my zapata.conf that's not correct? Any help would be very appreciated. I don't know if it's related, but, one or twice a day, when ou...

My office is investigating using an Asterisk PBX and also going to a VOIP provider for our main phone connections, but one of the tricky things is that we need to have outbound and inbound modem calls (fax too). I see a lot of talk about faxes but no mention of modems on this list. I get the impression that modems will be a problem for us. Is that true?