[asterisk-bugs] [Asterisk 0014007]: bad Hangup Event on channel

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Apr 2 17:52:40 CDT 2009


The following issue requires your FEEDBACK. 
====================================================================== 
http://bugs.digium.com/view.php?id=14007 
====================================================================== 
Reported By:                dlebegue
Assigned To:                mmichelson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14007
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.2  
SVN Revision (number only!): 159245 
Request Review:              
====================================================================== 
Date Submitted:             2008-12-02 07:16 CST
Last Modified:              2009-04-02 17:52 CDT
====================================================================== 
Summary:                    bad Hangup Event on channel
Description: 
after annulation of supervised transfer with
http://bugs.digium.com/view.php?id=3 (features.conf) and 

parked operation on the initial ZAP channel , the manager send me a
"Hangup 
Event" but the initial ZAP channel is really parked with moh.

The "Hangup Event" destroy the call in my interface because Hangup -> stop
of call!!!


====================================================================== 

---------------------------------------------------------------------- 
 (0102646) mmichelson (administrator) - 2009-04-02 17:52
 http://bugs.digium.com/view.php?id=14007#c102646 
---------------------------------------------------------------------- 
This issue has been idle for quite a while and needs a resolution, so I am
taking over. The problem is that I am having a lot of trouble understanding
exactly what the problem is here and how to reproduce it.

Let's try to break this down into steps instead of using prose to describe
the situation. Based on the log you provided, I think this is what you have
done.

mISDN/1-1 calls SIP/905.
SIP/905 answers the call.
SIP/905 initiates a supervised transfer to mISDN/1-u0.
While mISDN/1-u0 is ringing, SIP/905 presses
http://bugs.digium.com/view.php?id=3 to disconnect the call.
...(This is where things get confusing. I may have details wrong here)...
mISDN/1-1 and SIP/905 are connected again.
It appears that SIP/905 attempts to park mISDN/1-1. It is unclear exactly
how this is being accomplished. 
mISDN/1-1 gets tired of being parked and hangs up.

In the log you uploaded, you then stopped Asterisk using the "stop now"
command. In http://bugs.digium.com/view.php?id=14007#c97069, you show that
Asterisk crashed. The initial report did
not mention a crash at all (except in the "severity" field). Did the crash
occur when you first reported this against Asterisk 1.2, or is that
something that started happening when using 1.4?

I'm going to need to know exactly the steps to follow to make this problem
happen. It is really difficult trying to figure this out just based on the
description you have provided and the files you have uploaded.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-02 17:52 mmichelson     Note Added: 0102646                          
2009-04-02 17:52 mmichelson     Status                   assigned => feedback
======================================================================




More information about the asterisk-bugs mailing list