How it works
A server may return 503 during overload, maintenance or a component failure. It may include a Retry-After value to indicate when the client should try again. The cause should be investigated at the responding node rather than assumed to be the called endpoint.
Business example
A SIP trunk monitor detects repeated 503 responses and activates a configured backup route if one is available.
What to consider
A 503 response does not prove that the entire network has failed. Correlate responses with server load, SIP traces, upstream availability and routing policies.