Have you seen RFC3326? It might be just what you are looking for and I know at least a few implementations that support it to various extent.
-Max On Tue, Apr 28, 2020 at 2:01 PM Ranjit Avasarala <ranjitka...@gmail.com> wrote: > Hi SIP Experts > > there are numerous scenarios where a SIP server would respond with 500 > Internal Server Error response. Troubleshooting the 500 error is not easy > due to the lack of any reason in the response though some servers do append > Reason header. e.g. > 500 Internal Server Error > .................. > Reason: Insufficient Bearer Resources > > but the usage of Reason header is not very common and is optional. > > SO I would like to know if there is any specification that mandates Reason > header in 500 response so that the entities receiving it would know the > reason for 500 > > Thank you > Ranjit > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts Tel (Canada): +1-778-783-0474 _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
