I think the mail difference between recvonly and inactive is recvonly does tell the sender that rtcp reports shall be sent to sender who has sent sendonly. But with inactive you tell to sender that rtcp reports shall not be sent.
Somesh Mascon Global * Please do not take print out of this e-mail unless its absolutely necessary * -----Original Message----- From: [email protected] on behalf of Anuradha Gupta Sent: Sat 2/21/2009 4:12 PM To: kaiduan xie; [email protected] Subject: Re: [Sip-implementors] in-active in answer with sendonly in offer IMO, both the modes in the asnwer are valid. When an offer is recived as Sendonly then the UAS can decide while positively acknowledging the offer either -> only to listen and do not send any data which is recvonly -> do not desire communication in any direction which is inactive In both cases it should not release the resources but apply the desired mode. rgds Anuradha Aricent ________________________________________ From: [email protected] [[email protected]] On Behalf Of kaiduan xie [[email protected]] Sent: Saturday, February 21, 2009 1:12 AM To: [email protected] Subject: [Sip-implementors] in-active in answer with sendonly in offer Hi, all, What is the purpose of putting inactive in answer when receiving a sendonly offer? Rfc3264 Section 6.1 says, "If a stream is offered as sendonly, the corresponding stream MUST be marked as recvonly or inactive in the answer." In rfc5359, recvonly is returned in hold case. Thanks, kaiduan __________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now at http://ca.toolbar.yahoo.com. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors EMAIL DISCLAIMER : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorised distribution or copying is strictly prohibited. If you receive this transmission in error, please notify the sender by reply email and then destroy the message. Opinions, conclusions and other information in this message that do not relate to official business of Mascon shall be understood to be neither given nor endorsed by Mascon. Any information contained in this email, when addressed to Mascon clients is subject to the terms and conditions in governing client contract. Whilst Mascon takes steps to prevent the transmission of viruses via e-mail, we can not guarantee that any email or attachment is free from computer viruses and you are strongly advised to undertake your own anti-virus precautions. Mascon grants no warranties regarding performance, use or quality of any e-mail or attachment and undertakes no liability for loss or damage, howsoever caused. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
