On Mon, 2005-12-26 at 10:01 +0000, Andy Pandaram wrote: > In Sec 8.2.2 of RFC 3261, about Merged Requests, it says a UAS Core must > compare a request without To Tag against ongoing transactions. > > What kind of transactions are included in the "ongoing" transactions? > > Consider the 3 scenarios:
> 1) UAS received an INVITE. It had sent 180 Ringing. Now it receives > a merged request (same From tag, Call Id, CSeq, different Via branch ) Send 482 > 2) UAS received an INVITE. It had sent 400 Bad Request. Now it > receives a merged request (same From tag, Call Id, CSeq, different Via > branch ) If it's a bad request, it doesn't much matter whether you return 400 or 482. I'd send 400 since that is the more severe error. > 3) UAS received an INVITE. It had sent 200 Ok and received an ACK. > Now it receives a merged request (same From tag, Call Id, CSeq, > different Via branch ) Thangarajan already pointed out that the conflicting branch information may not be available, but the dialog information matches and now the CSeq on that dialog will be incorrect, so returning either Loop Detected or Out Of Sequence (depending on whether or not you have the branch info) would be fine. The important thing is that you not treat it as a new INVITE. -- Scott Lawrence tel:+1-781-938-5306;ext=162 or sip:[EMAIL PROTECTED] Consulting Engineer - Pingtel Corp. http://www.pingtel.com/ sipXpbx project coordinator - SIPfoundry http://www.sipfoundry.org/sipX _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
