> Need inputs in the following scenario (wrt UAS) > > - INVITE received with Session-Expires, Min-SE, Supported:timer, no > refresher is present > - 183 sent with Supported:timer > - UPDATE received with *no* Session-Expires, *no* Min-SE, > Supported:timer, no refresher is present > - 200 OK of UPDATE sent with *no* Session-Expires, *no* Min-SE, > Supported:timer, no refresher is present > - 200 OK of INVITE sent with *no* Session-Expires, *no* Min-SE, > Supported:timer, Require:timer, no refresher is present > > My questions are: > - Does receipt of UPDATE with no session timer values > turn off the session expiration?
No; however it does indicate that the UAC and proxies are not requesting to activate it on the early dialog. > Is the UAC saying that it does not support sessiontimer now? No. > - Who shall refresh the session in the above case (if any)? Based upon the INVITE 200 response, nobody (assuming Session-Expires not added to response by proxy). > - Does the UAS need to run a session timer (since it has > not sent session timer values in 200 OK of UPDATE and INVITE)? No; however it should become compliant to RFC 4028 and not add require timer to INVITE 2xx response unless it is also adding a Session-Expires header. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
