The Squawk tool is a WebRTC based audio feed designed to provide lighting fast breaking news via audio. When active, you may not hear constant talking. Reads are only done when breaking news is present. Below is a list of steps to follow to diagnose issues with the audio feed. Instructions on how to use Squawk can be found here.

If you can't hear squawk:

  1. Ensure you are pressing the play button and have squawk active
  2. Make sure nothing is muted (computer speakers, browser tab, system audio, etc)
  3. Test audio through Benzinga Pro. 3 dots in upper right > Account > Test Audio
  4. If you hear the beep, the next step is to Identify your web browser, and follow the steps below for your corresponding browser.

For Safari:

- Click Safari menu, top left corner
- Select Preferences
- Go to Advanced tab
- Enable Show Develop in menu bar at bottom of Advanced preference pane
- Go to newly enabled Develop menu > WebRTC (approx 2/3 of way down)
- Select Disable ICE Candidate Restrictions
-In Safari Preferences > Websites > Auto-Play on the left list > under Currently Open Websites > > change drop down to "Allow All Auto-Play"

For Chrome:

-Go to chrome://flags/ in your chrome browser address bar
-In search bar, search for  Anonymize local IPs exposed by WebRTC
-Disable Anonymize local IPs exposed by WebRTC
-Restart Chrome

Our squawk service requires access to specific ports to broadcast. If you are in a setting where there are strict network security rules and permissions, it is possible some of the necessary ports need to be opened by you, or your IT team:

The ports are:

3478 TCP & UDP
49152 - 65535 UDP
The audio server,, needs TCP/UDP 1024-65535 opened
The fallback audio server is
The turn server is at
Our turn server uses port 443,
Squawk is running on port 8080
Squawk WebSocket is at wss://
Some of the other hostnames that need to be added to whitelist:

Did this answer your question?