Skip to main content

How to Provide Audio Permissions for Calls

In this section, we'll show you how to give Double Nickel the audio permissions it needs for calls, in your browser, on your computer, and on your office network, and how to fix calls that connect with no sound.

In this section, we'll show you how to give Double Nickel the audio permissions it needs for calls, in your browser, on your computer, and on your office network, and how to fix calls that connect with no sound.

Calls from Double Nickel run directly in your browser, so three things have to line up: the browser must be allowed to use your microphone, your computer must let the browser use it, and the right headset must be selected. If all of that is in place and there is still no audio, the office network is the next suspect. Work through the fixes below in order.

Start Here: Match Your Symptom

What you see

Most likely cause

Start with

A Microphone Access Denied window appears when you click Call

The browser blocked the microphone

Fix 1

The applicant cannot hear you, but you hear them

Microphone permission or the wrong input device

Fix 1, then 2 and 3

You cannot hear the applicant, but they hear you

The wrong speaker or headset is selected

Fix 3

The call connects and the timer runs, but neither side hears anything

Office firewall blocking call audio

Fix 5 (after a quick pass through 1 to 4)

Calls work from home or on a hotspot, but not in the office

Office firewall blocking call audio

Fix 5

Fix 1: Allow the Microphone in Your Browser

The first time you place a call, the browser asks whether Double Nickel may use your microphone. If that prompt was dismissed or blocked, the browser remembers the choice and will not ask again.

If you see the Microphone Access Denied window

  1. Close the window and click on Call again

  2. Click on the microphone icon (or the lock icon) in the browser's address bar

  3. Select Allow and place the call again

Google Chrome

  1. Click on the lock or settings icon to the left of the address bar

  2. Set Microphone to Allow

  3. Reload Double Nickel and place the call again

If the microphone is already set to Allow and calls still have no audio, reset the permission so the browser asks fresh: go to Settings → Privacy and security → Site settings → Microphone, remove Double Nickel from the list, reload Double Nickel, click on Call, and click on Allow when the prompt appears.

Microsoft Edge

  1. Click on the lock icon to the left of the address bar

  2. Click on Permissions for this site

  3. Set Microphone to Allow, then reload Double Nickel

To reset the permission in Edge, go to Settings → Cookies and site permissions → Microphone, remove Double Nickel, reload, and click on Allow when prompted.

Safari

  1. With Double Nickel open, click on Safari → Settings for This Website

  2. Set Microphone to Allow

Fix 2: Allow the Microphone on Your Computer

Even when the browser is allowed, the operating system can block it. This is common on managed office computers.

Windows 10 and 11

  1. Open Settings

  2. Click on Privacy & security (Windows 11) or Privacy (Windows 10)

  3. Under App permissions, click on Microphone

  4. Make sure Microphone access is On

  5. Make sure Let desktop apps access your microphone is On, and that your browser (Chrome or Edge) is listed and allowed

If the browser is not listed, open Double Nickel, click on Call, and check the list again. Windows adds apps to the list the first time they ask for the microphone.

macOS

  1. Open System Settings

  2. Click on Privacy & Security, then Microphone

  3. Turn on the switch next to your browser

Fix 3: Select the Headset for Input and Output

The browser and the computer each keep their own choice of microphone and speaker. A headset can be plugged in and still not be the one in use, so check both places.

Plug in and confirm the headset is recognized

  • Plug the headset directly into the computer, not into a monitor or an unpowered hub, and check that it is switched on

  • Close other apps that may be holding the microphone, such as Teams, Zoom, or a softphone

Windows

  1. Open Settings → System → Sound

  2. Under Output, select the headset (for example, a Poly or Plantronics USB headset)

  3. Under Input, select the same headset, and speak to confirm the volume bar moves

macOS

  1. Open System Settings → Sound

  2. Select the headset under both Output and Input

In the browser

In Chrome and Edge, the microphone and speaker used by a site can be changed from the lock icon in the address bar, or under Site settings → Microphone, where a dropdown lists the available devices. Select the headset, then reload Double Nickel.

In the dialer

Check that you are not muted. The microphone button in the Double Nickel dialer toggles mute; click on it once to unmute if it shows the muted state.

Fix 4: Rule Out the Browser

  • Reload Double Nickel after every permission change. Permissions apply to new page loads.

  • Try the call in a different browser (Chrome if you were on Edge, or the other way round). If it works in one browser, the problem is that browser's permission or device settings.

  • Try an incognito or private window, which runs without extensions. Some ad-blocking and privacy extensions interfere with calling.

  • Make sure the browser is up to date.

Fix 5: Office Network and Firewall

If every permission is in place, the headset is selected, and the call still connects with silence on both sides, the office firewall is almost certainly blocking the call audio. The call itself is set up over a regular HTTPS connection, which nearly every network allows. The audio travels separately over a range of UDP ports, and strict firewalls block that range by default. A quick way to confirm: place the same call from home or on a phone hotspot. If it works there, it is the office network.

Double Nickel uses Twilio for calling. Share the rules below with your IT team. All of this traffic is outbound only. Twilio never initiates a connection into your network, so no inbound rules are needed.

Required

Voice audio will not work without this rule.

Purpose

Protocol

Destination

Ports

Voice media

UDP (outbound)

168.86.128.0/18

10,000 – 60,000

Recommended

These usually pass already, but confirm them if calls still fail after the UDP rule is in place.

Purpose

Protocol

Destination

Ports

Call signaling

TCP/TLS

voice-js.roaming.twilio.com

443

Call signaling

TCP/TLS

chunderw-vpc-gll.twilio.com

443

Call quality reporting

TCP/TLS

eventgw.twilio.com, eventgw.us1.twilio.com

443

Ringtones and call sounds

TCP/TLS

sdk.twilio.com

443

Only if the UDP range cannot be opened

Twilio can relay the audio through its TURN servers instead. Call quality is noticeably better over the direct UDP path above, so use this only as a fallback.

Purpose

Protocol

Destination

Ports

TURN relay (US East)

UDP and TCP

3.235.111.128/25, 34.203.250.0/23, 34.203.254.0/24, 54.172.60.0/23

3478, 443, 5349

TURN relay (US West)

UDP and TCP

34.216.110.128/27, 44.234.69.0/25, 54.244.51.0/24

3478, 443, 5349

Also ask IT to check

  • If the router or firewall has SIP ALG (Application Level Gateway) or stateful packet inspection enabled on UDP traffic, disable them. Both are known to interfere with browser calling even when the ports are open.

  • The rules need to cover the workstations recruiters call from, not only a server segment. If some users can call and others cannot, compare which network or VLAN each one is on.

Still No Audio?

Send us the following and we will help narrow it down:

  • Your operating system (Windows 10, Windows 11, macOS) and browser (Chrome, Edge, Safari)

  • Which of the fixes above you tried

  • Whether the applicant hears you, you hear them, neither, or both

  • Whether the same call works from home or on a hotspot

Contact [email protected] or use our in-app support messenger for assistance!

Did this answer your question?