Client Connectivity and Function Test before Joining an Adobe Connect Meeting

Note: This article is intended for end user subscribers to check connectivity for Adobe Connect Meeting access. For a more extensive article aimed at Administrators and Network teams see: https://blogs.connectusers.com/connectsupport/adobe-connect-meeting-latency-running-webrtc-enhanced-audio-video/

• There are tests you may run within the Adobe Connect Domain.
  • Try this URL: https://arcps.adobeconnect.com/common/help/en/support/meeting_test.htm
  • Then try it again, but replace arcps.adobeconnect.com for your actual domain name: https://mydomainname.com/common/help/en/support/meeting_test.htm
• There is also a simple test for Enhanced WebRTC Meeting access. To test your WebRTC connection you may use this: https://webcasts.com/webrtc/

These are the required Ports for WebRTC Audio/Video:

• UDP ports 30000-65535: Real-time media (audio, video, screen sharing)
• UDP & TCP port 3478: STUN/TURN for NAT/firewall traversal
• TCP port 443: Fallback for HTTPS and TURN over TLS

Here are solutions some organizations have successfully implemented if connectivity is limited by restrictive network and client infrastructure:

• Virtual Desktop Infrastructure (VDI) / Virtual Environments
  • Employees log into a virtual desktop hosted in a less-restricted network zone
  • The VDI environment has proper firewall rules allowing WebRTC ports
  • From within some DoD networks, personnel listening can hear VoIP if they sign in using AVD workspace and type the conference link into a browser. (Copy and paste will not work).
  • This is the most common enterprise solution

• Guest Network / Separate Training Network
  • Organizations create a dedicated network segment with relaxed firewall rules for training purposes
  • Employees connect to this network when attending external training

• VPN to Home Network
  • Employees use personal VPN to route traffic through their home internet
  • Bypasses corporate firewall restrictions
  • Note: Some organizations prohibit this for security reasons

• Personal Devices on Personal Networks
  • Employees use personal laptops/tablets on their home WiFi or mobile hotspot
  • Last resort when corporate IT cannot make exceptions

• Adobe Connect Desktop Application
  • Some networks that block browser-based WebRTC may allow the desktop app
  • This is worth testing though both use similar protocols
  • The application can be installed directly or rolled out via MSI
  • https://helpx.adobe.com/adobe-connect/connect-downloads-updates.html
• Beyond the scope of the end user client, there are network level solutions: Proxy Exception / Firewall Exception
  • IT teams allow *.webrtc.adobeconnect.com and *.adobeconnect.com for the Adobe Connect Hosted environment. Reference your Adobe Connect domain name if your Meeting is hosted elsewhere. For example on Adobe Connect Managed Services, *.acms.com and if hosted in Government Cloud, *.gc.acms.com
  • Open the required UDP ports (3478, 30000-65535) for these domains
  • This is the ideal solution but requires IT approval

For additional information see: Firewall and Proxy Server Configuration for Adobe Connect 12