The worst part of User Busy is not that your call failed. It is the small suspicion that creeps in afterwards, that the person you rang has decided not to take it. Two words, no ring, and a whole story invented in your head.
I know how frustrating that is when you need to reach somebody. Let me give you the answer straight away, because it will save you a lot of pointless tapping.
Your iPhone did not write those words. They arrived from the phone network, and the standard they come from says the network can send them all by itself, with the person you called never knowing you rang.
The short answer, and what it rules out
User Busy is a telephone network status code. Your carrier tried to set the call up, something at the far end refused it, and the reason code came back down the line to your screen.
That matters because of what it rules out immediately. Your handset placed the call successfully. Your number is active. Your dialer works.
None of the usual iPhone fixes touch any of that. Resetting network settings, toggling Airplane Mode and re-seating the SIM all act on the part that already did its job.
So the useful question is not what is wrong with the phone. It is which end this came from, and there is a two-minute way to find out.
Those two words come from a telephone standard
The code is defined in the ITU standard Q.850, which is the shared list of reasons phone networks give each other when a call does not connect. Cause 17 is the one you are looking at.
The standard's definition, quoted from a published cause-code reference: "This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network."
Read that second sentence twice. By the called user or by the network.
So User Busy does not prove the person is on another call. It proves that something between your carrier and their handset would not take the call, and the network is allowed to make that decision on their behalf.
That one clause changes what you should do next. Treat the code as proof that somebody is on the phone and you will go looking in the wrong place.
Count first, because one number and every number are different problems
This is the two-minute test, and it splits the whole thing.
Ring three different numbers you know work. A landline, a friend, and your own voicemail if you can.
If only one number gives User Busy and the rest connect, the problem sits at that number's end or on the route between your carrier and theirs. Nothing on your iPhone can reach it.
If every number gives User Busy, that is your line, and the conversation is with your carrier rather than with Settings.
If it changes depending on where you are standing, you are probably looking at a coverage problem wearing a different label, and our page on an iPhone stuck on SOS or No Service is the better starting point.
If it is one number, what is likely happening at their end
Several ordinary things produce this, and none of them is personal.
- They are already on a call and have no call waiting. The classic case, and the only one most articles mention.
- Their phone is off or has no signal, and their carrier answers for it rather than passing the call through to voicemail.
- Their line has a barring or a billing block on it. Incoming calls get refused at the network before their handset is ever asked.
- You are blocked, but their carrier does the blocking rather than their phone. Apple's own blocking works differently, and our page on what blocking actually does explains why an iPhone block sends you to voicemail instead.
- Two carriers that route badly between each other. Rare, real, and it shows up as one specific number failing from one specific network.
Test it before you assume anything. Ring the same number from a different phone, ideally on a different network. If it fails there too, your iPhone was never involved. Owners report the reverse case too, where their own callers hear it while their handset sits silent. That is the next section.
If people get User Busy when they ring you
This is the version that costs people work, and its causes are nothing like the ones we have just been through.
Start with Call Forwarding. If it is on and pointing at a number that cannot answer, your callers hit a wall while your own phone stays silent all day. Check at Settings, then Apps, then Phone, then Call Forwarding.
Then check Call Waiting in the same place. With it off, a second caller is refused while you are on the first call, which is correct behavior and reads to them as a rejection.
Then think about what else uses the line. A FaceTime Audio call, a WhatsApp call and a data-only call all occupy you in ways the cellular network may or may not know about, depending on your carrier.
And if none of that fits, ask your carrier to check the provisioning on your line and to look for any barring on incoming calls. Apple does not expose either of those anywhere in Settings. That is a five-minute job for them and impossible for you.
Where Apple's advice stops, and what to do about it
Apple has one page for calls that fail, and it is a good page. It just does not go here.
Apple documents three broad reasons a call will not go through on its failed and missed calls page: settings you have turned on, software that is out of date, and a problem on your network.
Read end to end, that page never uses the words User Busy. Neither do the 768 Apple support pages we hold cached locally. Apple does not set out to explain the network's own vocabulary, and that is a fair place for a handset maker to stop.
It does leave you holding a message nobody official has defined for you. Which is the reason this page exists.
Apple's ladder is still the right one to climb once, in its order, if every number fails. Carrier settings update first, at Settings, General, About. Then any waiting iOS update. Then, and only then, Reset Network Settings, which Apple warns "will erase all current saved settings, including Wi-Fi passwords, preferred networks, and VPN and APN settings that you've used before".
Our page on an iPhone showing Call Failed covers that ladder properly, including the one Wi-Fi test that separates your line from your handset.
What does not work
- Erasing the phone. The message is generated off your device. A clean install produces the same result on the same line.
- Taking the SIM out and putting it back. Useful when a phone cannot read the card at all, which shows a different message entirely.
- Turning 5G off. Voice call setup does not depend on it, and nothing in Apple's advice for a failed call mentions it.
- Calling repeatedly. If the network generated the code, repeating the call reproduces it. Wait a few minutes instead.
- Blaming the person. The standard allows the network to send this without their handset ever ringing, so they may genuinely not know.
Status: iOS 26.6, checked 17 August 2026. User Busy is ITU cause 17 and is passed to your iPhone by the network. Apple's page for failed calls, doc 118427, does not use the phrase.
What does User Busy mean on an iPhone?
It means the network could not deliver your call because the far end would not accept another one. It is a status code from the telephone network rather than a message iOS produced. The standard states the code may be generated by the called party or by the network itself, so it does not prove the person is on another call.
Does User Busy mean I have been blocked?
Not by itself. Blocking on an iPhone normally lets the call ring out and drops it into voicemail rather than refusing it at the network. A carrier-level block is a different mechanism and can produce this. The reliable test is to ring the same number from another phone on another network.
Why do my callers hear User Busy when my iPhone is free?
Check Call Forwarding first, then Call Waiting, both at Settings, Apps, Phone. Forwarding to a number that cannot answer refuses your callers while your handset stays quiet. If both are correct, ask your carrier to check the provisioning and any incoming barring on your line.
The Short Version
- Your iPhone did not write those words. They came down the line from the phone network.
- The code is ITU cause 17, and the standard says the network can generate it, not only the person you called.
- So it is not proof that anyone is on the phone, and it is not proof you have been blocked.
- Ring three known-good numbers. One failing is their end. All failing is your line.
- Confirm a single failing number by calling it from a different phone on a different network.
- If callers hear it when your phone is free, look at Call Forwarding, then Call Waiting.
- Nothing on the handset produced this, so erasing, re-seating the SIM and resetting settings all miss.
Where to Next
Two words with no explanation attached, and every instinct says to start pulling the phone apart. That instinct is the expensive one here.
Three test calls tell you whether your own phone belongs in this at all. More often than not, it does not.
If every number you try gives you the same two words, tell me what your carrier said when you rang them, and I will help you work out what to ask for next.
Isaac Smith is the founder and editor of PC Glance, a website that covers computers, laptops, and technology. He is a tech enthusiast and a computer geek who loves to share his insights and help his readers make smart choices when buying tech gadgets or laptops. He is always curious and updated about the latest tech trends.