thr3ads.net - asterisk users - [asterisk-users] beta4: outgoing call causes Red Alarm on TDM400P [Feb 2008]

If this information is useful, please help other people find it:
Share via:

sean darcy

2008-Feb-24 23:16 UTC

[asterisk-users] beta4: outgoing call causes Red Alarm on TDM400P

Calling out on PSTN over a TDM400P seems to generate a Red Alarm - 
whatever that is. I have another extension on the PSTN, and I can dial 
out over that. zttool shows no alarms.

asterisk*CLI> zap show status
Description                              Alarms  IRQ    bpviol CRC4 
Fra Codi Options  LBO
Wildcard TDM400P REV I Board 1           OK      0      0      0 
CAS Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)
     -- Starting simple switch on 'Zap/2-1'
     -- Executing [2560597 at internal:1] Answer("Zap/2-1",
"") in new stack
     -- Executing [2560597 at internal:2] Set("Zap/2-1",
"CALLERID="house"
<2038447>") in new stack
     -- Executing [2560597 at internal:3] Dial("Zap/2-1",
"Zap/4/2560597")
in new stack
     -- Called 4/2560597
[Feb 24 17:57:54] WARNING[9024]: chan_zap.c:4424 zt_handle_event: 
Detected alarm on channel 4: Red Alarm
     -- Hungup 'Zap/4-1'
   == Everyone is busy/congested at this time (1:0/0/1)
     -- Executing [2560597 at internal:4] Congestion("Zap/2-1",
"") in new
stack
[Feb 24 17:57:54] NOTICE[9024]: chan_zap.c:7514 handle_init_event: Alarm 
cleared on channel 4
   == Spawn extension (internal, 2560597, 4) exited non-zero on
'Zap/2-1'
     -- Hungup 'Zap/2-1'

Sometimes it works, and then doesn't:

.............
-- Starting simple switch on 'Zap/2-1'
     -- Executing [6378447 at internal:1] Answer("Zap/2-1",
"") in new stack
     -- Executing [6378447 at internal:2] Set("Zap/2-1",
"CALLERID="house"
<2038447>") in new stack
     -- Executing [6378447 at internal:3] Dial("Zap/2-1",
"Zap/4/6378447")
in new stack
     -- Called 4/6378447
     -- Zap/4-1 answered Zap/2-1
     -- Native bridging Zap/2-1 and Zap/4-1
     -- Hungup 'Zap/4-1'
   == Spawn extension (internal, 6378447, 3) exited non-zero on
'Zap/2-1'
     -- Hungup 'Zap/2-1'
     -- Starting simple switch on 'Zap/2-1'
     -- Executing [2560597 at internal:1] Answer("Zap/2-1",
"") in new stack
     -- Executing [2560597 at internal:2] Set("Zap/2-1",
"CALLERID="house"
<2038447>") in new stack
     -- Executing [2560597 at internal:3] Dial("Zap/2-1",
"Zap/4/2560597")
in new stack
     -- Called 4/2560597
[Feb 24 17:56:55] WARNING[9024]: chan_zap.c:4424 zt_handle_event: 
Detected alarm on channel 4: Red Alarm
............

This is beta4.

Any help appreciated.

sean

John Novack

2008-Feb-24 23:49 UTC

head link

[asterisk-users] beta4: outgoing call causes Red Alarm on TDM400P

sean darcy wrote:> Calling out on PSTN over a TDM400P seems to generate a Red Alarm - 
> whatever that is. Red Alarm USED to mean there was no battery on the line - assume this 
references an FXO port connected to a PSTN POTS line.

Is it possible Channel 4 is not connected?

John Novack
> I have another extension on the PSTN, and I can dial 
> out over that. zttool shows no alarms.
>
> asterisk*CLI> zap show status
> Description                              Alarms  IRQ    bpviol CRC4 
> Fra Codi Options  LBO
> Wildcard TDM400P REV I Board 1           OK      0      0      0 
> CAS Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)
>      -- Starting simple switch on 'Zap/2-1'
>      -- Executing [2560597 at internal:1] Answer("Zap/2-1",
"") in new stack
>      -- Executing [2560597 at internal:2] Set("Zap/2-1",
"CALLERID="house"
> <2038447>") in new stack
>      -- Executing [2560597 at internal:3] Dial("Zap/2-1",
"Zap/4/2560597")
> in new stack
>      -- Called 4/2560597
> [Feb 24 17:57:54] WARNING[9024]: chan_zap.c:4424 zt_handle_event: 
> Detected alarm on channel 4: Red Alarm
>      -- Hungup 'Zap/4-1'
>    == Everyone is busy/congested at this time (1:0/0/1)
>      -- Executing [2560597 at internal:4] Congestion("Zap/2-1",
"") in new
> stack
> [Feb 24 17:57:54] NOTICE[9024]: chan_zap.c:7514 handle_init_event: Alarm 
> cleared on channel 4
>    == Spawn extension (internal, 2560597, 4) exited non-zero on
'Zap/2-1'
>      -- Hungup 'Zap/2-1'
>
> Sometimes it works, and then doesn't:
>
> .............
> -- Starting simple switch on 'Zap/2-1'
>      -- Executing [6378447 at internal:1] Answer("Zap/2-1",
"") in new stack
>      -- Executing [6378447 at internal:2] Set("Zap/2-1",
"CALLERID="house"
> <2038447>") in new stack
>      -- Executing [6378447 at internal:3] Dial("Zap/2-1",
"Zap/4/6378447")
> in new stack
>      -- Called 4/6378447
>      -- Zap/4-1 answered Zap/2-1
>      -- Native bridging Zap/2-1 and Zap/4-1
>      -- Hungup 'Zap/4-1'
>    == Spawn extension (internal, 6378447, 3) exited non-zero on
'Zap/2-1'
>      -- Hungup 'Zap/2-1'
>      -- Starting simple switch on 'Zap/2-1'
>      -- Executing [2560597 at internal:1] Answer("Zap/2-1",
"") in new stack
>      -- Executing [2560597 at internal:2] Set("Zap/2-1",
"CALLERID="house"
> <2038447>") in new stack
>      -- Executing [2560597 at internal:3] Dial("Zap/2-1",
"Zap/4/2560597")
> in new stack
>      -- Called 4/2560597
> [Feb 24 17:56:55] WARNING[9024]: chan_zap.c:4424 zt_handle_event: 
> Detected alarm on channel 4: Red Alarm
> ............
>
> This is beta4.
>
> Any help appreciated.
>
> sean
>
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
>   
-- 
Dog is my co-pilot

Reasonably Related Threads

Search for more reasonably related threads

asterisk users - Feb 2008 - beta4: outgoing call causes Red Alarm on TDM400P

[asterisk-users] beta4: outgoing call causes Red Alarm on TDM400P

[asterisk-users] beta4: outgoing call causes Red Alarm on TDM400P

Reasonably Related Threads