Do I need a phone number to make outbound calls?

No. Outbound calls do not require purchasing a dedicated phone number.

Can I receive calls in my browser?

Yes. Inbound calling requires a unique US/Canada digital number ($2.14 to $5/month).

Browser Calling Guide

Safari Browser Calling Issues - Why Safari Fails and How StartACall Works

Start the call from any browser tab. There is no download, and you only add a number to receive inbound calls.

Product facts

Outbound: No dedicated number required.
Inbound: Requires US/Canada digital number ($2.14 to $5/month).
No apps: Works in Chrome, Safari, Edge, Firefox.

Read Troubleshooting

Browser CallingLive in Browser

No app required. Works directly in Safari, Chrome, and Firefox.

Why Safari Calls Fail

Understanding the common failure points helps you troubleshoot faster. Below are the most frequent causes for Safari call failures and what they look like.

Permission Blocks

Safari often requires an explicit user gesture for microphone or audio playback. If the site has no microphone permission, the call will not capture audio.

Cookie and Storage Restrictions

Apple's tracking and cookie rules can block third-party cookies and storage that some signaling flows depend on. That can break authentication and Twilio token retrieval for the call session.

Network and Codec Edge Cases

NAT or strict firewall rules can prevent direct peer connections. Safari's WebRTC differences can surface when negotiating codecs or SRTP keys with PSTN bridges.

Symptoms to watch for

Call connects but you or the other party are muted or one-way audio
Call fails during or immediately after authentication
Mic request never appears or gets denied silently

How StartACall Fixes Safari Problems

We designed StartACall to handle the full range of Safari quirks so your team can call from the browser with confidence.

Reliable Signaling

Server-issued Twilio access tokens and WebSocket-based signaling avoid reliance on blocked third-party cookies. This keeps sessions stable across Safari settings.

TURN Media Relays

When direct peer-to-peer fails, StartACall routes media through TURN servers so audio works even behind strict NATs and firewalls.

Twilio PSTN Bridge

We use Twilio to bridge WebRTC to the PSTN, handling codec negotiation and ensuring compatibility with traditional phone networks worldwide.

Client-Side Fixes

Graceful permission prompts with clear instructions
Polyfills and Safari-specific handling in our browser SDK
Fallback audio playback methods to avoid user gesture blocks

Server-Side Fixes

Short-lived access tokens to avoid stale sessions
Server-managed TURN/STUN allocation for media resiliency
Fallback SIP over WebSocket if a direct WebRTC negotiation fails

Built-in Diagnostics

StartACall provides real-time analytics and diagnostics so you can see permission status, ICE candidate exchange, and media relay usage. That makes it simple to identify whether a problem is a permission, network, or signaling issue.

Frequently Asked Questions

Is StartACall compatible with iOS Safari?

Yes. StartACall supports modern iOS Safari versions. Some older iOS versions lack full WebRTC features, so we recommend updating to the latest iOS for best results.

Why does my microphone prompt not appear in Safari?

If the prompt does not appear, check that the site is loaded over HTTPS, that you are not in Private Browsing, and that Safari > Settings for the website allows Microphone access. Reload the page after changing settings.

What if I get one-way audio?

One-way audio is usually a NAT or TURN issue. StartACall automatically falls back to TURN relays when direct media paths fail, which fixes most one-way audio problems.

Do I need to install anything?

No. StartACall is web-based. You can place calls from Safari, Chrome, or Firefox without installing apps or plugins.

Ready to stop worrying about Safari quirks?

Sign up and start making calls from your browser instantly. Built-in diagnostics and resilient media routing ensure calls work reliably in Safari.

Safari Browser Calling Issues: Why Safari Fails and How StartACall Works

In short

Safari often breaks browser based calls because of its strict WebRTC and autoplay rules, microphone permission prompts, and aggressive background tab throttling. StartACall is built to work inside Safari with no app download and no SIM card, so you can place outbound calls and receive inbound calls directly in the browser once you allow microphone access.

Frequently asked questions

Why does my microphone not work for calls in Safari?+

Safari only grants microphone access on secure HTTPS pages and asks you to approve it per site. Open Safari Settings, set the microphone permission for the page to Allow, reload, then start the call. In Private Browsing this permission can reset, so use a normal window.

Do I need to download an app to use StartACall in Safari?+

No. StartACall runs entirely in the browser. There is no app to install and no SIM card required. You open the page in Safari, allow the microphone, and place or receive calls.

Can I receive incoming calls in Safari with StartACall?+

Yes. Outbound calls need no phone number, but to receive inbound calls you add a US or Canada digital number for about $2.14 to $5 per month. Calls then ring directly in your Safari browser.

How much do calls cost?+

Outbound calling is pay as you go and billed per minute, with no phone number required. The only recurring cost is an optional US or Canada number for inbound calls at roughly $2.14 to $5 per month.