ResolveGrid Assist Firewall Settings

In this article we will go over the connectivity requirements of ResolveGrid needed by the network. If the ResolveGrid Assist app does not seem to connect when you log in, you’ll want to confirm that you have no network issues. If your connection is good but still does not seem to connect you may need to provide your IT team managing the network with this guide. By missing any of the following network port connection requirements might lead to a poor or problematic experience.  

CareAR Authentication Firewall Requirements

These are the connections outside of media traffic that are necessary for the optimal ResolveGrid experience. These remain the same regardless of Proxy, joining application, and Media Geofencing configuration.  

ResolveGrid Media Firewall Requirements (Installed Application)

When a ResolveGrid session is initiated, all users need to establish connectivity to transmit audio between participants, the camera of the collaborator, and the annotations placed. To accomplish this portion of the session is handled with the following media connections.

When using Media Geofencing your connection will utilize servers within the selected region using the *.agora.io domain.  

ResolveGrid Media Firewall Requirements (Web Host)

When joining a ResolveGrid session as the host through the web app will utilize a different series of connections than the installed application for media traffic. To establish proper connectivity the following connections are utilized: 
 

Need to refine Firewall controls further?

In some situations the firewall administrator may prefer a more restrictive firewall rule set over ideal connectivity. This is achievable through the media proxy service (configurable on the /admin page of the Resolve Grid tenant). To view these more restrictive firewall rules please visit our media proxy firewall guide available here: Media Proxy Firewall Configurations  

ResolveGrid Media TCP failover Mechanism

In the event the ResolveGrid application is deployed or launched in an environment that does not have the necessary firewall ports opened and the ResolveGrid tenant is configured to have media proxy off enables an alternative chance to still join the ResolveGrid session. In this scenario the ResolveGrid application will attempt a join workflow of TCP failover. In this mechanism instead when, and only when, the high range ports fail to establish port connectivity the client will further attempt to connect to 443 TCP instead. If any of the high range ports did establish port connectivity then TCP failover will not be attempted.  
 

In this TCP failover mechanism all the media traffic that would typically occur on the high range TCP and/or UDP ports will consolidate to 443 TCP streams instead.

Please note this is only for the media connection of the journey. The TCP failover mechanism will not be done on other events of the application such as Auth, Storage, Realtime Database, and so forth. TCP failover will also not be available to endpoint types that have Media Proxy set to on (configuration for host or guest inside of /admin). 

ResolveGrid System Emails

ResolveGrid utilizes email to process certain user-initiated actions. These emails are to facilitate session invitations, new user account creation, and password resets. ResolveGrid utilizes the following email addresses to serve these requests: 

If your email system has email filtering you may need to whitelist these addresses to assure emails do not move to spam or junk.  

The ResolveGrid System emails are generated during the following events:

Sender IP Address

Emails that are coming from the sender service@resolvegrid.ai are configured to inbound from 159.183.166.109.

Bandwidth Requirements

ResolveGrid sessions require at least 500 Kbps to maintain connection. Having more bandwidth than this can allow for an even better experience.