[asterisk-bugs] [Asterisk 0017099]: [patch] Failure to receive an ACK to a SIP Re-INVITE results in a SIP channel leak
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Apr 15 12:17:28 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17099
======================================================================
Reported By: tsearle
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17099
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: ready for testing
Asterisk Version: SVN
JIRA: SWP-1180
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 254800
Request Review:
======================================================================
Date Submitted: 2010-03-26 08:51 CDT
Last Modified: 2010-04-15 12:17 CDT
======================================================================
Summary: [patch] Failure to receive an ACK to a SIP Re-INVITE
results in a SIP channel leak
Description:
callflow
A -INVITE-> asterisk -INVITE-> B
A <-200 OK- asterisk <-200 OK- B
A --ACK---> asterisk --ACK---> B
asterisk <-INVITE- B
asterisk -200 OK-> B
(ack lost)
A --BYE---> asterisk
A <-200 OK- asterisk
no bye is generated on the B leg as it's still in invite pending
======================================================================
----------------------------------------------------------------------
(0120479) lmadsen (administrator) - 2010-04-15 12:17
https://issues.asterisk.org/view.php?id=17099#c120479
----------------------------------------------------------------------
Nothing at this time unless you wish to write a unit test here :)
Issue History
Date Modified Username Field Change
======================================================================
2010-04-15 12:17 lmadsen Note Added: 0120479
======================================================================
More information about the asterisk-bugs
mailing list