Hi, >>You can have network entities which act as "normal" UAS, which also >>want to send 199. They may e.g. have been configured to do so, since >>the forking proxy does not support 199. Etc. >>And, the text already says that a UAS should not send a 199, unless it has been configured to do so. But, I don't think >>we should forbid it from doing so. > > >No, but you need to motivate why they might do so. Explain that they're sending it because they think there's an upstream >forking proxy that won't. Explain that they might be a B2BUA that has created more than one early dialog with the caller, >and wants to clean some of them up. It makes little sense to say that UAs can do this without some kind of explanation >about why they would do so.
The text does talk about the case when the UAS knows, based on configuration, that the proxy does not support 199, but I agree that some text about UAS/B2BUAs creating more than one dialog can be added. 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
