Networks that allow TLS traffic by default should not need to explicitly allow CDN properties. However, for more restrictive environments where destinations outside your network must be specified, please reference the table below:
Networks that allow TLS traffic by default should not need to make allowances for API properties. However, for more restrictive environments where destinations outside your network must be specified, please reference the table below:
firestore.googleapis.com (signaling service):
Will not function properly if traffic to this domain passes through a proxy. As proxies typically do not handle persistent connections correctly (waiting for a full response from destination before flushing), the proxy should be configured to bypass this domain.
turn.us-east-1.socialive.us (STUN/TURN and NAT traversal):
Will not function properly if traffic to this domain passes through a proxy. The proxy should be configured to bypass this domain.
The IPs in the below table are used to facilitate the transmission of real-time media in the browser. In restrictive networks where destinations must be explicitly allowed, all IPs and corresponding port ranges below should be allowed.
RTP over UDP protocols are addressed in this document. SRTP is not a protocol. It is a profile for Real-time Transport Protocol (RTP) intended to provide encryption, authentication and integrity. Socialive uses SRTP for our WebRTC communications over RTP/UDP.