Overview
You must configure your network to permit communication to-and-from the 7SIGNAL Cloud hosting your instance. Please make sure the ports, protocols and links below are available or whitelisted.
In North America, outbound access must be allowed to this IP range 64.65.61.0/24 which is where 7SIGNAL customer cloud instances are hosted.
For locations connecting to EMEA or outside North America, please submit a support case via Request Support to request the IP address.
Required for Sensor Connectivity
| Source | Destination | Protocol/Port | Purpose |
| Ethernet IP |
64.65.61.0/24 |
TCP/443, TCP/7799, TCP/7800 |
Cloud Management |
We do not recommend filtering by port because it may cause service disruptions. As this is a cloud application and dynamic in nature, all ports should be allowed for the best customer experience.
Recommended for Sensor Connectivity
| Source | Destination |
Protocol/Port |
Purpose |
| Ethernet IP | time1.google.com | NTP (UDP/123) | Time |
| Ethernet IP | time2.google.com | NTP (UDP/123) | Time |
| Ethernet IP | time3.google.com | NTP (UDP/123) | Time |
| Ethernet IP | time4.google.com | NTP (UDP/123) | Time |
| Ethernet IP | 64.65.61.0/24 | UDP/514, TCP/6514 | Remote syslog |
Required for Agent Connectivity
| TCP/443 | HTTPS communication to the 7SIGNAL cloud |
| TCP/80 |
HTTP throughput testing to Sonar endpoint IP address (see bottom of page) |
| UDP/50000 to 50300 |
VoIP testing to Sonar IP address |
| ICMP |
Ping testing |
|
https://login.7signal.com |
Obtain OAuth token |
|
https://api.7signal.com |
Obtain config, submit results |
|
https://downloads.7signal.com |
Automatic software update |
|
https://janus-prod-stream-bucket.s3.us-east-2.amazonaws.com |
Obtain config, submit results |
7SIGNAL updates agent/app software about 4 or 5 times per year with feature enhancements and fixes. Customers will be notified via email of pending releases.
When the auto-update occurs, customers will see a temporary increase in WAN traffic and bandwidth utilization as devices download the update.
Required for Sonar® Cloud Endpoint
Click here to learn more about setting up a Docker® Sonar on your WAN.
| Source | Destination | Protocol/Port | Purpose |
| Ethernet/Wi-Fi | Sonar | HTTP (TCP/80) | Throughput Test |
| Ethernet/Wi-Fi | Sonar | UDP/50000-50300 | Voice Quality Test |
| Ethernet/Wi-Fi | Sonar | ICMP | Ping Test |
Sonar Cloud Endpoints
Sonar cloud endpoints are available for 7SIGNAL customers only.
| FQDN | Location |
| east1.sonar.7signal.com | New Jersey, US |
| east2.sonar.7signal.com | New York, US |
| central1.sonar.7signal.com | Atlanta, US |
| midwest1.sonar.7signal.com | Chicago, US |
| pacific1.sonar.7signal.com | San Francisco, US |
| emea1.sonar.7signal.com | Frankfurt, DE |
| emea2.sonar.7signal.com | London, GB |
| apac1.sonar.7signal.com | Singapore |
| sa.sonar.7signal.com | Sao Paulo, BR |
Sensor Port Check Verification
After a sensor is plugged into the network, you may find that it cannot connect to the cloud. If so, you can SSH to the sensor and run the 7config conn check command to gain more insight. You should expect to see the following output:
Success: Carat server reachable by using carat_ip:7799
Success: TLS connection established to Carat carat_ip:7799
Success: Carat server reachable by using carat_ip:7800
Success: TLS connection established to Carat carat_ip:7800