Network Checklist
This article provides technical details for configuring customer networks to work with Tango Tango. Most customers will not need to make any modifications to support Tango Tango, but some customer WiFI networks may require changes to adhere to these requirements.
General Network Checklist
Checklist
The following checklist is applicable to most customers using the Tango Tango service with their own Android, iOS, or Desktop/Laptop devices. Following this checklist can help ensure the best user experience possible when using the Tango Tango service.
- iOS devices must be able to connect to APNS and receive push notifications. (More Info)
- Android devices must be able to connect to FCM and receive push notifications. (More Info)
- Android devices which do not have the Google Play store must be able to receive push notifications from the Pushy push notification service (More Info).
- Devices can perform perform a GET request against our health check API (details below). This response should be received within 1 second.
- Devices must be able to join calls within 3 seconds - though they should join in less that 1 second for a good user experience. This latency can be observed by reviewing call detail records in the admin portal, or by contacting Tango Tango support for a report.
- When on WiFi, devices must be able to maintain a connection (via websocket) to the PTT service without reconnecting or dropping packets when roaming between access points.
- When on WiFi, configuration should be applied to drop devices that attempt to connect with a low signal level that won’t allow the device to meet these requirements.
Performing a Service Health Check
You can check connectivity to the Tango Tango PTT service by performing an HTTPS GET request against the /darmok
endpoint. It should reply with a 200 OK
response and the text jalad
.
The following curl command will perform this request and report how long it takes - but any HTTPS client or health checking tool should be able to perform this test.
curl -o /dev/null -s \
-w 'Total: %{time_total}s\n' \
https://manage.tangotango.io/darmok
Required Internet Hosts
The following information is for networks which perform outbound connection filtering. In all of the following cases, devices initiate the connection to the given host. The Tango Tango service never initiates a connection from our services or the services we use. No port forwarding is required.
Device Type | Host | Ports | URLs | Access Reason |
---|---|---|---|---|
All | manage.tangotango.io | 443/TCP | * | Push-to-talk Services |
All | login.tangotango.io cdn.auth0.com | 443/TCP | * | Authentication |
Web Android iOS | s3.amazonaws.com | 443/TCP | /manage-profile-photos/uploads/avatars/* | Avatar Images |
Web Android iOS | manage-profile-photos.s3.amazonaws.com | 443/TCP | /static/* | Avatar Images |
Web | x237hpjr3hy0.statuspage.io | 443/TCP | * | Service Status Update Notifications |
Web | api.mapbox.com events.mapbox.com | 443/TCP | * | Map Displays |
Android iOS ROIP | *.datadoghq.com | 443/TCP | * | Service Metrics and Logging |
iOS | 17.0.0.0/8 | 443/TCP 5223/TCP 2197/TCP | NA | APNS Push Notifications (More Info) |
Android | mtalk.google.com mtalk4.google.com mtalk-staging.google.com mtalk-dev.google.com alt1-mtalk.google.com alt2-mtalk.google.com alt3-mtalk.google.com alt4-mtalk.google.com alt5-mtalk.google.com alt6-mtalk.google.com alt7-mtalk.google.com alt8-mtalk.google.com android.apis.google.com device-provisioning.googleapis.com firebaseinstallations.googleapis.com | 5228/TCP 5229/TCP 5230/TCP 443/TCP | * | FCM Push Notifications (More Info) |
Android (w/o App Store) | *.pushy.me *.pushy.io | 443/TCP | * | Pushy Push Notifications (More Info) |
Additional Items for Tango Tango Managed Devices
These requirements only apply to devices sold and managed by Tango Tango, such as a Siyata SD7, that was purchased as part of a managed service agreement.
Checklist for Managed Devices
- Devices can connect to Esper for the purposes of device management (More Info).
Required Internet Hosts
The following information is for networks which perform outbound connection filtering. In all of the following cases, devices initiate the connection to the given host. The Tango Tango service never initiates a connection from our services or the services we use. No port forwarding is required.
Host | Ports | URLs | Access Reason |
*.amazonaws.com *.esper.cloud *.esper.io 8.8.8.8 services.shoonyacloud.com | 443/TCP | * | Esper Device Management (More Info) |
mqtt.shoonyacloud.com | 1883/TCP | NA | Esper Device Management (More Info) |
turn.shoonyacloud.com | 3478/TCP+UDP 5349/TCP+UDP 49152 - 65535/UDP | NA | Esper Device Management (More Info) |
*.firebaseio.com *.crashlytics.com *.googleapis.com | 443/TCP 5228/TCP 5229/TCP 5230/TCP | NA | Esper Device Management (More Info) |