We've discovered that the same considerations apply to 482 Merged Request responses. You'd think that 482 would not be possible in-dialog, but it happens when some step along the chain of proxies falls back from one transport method to another. This happens due to networking delays or sluggish response from the UAC.
Interestingly, RFC 5057 treats 482 as dialog-fatal. It really should only be transaction-fatal. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
