Technical Requirements for the Local Operator
Version 2.1 as of April 17th 2025
Local Operator works directly on the Connector
The Local Operator works directly on the connector. This is a change compared to earlier versions of the roclub connector which required the RIS PC to run the roclub app in a browser.
The new version of the connector is capable of starting a video conference with the Remote Operator, granting access to the scanner and using other functions of the roclub app to support the workflow. Up to three webcams (e.g. for the local operator, examination room and contrast media injector) can be connected to the connector via USB and integrated into the video conference.
Local Operator works on a RIS PC
To maximize the benefits of the roclub platform, Local Operators can set up an additional PC to access a full range of features beyond direct connector operation. This setup enhances collaboration, workflow efficiency, and support management.
With an additional PC, Local Operators as well as Dispatchers can:
- Monitor Scanner Activity: Keep an overview of active and upcoming scans.
- Communicate Seamlessly: Use chat functions before, within and outside of remote sessions.
- Share Examination Information Efficiently: Exchange and access information about the remote examination at hand.
- Manage Schedules: Utilize the calendar function to coordinate workforce management and workflows.
- Organize Teams: Oversee team structures. Add new members to the organization’s roclub account, edit and assign roles, as well as delete members from the roclub App.
- Request Support: Submit tickets directly to the roclub support team.
- Customize Preferences: Adjust user settings and profile preferences for a personalized experience.
Hardware Requirements
The workstation of the Local Operator at the scanner must be equipped with a PC to use the browser-based roclub app. Normally, the RIS PC can be used, provided it is connected to the internet and meets the following requirements:
- Processor: At least Intel Core i5 (10th Generation) or equivalent. Thin clients are not powerful enough for video conferencing.
- Memory: Minimum 8 GB RAM
- Operating System: Current, supported Windows (Windows 10 or 11) or Mac OS (macOS 13 or above)
- Monitor: Any resolution works. We recommend at least 1920 x 1200.
- Browser: Latest version of Chrome (Version 132 or above) or Microsoft Edge (Version 131 or above). The internet browser must be natively installed on the PC to connect USB webcams and audio devices – this is not easily possible via Remote Desktop.
- Webcams: Up to 3x webcams (e.g. Logitech Brio 4k or Logitech C920s).
- Speaker/Microphone: Conference speaker, e.g. Jabra Speak 510 or alternative speaker combination for webcam conferences (e.g. Logitech CONFERENCECAM CONNECT).
Note
Please be advised that incognito/InPrivate windows do not support all features required for the roclub App. Only use standard browser windows.
Network Requirements
Bandwidth
- At least 10 MBit/s download
- At least 10 MBit/s upload
NAT Configuration
Network Address Translation (NAT) can become particularly complex in scenarios involving symmetric NAT, where the translation of IP addresses and ports is dependent on both the source and destination. This behavior often complicates peer-to-peer communication and other network-dependent applications. For a more detailed explanation and guidance on configuring NAT in such environments, please refer to the comprehensive documentation available here: NAT Configuration.
Simplified Firewall Configuration
Simplified
Ensure unrestricted access to the public internet for the Local Operator or unrestricted communication through 443/TCP
Restrictive Firewall Configuration
In case you require a restrictive configuration of the Local Operator's firewall which blocks incoming or outgoing connections, it is necessary to whitelist specific endpoints used by the roclub teleoperation platform. The endpoints given below are the minimum requirements for the teleoperation platform to function. Please keep in mind that these endpoints may change, requiring manual updates to maintain product functionality.
Please also note that the connections for the video conferencing sessions vary depending on the Local Operator's geographical location. Globally required and location-dependent endpoints need to be accessible.
Globally required
Application
| Domain/FQDN | Purpose | Port |
|---|---|---|
| 139649709.fs1.hubspotusercontent-eu1.net | CDN for HubSpot (CRM) | 443/TCP |
| a92bd6013fd6568889a25f9ebd11f11c.cdn.bubble.io | CDN for Bubble.io applications | 443/TCP |
| api-eu1.hubspot.com | HubSpot (CRM) API endpoint | 443/TCP |
| api.flusk.eu | Security Monitoring API service | 443/TCP |
| app.hubspot.com | HubSpot (CRM) | 443/TCP |
| app.roclub.io | roclub application hosting | 443/TCP |
| cdn.jsdelivr.net | CDN for JavaScript libraries | 443/TCP |
| cdn.quilljs.com | CDN for Quill.js rich text editor | 443/TCP |
| cdn.releasenotes.io | CDN for sending out Release Notes | 443/TCP |
| cdnjs.cloudflare.com | Cloudflare CDN for JavaScript libraries | 443/TCP |
| controlplane.roclub.io | roclub API (Session/Connector Management) | 443/TCP |
| cta-eu1.hubspot.com | HubSpot (CRM) call-to-action service | 443/TCP |
| d1muf25xaso8hp.cloudfront.net | AWS CloudFront CDN resource | 443/TCP |
| d2tf8y1b8kxrzw.cloudfront.net | AWS CloudFront CDN resource | 443/TCP |
| embed.novu.co | Novu embeddable notifications service | 443/TCP |
| feedback-eu1.hubapi.net | HubSpot (CRM) feedback API | 443/TCP |
| fonts.googleapis.com | Google Fonts service | 443/TCP |
| fonts.gstatic.com | Google Fonts static resources | 443/TCP |
| forms-eu1.hscollectedforms.net | HubSpot (CRM) forms collection | 443/TCP |
| ipv4.geojs.io | GeoIP lookup service | 443/TCP |
| identity.roclub.io | roclub 0-Auth-2.0 Identity Service | 443/TCP |
| js-eu1.hs-analytics.net | HubSpot (CRM) analytics JavaScript | 443/TCP |
| js-eu1.hs-banner.com | HubSpot (CRM) banner scripts | 443/TCP |
| js-eu1.hs-scripts.com | HubSpot (CRM) scripts | 443/TCP |
| js-eu1.hscollectedforms.net | HubSpot (CRM) forms JavaScript | 443/TCP |
| js-eu1.hsforms.net | HubSpot (CRM) forms | 443/TCP |
| js-eu1.hubspot.com | HubSpot (CRM) JavaScript resources | 443/TCP |
| js-eu1.hubspotfeedback.com | HubSpot (CRM) feedback widget | 443/TCP |
| js-eu1.usemessages.com | HubSpot (CRM) messaging scripts | 443/TCP |
| meta-q.cdn.bubble.io | Metadata CDN for Bubble.io | 443/TCP |
| meta.cdn.bubble.io | Metadata CDN for Bubble.io | 443/TCP |
| monitor-v1.flusk.eu | Security monitoring service | 443/TCP |
| notify.bubble.io | Bubble.io notification service | 443/TCP |
| perf-eu1.hsforms.com | HubSpot (CRM) forms performance tracking | 443/TCP |
| plst237.s3.amazonaws.com | AWS S3 storage for PLST resources | 443/TCP |
| plugin-api.s3.amazonaws.com | AWS S3 storage for plugin API resources | 443/TCP |
| roclub.releasenotes.io | RoClub release notes hosting | 443/TCP |
| s3.amazonaws.com | AWS S3 storage service | 443/TCP |
| share-eu1.hsforms.com | HubSpot (CRM) forms | 443/TCP |
| static.hsappstatic.net | HubSpot (CRM) static content | 443/TCP |
| t.clarity.ms | Microsoft Clarity analytics service | 443/TCP |
| track-eu1.hubspot.com | HubSpot (CRM) tracking | 443/TCP |
| unpkg.com | CDN for npm packages | 443/TCP |
| websocket.prd.roclub.io | roclubs user online tracking service | 443/TCP |
| widget.releasenotes.io | ReleaseNotes.io widget hosting | 443/TCP |
| www.clarity.ms | Microsoft Clarity analytics service | 443/TCP |
| xk6y-5dsj-4bvg.f2.xano.io | Database Service | 443/TCP |
Video Conferencing
The following domains enable the video conferencing service.
| Domain/FQDN | Verwendung | Port |
|---|---|---|
| roclub.livekit.cloud | Video Conferencing | 443/TCP |
| *.host.livekit.cloud | TURN/UDP servers that assist in establishing connectivity | 3478/UDP |
| * | (optional) UDP connection for WebRTC | 50000-60000/UDP |
Location-dependent endpoints
In addition to the globally required endpoints, location-dependent endpoints are also necessary. To ensure the best possible performance in your video conferences, we use globally distributed video conferencing services. This guarantees fast and smooth teleoperation performance.
Europe
| Domain/FQDN | Verwendung | Port |
|---|---|---|
| ofrankfurt1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| ofrankfurt1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| omarseille1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| omarseille1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| olondon1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| olondon1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| roclub.ofrankfurt1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.ofrankfurt1b.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.omarseille1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.omarseille1b.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.olondon1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.olondon1b.production.livekit.cloud | Video Conferencing | 443/TCP |
Asia
| Domain/FQDN | Verwendung | Port |
|---|---|---|
| otokyo1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| otokyo1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| osingapore1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| osingapore1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| omumbai1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| omumbai1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| odubai1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| odubai1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| roclub.otokyo1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.otokyo1b.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.osingapore1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.osingapore1b.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.omumbai1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.omumbai1b.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.odubai1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.odubai1b.production.livekit.cloud | Video Conferencing | 443/TCP |
North America
| Domain/FQDN | Verwendung | Port |
|---|---|---|
| ophoenix1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| ophoenix1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| oashburn1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| oashburn1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| ochicago1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| ochicago1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| roclub.ophoenix1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.ophoenix1b.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.oashburn1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.oashburn1b.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.ochicago1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.ochicago1b.production.livekit.cloud | Video Conferencing | 443/TCP |
South America
| Domain/FQDN | Verwendung | Port |
|---|---|---|
| osaopaulo1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| osaopaulo1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| roclub.osaopaulo1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.osaopaulo1b.production.livekit.cloud | Video Conferencing | 443/TCP |
Africa
| Domain/FQDN | Verwendung | Port |
|---|---|---|
| ojohannesburg1a.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| ojohannesburg1b.turn.livekit.cloud | TURN/TLS. Used when UDP connection isn't viable | 443/TCP |
| roclub.ojohannesburg1a.production.livekit.cloud | Video Conferencing | 443/TCP |
| roclub.ojohannesburg1b.production.livekit.cloud | Video Conferencing | 443/TCP |
See also:
Technical Requirements for the Connector
Technical Requirements for the Remote Operator