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

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
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:                        
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:              2009-11-23 18:36 CST
====================================================================== 
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.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-23 18:36 lmadsen        Description Updated                          
2009-11-23 18:36 lmadsen        Additional Information Updated                  
 
======================================================================