The race condition is known. I assume that the answers can be found at https://lists.cs.columbia.edu/pipermail/sip-implementors/2010-October/025881.html
which indicates to look at https://lists.cs.columbia.edu/pipermail/sip-implementors/2010-May/025009.html http://www.ietf.org/mail-archive/web/sip/current/msg27736.html > -----Original Message----- > From: Jagan Mohan [mailto:[email protected]] > Sent: Tuesday, July 16, 2013 2:41 PM > To: SIP Implementors; [email protected] > Subject: [Sip-implementors] Need clarification on glare condition w.r.t > Session Refresh timer > > Hi, > > I have a call flow as shown below. > > > UAC -------------- UAS > > INVITE with SDP -------> > > <-------- 183 with SDP > > <-------- UPDATE without SDP > > <-------- 200 INVITE with SDP > > 200 UPDATE without SDP -------------> > > Here, there is negotiation of Session Timer and Refresher in INVITE > and > UPDATE transactions. > > Should the refresher be decided only based on 200 INVITE in this > case? > > Or should we avoid sending 200 INVITE till 200 UPDATE is received? > > Else any suggestion how do we handle this glare condition? > > Thanks, > Jagan > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
