Objective
When making outbound voice calls using SIP Trunking, Programmable SIP, or the Voice API, calls fail and your SIP logs show one of the following responses:
402 Payment RequiredSIP/2.0 503 Service Unavailable 4 Payment Required
Applies To
- Voice API
- SIP Trunking
- Programmable SIP
Procedure
Both error codes indicate that your Vonage account does not have sufficient balance or has reached its credit limit to process the call.
402 Payment Required — This code may appear in your call detail records (CDRs) or Voice API logs to indicate that the call was rejected due to a payment issue at the account level.
503 Service Unavailable 4 Payment Required — This is the SIP response your endpoint receives directly from the Vonage platform when a call attempt is rejected because the account balance is zero or the credit limit has been exceeded.
Although the two codes appear in different places, they share the same root cause: insufficient account funds.
-
Check your account balance
Log in to your Vonage API Dashboard and navigate to Billing to review your current balance and credit limit.
-
Top up your account
If your balance is zero or negative, add funds to your account. For instructions, refer to:
-
Set up low balance alerts
To avoid future interruptions, configure a low balance notification in your Dashboard under Settings > Notifications. This will alert you before your balance runs out.
-
Retest your calls
Once your balance has been topped up, retry your calls. They should complete successfully.
Additional Information
If your account balance appears sufficient but you are still receiving these errors, please contact Vonage Support and provide the following details to assist with investigation:
API Key
From and To numbers
Timestamp of the failed call
Call UUID (if available) — see What is a Call UUID?
Articles in this section
- SIP 402 and 503 "Payment Required" Error Codes on Voice Calls
- SIP Client Registration and Call Failure After Creating a Secondary API Secret
- Inbound Call Failover Not Working in SIP Trunking
- Why does my SIP endpoint reject the call with SIP 403 Forbidden?
- Is the Diversion header supported in SIP Trunking?
- No Audio In Programmable SIP IVR
- Does Vonage support Digest Authentication for inbound calls to a SIP endpoint?
- Is SIP REFER supported?
- How to Create a Redundant SIP-Forwarding Configuration
- Special Characters in Forward to SIP Address