SIP 202 Accepted vs 500 Server Internal Error
SIP 202 (Accepted) is a 2xx Success response, while 500 (Server Internal Error) is a 5xx Server Failure response. 202 indicates that the request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests. In contrast, 500 means that the server encountered an unexpected condition that prevented it from fulfilling the request.
Описание
The request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests.
Когда вы это видите
After sending a REFER request for call transfer. The transfer target acknowledges receipt but hasn't completed the transfer yet.
Как исправить
Wait for a NOTIFY to learn the outcome of the referred action. If no NOTIFY arrives, check subscription state and network connectivity.
Описание
The server encountered an unexpected condition that prevented it from fulfilling the request.
Когда вы это видите
When the SIP server has an internal error — database failure, unhandled exception, or resource exhaustion.
Как исправить
Check server logs for the specific error. Common causes include database connectivity issues, configuration errors, or memory exhaustion.
Ключевые различия
202 is a 2xx Success response, while 500 is a 5xx Server Failure response.
SIP 202: The request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests.
SIP 500: The server encountered an unexpected condition that prevented it from fulfilling the request.
You encounter 202 when after sending a REFER request for call transfer. The transfer target acknowledges receipt but hasn't completed the transfer yet.
You encounter 500 when when the SIP server has an internal error — database failure, unhandled exception, or resource exhaustion.
Когда что использовать
For 202 (Accepted): Wait for a NOTIFY to learn the outcome of the referred action. If no NOTIFY arrives, check subscription state and network connectivity. For 500 (Server Internal Error): Check server logs for the specific error. Common causes include database connectivity issues, configuration errors, or memory exhaustion.