Venkatesh Joshi wrote: >Hi, > >I have a situation where a phone sends a REGISTER message with "expires=3600" >in the Contact Header. > >The SIP registrar replies back with "Expires: 300" in the 200 OK response. > >In such a situation, which of these 2 values should be taken as the actual >expiration interval ? > >RFC 3261 -> section 10.3 is slightly obfuscated. > >In one instance it states that if REGISTER request has an "expires" parameter >or if the request has an "Expires" header field, that value MUST be taken as >the requested expiration. > > Just as it says, the "requested" expiration. This doesn't mean that the Registrar is going to entertain this request. So the registrar decides the expiration time.
> >Then, it also states that registrar MAY choose an expiration less than the >requested expiration interval. > >Does this mean that the value in the 200 OK message takes precedence ? > Ergo, 200 OK expiration interval rules. This shud be less or equal to the requested expiration, but not more. cheerz - Ben. *********************** 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
