[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
Sat Aug 14 21:39:27 CDT 2010
A NOTE has been added to this issue.
======================================================================
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: acknowledged
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:
======================================================================
Date Submitted: 2009-11-23 11:26 CST
Last Modified: 2010-08-14 21:39 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...
======================================================================
----------------------------------------------------------------------
(0125958) warlock52 (reporter) - 2010-08-14 21:39
https://issues.asterisk.org/view.php?id=16313#c125958
----------------------------------------------------------------------
we have a workarround that has currently helped us to stay out of
trouble...setting "ignoresdpversion=yes" in sip.conf has suppressed the
issue...this just as a tip for others that have run into the same problem.
Issue History
Date Modified Username Field Change
======================================================================
2010-08-14 21:39 warlock52 Note Added: 0125958
======================================================================
More information about the asterisk-bugs
mailing list