SIP 183 Session Progress vs 503 Service Unavailable
SIP 183 (Session Progress) is a 1xx Provisional response, while 503 (Service Unavailable) is a 5xx Server 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, 503 means that the server is temporarily unable to process the request due to overloading or maintenance. The client should retry after the time indicated in the Retry-After header.
Description
Used to convey information about the progress of the call that is not otherwise classified. Often carries early media (ringback tones, announcements) via SDP.
When You See It
During call setup, especially in PSTN interworking scenarios. The response may contain SDP for early media like custom ringback tones or IVR prompts.
How to Fix
No fix needed — this is informational. If early media is not playing, check codec negotiation and SDP handling in your UA.
Description
The server is temporarily unable to process the request due to overloading or maintenance. The client should retry after the time indicated in the Retry-After header.
When You See It
During server overload, maintenance windows, or when the server is rate-limiting requests. Common during traffic spikes.
How to Fix
Wait for the time specified in the Retry-After header. If persistent, check server capacity and consider load balancing across multiple SIP proxies.
Key Differences
183 is a 1xx Provisional response, while 503 is a 5xx Server 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 503: The server is temporarily unable to process the request due to overloading or maintenance. The client should retry after the time indicated in the Retry-After header.
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 503 when during server overload, maintenance windows, or when the server is rate-limiting requests. Common during traffic spikes.
When to Use Which
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 503 (Service Unavailable): Wait for the time specified in the Retry-After header. If persistent, check server capacity and consider load balancing across multiple SIP proxies.