Inquiry regarding communication between InRobot server and our client PC

Hi, thanks for reaching out. We have this overview of the URL and what connections are needed: 

 

1. Download docker images:

   • URL: registry-1.docker.io
   • Protocols: HTTPS, TCP
   • Ports: 443

2. Video stream:

   • URLs: eu.robotics.cognitedata.com OR us.robotics.cognitedata.com
   • Protocols: RTP, UDP
   • Ports: 20000-40000, 5000-5050

3. Video signaling:

   • URLs: eu.robotics.cognitedata.com 
   • Protocols: HTTPS, TCP
   • Ports: 443

4. Cognite API:

   • URLs: {cognite cluster}.cognitedata.com (example: api.cognitedata.com)
   • Protocols: HTTPS, GRPC, TCP
   • Ports: 443

5. Azure auth:

   • URL: login.microsoftonline.com
   • Protocols: HTTPS, TCP
   • Ports: 443

The laptop using InRobot will also need to have whitelisted: Video stream, Video signaling, Cognite  and Azure auth. I have also added a architecture drawing where you see the interaction between Inrobot, CDF, videostream and the robot. 
 

In addition I would recomend using firefox for debuging. If you visit “about:webrtc” url on firefox you get to a webrtc debugging tool where you can see what is failing for your webrtc connection. Then you can see if it is the signaling or stream which is failing and thus what ports that are blocking. If you also share a screen shot we could potentially help and have a look

https://www.webrtc-developers.com/debugging-webrtc-in-the-browsers/#firefox-aboutwebrtc

Hope this information helps and thanks againg for reaching out! 

Thank you for providing us with the information and the architecture drawing. We have reviewed the details and have a few follow-up inquiries and concerns regarding the video streaming communication.

Firstly, although we have already whitelisted the Video Streaming communication, we are still unable to view the video feed within the application. Furthermore, your Japanese support team had identified packet loss occurring within your server logs. We would appreciate further guidance or troubleshooting steps to resolve this issue.

Regarding the system architecture diagram, it appears that WebRTC communication is established from the Enterprise WebRTC media server to the client PCs. We would like to confirm if this interpretation is correct. Allowing communication from the internet to our internal LAN violates the security policies defined within our organization. We need to make any communication with external resources adhere to our established security guidelines. Therefore, Understanding the establishment of the session between the Enterprise WebRTC media server and the client PCs is of importance to us. Could you please provide detailed insights into how this session is established? Additionally, I want to highlight that I do not have our global IP address configured within InRobot App. Consequently, I believe it is not possible for the Enterprise WebRTC media server to establish a session with the client PCs directly.

Thank you for your continued support and prompt attention to our concerns. We eagerly await your response and any further assistance you can provide.

Thank you for the detailed response and explanations regarding the Video Streaming using the WebRTC media server. We greatly appreciate your assistance in clarifying the communication process.

To ensure we have a complete understanding, could you please confirm whether the session setup for Video Streaming occurs from the LAN to the internet? Understanding the direction of this communication will help us verify if our firewall blocks the Video Streaming. We noted that even in cases of bidirectional communication, if the session is established from the LAN to the internet direction, the firewall does not block the traffic. In our experimentation environment, we have confirmed that despite internet-to-LAN communication being blocked by our firewall, we are still able to utilize the Video Streaming feature of InRobot.

In our experimentation environment, the firewall passes all communication from the LAN to the internet, while blocking all traffic from the internet to the LAN. On the other hand, within our internal LAN, the firewall only passes HTTP/HTTPS communication from the LAN to the internet, and all incoming traffic from the internet to the LAN is blocked.

Given these firewall configurations, it appears that the firewall settings in our internal LAN are likely the cause of Video Streaming not functioning properly within our corporate network. Specifically, the limited permission for LAN-to-Internet communication other than HTTP/HTTPS within our internal LAN may be preventing the necessary communication required for Video Streaming in InRobot.

Once again, we appreciate your support and expertise in resolving these technical matters. Your continued guidance is highly valued.

Hello,

I would be grateful if you could let us have your answer concerning this matter. Could you please provide me with an update on the status of this matter?

Irie, 

So sorry for the late reply! 

I have reached out to our engineers again to get a propper answer, will get back to you as soon as possible. 

Hi Irie,

Yes, your analysis seems reasonable. 

To help us understand the problem better and to confirm your analysis, could you run the following web test and share a screenshot (ideally in your internal and experiment environment)? https://networktest.twilio.com/ 

These tests check your browser and network configuration with respect to WebRTC. We are moving our video streaming service to Twilio, and these network tests will test basic- as well as Twilio-specific requirements. This will confirm whether the initial signalling works (which is LAN → internet), as well as the UDP and TCP or TLS connectivity for the resulting session. 

Thank you again for your patience.

Hi @Irie, do you need any further help from us?

Thank you for your support and the suggested web test. I appreciate your assistance in resolving the Video Streaming issue.

I will perform the tests as you've recommended. Please allow me some time to complete them.

Your patience is greatly appreciated, and I'll keep you updated on the progress and results.