Sarkar, You are right. For Register Expires header has different meaning. For INVITE it means, how long the INVITE is valid.
20.19 Expires The Expires header field gives the relative time after which the message (or content) expires. The precise meaning of this is method dependent. Thanks, Neel > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sip-implementors- > [EMAIL PROTECTED] On Behalf Of Sarkar, Uttam > Sent: Tuesday, May 01, 2007 11:21 AM > To: [EMAIL PROTECTED]; Attila Sipos; Michael > Hirschbichler; [email protected] > Subject: Re: [Sip-implementors] Question regarding BNF and Contact:-Header > > If that appears in REGISTER then it's meaning is to de-register all the > conacts for that AoR. UAS can't drop that REGISTER request. > > -----Original Message----- > From: Bala Neelakantan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 01, 2007 11:53 AM > To: Sarkar, Uttam; 'Attila Sipos'; 'Michael Hirschbichler'; > [email protected] > Subject: RE: [Sip-implementors] Question regarding BNF and > Contact:-Header > > Having > > Contact: * > Expires:0 > > as a SIP header has a different meaning. In this case, this Expires is > associated with the SIP Message. Theoretically, the UAS can drop the > request. > > Thanks, > Neel > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:sip-implementors- [EMAIL PROTECTED] On Behalf Of > > Sarkar, Uttam > > Sent: Tuesday, April 17, 2007 7:25 AM > > To: Attila Sipos; Michael Hirschbichler; > > [email protected] > > Subject: Re: [Sip-implementors] Question regarding BNF and > > Contact:-Header > > > > You can do as follows. > > > > Contact: * > > Expires: 0 > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Attila > > Sipos > > Sent: Tuesday, April 17, 2007 8:13 AM > > To: Michael Hirschbichler; [email protected] > > Subject: Re: [Sip-implementors] Question regarding BNF and > > Contact:-Header > > > > > > I think your error is that you are trying to create a Contact header > > which is not valid. > > > > If the BNF grammar doesn't permit your header, then you shouldn't try > > to construct it. > > > > >>it is possible to create a > > >>"Contact" HCOLON STAR _or_ > > >>"Contact" HCOLON ((contact-param *(COMMA contact-param)) > > > > Correct, but "Contact: *; expires=0" is none of the above so it is not > > > valid. > > > > Regards, > > Attila > > > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Michael > > Hirschbichler > > Sent: 17 April 2007 10:40 > > To: [email protected] > > Subject: [Sip-implementors] Question regarding BNF and Contact:-Header > > > > > > Hi, > > > > I am trying to create the contact-header > > Contact: *; expires=0 > > but if I use the BNF in RFC 3261, I am not able to reconstruct it: > > RFC3261: > > ======================================================== > > ... > > Contact = ("Contact" / "m" ) HCOLON > > ( STAR / (contact-param *(COMMA contact-param))) > > contact-param = (name-addr / addr-spec) *(SEMI contact-params) > > name-addr = [ display-name ] LAQUOT addr-spec RAQUOT > > addr-spec = SIP-URI / SIPS-URI / absoluteURI > > display-name = *(token LWS)/ quoted-string > > > > SEMI = SWS ";" SWS ; semicolon > > STAR = SWS "*" SWS ; asterisk > > HCOLON = *( SP / HTAB ) ":" SWS > > RAQUOT = ">" SWS ; right angle quote LAQUOT = SWS "<"; left angle > > quote ... > > ======================================================== > > > > Regarding > > ("Contact" / "m" ) HCOLON ( STAR / (contact-param *(COMMA > > contact-param))) it is possible to create a "Contact" HCOLON STAR _or_ > > > "Contact" HCOLON ((contact-param *(COMMA contact-param)) > > > > So, where is my error? > > > > Best regards > > Michael > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
