[asterisk-bugs] [Asterisk 0012170]: SIP channel isn't closed when using TLS transport
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jul 31 13:23:22 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12170
======================================================================
Reported By: pj
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 12170
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: ready for testing
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 104031
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-03-07 15:40 CST
Last Modified: 2008-07-31 13:23 CDT
======================================================================
Summary: SIP channel isn't closed when using TLS transport
Description:
when H323 endpoint calls SIP, call is established and then h323 hangs up,
asterisk doesn't send sip BYE to sip endpoint and thus channel remains open
until RTP times out.
when I tried to setup call in oposite direction, ie. sip endpoint calls
h323, call is established, then h323 hangs up, sip BYE is send and channel
is correctly closed.
I'm not observing this issue, when using udp as sip signaling transport.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
has duplicate 0012700 Zaptel channel detects hangup, but does...
======================================================================
----------------------------------------------------------------------
(0090932) bbryant (administrator) - 2008-07-31 13:23
http://bugs.digium.com/view.php?id=12170#c90932
----------------------------------------------------------------------
pj, I didn't had a chance to look at it. Have you made sure that the
problem happens reliably only with the patch? It seems quite odd that this
patch would cause that issue.
Issue History
Date Modified Username Field Change
======================================================================
2008-07-31 13:23 bbryant Note Added: 0090932
======================================================================
More information about the asterisk-bugs
mailing list