El Monday 10 March 2008 11:26:16 Prasanna escribió: > Primarily to handle "forking". Only a TU will be able to distinguish > between 2 entities responding to a forked INVITE with 200 (vide the > To-tag). So it is required after the first 200 is sent (or received) > the transaction is destroyed. > Also the ACK matching being a functionality of TU, the retransmission is > a requirement of the TU.
Ok, but then, what would occur if a retransmited INVITE arrives after the 200 OK? since the transactino server has been already destroyed the INVITE will be identified as a NEW INVITE into the transport/transactions layers so, will be TU responsability to drop it? Thanks a lot. -- Iñaki Baz Castillo [EMAIL PROTECTED] _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
