[asterisk-bugs] [Asterisk 0016313]: Responds sendrecv to recvonly SDP, but RFC 3264 says sendonly and inactive are only possible replies

[Asterisk Bug Tracker]

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-06-28 06:19 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0123948) davidw (reporter) - 2010-06-28 06:19
 https://issues.asterisk.org/view.php?id=16313#c123948 
---------------------------------------------------------------------- 
I'm afraid your report is confused.  There is no "readonly" attribute, only
recvonly.  The correct responses to recvonly are sendonly or inactive.  In
practice, the only way of putting on hold which will work with most PABXes
is to send sendonly.

I suspect your real problem here may be that Asterisk doesn't track media
direction information for individual streams, which is a different issue,
and should be raised as such (if not already in the system).

You definitely need to either follow the SIP problem reporting rules and
provide a sip set debug trace at appropriate verbosity, or to identify
exactly what is wrong in the code. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-28 06:19 davidw         Note Added: 0123948                          
======================================================================