Posts made by joseph_1979

@f-pierresteguy_441320730525874 Due to battery constraint none of the battery operated cameras can be added to the NVR.

@robert-hammond_315369854550200 Yes, these are the MS C++ runtime libraries which come with the Visual Studio of 2015. Reolink Win client has been developed using Visual Studio (Recalling the time I used it to develop numerous applications esp IVR applications based on state machines).

@crimp-on_62210811129 eh he he......... I agree.

@cheropride-holopaw_627202696601603 Kindly email Reolink support who shall tell you what other options exist.

@dgordon42_415060065599711 The international network is a jungle and IP is based on best effort (CS0) unless being local where one has full control and prioritized traffic. Maybe when Japan Mobile operators NTT/KDDI/etc did the IR21 tests with Telstra this hasn't been rigorously tested out. Perhaps you can ask Telstra to do some data transfer tests with their Japanese roaming partners.

I had no issue to access my cameras from some European countries. If I had I ask for an immediate testing :).

@reolink-fiona This camera sees what our eyes can't see so clearly.

@dgordon42_415060065599711 WIFI and Mobile data are two distinct technologies but both can be integrated within IMS as one ecosystem. When you enabled the split tunneling feature the traffic between the client and the camera was routed through open Internet. Did you try to communicate with the camera with VPN completely disabled?

@joseph_1979 Unfortunately I had two instances where the E1 OD Pro failed to return to the configured guard position. On one instant it deviated by 60 degrees which is a lot. Reported to Reolink support.

@user_683805382926486_683805382926486 That's correct. So you have access to the cameras both directly and through the NVR. Note that through the NVR there might be some restrictions and so it is recommended to have such an access. However, if you want to remove the individual cameras, just delete them from the clients and leave the NVR.

@mjfreese86_436391733772417 Check out this link https://support.reolink.com/hc/en-us/articles/900000644286-Introduction-to-the-Working-Modes-and-the-Status-LED-of-Reolink-Go-PT-Go-PT-Plus/?gclid=Cj0KCQjwj_ajBhCqARIsAA37s0zGcxnrYtU_W4EmPs8ZkODdpwu646mSAtQfojAaoL5Mppdf00ANcuQaAm-sEALw_wcB

Most probably there is something wrong with the SIM. Are you able to extract the SIM? If yes then insert it in your phone, change the APN and check whether you are able to watch a youtube video. What did the T-mobile rep said? Did he check the IMSI attach and that in the HLR there is the anchored MME? Ensure that the 4G signal at the camera location is strong and if it handovers to 3G/HSPA then it will be difficult to communicate.

@user_701279314424005_701279314424005 Scenario 2 and use an HDMI splitter such as the Fonestar FO-554 HDMI splitter 1×4

@user_692864088391837_692864088391837 Battery operated cams do not have DDNS. Unfortunately the camera opens a random UDP port.

@alexis-pattein_669337290912125 Issue a request to Reolink support at https://support.reolink.com/hc/en-us/requests/new/

@melroy UID is like your ID number which is a unique identifier pointing to a number of profiles in various institutions. If you go to the hospital they will ask you for the ID and by entering this ID they will get all your health information.

When you power up your camera, it does some DNS queries to get the IP addresses (A record) of the P2P servers (provided by Amazon and Azure) and registers with the P2P servers using its UID (we are assuming here that UID is enabled). At regular intervals the camera sends packets to the P2P servers which shall include the UID (encrypted). The application on the P2P server decrypts the packet and extracts the UID. The application extracts the private IP and Public IP (BroadBand IP:Port) of the packet and populates them in the respective record associated with UID. If the camera changes IP then the record pointed out by the UID is updated accordingly. The credentials you created are not forwarded to the P2P servers. Well if you can emulate the P2P protocol and know the encryption method/phrase then you would be able to get the private and public IP of a particular UID. But so far there have been no such breaches and still you need the credentials to get access to the camera. Therefore it is imperative to follow the policies associated with passwords such as create a strong password and change it at regular intervals. At this point we see that there is a P2P socket between the camera and the P2P server. For your perusal the camera sends the alerts to the domain pushx.reolink.com. The application server will then forward the push message request to FCM (Android) or APNS (IoS) which shall push the message to your smartphone. Token provided by FCM to your smartphone on registration is forwarded to Reolink pushx application server. This token is included in the request made by this application server to the FCM to push the alert on your smartphone.

Now let's take a look from the client side. When you run the Reolink client, it will send a DNS query to 16 P2P servers (p2p1, p2p3, etc) and the response is the A record containing the IP address of the P2P server. Any P2P server which is not yet assigned will get the A record with the loop IP (127.0.0.1). For each working P2P server, the client requests the Public IP (the Relay P2P server with which the camera is connected) and Private IPs of the camera using destination port 9999. So if we have 8 working P2P servers and 8 cameras, then the client will send 64 requests over UDP. At the same time the client broadcast a packet with command aaaa0000 on the network with destination port 2000. Note that the Client broadcasts the packet with payload aaaa0000 using destination addresses 255.255.255.255.255 and 192.168.1.255 (or your configured IP subnet). Now 255.255. 255.255 is the limited broadcast address which is only propagated within the single subnet of the interface that sent it. It is never routed to other subnets unlike the subnet directed broadcast address 192.168. 1.255 which may be routed from elsewhere, depending on router configuration. So in most cases only the cameras within the same subnet receives this packet. If there are cameras on the same network they have port 2000 opened and are listening for any broadcast with command aaaa0000. If this is received then the camera will reply to the source IP with the command aaaa0000, UID, IP, port 9000, mac and ID. So once the client receives this on port 3000 then it will start communication with the camera using TCP and port 9000. Note that at this point the communication is directly between the client and the camera which are on the same network. At the same time the client also sends the request using the public IP. This public IP is not the public IP on your BB router but rather the IP of the AWS/Azure Relay P2P server to which the camera has been registered. But if communication using the private IP fails then the client establishes connectivity with this Relay P2P server. Recall that the camera has already a p2p socket opened with this server. Communication is over UDP. In my opinion, this has been adopted because a number of ISPs restrict users to connect directly to other devices. Technically this is not P2P as there is the Relay server in the middle. So in this case the encrypted packets flow from the client to the Relay server and from the Relay server to the camera and vice versa. In this case the encrypted credentials are sent to the camera through this Relay P2P server. And here comes a question....if there are 1000 12Mbps@25fps and using high def H.265 and the cameras are being accessed remotely using the public IP, then on the P2P relay servers we need a bandwidth of 17Gbps .......... which is really massive.....This explains the delay between viewing using private/local IP (cameras and client on same network) and public IP (other). And I do not think that neither Amazon nor Azure will give unlimited bandwidth.

Now the question being posed is 'Do we trust this setup?' Do you trust passing the bank information when buying over the internet? Do you trust ATM machines which are connected over BB? Do you trust your voice calls over 3G (A5/2 encryption)? etc etc.............. so you have the answer.

No matter how much security you have...there is always a way to get through. Even Alcatraz was a prison where nobody can escape...but they escaped. Nevertheless we need to do our best to protect and be secured.

Apologise for the lengthy answer...but this is high level...can go to the low level...ha ha these are rather simple protocols with the most complicated being within the Telco NEs.

@seb_526812765704330 We have requested the scene mode to have both a scheduler and a status. Moreover to be enhanced we asked for geofencing which shall toggle (if selected) the activation/deactivation of the scene mode automatically once we arrive or leave the premises.

@eddie_wedzinga_412993950507240 I have the WIFI version and have the volume control in the talk mode.

So ensure you have the recent firmware and using the latest client. Go to Reolink download center and check it out.

@brian-nielsen_442682315796643 We have requested the support team to inform dev team that a lot of customers are asking for the doorbell to do an outbound voip call to the smartphone with possible actions as is being done by other brands. Other than this we need the full profile T support with full duplex audio.

@myreolink_533265780207845 Definitely ftping the files to a remote physical/cloud ftp server is the best solution.

As for the encryption I have asked dev team to encypt the videos on both the SD and the NVR for a number of times. It is not only to protect but also to be protected. This is particular important for us to protect our privacy if such entities are stolen.

@robert-hammond_315369854550200 I was convinced that it does use the MS C++ library but I am away and don't have the notebooks.

@robert-hammond_315369854550200 I said either MS c++ or other dll library.