[asterisk-bugs] [Asterisk 0013645]: chan_iax2 isn't using HANGUP anymore?
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Oct 30 05:24:34 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13645
======================================================================
Reported By: dzajro
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13645
Category: Channels/chan_iax2
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
Asterisk Version: 1.4.22
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-10-07 17:27 CDT
Last Modified: 2008-10-30 05:24 CDT
======================================================================
Summary: chan_iax2 isn't using HANGUP anymore?
Description:
After upgrading to 1.4.22 problem with call disconnection appeared.
Scenario:
IP_PHONE <---sip---> ASTERISK_1 <----iax2----> ASTERISK_2 <---zap--->
PSTN
Call from IP_PHONE to PSTN to non_existing number (unassigned/unallocated
number, release cause 1) is no longer cleared immediately, but only after
approx. 10s.
iax2 debug shows, that there is no HANGUP message sent by ASTERISK_2.
Side effect - there is impossible to discover HANGUPCAUSE on ASTERISK_1,
cause HANGUPCAUSE is transmitted in HANGUP message :-(.
In fact, it looks, that there is HANGUP missing in case call was answered,
too.
I'm pretty sure, in 1.4.21.2 it worked. But I have no chance to rolback to
1.4.21.2 right now :(
======================================================================
----------------------------------------------------------------------
(0094388) vazir (reporter) - 2008-10-30 05:24
http://bugs.digium.com/view.php?id=13645#c94388
----------------------------------------------------------------------
The same for me, I've lost 2 days switching contexts and so on, trying to
find out what's happening with my dialplan, then finally switched from
1.4.22 to 1.4.21.1 - which got me normal behaviour. na d than found this
bug file...
Issue History
Date Modified Username Field Change
======================================================================
2008-10-30 05:24 vazir Note Added: 0094388
======================================================================
More information about the asterisk-bugs
mailing list