1. Section 8.1.1.8 mentions that "The Contact header field MUST be present and contain exactly one SIP or SIPS URI in any request that can result in the establishment of a dialog. For the methods defined in this specification, that includes only the INVITE request.".
2. Further section 12.2.1.1 states that "A UAC SHOULD include a Contact header field in any target refresh requests within a dialog, and unless there is a need to change it, the URI SHOULD be the same as used in previous requests within the dialog. A Contact header field in a target refresh request updates the remote target URI. This allows a UA to provide a new contact address, should its address change during the duration of the dialog. However, requests that are not target refresh requests do not affect the remote target URI for the dialog." >From the above, it is implied that Contact is NOT a MUST for an (RE-)INVITE request >within a dialog. Contact needs to be present for INVITE within a dialog only for >target refresh conditions. And this seem contradict Table 2, which says INVITE is >mandatory irrespective of one is within or outside of a dialog. Regards, Rajmohan -----Original Message----- From: Chris Boulton [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 9:22 PM To: Karpoor Lakshmi Sanjay-A17738; [EMAIL PROTECTED] Subject: RE: [Sip-implementors] Contact header It says requests - Not INVITE. This is to cover other methods sent within a dialog. So INVITE's MUST but other requests MAY. Regards, Chris. >-----Original Message----- >From: Karpoor Lakshmi Sanjay-A17738 [mailto:[EMAIL PROTECTED] >Sent: 30 July 2003 09:35 >To: [EMAIL PROTECTED] >Subject: [Sip-implementors] Contact header > >Table 2 of RFC 3261 says that Contact is Mandatory in INVITE Request. > >where as in Section 12.2 of RFC it says > >" Requests within a dialog MAY contain Record-Route and Contact header >fields. " That means it may or may not exist, but not mandatory. > >Is it not contradicting with the Table 2? > >Regards, >Lakshmi >_______________________________________________ >Sip-implementors mailing list >[EMAIL PROTECTED] >http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
