[asterisk-bugs] [Asterisk 0017878]: [patch] chan_sip fails to remove hold when receving a reINVITE without SDP
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Aug 18 04:47:42 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17878
======================================================================
Reported By: frawd
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17878
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: minor
Priority: normal
Status: confirmed
Asterisk Version: 1.6.2.11
JIRA: SWP-2064
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-08-17 11:05 CDT
Last Modified: 2010-08-18 04:47 CDT
======================================================================
Summary: [patch] chan_sip fails to remove hold when receving
a reINVITE without SDP
Description:
Patch for issue https://issues.asterisk.org/view.php?id=14448 never made it to
trunk so all versions above 1.4
suffer this problem.
Here is an updated patch for 1.6.2.11.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0014448 [patch] chan_sip fails to remove hold w...
======================================================================
----------------------------------------------------------------------
(0126070) frawd (reporter) - 2010-08-18 04:47
https://issues.asterisk.org/view.php?id=17878#c126070
----------------------------------------------------------------------
For more information, RFC-3261 states:
"A UAS providing an offer in a 2xx (because the INVITE did not contain an
offer) SHOULD construct the offer as if the UAS were making a brand new
call [...]"
Asterisk does actually comply with this RFC as it isn't obligated to do it
(SHOULD), but placing the call off-hold could be a nice practice.
Issue History
Date Modified Username Field Change
======================================================================
2010-08-18 04:47 frawd Note Added: 0126070
======================================================================
More information about the asterisk-bugs
mailing list