Why Did My Call Fail?
Every call failure reason explained in plain language. Timeout, busy, rejected, WebRTC errors, and what to do about each one.
Seeing a "Failed" status on a call can be frustrating, but it does not mean something is wrong with BubblyPhone. There are many reasons a call might not connect, and most of them are outside of our control. This article explains every failure reason you might see, what it means in plain language, and what you can do about it.
You are never charged for failed calls
Regardless of the reason, if a call shows as Failed, you were not charged. Billing only starts when the other person answers. Your balance was not affected.
No one answered
Shows as: timeout, no_answer
Your call went through successfully and rang on the other person's phone, but they did not pick up. This is not a problem with BubblyPhone — the call worked correctly on our end. The phone rang, but nobody answered it. Try calling at a different time, or check that you have the right number.
You cancelled the call
Shows as: originator_cancel
You hung up before the other person answered. The call was connecting normally — you ended it before they picked up. This often happens when you redial quickly or change your mind while the phone is still ringing. There is nothing wrong with the service.
Line was busy
Shows as: user_busy
The person you called was already on another call. Their phone line was occupied, so your call could not be connected. Try again in a few minutes.
Call was rejected
Shows as: call_rejected
The recipient's phone or their carrier rejected the incoming call. This can happen for several reasons: they may have spam call filtering enabled on their phone, their carrier may block international calls by default, or certain countries have restrictions on incoming calls from VoIP services. If you know the person, ask them to check whether their phone is set to block unknown or international numbers.
Number does not exist
Shows as: unallocated_number, not_found
The phone number you dialed is not in service or does not exist. Double-check the number carefully, digit by digit. Make sure you selected the correct country code from the dropdown. Remember to drop the leading zero from local numbers. For example, if the UK number is 020 7946 0958, you should enter 2079460958 after selecting +44. See How to Make International Calls for more dialing examples.
Connection failed
Shows as: webrtc_connection_failed
Your browser could not establish a connection for the call. This is typically caused by your internet connection, network settings, or browser configuration — not by BubblyPhone. Here are things to try:
- Switch to Wi-Fi instead of mobile data.
- Use Chrome or Firefox, which have the best WebRTC support.
- Close other apps that might be using your microphone, such as Zoom, Teams, Discord, or FaceTime.
- Use the Test Connection feature in the Dialer to check your setup before calling.
- If you are on a phone or tablet, try our iOS or Android app for a more reliable connection on mobile devices.
Network issue
Shows as: network_out_of_order, normal_temporary_failure
There was a temporary problem with the phone network in the destination country. This is a telecom infrastructure issue that is completely outside of BubblyPhone's control. It could be caused by congestion, maintenance, or a local outage. Try your call again in a few minutes. These issues are almost always temporary.
Call timed out
Shows as: recovery_on_timer_expire
The call took too long to connect. This can happen with certain international routes, during peak hours when phone networks are congested, or when routing through multiple carrier networks. Try calling again. If it happens repeatedly to the same number, the issue may be on the recipient's carrier side. For technical details, see SIP Error Codes Explained.
Destination out of order
Shows as: destination_out_of_order
The number you called appears to be temporarily out of service. The issue is on the recipient's end — their phone may be turned off, disconnected, or experiencing a service disruption. Try again later, or reach the person through a different method to confirm their number is still active.
You are NEVER charged for failed calls
Only calls that are answered cost money. If your call shows as Failed — for any reason at all — your balance was not affected. No minutes were deducted. No charges were applied.
Think you were incorrectly charged?
If you believe you were charged for a call that did not actually connect, go to your Call History, tap the call in question, and use the "Report Issue" button. Our team will review the call record and correct any billing errors. Learn more in Reading Your Call Details.