![]() A fiber internet connection is preferred. * If you plan to host 2 or more clients we recommend a 50Mbps minimum. Ping lower than 15 ms to server in same city as host.30Mbps download and 2Mbps upload speed or better via.Ping lower than 30ms to server in same city as host.10Mbps download and 2Mbps upload speed or better via.No Wi-Fi signal boosters, Ethernet over power line devices or mesh Wi-Fi systems.No downloads or uploads running in background.5Ghz Wi-Fi connection or Ethernet connection to router.For additional details on the Parsec Relay server, see the technical reference page. This greatly reduces attack surface as the only one port is exposed externally. The relay server only needs one port open externally, and one internally. The relay server is exposed to the web, so that clients can communicate with hosts through the relay - the relay server accepts incoming UDP packets from clients and relays them to the session host. The Parsec Relay server provides several benefits including additional security, simplified network configurations, and greater reliability when compared to the UPnP and basic NAT methods described above. It is possible, however, to leverage both the on-premises relay server, and our public STUN server as a fallback. This component is called the Parsec Relay server. ¹ Random by default, can be configured as static port.Įnterprise customers can choose to leverage an on-premises component that allows host computers to bypass communication to Parsec's public STUN server, keeping STUN communication internal to the corporate network. If fallback to Parsec's public STUN is not desired, the first and last two rules can be ignored as the session will not be P2P, but instead relayed through the relay server. If your organization leverages the Parsec Relay server, please see the technical reference page for additional networking requirements. Host and client must not be inside a "Double NAT" or CGNAT network.SSL traffic must not be decrypted using SSL inspection functionality on Firewall or security appliance. ![]() Firewall or security appliance must not block inbound/outbound TCP/UDP traffic from our applications.DNS must be able to resolve parsec.app and all sub domains, AWS S3 and Cloudfront.Here's how you set up a proxy with Parsec. Parsec API calls can be configured to work with your proxy if you'd like to put a proxy between the computer and the Parsec servers. Our Websocket API can be blocked to prevent non-Team accounts from hosting within your network, if you set up your own Team-specific domain. Bandwidth requirements for video conferencing vary depending on the software/platform you use, however the average seems to be about 2 Megabits/second both. All TCP traffic is encrypted and uses port 443, STUN UDP traffic uses port 3478, and the encrypted peer-to-peer UDP traffic uses port ranges specified in Parsec Settings or the configuration file. The Parsec application communicates with our backend via TCP, with our STUN server via UDP, and peer-to-peer with other Parsec hosts via UDP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |