Hi, when a UAS receives a CANCEL it must generate a 200 OK for that CANCEL with the same "To tag" that te one in the 487 that terminates the INVITE transaction.
But when a proxy receives a CANCEL the "To tag" in the 200 OK mustn't match the "To tag" in the 487. Since CANCEL is matched as transaction layer (no need for dialogs) I just can't understand why is needed a "To tag" in the 200 OK for a CANCEL. Also, I can't understand why different requeriments for UAS core and proxy core. IMHO this is one of the typical hyper-redundant issues that make SIP excesively complex with no reason. :( -- Iñaki Baz Castillo _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
