Hi, >>Yes, but the issue is how the proxy knows whether it has sent a 199 for the early dialog indicated in the error >>response. > >Again, the proxy needs to have a list of early dialogs and within that state data needs to remember whether or not a 199 >has been sent/forwarded to the UAC.
Again, I agree with you :) >>The issue is whether the proxy can detect that a final response is >>generated by another forking proxy, and therefor terminate more than one early dialog. > >It does not matter whether the final response came from a forking proxy or not. When a final response is received on a >client transaction, the proxy has to assume that all downstream forks that the request created have been terminated. RFC >3261 requires that the proxies and UASes send only one non-2xx final response, so any downstream proxy that forked the >request would not send back a non-2xx final response until all of its forks completed. Yes, and the issue was HOW the proxy knows WHICH downstream forks are terminated by the single final response. Your proposal is to look at the Via branch, and I think that may work. So, I think we're on the same page :) Regards, Christer _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip
