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

[sean darcy]

John Novack wrote:
> 
> 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.
> 
Yes.

> Is it possible Channel 4 is not connected?
> 

But:

>> 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
>> ........

sean