SIP 202 Accepted vs 482 Loop Detected
SIP 202 (Accepted) is a 2xx Success response, while 482 (Loop Detected) 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, 482 means that the server has detected a loop. The request was received with its own address in the Via header, indicating it has been forwarded back to itself.
Description
The request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests.
Quand vous le voyez
After sending a REFER request for call transfer. The transfer target acknowledges receipt but hasn't completed the transfer yet.
Comment résoudre
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 has detected a loop. The request was received with its own address in the Via header, indicating it has been forwarded back to itself.
Quand vous le voyez
When routing configuration causes a request to cycle between two or more proxies without reaching the callee.
Comment résoudre
Review proxy routing tables and DNS records. Check for circular references in SIP routing. Fix the routing configuration to break the loop.
Différences clés
202 is a 2xx Success response, while 482 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 482: The server has detected a loop. The request was received with its own address in the Via header, indicating it has been forwarded back to itself.
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 482 when when routing configuration causes a request to cycle between two or more proxies without reaching the callee.
Quand utiliser lequel
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 482 (Loop Detected): Review proxy routing tables and DNS records. Check for circular references in SIP routing. Fix the routing configuration to break the loop.