Zoom Phone Error Code 491 appears when a call attempt can’t be completed and Zoom shows a message similar to “The service is not available currently”. It’s a temporary condition in the call path, so the goal is to identify whether it’s mainly service-side availability or something on your network/device path that is blocking or delaying the call setup.
Table of Contents
What Error Code 491 Means
Meaning In Zoom Phone, error 491 is shown as a service-not-available condition. Zoom describes it as a situation where server issues might be preventing your call, so retrying later or checking with your Zoom Phone admin is the expected next step. [✅Source-1]
Zoom phone notifications often show a longer number like Call failed (code: 2202491). In that format, the last three digits are the actual error code (so 491 is the part you use when troubleshooting). [✅Source-2]
One subtle point matters for accuracy: the Zoom Phone error label “491” is what users see in the Zoom app experience, while 491 can also appear as a SIP status code in VoIP logs. They are related by the overall calling stack, but they are not guaranteed to be the same “root cause” in every environment. Keeping this distinction prevents wasted time and keeps troubleshooting tight and factual.
Where the Code Appears and What It Tells You
| Place You See It | What You Typically Notice | What It Usually Points To | Best First Move |
|---|---|---|---|
| Zoom Desktop App | Call failed with a code ending in 491 | Call setup could not complete at that moment | Retry after a short pause; then test another network |
| Zoom Mobile App | Outbound call won’t connect; message indicates service unavailable | Either service-side availability or local network path issues | Switch between Wi-Fi and mobile data to compare |
| Desk Phone / SIP Device | Dial attempt fails or device looks registered but calls fail | Provisioning/firmware/network reachability may need attention | Check firmware and confirm required connectivity |
| Admin Troubleshooting | Call logs show repeated failures around the same time | Pattern can indicate a shared network control point | Validate firewall/proxy allowance for Zoom Phone |
If multiple users see the same behavior at the same time, it often behaves like a shared dependency (for example, a common network policy or a temporary service-side condition). If only one device is affected, focus on that device’s app state, sign-in state, or local network path. Keep the mindset specific and test-driven.
Fast Checks That Usually Save Time
- Pause for 30–60 seconds before retrying. Rapid redial loops can keep you inside the same temporary failure window.
- Dial a second, known-good number (for example, a colleague’s direct line). This helps separate a single destination issue from a general outbound issue.
- Switch networks once: Wi-Fi to mobile data (or vice versa). A clean A/B test is more useful than ten small tweaks.
- Sign out of Zoom, then sign back in. This refreshes the session and can clear a stuck registration state without changing any settings.
- If you are on a managed office network, ask your admin if a firewall or proxy change happened recently. Small policy updates can block required paths while everything else still “looks online”.
Practical Tip When Zoom Phone problems behave differently across networks (for example, calls work on mobile data but fail on office Wi-Fi), Zoom suggests checking the firewall/ports for the network where calls fail. [✅Source-3]
Separate Zoom-Side Symptoms From Network-Side Symptoms
Signs It’s More Likely Service-Side
- Several users in different networks see similar failures at the same time.
- The issue appears suddenly and then clears without changes, which fits a temporary availability pattern.
- Retrying later succeeds, matching the “try again later” guidance associated with service unavailable messaging.
Signs It’s More Likely Network/Device-Side
- Calls fail only on one network (office Wi-Fi) but work on another (mobile data).
- Only one device fails while the same user account works elsewhere, pointing to a local path.
- Other Zoom features work, yet phone calling fails, which can happen when specific ports are restricted.
When your goal is speed, prioritize tests that produce a clear fork. The fastest fork is usually “same user, different network” or “same network, different user”. You only need a couple of comparisons to decide whether you should focus on network controls or on service availability.
Network and Firewall Items for Admins
If your checks point to a network control point, the most useful admin action is to verify that Zoom Phone’s required connectivity is allowed, especially through firewalls, proxies, and web security gateways. Zoom’s official network guidance includes Zoom Phone-specific firewall rules and notes for common edge cases. [✅Source-4]
| Zoom Phone Connectivity Item | Why It Matters | Example to Verify |
|---|---|---|
| Signaling reachability | Call setup needs a reliable path; blocked signaling can look like “service unavailable” to the end user | Confirm Zoom Phone firewall rules are allowed on outbound policies |
| Media/NAT traversal | Even if signaling connects, media or traversal restrictions can break call establishment or quality | Ensure required UDP/TCP behavior isn’t forced through a restrictive proxy |
| Proxy inspection side effects | Some proxies alter or delay sessions; timing issues can cascade into failed setup attempts | Test a direct path (no proxy) on a controlled segment, if policy allows |
Use Built-In Tests Before Changing Settings
Zoom provides a Network Connectivity Tool that can run a Zoom Phone test and report metrics such as latency, packet loss, jitter, and the audio codec used during the test. This is a fast way to validate the network path with data, instead of guessing. [✅Source-5]
- If the test shows stable metrics yet calls still fail with 491, focus next on account-level behavior and the time pattern of failures.
- If the test shows notable loss/jitter, treat it as a network quality or routing problem first; that reduces failed call setup attempts and improves overall results.
Desk Phone and SIP Device Notes
Desk phones and SIP devices add two common variables: firmware alignment and secure signaling compatibility. Zoom notes that Zoom Phone certified desk phones must support TLS 1.2, and they should run the latest firmware version listed for the device. Keeping firmware current helps avoid odd call setup behavior that can surface as intermittent failures. [✅Source-6]
Device-Focused Checklist
- Confirm the device model is supported and registered as expected in your environment.
- Update the device to the recommended firmware; then reboot to ensure the update is fully applied.
- If the device was recently moved networks, re-check that the new network allows the required secure signaling path.
Confirm Service Status When Timing Suggests It
When you suspect a broad issue (many users, multiple locations, same time window), checking the official Zoom Service Status can quickly confirm whether there is an active incident or maintenance period affecting phone services. It’s a clean step that keeps troubleshooting aligned with reality and avoids unnecessary changes. [✅Source-7]
If You See “491” in VoIP Logs
In SIP (a common VoIP signaling standard), 491 can mean “Request Pending”—a dialog already has a pending request and the peer rejects a new one until the “glare” is resolved. This is typically associated with overlapping session-modification requests (like two sides changing the call at the same time). [✅Source-8]
How this helps in practice: if your environment captures SIP signaling and you notice 491 Request Pending around the same time users report call failures, look for repeated retries or overlapping call-control actions (hold/resume, transfers, quick device switching). The safest response is to reduce collisions: let the dialog settle, then retry cleanly, rather than forcing repeated actions back-to-back.
Collect the Right Evidence Before Escalating
When escalation is needed, focus on information that directly improves diagnosis: exact time of the failure, whether it was outbound or inbound, the device/app used, and whether the call succeeds on a different network. If you have a Zoom Phone license, Zoom notes you can view diagnostic information during a phone call, including items like a Register ID that may be requested for network troubleshooting. [✅Source-9]
- Capture the full error line (including the longer code if shown) and note the last three digits 491.
- Record whether the issue occurs on Wi-Fi, mobile data, or a wired network.
- Note if the same account can call from a second device, which is a strong troubleshooting signal.
- Note if other users are affected at the same time.
Zoom also supports sending a Zoom Phone problem report so support teams can review logs alongside your description (including the date/time the issue occurred). If you already have a support ticket, you can include the ticket ID when you send the report, which keeps the workflow clean and trackable. [✅Source-10]
FAQ
What does Zoom Phone Error Code 491 mean in plain words?
It means the call couldn’t be completed at that moment and Zoom is reporting a service-not-available condition. The most reliable next steps are to retry after a short pause and, if it repeats, check whether the issue is tied to a specific network or affects multiple users.
Why does the error show as a longer number like 2202491?
Zoom often displays a longer call-failure code where the last three digits are the part used for troubleshooting. If the notification ends in 491, you treat it as error code 491.
How can I quickly tell if it is my network or something broader?
Do one clean A/B test: place the same call on a different connection (for example, switch from office Wi-Fi to mobile data). If it works on one network and fails on another, that points to network controls like firewall/ports or proxy behavior.
What should an admin collect before opening a support case?
Collect the failure time window, user/extension, device type, the full call-failed code, and whether the issue reproduces on another network. If available, include phone call diagnostics (like Register ID) and submit a problem report so logs align with the description.
Does “491” always mean the SIP status code 491 Request Pending?
No. The Zoom Phone error label “491” is what users see in the Zoom Phone experience. In VoIP signaling logs, “491” can also appear as a SIP response meaning Request Pending. Treat them as related concepts, but confirm using the context (user-facing message vs signaling logs).