SIP 202 Accepted vs 483 Too Many Hops
SIP 202 (Accepted) is a 2xx Success response, while 483 (Too Many Hops) 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, 483 means that the Max-Forwards header has reached zero, indicating the request has passed through too many proxies.
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 Max-Forwards header has reached zero, indicating the request has passed through too many proxies.
When You See It
When a request traverses more proxies than the Max-Forwards counter allows (default 70). Often indicates a routing loop.
How to Fix
Check for routing loops. If the path is legitimately long, increase Max-Forwards. Usually indicates misconfigured routing.
Key Differences
202 is a 2xx Success response, while 483 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 483: The Max-Forwards header has reached zero, indicating the request has passed through too many proxies.
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 483 when when a request traverses more proxies than the Max-Forwards counter allows (default 70). Often indicates a routing loop.
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 483 (Too Many Hops): Check for routing loops. If the path is legitimately long, increase Max-Forwards. Usually indicates misconfigured routing.