RFC 4566 section 6:
If none of the attributes "sendonly", "recvonly", "inactive",
and "sendrecv" is present, "sendrecv" SHOULD be assumed as the
default for sessions that are not of the conference type
"broadcast" or "H332" (see below).
RFC 3264 section 5.1:
If the offerer wishes to both send and
receive media with its peer, it MAY include an "a=sendrecv"
attribute, or it MAY omit it, since sendrecv is the default.
> -----Original Message-----
> From: [email protected] [mailto:sip-
> [email protected]] On Behalf Of Rishabh
> Sent: Thursday, April 01, 2010 7:12 AM
> To: [email protected]
> Subject: [Sip-implementors] SIP_INVITE
>
> Dear all,
>
> Just wanted to know that if we don't put "sendrecv" in media
> attribute in INVITE.
>
> Is that a problem with that????
>
>
> Regards
> Rishabh Jain
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
