If timer B is going to run till 1XX response only, who will make sure that we don't remain in "Proceeding" state for ever? This was the reason I did not mention timer B during the initial post, as it is not exactly timer B. But there has to be some timer to make sure that we don't remain in Proceeding state for ever and also don't respond with ACK to 200 OK after some point.
Are we supposed to have some timer here? What will be the duration? Regards Ashish Vyas ________________________________ From: Brett Tate <[email protected]> To: Ashish Vyas <[email protected]>; "[email protected]" <[email protected]> Sent: Wed, May 25, 2011 1:57:49 PM Subject: RE: [Sip-implementors] Response to late 200 OK to INVITE Timer B stops (or becomes useless) after the 100 is received since client moves to Proceeding state. See rfc3261 section 17.1.1.2 text and figure 5. Timer B is only applicable to Calling state. From:Ashish Vyas [mailto:[email protected]] Sent: Wednesday, May 25, 2011 4:15 AM To: Brett Tate; [email protected] Subject: Re: [Sip-implementors] Response to late 200 OK to INVITE Late means after timer B fire. after timer B fire there is no CANCEL from the client. Is client supposed to send one? Before timer B fire there was 100 Trying from server, nothing else. Regards Ashish ________________________________ From:Brett Tate <[email protected]> To: Ashish Vyas <[email protected]>; "[email protected]" <[email protected]> Sent: Wed, May 25, 2011 1:23:21 PM Subject: RE: [Sip-implementors] Response to late 200 OK to INVITE You have not provided enough information concerning the message flow and what "late 200" means. Did the client send CANCEL? Were any other 101-6xx responses received for the INVITE? RFC 6026 provides some details and introduces some new timers. > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Ashish Vyas > Sent: Wednesday, May 25, 2011 3:23 AM > To: [email protected] > Subject: [Sip-implementors] Response to late 200 OK to INVITE > > Dear all > > I am not sure the behaviour of client in this scenario, RFC 3261 was > not clear > to me. > > Say my T1 is 500 ms. > Client sends INVITE to server. Server responds with 100 Trying. Now > after say 60 > seconds server sends 200 OK to client. > Should client ACK this 200 OK? Or should simply ignore? or should it > send 481? > > Thanks > Ashish > _______________________________________________ > 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
