Jigsaw WebRTC Whitelisting Info

Have more questions? Submit a request

Jigsaw® is a fully functional platform that utilizes WebRTC and HTML5. It’s a feature rich application which streams live video, and it performs better over UDP traffic because of its speed and data accuracy.  Jigsaw has two types of traffic, general web page traffic and streaming traffic for the live classrooms.  Just like all other sites, our web pages use HTTP and HTTPS "protocols" (which just means the way in which the data being sent/received is organized).  It is browser and firewall friendly; however, there may be times when personal or network settings require you to whitelist specific ports. 

Connections are initiated from the client-side and in most cases the application will work without requiring a network team to modify configurations.  However, in some environments which are more restrictive to outbound traffic, the information provided is needed to allow the services to work.  Unblocking UDP, and confirming proxy and firewall settings will assure higher quality and a more consistent Jigsaw user experience.

Please Note:  If any user encounters issues with screen sharing consistently not starting, or they are not able to join a Jigsaw session at all; it is usually due to network restrictions blocking UDP traffic.

 


AWS CloudFront (CDN for assets)

AWS Load Balancers (general purpose)

  • Hostnames served:
    • app.jigsawinteractive.com
    • core-api.jigsawinteractive.com
    • api.jigsawinteractive.com
    • bor-api.jigsawinteractive.com
    • dashboard.jigsainteractive.com
    • sock.jigsawinteractive.com
    • cf.jigsawinteractive.com
    • rum.jigsawinteractive.com
  • IPs change periodically (usually monthly) and are controlled by AWS
  • Ports: 443, 80
  • Type of traffic:  TCP (HTTP/HTTPS and WSS)
  • Current IPs (discovered using dig app.jigsawinteractive.com @1.1.1.1 on January 31, 2022):
    • 34.204.131.51
    • 34.235.219.98
    • 44.196.194.118

AWS Load Balancers (for special purposes, media server session sticking, whiteboard V2)

  • Hostnames served:
    • ms.jigsawinteractive.com
    • wb.jigsawinteractive.com
  • IPs change periodically (usually monthly) and are controlled by AWS
  • Ports: 443, 80
  • Type of traffic:  TCP (HTTP/HTTPS and WSS)
  • Current IPs (discovered using dig app.jigsawinteractive.com @1.1.1.1 on January 31, 2022):
    • 3.215.91.184
    • 35.173.72.133
    • 52.3.210.101

Media Servers (cameras, mics, or any WebRTC streams)

  • Hostnames served:
    • media-ips.jigsawinteractive.com
  • IPs (all are taken from the pool below)
  • Ports:  10000-65535 (extended range will be used in future.  So far we utilize: 40000-59999)
  • Types of traffic:  WebRTC over UDP (SSL encrypted packages) and eventually WebRTC over TCP (SSL encrypted packages)
  • Current IP Pool (discovered using dig media-ips.jigsawinteractive.com @1.1.1.1 on January 31, 2022)
    • 100.24.108.100
    • 18.214.125.127
    • 18.232.15.79
    • 184.73.240.59
    • 3.210.46.13
    • 3.221.32.135
    • 3.222.134.160
    • 3.223.220.95
    • 3.223.68.20
    • 3.226.51.42
    • 3.228.39.114
    • 3.231.30.100
    • 3.232.208.125
    • 3.233.162.12
    • 34.193.3.49
    • 34.195.9.141
    • 34.196.135.143
    • 34.196.16.45
    • 34.198.216.84
    • 34.206.124.182
    • 34.224.107.199
    • 34.225.12.181
    • 34.232.12.160
    • 34.234.105.5
    • 34.234.232.36
    • 34.238.5.63
    • 35.169.38.241
    • 35.173.22.28
    • 52.0.126.79
    • 52.202.228.190
    • 52.21.255.218
    • 52.45.167.204
    • 52.55.85.134
    • 52.73.196.23
    • 54.144.146.170
    • 54.152.138.62
    • 54.156.169.83
    • 54.156.222.106
    • 54.159.142.195
    • 54.209.85.253
    • 54.211.234.108
    • 54.211.47.250
    • 54.226.222.167
    • 54.86.117.3
    • 54.87.167.185

Twilio STUN/TURN servers (only used if IPs/Hostnames/Protocols above are blocked)

Jigsaw Whiteboard integrated "Equation Editor" (via 3rd party vendor WIRIS)

Note:  this will only prevent the Equation Editor from working.

Jigsaw Instrumentation Logs v1 (will be replaced by RTA)

Note:  this will only prevent the Instrumentation Logs v1 from working.

Articles in this section

Was this article helpful?
12 out of 46 found this helpful
Share