You must configure your network to permit communication to-and-from the Sapphire Cloud hosting your instance. Here is a list of the ports and protocols required.
Overview
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.
NTP/123 outbound must also be allowed.
Required for Sapphire Eye Connectivity
Source | Destination | Protocol/Port | Purpose |
Sapphire Eye Ethernet IP |
64.65.61.0/24 |
TCP/7799, TCP/7800 |
Cloud Management |
We do not recommend filtering by port, as 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 Sapphire Eye Connectivity
Source | Destination |
Protocol/Port |
Purpose |
Sapphire Eye Ethernet IP | time1.google.com | NTP (UDP/123) | Time |
Sapphire Eye Ethernet IP | time2.google.com | NTP (UDP/123) | Time |
Sapphire Eye Ethernet IP | time3.google.com | NTP (UDP/123) | Time |
Sapphire Eye Ethernet IP | time4.google.com | NTP (UDP/123) | Time |
Sapphire Eye Ethernet IP | 64.65.61.0/24 | UDP/514, TCP/6514 | Sapphire Eye remote syslog |
Required for Sonar® Cloud Endpoint Testing
Source | Destination | Protocol/Port | Purpose |
Sapphire Eye Ethernet/Wi-Fi | Sonar Server | HTTP (TCP/80) | Throughput Test |
Sapphire Eye Ethernet/Wi-Fi | Sonar Server | UDP/50000-50300 | Voice Quality Test |
Sapphire Eye Ethernet/Wi-Fi | Sonar Server | ICMP | Ping Test |
Sonar Cloud Endpoints
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 |
Port Check Verification
After a Sapphire Eye is plugged into the network, you may find that it cannot connect to the cloud. If so, you can SSH to the Sapphire Eye 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