SIP 100 Trying vs 436 Bad Identity-Info
SIP 100 (Trying) is a 1xx Provisional response, while 436 (Bad Identity-Info) is a 4xx Client 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, 436 means that the Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
Mô tả
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.
Khi bạn thấy mã này
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.
Cách khắc phục
No fix needed — this is normal call setup behavior. If stuck on 100 Trying for too long, check network connectivity and proxy configuration.
Mô tả
The Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
Khi bạn thấy mã này
When the Identity-Info URI in the request points to an unreachable or invalid certificate location.
Cách khắc phục
Ensure the Identity-Info URI is reachable and points to a valid certificate. Check DNS resolution and TLS configuration.
Sự khác biệt chính
100 is a 1xx Provisional response, while 436 is a 4xx Client 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 436: The Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
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 436 when when the Identity-Info URI in the request points to an unreachable or invalid certificate location.
Khi nào dùng cái nào
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 436 (Bad Identity-Info): Ensure the Identity-Info URI is reachable and points to a valid certificate. Check DNS resolution and TLS configuration.