[asterisk-bugs] [Asterisk 0018584]: The response to a CANCEL request does not always comply with RFC3261
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jan 12 10:20:07 CST 2011
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=18584
======================================================================
Reported By: jacco
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18584
Category: Channels/chan_sip/General
Reproducibility: sometimes
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: 1.8.1.1
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-01-06 09:54 CST
Last Modified: 2011-01-12 10:20 CST
======================================================================
Summary: The response to a CANCEL request does not always
comply with RFC3261
Description:
The response to a CANCEL request when the original request was an INVITE
does not always comply with RFC3261.
It sometimes send a 200 OK as the answer to the INVITE instead of
responding with a 487 to the INVITE request.
Quote from paragraph 9.2: "If the original request was an INVITE, the UAS
SHOULD immediately respond to the INVITE with a 487"
this bug is timing/load dependend
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2011-01-12 10:20 lmadsen Description Updated
2011-01-12 10:20 lmadsen Additional Information Updated
======================================================================
More information about the asterisk-bugs
mailing list