What are Rainbow Network Requirements? [EN]

This article provides technical requirements to connect Rainbow clients and Agent to Rainbow Cloud services.

USED PROTOCOLS

The Rainbow solution provides multiple client-side applications to connect to the service:

All applications aim at providing the same level of services and features and interact with server-side components the following way:

Through HTTPS (443) for all REST API communications and resources loading.
Through secure Web Sockets (WSS, 443) for all XMPP messages and notifications.
Through DTLS and SRTP with or without STUN/TURN for WebRTC-based audio/video media streams.

CONNECTIONS AND PORTS USED

Depending on the presence of an HTTP Proxy (Web Proxy), following connections take place between Rainbow client/Agent and Rainbow Cloud Services

Protocols	No Proxy	HTTP Proxy configured
HTTPS (Resources and REST API)	Direct, TCP port 443	Enforced through the Proxy, TCP port 80/443
Web Sockets (XMPP)	Direct, TCP port 443	WebSocket, enforced through the Proxy, via HTTP switch, TCP port 443
ICE/TURN(s)	Direct, TCP ports 80 and 443	Enforced through the proxy via HTTP Connect tunnel TCP port 80 or 443
DTLS-SRTP (Media)	Direct, TCP or UDP, dynamic port range (49152 – 65535) for local call, TCP/port 80/443 for Wan if turn is used	Encapsulated in TURN, enforced through the proxy via HTTP Connect tunnel TCP port 80/443

DOMAIN USED

Rainbow cloud services use the following domains

Used by	Purpose	Domains
Rainbow Clients	Resources (website, images, client package, Agent package, …)	web.openrainbow.com
Rainbow Clients	REST API	openrainbow.com
Rainbow Clients	XMPP over Secured WebSockets	openrainbow.com
Rainbow Clients	STUN/TURN	turn-eu1.openrainbow.com turn-na1.openrainbow.com turn-as1.openrainbow.com turn-oc1.openrainbow.com