Dialog is confirmed at UAC when 2xx "arrives". Dialog is confirmed at UAS when ACK "arrives"
So if UAS keeps on transmitting 2xx but doesn't receive ACK it means dialog 1. Dialog might or might not be confirmed at UAC. 2. Dialog is not confirmed at UAS. -Nitin On Thu, Jul 31, 2008 at 10:10 AM, Rockson Li (zhengyli) <[EMAIL PROTECTED]>wrote: > inline > -Rockson > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Ivar Lumi > Sent: Wednesday, July 30, 2008 11:31 PM > To: [email protected] > Subject: [Sip-implementors] UAS early dialog to confirmed > > Hi, > > When UAS early dialog get into confirmed state ? > > In rfc 3261 12. > A dialog can also be in the "early" state, which occurs when it is > created with a provisional response, > and then transition to the "confirmed" state when a 2xx final > response arrives. > > From there: it's confirmed when 2xx is sent. > [RL] note it says a 2xx final response *arrives*, so this is from UAC's > perspective. > > Now .... > > RFC 3261 13.3.1.4. > If the server retransmits the 2xx response for 64*T1 seconds > without > receiving an ACK, the dialog is confirmed, but the session SHOULD > be > terminated. This is accomplished with a BYE, as described in > Section > 15. > > From there: It's confirmed only if ACK received or wait time reached. > [RL] this is correct. > > Seems i miss the place in rfc what gives 100% answer to it. > > Thanks. > _______________________________________________ > 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 > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
