SIP 100 Trying vs 202 Accepted
SIP 100 (Trying) is a 1xx Provisional response, while 202 (Accepted) is a 2xx Success response. 100 indicates that the request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses. In contrast, 202 means that the request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests.
描述
The request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses.
何时出现
Immediately after sending an INVITE. The proxy has received the call and is searching for the callee. This is the SIP equivalent of a dial tone.
如何修复
No fix needed — this is normal call setup behavior. If stuck on 100 Trying for too long, check network connectivity and proxy configuration.
描述
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.
主要区别
100 is a 1xx Provisional response, while 202 is a 2xx Success response.
SIP 100: The request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses.
SIP 202: The request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests.
You encounter 100 when immediately after sending an INVITE. The proxy has received the call and is searching for the callee. This is the SIP equivalent of a dial tone.
You encounter 202 when after sending a REFER request for call transfer. The transfer target acknowledges receipt but hasn't completed the transfer yet.
何时使用哪个
For 100 (Trying): No fix needed — this is normal call setup behavior. If stuck on 100 Trying for too long, check network connectivity and proxy configuration. 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.