I think, we should not mix network behavior with UAC behavior. What if the transport is TCP? In that case requests will be sequenced automatically.
On Tue, May 5, 2009 at 3:52 PM, Rastogi, Vipul (Vipul) <vrast...@avaya.com> wrote: > That is correct but here we are mixing network behavior with UAC behavior. > UAC can send such MESSAGES, 3261 does not restrict UAC. > > > -----Original Message----- > From: sip-implementors-boun...@lists.cs.columbia.edu > [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Iñaki > Baz Castillo > Sent: Tuesday, May 05, 2009 3:49 PM > Cc: sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] Multiple concurrent transactions > > 2009/5/5 Pandurangan R S <pandurangan....@gmail.com>: >>>> If it didn't arrive, then the UAS would discard the new request >>>> since CSeq is incorrect (UAS expects 101 instead of 102). >> >> I think UAS expects a Cseq that is simply greater (not next number) >> than the Cseq received in a previous request from UAC. >> So it will accept 102, 103 etc.. > > If the UAC sends: > > - INFO "1" (CSeq 101) > - INFO "2" (CSeq 102) > - INFO "3" (CSeq 103) > > and it doesn't wait for each transaction to be terminated, then if the third > request (CSeq 103) arrives before the others, the others will be rejected > when arriving (since CSeq is less than the last received: > 103). > > -- > Iñaki Baz Castillo > <i...@aliax.net> > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
