Indeed, as Rainbow is growing, we must add new IPs, URLs and protocols when adding new servers, location, or features.
In any case of addition, we will update this document 7 days before activating new servers and services to let you time to configure your edge security equipment.
Note:
Edition 31 changes are highlighted in Green in the document:
-
Addition of new public IP addresses and servers in US /EMEA /DE.
-
Rainbow Clients/SDK - WebRTC conferences (for reverse DNS only)
-
rtc-sbg1.openrainbow.com to rtc-sbg10.openrainbow.com
rtc-gra17.openrainbow.com to rtc-gra26.openrainbow.com
rtc-lim23.openrainbow.com to rtc-lim32.openrainbow.com
rtc-rbx29.openrainbow.com to rtc-rbx38.openrainbow.com
rtc-vin13.openrainbow.com to rtc-vin16.openrainbow.com
-
- Load balancers
Germany 54.37.95.41 ; 51.195.21.111
-
- Turn media relays
51.195.68.2 ; 51.195.1.23
-
- Conferencing Media Servers
North America 15.204.13.228 ; 51.81.232.190 ; 51.81.224.231
Europe / France 178.32.113.157 ; 178.32.106.141 ; 178.32.116.183 ; 178.32.117.70 ; 178.32.111.240 ; 178.32.115.136 ; 178.32.113.191 ; 178.32.116.101 ; 178.32.108.79 ; 178.32.114.250 ; 178.32.104.245 ; 178.32.114.56 ; 178.32.107.241 ; 178.32.113.83 ; 178.32.106.248 ; 178.32.116.5 ; 178.32.116.254 ; 178.32.116.147 ; 87.98.184.126 ; 178.32.114.241 ; 178.32.113.111
Europe / Germany 51.89.1.152 ; 51.38.121.160 ; 51.89.124.29 ; 51.89.124.22 ; 51.89.95.97 ; 51.38.117.99 ; 51.75.84.169 ; 51.75.84.149 ; 51.89.121.223 ; 51.38.104.132 ; 54.37.194.109 ; 51.89.95.80 ; 51.195.67.96 ; 51.195.32.12 ; 51.195.68.28
Summary of ports/protocols requirements:
Rainbow Collaboration
The table below gives minimum requirements for deployment of Rainbow as a collaboration solution, without telephony services.
|
Protocol |
Port |
Main use |
Source |
Destination (a) |
|
TCP |
443 |
Signaling, APIs Messaging, filesharing |
All Rainbow clients and applications |
*.openrainbow.com openrainbow.com openrainbow.io |
|
UDP (b) |
3478 |
Audio/video/desktop sharing media |
All Rainbow clients |
*.openrainbow.com |
|
TCP (c) |
5228-5229-5230 |
Android push notif |
Pure wifi Android devices |
Google FCM servers |
|
TCP (d) |
443, 5223, 2197 |
Apple push not |
Pure wifi iOS devices |
Apple APNS servers |
(a) details on FQDN and IP addresses of Rainbow servers are provided in section 5
(b) the solution can fall back on TCP/443 if the infrastructure does not allow UDP (UDP remains highly recommended for best quality of service for multi-media flows)
(c) Google requires that if the network implements Network Address Translation (NAT) or Stateful Packet Inspection (SPI), a 30 minute or larger timeout is maintained for FCM connections over ports 5228-5230 Google Reference: https://firebase.google.com/docs/cloud-messaging/concept-options
(d) Apple reference: https://support.apple.com/en-ph/102266
Rainbow Hybrid Telephony
The table below gives minimum requirements for deployment of Rainbow on top of an existing customer PBX, providing telephony services and optionally advanced collaboration services.
|
Protocol |
Port |
Main use |
Source |
Destination (a) |
|
TCP |
443 |
Signaling, APIs Messaging, filesharing |
All Rainbow clients and applications WebRTC Gateway PBX |
*.openrainbow.com openrainbow.com openrainbow.io |
|
UDP (b)(c) |
3478 |
Softphony with remote users Audio/video/desktop sharing media for collaboration |
All Rainbow clients WebRTC Gateway |
*.openrainbow.com |
|
TCP (d) |
5228-5229-5230 |
Android push notification |
Rainbow on pure wifi Android devices |
Google FCM servers |
|
TCP (e) |
443, 5223, 2197 |
Apple push not |
Pure wifi iOS devices |
Apple APNS servers |
(a) details on FQDN and IP addresses of Rainbow servers are provided in section 5
(b) the solution can fall back on TCP/443 if the infrastructure does not allow UDP (UDP remains highly recommended for best quality of service for multi-media flows)
(c) the NAT gateway implemented between the WebRTC Gateway and Rainbow must avoid too fast reuse of WAN ports. This can be achieved by implementing a 10mn timeout on NAted connection. See note of section 4.6.1 for details.
(d) Google requires that if the network implements Network Address Translation (NAT) or Stateful Packet Inspection (SPI), a 30 minute or larger timeout is maintained for FCM connections over ports 5228-5230 Google Reference: https://firebase.google.com/docs/cloud-messaging/concept-options
(e) Apple reference: https://support.apple.com/en-ph/102266
Rainbow Hub
The table below gives minimum requirements for deployment of the Rainbow Hub solution. The latter provides cloud telephony services and optionally advanced collaboration services.
|
Protocol |
Destination Port |
Main use |
Source |
Destination (a) |
|
TCP |
443 |
Signaling, APIs Messaging, filesharing |
Rainbow applications
|
*.openrainbow.com openrainbow.com openrainbow.io |
|
UDP |
3478 |
Softphony Audio/video/desktop sharing media |
Rainbow applications
|
*.openrainbow.com |
|
TCP (b) |
5228,5229,5230 |
Android push notif. |
Rainbow on pure wifi Android devices |
Google FCM servers |
|
TCP (c) |
443, 5223, 2197 |
Apple push notif. |
Rainbow on pure wifi ios devices |
Apple APNS servers |
|
TCP |
5061 |
SIP |
SIP devices |
*.openrainbow.com |
|
TCP |
443 |
Config and APIs |
SIP devices |
*.openrainbow.com |
|
UDP |
30000-44999 |
SRTP media |
SIP devices Rainbow applications (softphony) |
*.openrainbow.com |
|
UDP |
53 |
DNS |
SIP devices |
DNS server |
|
UDP |
123 |
NTP |
SIP devices |
pool.ntp.org |
(a) details on FQDN and IP addresses of Rainbow servers are provided in section 5
(b) Google requires that if the network implements Network Address Translation (NAT) or Stateful Packet Inspection (SPI), a 30 minute or larger timeout is maintained for FCM connections over ports 5228-5230 Google Reference: https://firebase.google.com/docs/cloud-messaging/concept-options
(c) Apple reference: https://support.apple.com/en-ph/102266
Comentarios
1 comentario
Thank you for the new edition of this document. Please consider adding a chapter for WiFi requirements. This will be useful for users with Rainbow on a mobile phone or even on a laptop and for remote workers.
El artículo está cerrado para comentarios.