For UAS, whether or not the SDP offer without a=sendrecv is processed as sendrecv?
In our UAS implementation, if the incoming non-initial SDP offer carrys no direction attribute, it will be regarded as no mode requirement. I think it is incompliant to the RFC3264. Alex Zhang ESN: 6-554-8782 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arun Arora Sent: Friday, July 04, 2008 12:29 PM To: [email protected] Subject: Re: [Sip-implementors] a=sendrecv in SDP answer No, it can't be done this way. By adding a=sendrerv we are clearly distinguishing b/w RFC 2543 and RFC 3261. So, For an "a=sendrecv" there has to be an "a" attribute in the answer. Arun --- On Fri, 4/7/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Subject: [Sip-implementors] a=sendrecv in SDP answer To: [email protected] Date: Friday, 4 July, 2008, 7:04 AM RFC3261 - 6.1, pargraph 4: "If an offered media stream is listed as sendrecv (or if there is no direction attribute at the media or session level, in which case the stream is sendrecv by default), the corresponding stream in the answer MAY be marked as sendonly, recvonly, sendrecv, or inactive." My question is that: If the SDP offer contains the a=sendrecv, can the SDP answer omit the a= line to represent the default value, i.e: Offer (a=sendrecv) ----> <--- Answer(no a=sendrecv line ) Thanks, Alex _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors Bring your gang together. Do your thing. Find your favourite Yahoo! group at http://in.promos.yahoo.com/groups/ _______________________________________________ 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
