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 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:37:54 WARNING[32537] chan_zap.c: Detected alarm on channel 4: Red Alarm Feb 7 13:37:54 WARNING[32557] chan_zap.c: Detected alarm on channel 5: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 7: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 9: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 11: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 12: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 13: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 14: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 15: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 16: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 17: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 18: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 19: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 20: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 21: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 22: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 23: Red Alarm Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 24: Red Alarm Feb 7 13:37:54 WARNING[32566] chan_zap.c: Detected alarm on channel 8: Red Alarm Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 1 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 2 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 3 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 4 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 5 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 6 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 7 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 8 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 9 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 10 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 11 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 12 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 13 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 14 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 15 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 16 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 17 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 18 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 19 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 20 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 21 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 22 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 23 Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 24 Here are other items that appear in the logs quite frequently that I think are related (and probably all related to timing): Feb 7 15:52:13 WARNING[8920] chan_zap.c: Ring/Off-hook in strange state 6 on channel 4 Feb 7 15:52:21 WARNING[2524] chan_zap.c: zt hook failed: Device or resource busy We also get ghost calls from time to time. More info: E&M Wink, B8ZS, ESF Digium Wildcard TE405P The telco told me that timing must be provided by us, but when I tried that all hell broke loose.
You need to call your telco and check your cables. Red alarms are typically a loss of the physical T-1 layer and are typically a telco or cable issue. Wayne Jensen wrote:> 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 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:37:54 WARNING[32537] chan_zap.c: Detected alarm on channel > 4: Red Alarm > Feb 7 13:37:54 WARNING[32557] chan_zap.c: Detected alarm on channel > 5: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 7: > Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel 9: > Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 11: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 12: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 13: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 14: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 15: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 16: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 17: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 18: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 19: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 20: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 21: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 22: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 23: Red Alarm > Feb 7 13:37:54 WARNING[2524] chan_zap.c: Detected alarm on channel > 24: Red Alarm > Feb 7 13:37:54 WARNING[32566] chan_zap.c: Detected alarm on channel > 8: Red Alarm > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 1 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 2 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 3 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 4 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 5 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 6 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 7 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 8 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 9 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 10 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 11 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 12 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 13 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 14 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 15 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 16 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 17 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 18 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 19 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 20 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 21 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 22 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 23 > Feb 7 13:37:59 NOTICE[2524] chan_zap.c: Alarm cleared on channel 24 > > Here are other items that appear in the logs quite frequently that I > think are related (and probably all related to timing): > > Feb 7 15:52:13 WARNING[8920] chan_zap.c: Ring/Off-hook in strange > state 6 on channel 4 > Feb 7 15:52:21 WARNING[2524] chan_zap.c: zt hook failed: Device or > resource busy > > We also get ghost calls from time to time. > > More info: > E&M Wink, B8ZS, ESF > Digium Wildcard TE405P > > The telco told me that timing must be provided by us, but when I tried > that all hell broke loose. > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
I had this happen to me because I was not configured properly and for some reason the telco was automatically dropping me every so often. I called the telco and they corrected me. Shane
> 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.Red alarm means that the hardware is not seeing the T1 signal coming in. This most likely is a cable or wiring or perhaps a hardware problem.> ... > The telco told me that timing must be provided by us, but when I tried > that all hell broke loose.Timing to a telco switch is *always* going to be provided by the telco switch. Don Pobanz