{"code":"var Component=(()=>{var u=Object.create;var a=Object.defineProperty;var p=Object.getOwnPropertyDescriptor;var g=Object.getOwnPropertyNames;var m=Object.getPrototypeOf,f=Object.prototype.hasOwnProperty;var y=(n,e)=>()=>(e||n((e={exports:{}}).exports,e),e.exports),w=(n,e)=>{for(var i in e)a(n,i,{get:e[i],enumerable:!0})},r=(n,e,i,s)=>{if(e&&typeof e==\"object\"||typeof e==\"function\")for(let o of g(e))!f.call(n,o)&&o!==i&&a(n,o,{get:()=>e[o],enumerable:!(s=p(e,o))||s.enumerable});return n};var b=(n,e,i)=>(i=n!=null?u(m(n)):{},r(e||!n||!n.__esModule?a(i,\"default\",{value:n,enumerable:!0}):i,n)),v=n=>r(a({},\"__esModule\",{value:!0}),n);var h=y((T,l)=>{l.exports=_jsx_runtime});var k={};w(k,{default:()=>d});var t=b(h());function c(n){let e={a:\"a\",code:\"code\",em:\"em\",h2:\"h2\",h3:\"h3\",img:\"img\",li:\"li\",ol:\"ol\",p:\"p\",strong:\"strong\",ul:\"ul\",...n.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsxs)(e.p,{children:[\"Your iPhone is face-down on the desk across the room, your Mac is right in front of you, and the Phone app sits in the Dock doing absolutely nothing while a call you needed goes to voicemail. Or worse: the Mac does ring, you click Accept, and after a two-second pause you get \",(0,t.jsx)(e.strong,{children:\"Call Failed\"}),\" and a caller who now thinks you hung up on them. The standalone Phone app is one of the better additions macOS Tahoe brought to the Mac, and when it does not work it is genuinely maddening because Apple has published almost nothing about why it breaks.\"]}),`\n`,(0,t.jsx)(e.p,{children:(0,t.jsx)(e.img,{alt:\"The Phone app on a Mac running macOS Tahoe\",src:\"/images/blog/phone-app-mac-not-ringing-calls-failing-macos-tahoe-fix-2026/hero.webp\",width:\"1024\",height:\"541\"})}),`\n`,(0,t.jsx)(e.p,{children:\"This guide is a fix ladder. It starts with the cheap, high-yield checks that resolve most cases in under two minutes, and it descends through notification routing, audio routing, network filtering, firewall rules, registration resets, and finally the nuclear options. Every step includes the reason it matters, because the Phone app fails in ways that only make sense once you understand what is actually happening between your iPhone, Apple's servers, and your Mac.\"}),`\n`,(0,t.jsx)(e.p,{children:\"One framing note before we start. Almost nothing in this article is documented by Apple as a troubleshooting step, because Apple's Phone app documentation covers how to use the app, not how to repair it. What follows is a mix of Apple's stated requirements \\u2014 which are documented \\u2014 and community-reported fixes gathered from Apple Support Communities and MacRumors threads where users compared notes. I will tell you which is which at every step. Treat the community-reported items as things that have worked for many people, not as guaranteed solutions.\"}),`\n`,(0,t.jsx)(e.h2,{id:\"key-takeaways\",children:\"Key Takeaways\"}),`\n`,(0,t.jsxs)(e.ul,{children:[`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"The Phone app is a new front end on old plumbing.\"}),\" It shipped with macOS 26 Tahoe, but it rides on iPhone Cellular Calls (Calls on Other Devices), the same Continuity system FaceTime has used for years. Nearly every failure is a Continuity failure, not a Phone app bug.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"The single highest-yield fix is on your iPhone, not your Mac.\"}),\" Settings > Apps > Phone > Calls on Other Devices is widely reported to reset or silently drop devices after iOS updates. Re-check it after every update before you troubleshoot anything else.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Silent ringing is usually a notification or audio-routing problem, not a call problem.\"}),' Notifications, alert style, \"Play sound for notifications,\" Focus modes, and the output device in System Settings > Sound all sit between a successfully delivered call and a sound you can actually hear.']}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:'\"Call Failed\" on answer points at the network, not at registration.'}),\" If the Mac rings, the invitation reached you. A VPN, content filter, custom DNS, or the macOS firewall blocking the media path is the most commonly reported cause of a call that rings but dies on pickup.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Signing out of FaceTime and back in re-registers your Mac with Apple's call routing\"}),\" and is one of the most consistently reported fixes in community threads \\u2014 but do it after the free checks, because it is disruptive and sometimes triggers a re-verification loop.\"]}),`\n`]}),`\n`,(0,t.jsx)(e.h2,{id:\"how-calls-actually-reach-your-mac\",children:\"How Calls Actually Reach Your Mac\"}),`\n`,(0,t.jsx)(e.p,{children:'You cannot troubleshoot this properly without a mental model, because five very different failures all present as \"my Mac does not ring.\"'}),`\n`,(0,t.jsxs)(e.p,{children:[\"Your Mac has no cellular radio. It cannot receive a phone call. What actually happens is that your \",(0,t.jsx)(e.strong,{children:\"iPhone\"}),\" receives the call over cellular (or over Wi-Fi Calling), and then relays an invitation to your other Apple devices. That relay is the Continuity feature Apple calls \",(0,t.jsx)(e.strong,{children:\"iPhone Cellular Calls\"}),\", controlled on the iPhone by the \",(0,t.jsx)(e.strong,{children:\"Calls on Other Devices\"}),\" setting. The Phone app in Tahoe is a dedicated interface for that relay, plus call history and contacts sync \\u2014 but the relay itself predates it by a decade and is shared with FaceTime.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"There are three distinct stages, and each one fails differently.\"}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Stage one is registration.\"}),` Your Mac tells Apple's servers \"I am a valid endpoint for this Apple Account, and I am willing to receive relayed calls.\" This registration is tied to your FaceTime sign-in, not to the Phone app. If registration is broken, your Mac does not appear in the device list on your iPhone, or it appears but never receives anything. Symptoms: total silence, no missed-call entry in the Phone app afterward, and often the Mac missing from the iPhone's device list.`]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Stage two is the invitation.\"}),\" When a call arrives, your iPhone (via Apple's push infrastructure) signals your Mac that a call is incoming. This is a small, lightweight signal. If it arrives, your Mac knows about the call. Whether you \",(0,t.jsx)(e.em,{children:\"hear\"}),\" about it is a separate question entirely, handled by macOS notifications and audio. Symptoms of an invitation that arrived but was never surfaced: the call shows up in the Phone app's recents as a missed call even though you never heard a thing. That is a crucial diagnostic \\u2014 a silent missed call that still logs means stages one and two worked, and your problem is notifications or audio.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Stage three is the media path.\"}),` You click Accept, and now actual audio has to flow. This is where the call needs a working two-way path between your Mac and either your iPhone or Apple's relay servers, depending on network conditions. This stage is far more demanding than the invitation, which is why \"rings but fails on answer\" is such a distinctive symptom. The invitation is a postcard; the media path is a phone line. A VPN, a firewall, or a filtering DNS resolver can happily let the postcard through and then strangle the phone line.`]}),`\n`,(0,t.jsxs)(e.p,{children:[\"Once you internalize that split, the ladder below stops looking like a random list of toggles. Each step targets one specific stage. If you want the broader picture of how these subsystems interact, our \",(0,t.jsx)(e.a,{href:\"/blog/macos-tahoe-continuity-features-complete-troubleshooting-guide-2025\",children:\"complete Continuity troubleshooting guide for macOS Tahoe\"}),\" covers the shared foundations that Handoff, Universal Clipboard, and call relay all sit on.\"]}),`\n`,(0,t.jsx)(e.h3,{id:\"quick-triage\",children:\"Quick triage\"}),`\n`,(0,t.jsx)(e.p,{children:\"Find your symptom below and jump to the step it points at. Working the ladder from the top is still the safest approach, but if you are short on time, start where your symptom lands.\"}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"No ring at all, and no missed-call entry in the Phone app afterward.\"}),`\nStage one or two is broken. Start at Step 1 (requirements) and pay very close attention to Step 2 (the iPhone toggle). This is the most common presentation and it is usually the device list on the iPhone. If those check out, go to Step 7 (FaceTime re-registration).`]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsxs)(e.strong,{children:[\"No ring at all, but the call \",(0,t.jsx)(e.em,{children:\"does\"}),\" show up as missed in the Phone app's recents.\"]}),`\nStages one and two are fine \\u2014 the invitation reached your Mac. Your problem is presentation. Go straight to Step 3 (notifications) and Step 4 (sound routing). Also check Step 8 (Voice Control), which is a community-reported ringer killer.`]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"It rings, you click Accept, and you get Call Failed or immediate silence.\"}),`\nStage three. Go to Step 5 (VPN and network filters) first, then Step 6 (firewall). This split is diagnostic gold: registration and invitation are both proven working, so stop re-checking them.`]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Outgoing calls work but incoming calls never arrive.\"}),`\nSee the dedicated section on that split further down. This almost always means your Mac can reach out but is not registered as a valid `,(0,t.jsx)(e.em,{children:\"destination\"}),\", which narrows things considerably.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"The Phone app will not open, shows no account, or shows an empty state where your call history should be.\"}),`\nRegistration or sign-in. Go to Step 7, then to the Apple Account checks in Step 10.`]}),`\n`,(0,t.jsx)(e.h2,{id:\"step-1-the-requirements-nobody-checks\",children:\"Step 1: The Requirements Nobody Checks\"}),`\n`,(0,t.jsx)(e.p,{children:`These are Apple's documented requirements for iPhone Cellular Calls, and they are boring enough that almost everyone assumes they are satisfied without looking. Check them anyway. A meaningful share of the \"Phone app is broken\" threads resolve here.`}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Both devices signed into the same Apple Account.\"}),\" Not just iCloud \\u2014 specifically the account used for FaceTime. On the Mac, open \",(0,t.jsx)(e.strong,{children:\"FaceTime > Settings > General\"}),\" and read the account shown. On the iPhone, open \",(0,t.jsx)(e.strong,{children:\"Settings > Apps > FaceTime\"}),\" and compare. They must be identical. If you have ever used a separate Apple Account for purchases versus iCloud, this is exactly the kind of setup that quietly breaks call relay.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Both devices on the same Wi-Fi network.\"}),\" This one gets dismissed as legacy advice, and it should not be. Apple documents same-network as a requirement for iPhone Cellular Calls, and the reason is architectural: the relay path is designed to hand the call between devices on a common local network. There is a genuine exception, which is Wi-Fi Calling \\u2014 if you have Wi-Fi Calling enabled with your carrier and configured to allow calls on other devices, your Mac can receive calls even when the iPhone is elsewhere. Without Wi-Fi Calling, same network is not a suggestion.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[\"The practical trap here is not being on a \",(0,t.jsx)(e.em,{children:\"different\"}),\" network but being on a technically different one that looks the same. A 2.4 GHz and 5 GHz SSID split, a guest network, a mesh system putting the two devices on different subnets, or a Mac connected by Ethernet while the iPhone is on Wi-Fi will all defeat this. On the Mac, hold Option and click the Wi-Fi menu bar icon to see the exact network and IP address; compare the first three octets of the IP against what the iPhone reports under \",(0,t.jsx)(e.strong,{children:\"Settings > Wi-Fi > (i)\"}),\". If those differ, your devices are not on the same network in the way that matters, even if the network name is identical.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Bluetooth on, on both devices.\"}),\" Bluetooth is what several Continuity features use for proximity discovery, and while Apple's call-specific documentation emphasizes Wi-Fi, keeping Bluetooth on costs you nothing and removes a variable. If your Mac's Bluetooth stack is itself unstable \\u2014 devices refusing to pair, connections dropping under load \\u2014 that is worth fixing on its own terms before you blame the Phone app, because an unreliable Bluetooth stack will also make your audio output flaky in exactly the way described in Step 4.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Handoff enabled on both.\"}),\" On the Mac: \",(0,t.jsx)(e.strong,{children:\"System Settings > General > AirDrop & Handoff\"}),', with \"Allow Handoff between this Mac and your iCloud devices\" turned on. On the iPhone: ',(0,t.jsx)(e.strong,{children:\"Settings > General > AirPlay & Continuity > Handoff\"}),\". Handoff is the umbrella switch for a family of Continuity behaviors, and turning it off can take call relay with it. If Handoff itself is misbehaving on your setup, the same underlying plumbing is what breaks \",(0,t.jsx)(e.a,{href:\"/blog/mac-wont-connect-iphone-personal-hotspot-instant-hotspot-macos-tahoe-fix-2026\",children:\"Instant Hotspot connections between Mac and iPhone\"}),\", and fixing it there often fixes it here.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Physical proximity, within reason.\"}),\" Same room, or at least same floor. The relay is not meant to work from another building over the internet unless Wi-Fi Calling is carrying that load.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"Run all five. If any one of them was off, turn it on, restart both devices, and test before going further \\u2014 you may be done.\"}),`\n`,(0,t.jsx)(e.h2,{id:\"step-2-the-iphone-toggle-that-updates-silently-flip\",children:\"Step 2: The iPhone Toggle That Updates Silently Flip\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"If you only do one thing from this article, do this one. Community threads on Apple Support Communities and MacRumors converge on this setting more than any other, and specifically on the observation that \",(0,t.jsx)(e.strong,{children:\"iOS updates frequently reset it or drop devices from its list\"}),\".\"]}),`\n`,(0,t.jsxs)(e.p,{children:[\"On your iPhone, go to \",(0,t.jsx)(e.strong,{children:\"Settings > Apps > Phone > Calls on Other Devices\"}),\".\"]}),`\n`,(0,t.jsx)(e.p,{children:\"Two things must be true here, and people routinely check only the first:\"}),`\n`,(0,t.jsxs)(e.ol,{children:[`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Allow Calls on Other Devices\"}),\" must be on.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Your specific Mac must be listed and enabled\"}),\" in the device list below it.\"]}),`\n`]}),`\n`,(0,t.jsx)(e.p,{children:\"That second point is the whole game. The master toggle can be on while your MacBook is either absent from the list or present with its individual switch off. Users report both after updating iOS: the device list rebuilds and the Mac either does not come back or comes back disabled. If your Mac is not in the list at all, that is a registration problem \\u2014 go to Step 7 to re-register it, then come back here.\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"While you are on the iPhone, also check \",(0,t.jsx)(e.strong,{children:\"Settings > Apps > FaceTime > Calls from iPhone\"}),\". This is the FaceTime-side switch for the same relay, and it should be on. Historically these two settings have been linked in some iOS versions and independent in others; check both regardless.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[\"The behavioral takeaway is more valuable than the fix itself: \",(0,t.jsx)(e.strong,{children:\"after every iOS update, before you assume the Phone app is broken, open this screen.\"}),\" It takes ten seconds. It is reported to have silently changed often enough that treating it as a post-update ritual will save you the entire rest of this article most of the time. This is a community-observed pattern, not an Apple-acknowledged bug, so I cannot tell you which iOS versions do it or why \\u2014 only that it is reported consistently enough to be worth the habit.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"If the toggle was already correct, toggle it off, wait about thirty seconds, and toggle it back on anyway. Several reports describe the setting displaying as enabled while the underlying registration had gone stale; forcing the state change rewrites it.\"}),`\n`,(0,t.jsx)(e.h2,{id:\"step-3-notification-settings-on-the-mac\",children:\"Step 3: Notification Settings on the Mac\"}),`\n`,(0,t.jsx)(e.p,{children:\"If your calls log as missed but never made a sound, stop looking at the Phone app. The call arrived. macOS simply did not tell you about it.\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"Open \",(0,t.jsx)(e.strong,{children:\"System Settings > Notifications\"}),\", scroll to \",(0,t.jsx)(e.strong,{children:\"Phone\"}),\", and check every one of these:\"]}),`\n`,(0,t.jsxs)(e.ul,{children:[`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Allow notifications\"}),\" \\u2014 on. Obvious, but this gets switched off by people who were annoyed by something else entirely.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Alert style\"}),\" \\u2014 set to \",(0,t.jsx)(e.strong,{children:\"Alerts\"}),\", not \",(0,t.jsx)(e.strong,{children:\"Banners\"}),\" and definitely not \",(0,t.jsx)(e.strong,{children:\"None\"}),\". Banners disappear on their own after a few seconds, which for a ringing phone call is close to useless. Alerts persist until dismissed.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Play sound for notifications\"}),' \\u2014 on. This is the direct ringer switch. With it off, you get a visual notification and total silence, which is exactly the \"logged but never rang\" symptom.']}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Show on Lock Screen\"}),\" and \",(0,t.jsx)(e.strong,{children:\"Show in Notification Center\"}),\" \\u2014 on, so you can see what you missed.\"]}),`\n`]}),`\n`,(0,t.jsxs)(e.p,{children:[\"Now repeat all of that for \",(0,t.jsx)(e.strong,{children:\"FaceTime\"}),\" in the same list. The two apps share the underlying call system and users report the alert surfacing under either one depending on the call type.\"]}),`\n`,(0,t.jsx)(e.h3,{id:\"the-setting-almost-nobody-finds\",children:\"The setting almost nobody finds\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"Still in \",(0,t.jsx)(e.strong,{children:\"System Settings > Notifications\"}),\", scroll to the very bottom of the main pane, below the app list. There is a section of global notification options, and one of them is \",(0,t.jsx)(e.strong,{children:\"Allow notifications when mirroring or sharing the display\"}),\".\"]}),`\n`,(0,t.jsx)(e.p,{children:\"If that is off \\u2014 and it is off by default for many users \\u2014 then any time you are mirroring to an external display, screen sharing, presenting, or in some cases simply connected to certain external monitors, macOS suppresses notifications entirely. Including your incoming calls. People spend hours on this one because the symptom is maddeningly conditional: calls ring perfectly at the coffee shop and never ring at the desk with the big monitor. If your failures correlate with your desk setup, this is almost certainly it.\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"While you are in that bottom section, also check \",(0,t.jsx)(e.strong,{children:\"Allow notifications when the screen is asleep\"}),\" and \",(0,t.jsx)(e.strong,{children:\"Allow notifications when the screen is locked\"}),\", depending on how you use the machine.\"]}),`\n`,(0,t.jsx)(e.h3,{id:\"focus-modes-do-not-disturb-and-focus-sharing\",children:\"Focus modes, Do Not Disturb, and Focus sharing\"}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"System Settings > Focus.\"}),\" Check whether any Focus is currently active, and check what each of your Focus modes does to the Phone app. A Focus that allows calls only from Favorites will silence everyone else, which looks identical to a broken ringer if you happen to test with a number that is not a favorite.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[\"The compounding problem is \",(0,t.jsx)(e.strong,{children:\"Focus sharing across devices\"}),'. If \"Share across devices\" is on, a Focus you enabled on your iPhone last night is also active on your Mac right now, and you may have no memory of turning anything on at the Mac. Look at the top of Control Center on the Mac for an active Focus indicator before you conclude anything.']}),`\n`,(0,t.jsxs)(e.p,{children:[\"Also check \",(0,t.jsx)(e.strong,{children:\"System Settings > Screen Time > Communication Limits\"}),\". Communication limits restrict who can reach you during downtime, and they apply to phone calls. If you set these up for a child's account or set them for yourself during a focus experiment and forgot, they will quietly filter incoming calls.\"]}),`\n`,(0,t.jsx)(e.p,{children:(0,t.jsx)(e.img,{alt:\"macOS Tahoe System Settings showing notification options for the Phone app\",src:\"/images/blog/phone-app-mac-not-ringing-calls-failing-macos-tahoe-fix-2026/content-1.webp\",width:\"1024\",height:\"541\"})}),`\n`,(0,t.jsx)(e.h2,{id:\"step-4-sound-routing--the-ring-is-playing-just-not-where-you-are\",children:\"Step 4: Sound Routing \\u2014 The Ring Is Playing, Just Not Where You Are\"}),`\n`,(0,t.jsx)(e.p,{children:\"This is the sneakiest category of failure because absolutely everything is working correctly. The call arrives, the notification fires, the ringtone plays \\u2014 into a device you cannot hear.\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"Open \",(0,t.jsx)(e.strong,{children:\"System Settings > Sound\"}),\" and check three things.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"The output device.\"}),\" Whatever is selected here receives your system sounds, including the ringer. If it is set to a Bluetooth speaker in another room, to AirPods that are in their case, or to a display's built-in speakers, that is where the ring is going. The display case is especially common: many external monitors have speakers that macOS will happily select as the default output, and many of those speakers are either muted at the hardware level, powered down when the monitor is in a low-power state, or simply inaudible. You will see the audio meter move and hear nothing.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"The alert volume.\"}),\" Below the output device there is a separate \",(0,t.jsx)(e.strong,{children:\"Alert volume\"}),\" slider. It is \",(0,t.jsx)(e.em,{children:\"not\"}),\" the same as your main output volume, and it can be at or near zero while music plays at full volume. Because alert volume scales relative to output volume, an alert slider at 10% with output at 30% produces something close to inaudible. Set alert volume high while you are testing.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:'\"Play sound effects through\"'}),\" determines which device alerts specifically use, and it can differ from your main output device. If this is pointed at something disconnected or asleep, alerts go nowhere.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"Bluetooth output adds its own wrinkle. Many Bluetooth speakers and headphones sleep aggressively to save battery, and the first fraction of a second of audio after they wake is swallowed while the link re-establishes. On a short ring that can mean you hear nothing at all, or catch the tail end of the second ring. If your ringer only fails when Bluetooth audio is connected, that is the mechanism. Test with output set to the Mac's built-in speakers to confirm before chasing anything else.\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"If your Mac's audio behavior is broadly weird \\u2014 devices disappearing, output switching on its own, volume not sticking \\u2014 that is a separate problem worth fixing first, and our \",(0,t.jsx)(e.a,{href:\"/blog/macos-tahoe-audio-complete-guide-2025\",children:\"complete macOS Tahoe audio guide\"}),\" covers the device-selection and Core Audio issues in depth.\"]}),`\n`,(0,t.jsx)(e.h2,{id:\"step-5-vpns-content-filters-and-custom-dns\",children:\"Step 5: VPNs, Content Filters, and Custom DNS\"}),`\n`,(0,t.jsx)(e.p,{children:'Now we move from stage two to stage three, which is where \"rings but fails\" lives.'}),`\n`,(0,t.jsxs)(e.p,{children:[\"The most consistently reported network-side fix in community threads is simply \",(0,t.jsx)(e.strong,{children:\"disconnecting the VPN\"}),\". Users describe calls that ring normally on the Mac, then fail the moment they answer, with the call dropping to \",(0,t.jsx)(e.strong,{children:\"Call Failed\"}),\" \\u2014 and the problem disappearing entirely with the VPN off.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"Here is the mechanism, and I want to be explicit that this is a general explanation of how this class of connectivity works, not a statement from Apple about the Phone app's internals. Real-time voice needs a low-latency, two-way media path. Establishing that path typically requires the endpoints to discover how they are reachable through whatever NAT sits in front of them, and to fall back to a relay server if a direct path is not possible. A VPN changes your apparent network location, often routes traffic through a distant exit node, and frequently blocks or mangles the specific traversal traffic that this negotiation depends on. The lightweight invitation that makes your Mac ring is much easier to deliver than the media path that has to follow it. That asymmetry is exactly why the call rings and then fails.\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"Some VPN clients also install a system-level content filter or a network extension that inspects traffic. Those can interfere even when the VPN tunnel itself is disconnected, because the extension remains loaded. Check \",(0,t.jsx)(e.strong,{children:\"System Settings > General > Login Items & Extensions > Network Extensions\"}),\" to see what is installed, and consider fully quitting the VPN client rather than just toggling the connection.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Content filters and parental-control tools\"}),\" are the same category. Anything that intercepts DNS or inspects traffic \\u2014 enterprise security agents, ad-blocking proxies, family-safety tools \\u2014 belongs on the suspect list.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Custom DNS\"}),\" deserves its own mention. If you have set a custom DNS resolver in \",(0,t.jsx)(e.strong,{children:\"System Settings > Network > (your interface) > Details > DNS\"}),\", or if you are using encrypted DNS via a configuration profile, and that resolver blocks or misroutes Apple's service domains, call setup can fail while ordinary browsing looks perfectly fine. Test by temporarily reverting to your router's DNS: remove your custom entries so the field falls back to DHCP-provided values, then test a call. If that fixes it, your resolver was filtering something it should not.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"The test procedure for this whole step is simple. Disconnect the VPN, quit its client entirely, revert DNS to automatic, and place a test call. If it works, reintroduce one item at a time until it breaks again. That tells you which product to configure or replace, rather than leaving you permanently without a VPN.\"}),`\n`,(0,t.jsx)(e.h2,{id:\"step-6-the-macos-firewall\",children:\"Step 6: The macOS Firewall\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"The macOS application firewall blocks \",(0,t.jsx)(e.em,{children:\"incoming\"}),\" connections. Calls are, definitionally, incoming. This is a natural suspect and it is worth ruling in or out precisely.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[\"Go to \",(0,t.jsx)(e.strong,{children:\"System Settings > Network > Firewall\"}),\". If it is off, this step is not your problem \\u2014 move on. If it is on, here is the correct procedure:\"]}),`\n`,(0,t.jsxs)(e.ol,{children:[`\n`,(0,t.jsxs)(e.li,{children:[\"Turn the firewall \",(0,t.jsx)(e.strong,{children:\"off temporarily\"}),\".\"]}),`\n`,(0,t.jsx)(e.li,{children:\"Place a test call to your own number from another phone.\"}),`\n`,(0,t.jsx)(e.li,{children:\"If the call now works, you have confirmed the firewall was the cause.\"}),`\n`,(0,t.jsx)(e.li,{children:(0,t.jsx)(e.strong,{children:\"Turn the firewall back on.\"})}),`\n`,(0,t.jsxs)(e.li,{children:[\"Click \",(0,t.jsx)(e.strong,{children:\"Options\"}),\", and make sure \",(0,t.jsx)(e.strong,{children:\"Block all incoming connections\"}),\" is \",(0,t.jsx)(e.em,{children:\"not\"}),\" enabled \\u2014 that setting blocks essentially everything, including the services calls depend on.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[\"In the same Options sheet, ensure \",(0,t.jsx)(e.strong,{children:\"FaceTime\"}),\" and \",(0,t.jsx)(e.strong,{children:\"Phone\"}),\" are set to \",(0,t.jsx)(e.strong,{children:\"Allow incoming connections\"}),\". Add them with the \",(0,t.jsx)(e.strong,{children:\"+\"}),\" button if they are not listed; they live in \",(0,t.jsx)(e.code,{children:\"/System/Applications/\"}),\".\"]}),`\n`,(0,t.jsxs)(e.li,{children:[\"Leave \",(0,t.jsx)(e.strong,{children:\"Automatically allow built-in software to receive incoming connections\"}),\" enabled.\"]}),`\n`]}),`\n`,(0,t.jsxs)(e.p,{children:[\"I want to be direct about this: \",(0,t.jsx)(e.strong,{children:\"leaving the firewall off is not the fix.\"}),\" Turning it off is a diagnostic, and it should be on for the entire time you are not actively testing. If step six does not stick \\u2014 if you allow the apps and calls still fail with the firewall on \\u2014 then you have learned something useful and the right next move is Step 7 and then Step 10, not permanently disabling a security control.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"One more note: if you use a third-party firewall such as an outbound-connection blocker, it is a much more likely culprit than the built-in one, and it needs to be checked the same way. Those tools block outgoing connections too, which can break the registration in stage one as well as the media path in stage three.\"}),`\n`,(0,t.jsx)(e.h2,{id:\"step-7-sign-out-of-facetime-and-sign-back-in\",children:\"Step 7: Sign Out of FaceTime and Sign Back In\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"This is the single most consistently reported \",(0,t.jsx)(e.em,{children:\"fix\"}),\" in community threads, as opposed to Step 2 which is the most consistently reported \",(0,t.jsx)(e.em,{children:\"cause\"}),\". It works because it forces your Mac to tear down and rebuild its registration with Apple's call routing \\u2014 stage one, in the model above. A stale or partially broken registration is invisible from the user interface; everything looks signed in and correct while Apple's side has your Mac in a bad state.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"The sequence matters. Do it in this order:\"}),`\n`,(0,t.jsxs)(e.ol,{children:[`\n`,(0,t.jsxs)(e.li,{children:[\"Open \",(0,t.jsx)(e.strong,{children:\"FaceTime\"}),\". From the menu bar, choose \",(0,t.jsx)(e.strong,{children:\"FaceTime > Settings > General\"}),\".\"]}),`\n`,(0,t.jsxs)(e.li,{children:[\"Click \",(0,t.jsx)(e.strong,{children:\"Sign Out\"}),\". Confirm.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Quit FaceTime and quit the Phone app\"}),\" completely (Command-Q, not just closing the window).\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Restart the Mac.\"}),\" Do not skip this. The restart is what clears the in-memory state that would otherwise be reused when you sign back in, and community reports consistently describe sign-out-without-restart as not working.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[\"After the restart, open FaceTime and \",(0,t.jsx)(e.strong,{children:\"sign back in\"}),\" with your Apple Account.\"]}),`\n`,(0,t.jsx)(e.li,{children:\"Wait. Registration is not instantaneous \\u2014 give it a few minutes and do not immediately start toggling other things.\"}),`\n`,(0,t.jsxs)(e.li,{children:[\"Go back to your \",(0,t.jsx)(e.strong,{children:\"iPhone > Settings > Apps > Phone > Calls on Other Devices\"}),\" and confirm your Mac now appears in the device list and is enabled. Newly re-registered devices frequently show up disabled.\"]}),`\n`]}),`\n`,(0,t.jsxs)(e.p,{children:[\"That last point is why Step 2 and Step 7 belong together. Re-registering the Mac often makes it reappear in the iPhone's device list as a \",(0,t.jsx)(e.em,{children:\"new\"}),\" entry, defaulted to off. If you re-register and never check the iPhone, you will conclude the fix did not work when it actually did half the job.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[\"If signing back in gets stuck \\u2014 spinning indefinitely, or repeatedly asking for verification \\u2014 check that your Apple Account is healthy on the Mac generally (\",(0,t.jsx)(e.strong,{children:\"System Settings > [your name]\"}),\"), that you have a working internet connection without the filters from Step 5, and that your system clock is set automatically. An incorrect system clock breaks certificate validation and will block re-registration with symptoms that look nothing like a clock problem.\"]}),`\n`,(0,t.jsx)(e.p,{children:(0,t.jsx)(e.img,{alt:\"Two-device diagram showing an incoming call relayed from an iPhone to a Mac over Wi-Fi\",src:\"/images/blog/phone-app-mac-not-ringing-calls-failing-macos-tahoe-fix-2026/content-2.webp\",width:\"1024\",height:\"541\"})}),`\n`,(0,t.jsx)(e.h2,{id:\"step-8-the-voice-control-conflict\",children:\"Step 8: The Voice Control Conflict\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"This one is odd enough that I want to flag its status clearly: \",(0,t.jsx)(e.strong,{children:\"this is community-reported, not Apple-documented, and there is no official explanation for it.\"}),\" Multiple users in Tahoe Phone app threads report that having \",(0,t.jsx)(e.strong,{children:\"Voice Control\"}),\" active suppresses the ringer \\u2014 calls arrive, they log correctly, and no sound plays. Turning Voice Control off restores ringing.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[\"Check \",(0,t.jsx)(e.strong,{children:\"System Settings > Accessibility > Voice Control\"}),\". If it is on and you are not deliberately using it, turn it off and test.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"The plausible mechanism is that Voice Control takes exclusive control of the audio input path and can affect how the system handles audio sessions around incoming calls, but I cannot verify that and neither has Apple. What I can say is that it costs you thirty seconds to check, and if you turned Voice Control on once to try it and forgot about it, this could be your entire problem.\"}),`\n`,(0,t.jsx)(e.p,{children:\"The broader lesson is worth generalizing: any accessibility feature or third-party utility that grabs the audio session, remaps system sounds, or sits in the audio chain \\u2014 virtual audio devices, audio routing utilities, streaming and podcasting software, meeting apps that install audio drivers \\u2014 is a candidate. If you have any of those installed, quit them and test.\"}),`\n`,(0,t.jsx)(e.h2,{id:\"step-9-default-call-handler-conflicts\",children:\"Step 9: Default Call Handler Conflicts\"}),`\n`,(0,t.jsx)(e.p,{children:\"macOS has a notion of a default application for handling calls, in the same way it has a default browser and default mail client. Apps like Microsoft Teams, Zoom, Skype, and various softphone and VoIP clients will register themselves as the system call handler \\u2014 sometimes during installation without asking, sometimes via a prompt you clicked through months ago.\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"When another app owns that role, \",(0,t.jsx)(e.code,{children:\"tel:\"}),\" links from Contacts, Safari, and Spotlight open in that app instead of Phone, and the overall call experience gets confusing enough that people report it as the Phone app being broken. To be precise about what this does and does not do: a hijacked default handler changes where \",(0,t.jsx)(e.em,{children:\"outgoing\"}),' calls originate and where clicked phone numbers go. It is not usually the cause of a Mac that does not ring for incoming calls. But it is absolutely the cause of \"I click a number and nothing useful happens,\" and it is worth resetting while you are here.']}),`\n`,(0,t.jsxs)(e.p,{children:[\"To check and change it, open \",(0,t.jsx)(e.strong,{children:\"FaceTime > Settings > General\"}),\" and look for the \",(0,t.jsx)(e.strong,{children:\"Default for calls\"}),\" dropdown. Set it to \",(0,t.jsx)(e.strong,{children:\"FaceTime\"}),\" (which routes through the system call stack that Phone uses). If a third-party app is selected there, that is your answer.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"Some apps will re-claim the role every time they launch, or on their next update. If you find yourself resetting this repeatedly, look inside the offending app's own settings \\u2014 Teams and Zoom both have a preference controlling whether they register as the system phone handler, and turning it off at the source is the only durable fix.\"}),`\n`,(0,t.jsx)(e.h2,{id:\"when-outgoing-calls-work-but-incoming-calls-do-not\",children:\"When Outgoing Calls Work but Incoming Calls Do Not\"}),`\n`,(0,t.jsx)(e.p,{children:\"This split is diagnostically valuable and deserves its own treatment, because it eliminates a huge amount of the search space.\"}),`\n`,(0,t.jsx)(e.p,{children:\"If you can place a call from your Mac and it connects and sounds fine, then the following are all proven working: your Apple Account sign-in, the network path between your Mac and Apple's servers, your microphone and speaker configuration for calls, and the basic relay to your iPhone. Outgoing calls from the Mac are relayed through your iPhone just like incoming ones, so a successful outgoing call proves the pipe exists in at least one direction.\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"What that leaves is the \",(0,t.jsx)(e.em,{children:\"destination\"}),\" side: your Mac being registered as a valid target for incoming calls, and the invitation being surfaced when it arrives.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"Work these in order:\"}),`\n`,(0,t.jsxs)(e.ol,{children:[`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"The iPhone device list (Step 2).\"}),\" Your Mac being missing or disabled there breaks incoming while leaving outgoing intact, because outgoing calls are initiated by the Mac rather than routed to it. This is by far the most likely cause of this specific split.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"Notification suppression (Step 3).\"}),\" If calls are logging as missed, this is your answer. Check the Phone app's recents immediately after a failed incoming call \\u2014 the presence or absence of that entry decides between causes one and two, and it takes five seconds.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"FaceTime re-registration (Step 7).\"}),\" A partially valid registration can support outgoing while failing incoming.\"]}),`\n`,(0,t.jsxs)(e.li,{children:[(0,t.jsx)(e.strong,{children:\"The firewall (Step 6).\"}),\" The macOS application firewall blocks \",(0,t.jsx)(e.em,{children:\"incoming\"}),\" connections specifically. An outgoing-works/incoming-fails pattern is exactly the fingerprint you would expect from a firewall issue.\"]}),`\n`]}),`\n`,(0,t.jsxs)(e.p,{children:[\"Note that this pattern rules \",(0,t.jsx)(e.em,{children:\"out\"}),\" most of Step 5 as a cause. If a VPN were mangling the media path, outgoing calls would fail too. VPNs remain a suspect only in the narrower case where the Mac rings and then fails on answer.\"]}),`\n`,(0,t.jsx)(e.h2,{id:\"carrier-side-factors-and-wi-fi-calling\",children:\"Carrier-Side Factors and Wi-Fi Calling\"}),`\n`,(0,t.jsx)(e.p,{children:\"Everything above assumes your iPhone is receiving calls normally and the only question is whether they reach the Mac. Sometimes the carrier layer is the constraint.\"}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Wi-Fi Calling is what lets your Mac receive calls when your iPhone is not on the same network.\"}),\" Without it, Apple's requirement of same-Wi-Fi applies strictly. With it, your Mac can be at home while your iPhone is in your bag at the office, and calls still arrive \\u2014 but only if Wi-Fi Calling is both enabled with your carrier and configured to permit calls on other devices. On the iPhone, that is \",(0,t.jsx)(e.strong,{children:\"Settings > Apps > Phone > Wi-Fi Calling\"}),\", where you will find both \",(0,t.jsx)(e.strong,{children:\"Wi-Fi Calling on This iPhone\"}),\" and, when supported, \",(0,t.jsx)(e.strong,{children:\"Add Wi-Fi Calling For Other Devices\"}),\". Both matter.\"]}),`\n`,(0,t.jsx)(e.p,{children:\"Wi-Fi Calling availability is a carrier decision, not an Apple one. Not every carrier supports it, not every plan includes it, and support for calls on other devices is a separate capability from basic Wi-Fi Calling on the handset. Some carriers require account-level provisioning before the option appears at all. I am deliberately not naming carriers or describing specific policies here, because those change constantly and vary by region and plan \\u2014 check with your carrier directly rather than trusting any article, including this one, about what your specific plan supports.\"}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Dual-SIM and eSIM configurations behave differently\"}),\", and this is under-discussed. When your iPhone has two active lines, the relay has to decide which line's calls go to which devices, and users with dual-SIM setups report inconsistent behavior on secondary lines. If you have two lines active, test with your primary line first to establish a baseline, then test the secondary. If only the secondary fails, the problem is line-specific rather than device-specific and no amount of Mac-side troubleshooting will help.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Recent SIM changes matter too.\"}),\" After a SIM swap, an eSIM transfer to a new iPhone, or a carrier port, your number needs to re-register against your Apple Account before call relay reliably works. This usually resolves itself within a few hours but occasionally needs a nudge: toggle iMessage and FaceTime off and back on on the iPhone, and confirm your phone number appears as a checked address in FaceTime's settings on both devices. The same registration mechanism underlies \",(0,t.jsx)(e.a,{href:\"/blog/imessage-not-syncing-between-mac-and-iphone-macos-tahoe-fix-2026\",children:\"iMessage syncing between Mac and iPhone\"}),\", which is why the two problems so often appear together after a SIM change.\"]}),`\n`,(0,t.jsx)(e.h2,{id:\"step-10-deeper-resets-in-order\",children:\"Step 10: Deeper Resets, in Order\"}),`\n`,(0,t.jsx)(e.p,{children:\"If you are here, the targeted fixes did not land. Work these in order \\u2014 they are sorted by increasing disruption, and there is no reason to jump to the end.\"}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Restart both devices.\"}),\" Genuinely both, and the iPhone too, not just the Mac. Continuity state lives on both ends and a one-sided restart leaves half the stale state in place. Shut down rather than just restarting the Mac if you want to be thorough.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Toggle Wi-Fi and Bluetooth off and on, on both devices.\"}),\" On the Mac, use the menu bar or Control Center. Do it on both devices within the same minute so that discovery re-runs cleanly on both ends. Cheap, occasionally effective.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Confirm you are on a current macOS build.\"}),\" Continuity regressions get fixed in point releases, and running an older 26.x build against a current iOS version is a real source of mismatch. The current stable release is macOS Tahoe 26.6, and if you are behind, our \",(0,t.jsx)(e.a,{href:\"/blog/macos-tahoe-26-6-released-complete-update-guide-security-fixes-2026\",children:\"macOS Tahoe 26.6 update guide\"}),\" covers what changed and how to update cleanly. If you are on a macOS 27 beta, understand that Continuity between a beta Mac and a release iPhone is a well-known source of instability, and the correct move may be to stop troubleshooting and wait for the next beta.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Sign out of your Apple Account on the Mac entirely and sign back in.\"}),\" This is a bigger hammer than the FaceTime-only sign-out in Step 7, and correspondingly more disruptive \\u2014 it affects iCloud Drive, Photos, Keychain, and everything else. Go to \",(0,t.jsx)(e.strong,{children:\"System Settings > [your name] > Sign Out\"}),\". Before you do: make sure you know your Apple Account password and have access to a trusted device or phone number for two-factor verification, and let iCloud Drive finish syncing so you do not lose local-only changes. Restart, sign back in, wait for iCloud to settle, then test.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Reset network settings on the iPhone.\"}),\" \",(0,t.jsx)(e.strong,{children:\"Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings.\"}),\" This clears saved Wi-Fi networks and passwords, VPN configurations, and cellular settings on the iPhone. You will need to rejoin Wi-Fi networks afterward, so have your passwords available. It is disruptive but not destructive to data. There is no exact equivalent on the Mac, which is why this step is iPhone-side.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Create a fresh macOS user account.\"}),\" This is the most useful diagnostic on the list and almost nobody does it. Go to \",(0,t.jsx)(e.strong,{children:\"System Settings > Users & Groups > Add Account\"}),\", create a new administrator account, log into it, sign into FaceTime with the same Apple Account, and test an incoming call. If calls work in the new account, your problem is per-user configuration \\u2014 a preference file, a login item, an audio utility, a notification setting \\u2014 and not a system-level or account-level problem. That instantly rules out most of the scary explanations and tells you the fix lives in your user library. If calls fail in the new account too, the problem is system-wide or account-wide, and the remaining candidates are your Apple Account, your network, or the macOS install itself.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Contact Apple Support.\"}),\" If the fresh-user test fails and you have worked the ladder, this is a legitimate escalation. Bring: your exact macOS version and build (\",(0,t.jsx)(e.strong,{children:\"Apple menu > About This Mac\"}),\"), your exact iOS version, the specific symptom in the triage vocabulary above (no ring versus rings-then-fails versus outgoing-works-only), whether the call logs as missed, whether a fresh user account reproduces it, and a list of what you have already tried. That last item matters more than people expect \\u2014 it moves the conversation past the first-tier script quickly.\"]}),`\n`,(0,t.jsx)(e.h2,{id:\"troubleshooting-common-issues\",children:\"Troubleshooting Common Issues\"}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Problem: The Mac rings, but the call connects with no audio in either direction.\"}),`\n`,(0,t.jsx)(e.strong,{children:\"Solution:\"}),\" This is stage three succeeding at connection and failing at media. Check the input and output devices in \",(0,t.jsx)(e.strong,{children:\"System Settings > Sound\"}),\" while the call is active, since macOS can select a different device for calls than for general playback. Then check \",(0,t.jsx)(e.strong,{children:\"System Settings > Privacy & Security > Microphone\"}),\" and confirm the Phone app has permission. If a virtual audio device or meeting app is installed, quit it and test again.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Problem: My Mac shows up in the iPhone's device list, but the switch turns itself back off.\"}),`\n`,(0,t.jsx)(e.strong,{children:\"Solution:\"}),\" A device entry that will not stay enabled usually means the registration behind it is stale or duplicated. Do the full FaceTime sign-out, restart, sign-in sequence in Step 7, then check the list again. If you see two entries for the same Mac, that confirms duplicate registrations \\u2014 the sign-out cycle is what clears the orphan.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Problem: Calls ring on my Mac but with a several-second delay, and by the time I answer the caller has hung up.\"}),`\n`,(0,t.jsx)(e.strong,{children:\"Solution:\"}),\" Delay in the invitation usually points at network quality between your iPhone and Mac rather than at any setting. Confirm both devices are on the same band of the same network, check whether your Wi-Fi is congested, and test with the Mac on Wi-Fi rather than Ethernet. Aggressive Bluetooth audio sleep can also eat the first ring or two \\u2014 test with built-in speakers.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Problem: Everything worked, then stopped after an iOS or macOS update.\"}),`\n`,(0,t.jsx)(e.strong,{children:\"Solution:\"}),\" Go straight to Step 2 and check the device list on the iPhone. This is the single most commonly reported post-update failure. If the list looks correct, do the Step 7 re-registration, since updates on either side can invalidate the existing registration. Then confirm both devices are on current, compatible releases.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Problem: Calls ring on my Mac when I do not want them to \\u2014 for example on a shared or work machine.\"}),`\n`,(0,t.jsx)(e.strong,{children:\"Solution:\"}),\" This is the same setting used in reverse. On the iPhone, go to \",(0,t.jsx)(e.strong,{children:\"Settings > Apps > Phone > Calls on Other Devices\"}),\" and turn off just that Mac's individual switch, leaving the feature on for your other devices. Do not turn off the master toggle unless you want to disable relay everywhere.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[(0,t.jsx)(e.strong,{children:\"Problem: The Phone app opens but shows no call history and no contacts.\"}),`\n`,(0,t.jsx)(e.strong,{children:\"Solution:\"}),\" Call history and contacts sync through iCloud, not through the call relay. Check \",(0,t.jsx)(e.strong,{children:\"System Settings > [your name] > iCloud\"}),\" and confirm Contacts is enabled. An empty Phone app with working calls is an iCloud sync problem; an empty Phone app with no working calls is a sign-in problem, and Step 7 is the right starting point.\"]}),`\n`,(0,t.jsx)(e.h2,{id:\"faq\",children:\"FAQ\"}),`\n`,(0,t.jsx)(e.h3,{id:\"does-the-phone-app-on-mac-work-without-my-iphone-nearby\",children:\"Does the Phone app on Mac work without my iPhone nearby?\"}),`\n`,(0,t.jsx)(e.p,{children:\"Only if Wi-Fi Calling is enabled with your carrier and configured to allow calls on other devices. Without Wi-Fi Calling, Apple requires both devices on the same Wi-Fi network, because your Mac has no cellular radio and relies on your iPhone to relay the call to it.\"}),`\n`,(0,t.jsx)(e.h3,{id:\"why-does-my-mac-ring-but-then-say-call-failed-when-i-answer\",children:\"Why does my Mac ring but then say Call Failed when I answer?\"}),`\n`,(0,t.jsx)(e.p,{children:\"The invitation that makes your Mac ring is lightweight and easy to deliver. The audio path that follows is much more demanding. A VPN, content filter, custom DNS resolver, or firewall can pass the first and block the second. Disconnect your VPN and test before changing anything else.\"}),`\n`,(0,t.jsx)(e.h3,{id:\"did-the-phone-app-exist-on-mac-before-macos-tahoe\",children:\"Did the Phone app exist on Mac before macOS Tahoe?\"}),`\n`,(0,t.jsx)(e.p,{children:\"No. The standalone Phone app came to the Mac in macOS 26 Tahoe. Before that, calls on the Mac ran through FaceTime, using the same iPhone Cellular Calls relay. The Phone app is a new interface on an existing system, which is why so many of its fixes live in FaceTime's settings.\"}),`\n`,(0,t.jsx)(e.h3,{id:\"will-turning-off-my-firewall-fix-the-phone-app-permanently\",children:\"Will turning off my firewall fix the Phone app permanently?\"}),`\n`,(0,t.jsx)(e.p,{children:\"Turning it off is a diagnostic, not a fix. If calls work with the firewall off, turn it back on and use Options to allow incoming connections for FaceTime and Phone, and confirm Block all incoming connections is disabled. Leaving the firewall off trades a call problem for a security problem.\"}),`\n`,(0,t.jsx)(e.h3,{id:\"why-does-my-mac-stop-ringing-after-every-ios-update\",children:\"Why does my Mac stop ringing after every iOS update?\"}),`\n`,(0,t.jsx)(e.p,{children:\"Community reports consistently describe the Calls on Other Devices device list on the iPhone being reset or dropping devices after updates. Apple has not acknowledged this, so treat it as a pattern rather than a confirmed bug. Checking that screen after each update is the cheapest habit you can build.\"}),`\n`,(0,t.jsx)(e.h3,{id:\"how-do-i-tell-whether-it-is-a-call-problem-or-a-notification-problem\",children:\"How do I tell whether it is a call problem or a notification problem?\"}),`\n`,(0,t.jsx)(e.p,{children:\"Have someone call you, let it fail, then open the Phone app and look at Recents. If the call appears as missed, it reached your Mac and the failure is in notifications or audio. If nothing is logged at all, the call never arrived and the problem is registration or the iPhone-side toggle.\"}),`\n`,(0,t.jsx)(e.h2,{id:\"conclusion\",children:\"Conclusion\"}),`\n`,(0,t.jsx)(e.p,{children:\"The Phone app on Mac fails in ways that look identical from the outside and have completely different causes underneath, which is why generic advice performs so poorly here. The model that makes it tractable is the three stages: registration puts your Mac on the list of valid destinations, the invitation tells it a call is arriving, and the media path carries the actual audio. Silence with no log entry is stage one or two. Silence with a logged missed call is notifications or audio. A ring that dies on answer is stage three, and that means the network.\"}),`\n`,(0,t.jsxs)(e.p,{children:[\"Start with the iPhone. \",(0,t.jsx)(e.strong,{children:\"Settings > Apps > Phone > Calls on Other Devices\"}),\", confirm the master toggle and confirm your specific Mac is present and enabled. That one screen resolves more of these cases than everything else on the list combined, and it is worth re-checking after every iOS update as a matter of routine. From there, work down: notifications, sound routing, VPN, firewall, then the FaceTime sign-out-restart-sign-in cycle that re-registers your Mac. If you get all the way to a fresh user account and calls still fail there, you have done real diagnostic work and Apple Support can pick it up from a much better starting point than most people give them.\"]}),`\n`,(0,t.jsxs)(e.p,{children:[\"If the rest of your Continuity setup is shaky too \\u2014 Handoff dropping, Universal Clipboard missing, devices not seeing each other \\u2014 fix that foundation first. Our guides on \",(0,t.jsx)(e.a,{href:\"/blog/iphone-mirroring-not-working-macos-tahoe-26-4-fix-2026\",children:\"iPhone Mirroring failures on macOS Tahoe\"}),\" and \",(0,t.jsx)(e.a,{href:\"/blog/macos-tahoe-continuity-features-complete-troubleshooting-guide-2025\",children:\"Continuity troubleshooting more broadly\"}),\" cover the shared plumbing, and repairing it there usually brings the Phone app back with it.\"]})]})}function d(n={}){let{wrapper:e}=n.components||{};return e?(0,t.jsx)(e,{...n,children:(0,t.jsx)(c,{...n})}):c(n)}return v(k);})();\n;return Component;","toc":[{"title":"Key Takeaways","url":"#key-takeaways","depth":2},{"title":"How Calls Actually Reach Your Mac","url":"#how-calls-actually-reach-your-mac","depth":2},{"title":"Quick triage","url":"#quick-triage","depth":3},{"title":"Step 1: The Requirements Nobody Checks","url":"#step-1-the-requirements-nobody-checks","depth":2},{"title":"Step 2: The iPhone Toggle That Updates Silently Flip","url":"#step-2-the-iphone-toggle-that-updates-silently-flip","depth":2},{"title":"Step 3: Notification Settings on the Mac","url":"#step-3-notification-settings-on-the-mac","depth":2},{"title":"The setting almost nobody finds","url":"#the-setting-almost-nobody-finds","depth":3},{"title":"Focus modes, Do Not Disturb, and Focus sharing","url":"#focus-modes-do-not-disturb-and-focus-sharing","depth":3},{"title":"Step 4: Sound Routing — The Ring Is Playing, Just Not Where You Are","url":"#step-4-sound-routing--the-ring-is-playing-just-not-where-you-are","depth":2},{"title":"Step 5: VPNs, Content Filters, and Custom DNS","url":"#step-5-vpns-content-filters-and-custom-dns","depth":2},{"title":"Step 6: The macOS Firewall","url":"#step-6-the-macos-firewall","depth":2},{"title":"Step 7: Sign Out of FaceTime and Sign Back In","url":"#step-7-sign-out-of-facetime-and-sign-back-in","depth":2},{"title":"Step 8: The Voice Control Conflict","url":"#step-8-the-voice-control-conflict","depth":2},{"title":"Step 9: Default Call Handler Conflicts","url":"#step-9-default-call-handler-conflicts","depth":2},{"title":"When Outgoing Calls Work but Incoming Calls Do Not","url":"#when-outgoing-calls-work-but-incoming-calls-do-not","depth":2},{"title":"Carrier-Side Factors and Wi-Fi Calling","url":"#carrier-side-factors-and-wi-fi-calling","depth":2},{"title":"Step 10: Deeper Resets, in Order","url":"#step-10-deeper-resets-in-order","depth":2},{"title":"Troubleshooting Common Issues","url":"#troubleshooting-common-issues","depth":2},{"title":"FAQ","url":"#faq","depth":2},{"title":"Does the Phone app on Mac work without my iPhone nearby?","url":"#does-the-phone-app-on-mac-work-without-my-iphone-nearby","depth":3},{"title":"Why does my Mac ring but then say Call Failed when I answer?","url":"#why-does-my-mac-ring-but-then-say-call-failed-when-i-answer","depth":3},{"title":"Did the Phone app exist on Mac before macOS Tahoe?","url":"#did-the-phone-app-exist-on-mac-before-macos-tahoe","depth":3},{"title":"Will turning off my firewall fix the Phone app permanently?","url":"#will-turning-off-my-firewall-fix-the-phone-app-permanently","depth":3},{"title":"Why does my Mac stop ringing after every iOS update?","url":"#why-does-my-mac-stop-ringing-after-every-ios-update","depth":3},{"title":"How do I tell whether it is a call problem or a notification problem?","url":"#how-do-i-tell-whether-it-is-a-call-problem-or-a-notification-problem","depth":3},{"title":"Conclusion","url":"#conclusion","depth":2}],"estimatedTime":36}