On Monday, July 18, 2011, Krishna Moorthy <[email protected]> wrote: > Hi all, > > What if in the incoming request, the UAC does not add the "refresher" > parameter ( request has Min-SE and Session -expires) ? How should the UAS > behave at this point for session refresh ? > > > 1) In such a case, would it be more appropriate if the UAS owns the > responsibility of refreshing the session ? so in the 200 OK, the UAS should > add the "refresher=uas" > > 2) Or should the UAS assume that the UAC should be the refresher ? and > add "refresher = uac" in 200 OK ? > > I want to go with point 1, the fundamental design should be such that If the > UAC wishes to be the refresher, then it has to come through a signaling > change, if the refresher parameter is missing but has the Min-SE and the > session -expires headers, then its safe for the UAS to assume that > The UAC supports Session timers but does notant to be the refresher itself, > so the UAS would be the refresher. This behavior would solve compatibility > issues and interoperability issues. > > I would like to hear your thoughts. Thanks.
Hi Krishna, have a look at rfc4028, Section 9, Table 2. The paragraph under says that if UAC did not provide the refresher parameter the UAS can decide what to put into the response (uac/uas).. Regards, Brez _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
