SIP 183 Session Progress vs 401 Unauthorized
SIP 183 (Session Progress) is a 1xx Provisional response, while 401 (Unauthorized) 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, 401 means that the request requires user authentication. The response includes a WWW-Authenticate header with a challenge for the realm.
説明
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 requires user authentication. The response includes a WWW-Authenticate header with a challenge for the realm.
このコードが表示される場合
When making a request that requires Digest authentication. Common for REGISTER and INVITE requests to authenticated SIP trunks.
解決方法
Resend the request with proper Authorization header containing valid credentials (Digest authentication).
主な違い
183 is a 1xx Provisional response, while 401 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 401: The request requires user authentication. The response includes a WWW-Authenticate header with a challenge for the realm.
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 401 when when making a request that requires Digest authentication. Common for REGISTER and INVITE requests to authenticated SIP trunks.
どちらをいつ使うか
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 401 (Unauthorized): Resend the request with proper Authorization header containing valid credentials (Digest authentication).