In general, i belive it wont make difference, if you consider 0 as invalid and 1 to be valid, in both cases it's real that content expired before final response sent and you handle it with 487 Request Terminated as rfc says.
Aneesh Naik wrote: > I think INVITE with Expires 0 would be an Invalid value. > I would expect that an Expires with value as 0 in INVITE request be > considered as a special case and UAS should respond back immediately. > Immediately would be relative depending on the time required to > process the message by the UAS. But it should not return 487 Request > Terminated. > > Thanks, > Aneesh > > On Feb 4, 2008 7:41 PM, Ivar Lumi <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > Hi, > > RFC 3261 section 13.3.1 > > If the request is an INVITE that contains an Expires header field, the > UAS core sets a timer for the number of seconds indicated in the > header > field value. When the timer fires, the invitation is considered to be > expired. If the invitation expires before the UAS has generated a > final > response, a 487 (Request Terminated) response SHOULD be generated. > > I get from this, that you must return 487 (Request Terminated). > > Aneesh Naik wrote: > > Hi All, > > > > Can Expires header have a value of "0" for INVITE request? > > If yes then how should it be handled because the request will > expires as > > soon as it is received by UAS. > > > > Thanks, > > Aneesh > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > <mailto:[email protected]> > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > > > > -- > Aneesh _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
