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
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]>
Su
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 i
