SIP 202 Accepted vs 406 Not Acceptable
SIP 202 (Accepted) is a 2xx Success response, while 406 (Not Acceptable) is a 4xx Client 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, 406 means that the resource identified by the request is only capable of generating responses with content characteristics not acceptable according to the Accept header.
Descripción
The request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests.
Cuándo lo verás
After sending a REFER request for call transfer. The transfer target acknowledges receipt but hasn't completed the transfer yet.
Cómo solucionarlo
Wait for a NOTIFY to learn the outcome of the referred action. If no NOTIFY arrives, check subscription state and network connectivity.
Descripción
The resource identified by the request is only capable of generating responses with content characteristics not acceptable according to the Accept header.
Cuándo lo verás
When content negotiation fails — the server cannot produce a response matching the Accept header fields in the request.
Cómo solucionarlo
Review the Accept headers in your request and broaden the acceptable content types.
Diferencias clave
202 is a 2xx Success response, while 406 is a 4xx Client Failure response.
SIP 202: The request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests.
SIP 406: The resource identified by the request is only capable of generating responses with content characteristics not acceptable according to the Accept header.
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 406 when when content negotiation fails — the server cannot produce a response matching the Accept header fields in the request.
Cuándo usar cada uno
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 406 (Not Acceptable): Review the Accept headers in your request and broaden the acceptable content types.