Hi
RFC 3428 [Sec 7 UAS Processing] states that: "A UAS that receives a MESSAGE request processes it following the rules of SIP [1]". Further RFC 3261 also lists some cases where certain headers must not be present in some request and these header fields MUST be ignored if they are present in these requests. In that case, it seems a good option to ignore the Contact header in MESSAGE request and process it successfully. Regards Rohit Aggarwal Aricent -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Avasarala Ranjit-A20990 Sent: Thursday, November 19, 2009 5:53 PM To: [email protected]; [email protected] Subject: Re: [Sip-implementors] MESSAGE with Contact Header -- UAS processing Since there is no dialog established and message is a one way request, there is no need to send any error response. Ideally UAS should not send 200 OK with Contact header because there is no further data exchange. So now by sending 4xx, u need to put a new Call-Id which will lead to other complications. So better to ignore. Regards Ranjit -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Thursday, November 19, 2009 5:40 PM To: Avasarala Ranjit-A20990; [email protected] Subject: RE: [Sip-implementors] MESSAGE with Contact Header -- UAS processing Thanks Ranjit, So, should the UAS send 200 OK Response after stripping the Contact Header, if the incoming MESSAGE has Contact Header present in it?? Or is sending 4xx is a better option? For eg: 400 Bad Request. Regards, Sunil -----Original Message----- From: Avasarala Ranjit-A20990 [mailto:[email protected]] Sent: Thursday, November 19, 2009 5:28 PM To: Sunil Bhagat (WT01 - Telecom Equipment); [email protected] Subject: RE: [Sip-implementors] MESSAGE with Contact Header -- UAS processing Ideally UAS that receives the message request *should not* insert contact header in the 2xx response, because there is no dialog established. So if a UAC receives a 2xx response with Contact header, then it can either ignore it (which is better) or flag an error (which may not be the case). Regards Ranjit -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, November 19, 2009 5:20 PM To: [email protected] Subject: [Sip-implementors] MESSAGE with Contact Header -- UAS processing Hi, RFC 3428 says that Contact Header should not be present in MESSAGE or 2xx Response. UAS Processing "UAS MUST NOT insert a Contact header field into a 2xx response." But what if MESSAGE with Contact header reaches the UAS? Should the UAS send a 2xx response? Or any 4xx response; if yes, which one? Also, how should UAC handle 2xx response for MESSAGE, if Contact Header is present in it? Thanks, Sunil Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.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
