A proxy would normally have started timer C, which results in a 408 (rfc talks about 180 seconds as typical interval) and cleans up the client transaction. The 408 ends the server transaction (unless there are other branches)
The proxy is allowed to act as if timer C expired upon a CANCEL timeout, and send 408 sooner. It should not generate a 487 response itself Regards, Jeroen -----Oorspronkelijk bericht ----- Van: "M. Rangnathan" <[EMAIL PROTECTED]> Aan: "Jeroen van Bemmel" <[EMAIL PROTECTED]> CC: "M. Rangnathan" <[EMAIL PROTECTED]>; "Sip-Implementors" <[email protected]> Verzonden: 22-12-06 03:10 Onderwerp: Re: [Sip-implementors] Coupling between CANCEL Timout and INVITE clienttransaction Thanks. Should a proxy server also do this action (i.e. Terminate the INVITE if the CANCEL times out?). Ranga Jeroen van Bemmel wrote: > Yes, also because older UAS won't send 487 response for INVITE anyway, > so the UAC needs to handle this case > > Regards, > Jeroen > > M. Rangnathan wrote: > >> I have the following scenario: >> >> UAC sends out INVITE >> UAS responds with RINGING >> UAC sends out CANCEL >> UAS does not repsond to CANCEL (for example, it dies). >> UAC cancel transaction Times Out. >> >> Question -- should the UAC also delete the INVITE Client Transaction >> that it was originally trying to CANCEL ? ( I think the answer is >> "yes" but I want to be sure. ) >> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
