Gustavo Cordeiro
2007-Sep-13 18:31 UTC
[asterisk-users] ZAP to invalid SIP device call looping
Hello, When I receive calls in one FXO port (TDM400 or A200, occurs in both) and it dial to one invalid SIP extension, the call never hangup. The call would have to be dropped, but it seems that "Starting simple switch on 'Zap/1-1'" and "Hungup 'Zap/1-1'" occurs almost at the same time. If the dial is made to a valid SIP extension, the call is proceeded and terminated without any problem. Anybody had the same situation? Thanks in advance! Regards, Gustavo - Asterisk 1.4.11 - Zaptel 1.4.5.1 - Call log: -- Starting simple switch on 'Zap/1-1' -- Executing [s at fxo-01:1] Dial("Zap/1-1", "SIP/at001-a|30|r") in new stack == Everyone is busy/congested at this time (1:0/0/1) -- Executing [s at fxo-01:2] Hangup("Zap/1-1", "") in new stack == Spawn extension (fxo-01, s, 2) exited non-zero on 'Zap/1-1' -- Hungup 'Zap/1-1' -- Starting simple switch on 'Zap/1-1' -- Executing [s at fxo-01:1] Dial("Zap/1-1", "SIP/at001-a|30|r") in new stack == Everyone is busy/congested at this time (1:0/0/1) -- Executing [s at fxo-01:2] Hangup("Zap/1-1", "") in new stack == Spawn extension (fxo-01, s, 2) exited non-zero on 'Zap/1-1' -- Hungup 'Zap/1-1' -- Starting simple switch on 'Zap/1-1' -- Executing [s at fxo-01:1] Dial("Zap/1-1", "SIP/at001-a|30|r") in new stack == Everyone is busy/congested at this time (1:0/0/1) -- Executing [s at fxo-01:2] Hangup("Zap/1-1", "") in new stack == Spawn extension (fxo-01, s, 2) exited non-zero on 'Zap/1-1' -- Hungup 'Zap/1-1' -- Starting simple switch on 'Zap/1-1' -- Executing [s at fxo-01:1] Dial("Zap/1-1", "SIP/at001-a|30|r") in new stack == Everyone is busy/congested at this time (1:0/0/1) -- Executing [s at fxo-01:2] Hangup("Zap/1-1", "") in new stack == Spawn extension (fxo-01, s, 2) exited non-zero on 'Zap/1-1' -- Hungup 'Zap/1-1' ... - extensions.conf: [fxo-01] exten = s,1,dial(SIP/at001-a,30,r) exten = s,n,hangup() - zapata.conf: [channels] usecallerid = no callwaiting = no echocancel = yes echotraining = yes echocancelwhenbridged = yes immediate = no busydetect = yes busycount = 3 callprogress = yes progzone = br faxdetect = no context = fxo-01 signalling = fxs_ks channel = 1 _________________________________________________________________ O Windows Live Spaces ? seu espa?o na internet com fotos (500 por m?s), blog e agora com rede social http://spaces.live.com/
Reasonably Related Threads
- Configuring chan_dahdi.conf for Sangoma A200/Remora FXO/FXS Analog AFT card
- Hangup or busy when the peer answer outgoing calls
- Sangoma A200 preventing Zap channels from disconnecting immediately after PSTN line hangs up (getting empty voicemails)
- CALLERID problems asterisk segfaults
- Card don't hangup but Asterisk hangup