An Offer can have both the attribute, but not within the same media description. It doesn't make sense to have both sendonly and sendrecv attributes for the same media description. The specs do not explicitly explain how to handle such a situation, I would say, the UA receiving it should respond back with 488 Not Acceptable Here.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of venu Y Sent: Thursday, March 08, 2012 1:10 PM To: [email protected] Subject: [Sip-implementors] Regarding SDP attributes I think we should take last a= line Does that mean we cannot send both the attributes in one-offer. I think in such case end point should pick last a: line. My guess. Please let me know with little explanation. Thanks, -Abhishek On Wed, Mar 7, 2012 at 4:05 PM, Worley, Dale R (Dale) <[email protected] >wrote: > No: their meanings are incompatible. > > Dale > > ________________________________________ > From: [email protected] [ > [email protected]] On Behalf Of Abhishek > Lal [[email protected]] > Sent: Tuesday, March 06, 2012 7:53 PM > To: [email protected] > Subject: [Sip-implementors] Regarding SDP attributes > > Hi All, > > Can we send both attributes (sendrecv & sendonly) in single Request. > > a=rtpmap:0 PCMU/8000/1 > a=rtpmap:8 PCMA/8000/1 > *a=sendrecv* > a=ptime:20 > *a=sendonly* > * > * > * > * > ** > Regards, > -Abhishek > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
