SIP 202 Accepted vs 438 Invalid Identity Header
SIP 202 (Accepted) is a 2xx Success response, while 438 (Invalid Identity Header) 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, 438 means that the server obtained the certificate from the Identity-Info header but the signature in the Identity header is invalid.
Description
The request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests.
When You See It
After sending a REFER request for call transfer. The transfer target acknowledges receipt but hasn't completed the transfer yet.
How to Fix
Wait for a NOTIFY to learn the outcome of the referred action. If no NOTIFY arrives, check subscription state and network connectivity.
Description
The server obtained the certificate from the Identity-Info header but the signature in the Identity header is invalid.
When You See It
When the cryptographic signature in the Identity header does not match the message content, indicating possible tampering.
How to Fix
Regenerate the Identity header with a correct signature. Ensure no intermediary is modifying signed headers after signing.
Key Differences
202 is a 2xx Success response, while 438 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 438: The server obtained the certificate from the Identity-Info header but the signature in the Identity header is invalid.
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 438 when when the cryptographic signature in the Identity header does not match the message content, indicating possible tampering.
When to Use Which
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 438 (Invalid Identity Header): Regenerate the Identity header with a correct signature. Ensure no intermediary is modifying signed headers after signing.