SIP 182 Queued vs 436 Bad Identity-Info
SIP 182 (Queued) is a 1xx Provisional response, while 436 (Bad Identity-Info) is a 4xx Client Failure response. 182 indicates that the called party is temporarily unavailable but the server has decided to queue the call rather than reject it. The call will be attempted when the callee becomes available. In contrast, 436 means that the Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
描述
The called party is temporarily unavailable but the server has decided to queue the call rather than reject it. The call will be attempted when the callee becomes available.
何时出现
In call center or queuing scenarios where the callee is busy but the system holds the call in a queue.
如何修复
Wait for the call to be dequeued. If queuing is not desired, configure the server to reject calls instead of queuing them.
描述
The Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
何时出现
When the Identity-Info URI in the request points to an unreachable or invalid certificate location.
如何修复
Ensure the Identity-Info URI is reachable and points to a valid certificate. Check DNS resolution and TLS configuration.
主要区别
182 is a 1xx Provisional response, while 436 is a 4xx Client Failure response.
SIP 182: The called party is temporarily unavailable but the server has decided to queue the call rather than reject it. The call will be attempted when the callee becomes available.
SIP 436: The Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
You encounter 182 when in call center or queuing scenarios where the callee is busy but the system holds the call in a queue.
You encounter 436 when when the Identity-Info URI in the request points to an unreachable or invalid certificate location.
何时使用哪个
For 182 (Queued): Wait for the call to be dequeued. If queuing is not desired, configure the server to reject calls instead of queuing them. For 436 (Bad Identity-Info): Ensure the Identity-Info URI is reachable and points to a valid certificate. Check DNS resolution and TLS configuration.