[Bristuff-users] Is "Hanging up owner" related to "Cause 34" problem?

[asterisk at wiegand.name]

Hello,

when our Asterisk accepted no more calls yesterday with a "Hanging up owner" message, I also found a "Cause 34" message in the logs,
but there were enough free channels! So I discovered this list and read all the "Cause 34" messages. I wonder if the "Hanging up
owner" deadlock could be caused by this?

Even if it is not related, we face the "Hanging up owner" problem on different machines sometimes. It can work two months without
problems, but also happened two times in one week, bringing all channels down. So a solution would be most appreciated.

Here are the details:
Asterisk 1.4.19.1-BRIstuffed-0.4.0-RC1 on a Debian box.
Digium, Inc. Wildcard TE205P connected to a PRI Telco line (30 channels).
(Im breaking up the log for readability)

SIP 454 tried to dial 0170XXXXXXXX. It is 100% sure that there have been free channels at that moment.

[2008-10-24 11:02:53]     
-- Executing [0170XXXXXXX at dial-extern:5] Dial("SIP/454-08315540", "Zap/g1/0170XXXXXXX|120|T") in new stack

g1 is outoing to the telco.

[2008-10-24 11:02:53] 
WARNING[6594] app_dial.c: Unable to create channel of type 'Zap' (cause 34 - Circuit/channel congestion)

[2008-10-24 11:02:53]
== Everyone is busy/congested at this time (1:0/1/0)

This seems to me like the "Cause 34 on free channel" problem discussed elsewhere in this list. 
Now it continues, I jump to +201 in the dialplan after the dial command. Unfortunately there was an error in the dialplan:

[2008-10-24 11:02:53]
-- Executing [0170XXXXXXX at dial-extern:206] NoOp("SIP/454-08315540", "##") in new stack

[2008-10-24 11:02:53]
-- Executing [0170XXXXXXX at dial-extern:207] GotoIf("SIP/454-08315540", "1?s2m-error|0170XXXXXXX|1:gsm-error|0170XXXXXXX|1") in new
stack

[2008-10-24 11:02:53]     -- Goto (s2m-error,0170XXXXXXX,1)

[2008-10-24 11:02:53] WARNING[6594] pbx.c: Channel 'SIP/454-08315540' sent into invalid extension '0170XXXXXXX' in context
's2m-error', but no invalid handler

Context [s2m-error] was missing the '1' priority :-( --- blame me, if that causes the following errors, though I doubt it. Here the
"Hanging up owner"  hing starts:

[2008-10-24 11:02:57] WARNING[29933] chan_zap.c: Ring requested on channel 0/1 already in use on span 1. Hanging up owner.
[2008-10-24 11:03:01] WARNING[29933] chan_zap.c: Ring requested on channel 0/1 already in use on span 1. Hanging up owner.

[2008-10-24 11:03:05] VERBOSE[29933] logger.c: [2008-10-24 11:03:05]     -- Channel 0/30, span 1 got hangup, cause 102

I see 102 is AST_CAUSE_RECOVERY_ON_TIMER_EXPIRE. What does this mean?