[asterisk-bugs] [Asterisk 0016313]: Responds sendrecv to recvonly SDP, but RFC 3264 says sendonly and inactive are only possible replies
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Aug 31 12:00:02 CDT 2010
The following issue has been CLOSED
======================================================================
https://issues.asterisk.org/view.php?id=16313
======================================================================
Reported By: davidw
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16313
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Asterisk Version: SVN
JIRA: SWP-447
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!): 230951
Request Review:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 2009-11-23 11:26 CST
Last Modified: 2010-08-31 12:00 CDT
======================================================================
Summary: Responds sendrecv to recvonly SDP, but RFC 3264 says
sendonly and inactive are only possible replies
Description:
Whilst looking at possible solutions to
https://issues.asterisk.org/view.php?id=16254, I noticed that Asterisk can
never send a sendonly SDP response. Moreover it treats an inbound recvonly
as an unrecognized case. The result is that it sends the default sendrecv
response.
RFC 3624 says that the only acceptable responses to recvonly are sendonly
and inactive. I.E., reading between the lines, the response cannot offer
more capabilities than the request would allow.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0016373 Asterisk ignoring sendonly SDP generate...
======================================================================
----------------------------------------------------------------------
(0126477) lmadsen (administrator) - 2010-08-31 12:00
https://issues.asterisk.org/view.php?id=16313#c126477
----------------------------------------------------------------------
Suspending this issue. No SIP debug information supplied as requested.
Please reopen if you are able to supply said information. Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2010-08-31 12:00 lmadsen Note Added: 0126477
2010-08-31 12:00 lmadsen Status acknowledged => closed
======================================================================
More information about the asterisk-bugs
mailing list