If anyone is really into solving this rare scenario, one possible solution is to wait a bit longer after the CANCEL, for example 64*T1 + T4.
Unfortunately, this does not really solve the problem. Suppose we have more than one proxy in a chain, each with this timer of 64T1+T4. We end up having a problem still (since the first proxy's timer pops, then the second, etc). It seems to me that we should set a timer for 64T1 that causes a 408 to be forwarded back, and tear down the transaction later (maybe another 64T1 later). This way, we can ACK the responses that might come in as a result of timers popping downstream. Alternately, we could just ACK all stray responses.
Best regards, Byron Campen
Cheers, Gilad _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use [email protected] for questions on current sip Use [EMAIL PROTECTED] for new developments of core SIP
_______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
