It is not mandated either way. It could be sent at any interval between the last UPDATE/INVITE and 100 seconds. I believe it is recommended, and standard practice follows, that half-life is when to send it out, but it is not required.
Joel Gerber Network Operations Specialist - Telephone Telephone Eastlink joel.ger...@corp.eastlink.ca T: 519.786.1241 -----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of isshed Sent: March-27-15 9:02 AM To: Brett Tate Cc: sip-implementors Subject: Re: [Sip-implementors] Sessions Expires with Info Thanks everyone for the responses. Brett, Lets assume the expires value is 100. the Update/Invite will go after 50 seconds after message (3). right? Thanks, On Fri, Mar 27, 2015 at 4:59 PM, Brett Tate <br...@broadsoft.com> wrote: >> The INFO can be out of dialog as well. > > INFO is a mid-dialog request. RFC 6086 section 1. > > "Use of the INFO method does not constitute a separate dialog usage. > INFO messages are always part of, and share the fate of, an invite > dialog usage [RFC5057]. INFO messages cannot be sent as part of other > dialog usages, or outside an existing dialog." > > >> > I have a scenario where my phone has negotiated with server as 60 >> > seconds expires and UAC as refreshers. > > For completeness, I should mention that the negotiated value is below > the absolute minimum mentioned within RFC 4028 section 4. > > "The absolute minimum for the Session-Expires header field is 90 seconds." _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
