SIP 100 Trying vs 501 Not Implemented
SIP 100 (Trying) is a 1xx Provisional response, while 501 (Not Implemented) is a 5xx Server Failure 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, 501 means that the server does not support the functionality required to fulfill the request. The method is recognized but not implemented.
설명
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 server does not support the functionality required to fulfill the request. The method is recognized but not implemented.
이 코드를 보게 되는 경우
When the SIP method is valid but the server has not implemented it (e.g., INFO, UPDATE, PRACK on a basic server).
해결 방법
Use a different method that the server supports. Check the Allow header in responses to see supported methods.
주요 차이점
100 is a 1xx Provisional response, while 501 is a 5xx Server Failure 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 501: The server does not support the functionality required to fulfill the request. The method is recognized but not implemented.
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 501 when when the SIP method is valid but the server has not implemented it (e.g., INFO, UPDATE, PRACK on a basic server).
언제 어떤 것을 사용할지
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 501 (Not Implemented): Use a different method that the server supports. Check the Allow header in responses to see supported methods.