All Collections
Pro Tips & Features
Squawk tips and troubleshooting
Squawk tips and troubleshooting

Troubleshooting steps for the Squawk tool

Ryan Faloona avatar
Written by Ryan Faloona
Updated over a week ago

The Squawk tool is a WebRTC-based audio feed designed to provide lightning-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 the Safari menu in the top left corner

- Select Preferences

- Go to the Advanced tab

- Enable Show Develop in the menu bar at bottom of the Advanced preference pane

- Go to the newly enabled Develop menu > WebRTC (approx 2/3 of the 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 the search bar, search for Anonymize local IPs exposed by WebRTC

-Disable Anonymize local IPs exposed by WebRTC

-Restart Chrome

Network Setup:

Our squawk service requires access to specific ports to deliver audio. 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. Also need to whitelist a few IPs and hostnames related to our media servers.


● Open a few UDP and TCP ports (5-10 max should be enough) from the range 10000-60000, to allow media traffic(audio) to flow to your network.

● Allow traffic from port 443

Whitelist the following IPs:

Primary Media Servers:




Fall back media server:







In general, you should allow network access to the URI pattern https://** using port 443 for all our services to work flawlessly.

You may also verify the WebRTC connectivity works on your end via

If none of the above works and you are still facing any issue, we may need some log dump from your browser’s WebRTC engine. Follow the below step for generating the dump:

● Open Benzinga Pro in chrome and start squawk.

● Open a new tab in chrome and go to chrome://webrtc-internals/ in the Chrome browser.

● Once the page is loaded, go to the tab

● Now go to Create Dump (upper left corner of the page), then click Download the PeerConnection updates and stats data. And send that dump file to us.

Did this answer your question?