SIP 182 Queued vs 428 Use Identity Header
SIP 182 (Queued) is a 1xx Provisional response, while 428 (Use Identity Header) 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, 428 means that the server requires an Identity header to verify the caller's identity but it was not included in the request.
Deskripsi
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.
Ketika Anda Melihatnya
In call center or queuing scenarios where the callee is busy but the system holds the call in a queue.
Cara Memperbaiki
Wait for the call to be dequeued. If queuing is not desired, configure the server to reject calls instead of queuing them.
Deskripsi
The server requires an Identity header to verify the caller's identity but it was not included in the request.
Ketika Anda Melihatnya
In environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
Cara Memperbaiki
Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.
Perbedaan Utama
182 is a 1xx Provisional response, while 428 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 428: The server requires an Identity header to verify the caller's identity but it was not included in the request.
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 428 when in environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
Kapan Menggunakan Yang Mana
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 428 (Use Identity Header): Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.