search for: alarm's

...1.0.9, libpri 1.0.9 and zaptel 1.0.9.2 connected to an AXE 10 (APZ 21220 System 64) in the network side. I know the system and the wildcard I´m using are ok because I´ve used them before with other PRI connections (to a Siemens EWSD) without any problem. First the PRI didn´t work (I got the TE110P alarmed with red). After troubleshooting with the Telco, they told me to disable crc4 and then I got the green ligth, the 30 B channels cleared, and I was able to dialout to the PSTN but only until the channels restart, because this made the call to hangup. Besides, when I make a call towards the system,...

...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:50 WARNING[3397]: chan_zap.c:5684 handle...

Asterisk is getting red alarms on my T1, sometimes once 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...

...l, any body can tell me why i am receiving this message in my sever ? I have running * with 10 Digital Lines, but i am receiving a lot of times this message . Is a software issue or is a hardware issue ? Regards. Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event: Unicall/5 event Alarm Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event: Unicall/5 Alarm masks 0x0000 0x0004 Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3096 handle_uc_event: Unicall/5 Alarm No Alarm raised, Yellow Alarm cleared Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event: Unica...

...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 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm cleared on channel 3 Mar 31 14:34:07 NOTICE[2362]: chan_zap.c:6880 handle_init_event: Alarm cleared on channel...

...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 cancellation on channel 33...

...dn 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: Yellow Alarm Jan 26 19:39:45 WARNING[2159]...

...Does anyone have any suggestions / ideas ? Thanks Ruairi Sep 24 11:56:30 asterisk01 -- MARK -- Sep 24 11:59:02 asterisk01 ntpd[3615]: synchronized to 172.16.22.60, stratum 4 Sep 24 11:59:28 asterisk01 kernel: wcte12xp: NMF workaround on! Sep 24 11:59:28 asterisk01 kernel: wcte12xp: Setting yellow alarm Sep 24 11:59:29 asterisk01 kernel: wcte12xp: NMF workaround off! Sep 24 11:59:34 asterisk01 kernel: wcte12xp: Clearing yellow alarm Sep 24 12:16:30 asterisk01 -- MARK -- Sep 24 12:17:01 asterisk01 /USR/SBIN/CRON[8325]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Sep 24 12:3...

...hink, is that your processor occasionally does not keep up with the frame transmitter on the PRI board - something that will happen from time to time, and asterisk should recover. (although, as previously discussed, asterisk's minimal error handling makes this worse than it should be) The red alarms indicate a loss of synchronisation, or a very high bit error rate. This is a basic problem and should not occur. Are you sure the switch is not shutting down the T1's as part of some housekeeping? Regards, Scott M. Stingel Emerging Voice Technology Inc. Palo Alto, California and London, E...

...XT-PIC eth0 14: 21317 XT-PIC ide0 NMI: 0 ERR: 0 / Is this something I should be seeking support from Digium on being their card? Apr 12 11:04:59 WARNING[1226062640]: PRI: Short write: -1/15 (Unknown error 500) Apr 12 11:04:59 WARNING[1226062640]: Detected alarm on channel 1: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 2: Red Alarm Apr 12 11:04:59 WARNING[1192491824]: Unable to disable echo cancellation on channel 2 Apr 12 11:04:59 WARNING[1192491824]: Detected alarm on channel 3: Red Alarm Apr 12 11:04:59 WARNING[1192491824]:...

...t (6) on Primary D-channel of span 1 May 31 20:23:49 WARNING[1522] chan_zap.c: [Span 0 D-Channel 0] PRI: Write to 48 failed: Unknown error 500 May 31 20:23:49 WARNING[1522] chan_zap.c: [Span 0 D-Channel 0] PRI: Short write: 0/15 (Unknown error 500) May 31 20:23:49 WARNING[1522] chan_zap.c: Detected alarm on channel 3: Red Alarm May 31 20:23:49 WARNING[1522] chan_zap.c: [Span 0 D-Channel 0] PRI: Write to 48 failed: Unknown error 500 May 31 20:23:49 WARNING[1522] chan_zap.c: [Span 0 D-Channel 0] PRI: Short write: 0/15 (Unknown error 500) May 31 20:23:49 WARNING[1522] chan_zap.c: Detected alarm on cha...

Hello, About every 2 or 3 days I notice in the messages log file: Dec 17 08:39:27 WARNING[1220]: Detected alarm on channel 2: Red Alarm Dec 17 08:39:27 WARNING[1220]: Detected alarm on channel 3: Red Alarm Dec 17 08:39:27 WARNING[1220]: Detected alarm on channel 4: Red Alarm Dec 17 08:39:27 WARNING[1220]: Detected alarm on channel 5: Red Alarm Dec 17 08:39:27 WARNING[1220]: Detected alarm on channel 6: Red A...

SYNOPSIS Erratic red alarm T1 PRI on asterisk, but zttool running concurrently during alarm shows no errors, irq misses, or alarms, on any span. Using asterisk and quad Digium T405P, configured as follows: Span 1 connects to ISDN PRI (fractional 8 B channels, D channel 24). Span 2 connects to T1 Mux and analog stations. S...

...f 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 DEBUG[15151] chan_zap.c: Exception on 19, channel 2 Mar 29 17:08:18 DEBUG[15148] chan_zap.c: Exception on 18, channel 1 Mar 29 17:08:18 DEBUG[15148] chan_zap.c: Got event Alarm(4) on channel 1 (index 0) Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 1 Mar 29 17:08:18 WARNING[24038] chan_zap.c: No D-channels available! Using Primary channel 24 as D-channel anyway! Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm...

...in use when this happens. Mar 30 12:01:41 WARNING[81926]: chan_zap.c:6017 zt_pri_error: PRI: Read on 72 failed: Unknown error 500 Mar 30 12:01:41 NOTICE[81926]: chan_zap.c:6733 pri_dchannel: PRI got event: 4 on span 2 Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected alarm on channel 32: Yellow Alarm Mar 30 12:01:41 WARNING[98311]: chan_zap.c:1151 zt_disable_ec: Unable to disable echo cancellation on channel 32 Mar 30 12:01:41 WARNING[98311]: chan_zap.c:4938 handle_init_event: Detected alarm on channel 33: Yellow Alarm Mar 30 12:01:41 WARNING[98311]: chan_zap.c:115...

...m hardware (t100p, and x100p's.) I am not 100% certain these are fixxes, but just something for people to try if they are expierencing issues with the hardware performing quirky. 1st) Do NOT use Promise Array ATA Raid controllers in a sytem with Digium Hardware. This created many random red alarm issues with the X100P card, as I would see an error generated by both Asterisk and the Array Card. 2.) RedHat 9 with vsftpd running, set tcpwrapper=yes if you use the Asterisk Box as a FTP boot server and the PBX. My polycom phones would sometime act quirky, and I would get multiple errors from...

Hello, I am missing any description of zaptel/DAHDI alarms. The TE200 series user manual contains only a description of LEDs states. These alarms states are visible in zttool/dahditool or in astersick CLI (zap show status) and I wonder what is the real meaning of these alarms for E1 channel. Possible alarm states (based on zaptel.h 1.2): 1. No alarms 2...

...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]: chan_zap.c:6672 handle_init_event: Detected alarm on channel 2: Red Alarm [Nov 16 15:57:09] WARNING[2868]: chan_zap.c:1464 zt_disable_ec: Unable to disable echo cancellation on channel 2 [Nov 16 15:57:09] WARNING[2868]: chan_zap.c:6672 handle...

...-----------> Sip Phone<br> <br> When i make a call from Telco Phone to Sip Phone, the call complete, but when i disconnect the link and reconnect in few seconds, the Asterisk clear call:<br> <br> <b>[Apr&nbsp; 3 10:44:40] WARNING[13081]: chan_dahdi.c:4385 handle_alarms: Detected alarm on channel 1: Red Alarm<br> [Apr&nbsp; 3 10:44:40] NOTICE[21088]: chan_dahdi.c:9558 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1</b><br> &nbsp; <b>== Spawn extension (disc-from-trunk-TR001, 9800, 2) exited non-zero on 'DA...

...ICE[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:57 NOTICE[5484]: chan_zap.c:8176 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Dec 28 21:31:57 NOTICE[5484]: chan_zap.c:8176 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1 Dec 28 21:31:57 WARNING[5484]: chan_zap.c:2289 pri_find_dchan: No D-channels available! Using Primary channel 16 as D-channel anyway! Dec 28 21:31:57 WARNING[5485]: chan_zap.c:6337 handle_init_event: Detected alarm on channel 1: Red Alarm Dec 28 21:31:57 WARNING[5...