Paul Kyzivat <pkyzi...@alum.mit.edu> writes: > On 10/29/19 12:05 AM, Ranjit Avasarala wrote: >> Currently, in all the above cases the SIP Proxy server that receives the >> request, responds with a 400 Bad Request. >> Though 400 Bad Request is acceptable given that there is some issue in the >> SIP request, a more detailed error would be more useful - as sometimes >> interpreting 400 Bad Request is harder > > You can use the Reason-Phrase in the 400 response to clarify what you > are complaining about. This should be sufficient to help a developer to > diagnose the issue and fix it. It won't be sufficient to all a > preprogrammed reaction in the UAC, but I don't see that as a reasonable > expectation for problems like this.
I would suggest using the Warning header with warn-code 399 and reporting the problem in the warn-text. The problem in practice is that this sort of error is not particularly common once a system has been shaken down in production use. And it's really hard to provide any sort of automated reponse that is useful, because there are so many possibilities. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
