From: "Attila Sipos" <[EMAIL PROTECTED]> Clearly 486 is completely the wrong cause here. I think this is obvious to anyone who knows telephony or SIP.
Can't we just tell these vendors to fix their implementations and then we can just use 5xx causes to route elsewhere. We can have any convention we want, I suppose, but we first have to establish it. For instance, right now there are several 4xx codes that can plausibly be generated at a proxy/gateway or UA. 500 is even worse -- it is used as a generic "server failure" response, but also for "CSeq out of order", which is a UA response. I suppose it's also possible that there are other solutions than ensuring responses are tagged appropriately in regard to cause. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
