Live view starts with Low resolution
-
UID connected cameras always start Live View with Low Resolution. LAN connected cameras start with the resolution that was selected last. How can this behaviour be changed so that remote cameras Live View always starts with the last selected resolution? [Windows Client v8.12.1]
0View 1 replies-
@mart-tob_723653357826278 This is how it is designed to work when connected from an external network. Assuming that you have done the installation and you run the Android/Win client. When you run the client it will send DNS queries to get the IPs of the P2P servers which are AWS/Azure. Client receives the DNS response for the 16 P2P servers ( not all used...some point to loop back IP...future expansion). Then the client sends a request to each P2P server with the UID of each camera. The P2P servers send the local IP of each camera together with a public IP on the P2P server. When the client receives these responses it will first start to establish communication using the private IPs and port 9000. If the client is on the same network as the camera then the camera will respond and communication will be established (TCP). Here the stored stream mode will be used as bandwidth is not an issue. Note that at regular intervals the camera sends a heart beat message to the P2P servers and from this message the P2P servers get the private IP of the camera and its assigned public IP/port on your BB router.
If, however, the client is on an external network, it will not receive any replies when using the private IPs and so it will use the public IPs. So the client will establish a session with the P2P Relay servers and the P2P server establishes a session with the camera (using the BB router public IP/port mentioned above). So the flow of media and messages is through the P2P servers and UDP is used as the transport prot. The P2P Relay servers don't have infinite bandwidth and this bandwidth is not free and so Reolink has to pay for it. So in order not to create congestion on the allocated bandwidth they opted to have the stream mode to default to FLUENT irrespective of what you set it before (my personal thinking). So here is a trade off.......
Note that media and messages are encrypted at both ends. The flow can easily be seen by capturing traces on the egress of the BB router using Wireshark. -
@joseph_1979 Thank you - that explanation about P2P servers makes sense. I have now tried a direct connection using IP/Domain name and port 9000 (having forwarded port 9000 on the camera's router). This time the resolution starts at Mid but seems to stick at High once it has been selected, which is preferable for my installation.
A further question - if more than one camera is to be connected, should the service port on each be changed from 9000 to say 9001, 9002, 9003 etc? And then adjust the port forwarding accordingly to forward cam1:9001 fw to 9001, cam2:9002 fw to 9002, cam3:9003 fw to 9003 etc? Or is it better to keep the service port for each camera at 9000 but adjust the port forwarding so that cam1:9000 fw to 9001, cam2:9000 fw to 9002, cam3:9000 fw to 9003? -
@mart-tob_723653357826278 You're welcome. The server port can be changed and you can assign different server port for each camera. Then use port forwarding in the BB router to route it to the respective camera. In this way you shall get the clear mode.
I recall testing this quite some time ago but I forgot whether I tried it locally. Maybe you can test it out.
-
