SIP 183 Session Progress vs 491 Request Pending
SIP 183 (Session Progress) is a 1xx Provisional response, while 491 (Request Pending) is a 4xx Client Failure response. 183 indicates that used to convey information about the progress of the call that is not otherwise classified. Often carries early media (ringback tones, announcements) via SDP. In contrast, 491 means that the request was received by a UAS that had a pending request within the same dialog. The UAS cannot process both requests simultaneously.
Описание
Used to convey information about the progress of the call that is not otherwise classified. Often carries early media (ringback tones, announcements) via SDP.
Когда вы это видите
During call setup, especially in PSTN interworking scenarios. The response may contain SDP for early media like custom ringback tones or IVR prompts.
Как исправить
No fix needed — this is informational. If early media is not playing, check codec negotiation and SDP handling in your UA.
Описание
The request was received by a UAS that had a pending request within the same dialog. The UAS cannot process both requests simultaneously.
Когда вы это видите
When sending a re-INVITE while another re-INVITE is still being processed. Common during hold/unhold or codec change sequences.
Как исправить
Wait for the pending transaction to complete before sending a new one. Implement proper glare handling (RFC 3261 Section 14.1).
Ключевые различия
183 is a 1xx Provisional response, while 491 is a 4xx Client Failure response.
SIP 183: Used to convey information about the progress of the call that is not otherwise classified. Often carries early media (ringback tones, announcements) via SDP.
SIP 491: The request was received by a UAS that had a pending request within the same dialog. The UAS cannot process both requests simultaneously.
You encounter 183 when during call setup, especially in PSTN interworking scenarios. The response may contain SDP for early media like custom ringback tones or IVR prompts.
You encounter 491 when when sending a re-INVITE while another re-INVITE is still being processed. Common during hold/unhold or codec change sequences.
Когда что использовать
For 183 (Session Progress): No fix needed — this is informational. If early media is not playing, check codec negotiation and SDP handling in your UA. For 491 (Request Pending): Wait for the pending transaction to complete before sending a new one. Implement proper glare handling (RFC 3261 Section 14.1).