Question regarding remote commands through GPRS (not SMS). In order for the commands to excecute imediatly, the tracker needs to be with a live connection to Ruhavik, my question is, how long does Ruhavik allow a connection to be alive before it closes the TCP connection? I ask this so that I can setup my tracker to ping Ruhavik around 10 seconds before Ruhavi´s connection timeout policy.

Thanks

  • rost replied to this.

    Hello, jcvillalobos ,

    This is how we work on our side. The idle time of a TCP connection is how much time has passed since the last time data was sent or received on it. So, if the connection is not authorized, then after 30 seconds of inactivity, we close it. This is necessary to quickly close hanging connections and get rid of various attacks.
    But all trackers that immediately after connecting send their ident(ID) and the connection becomes authorized, and another timer starts to operate - 10 minutes.
    Each tracker has different settings, but I think everyone has something to keep the connection going, so make sure to send heartbeat or ping packets every 9-10 minutes for example, or just that connections are always sent at least once every 9-10 minutes . In general, this should work.

    However, our recommendation is still to configure sending of connection maintenance packets once every 1 minute, it will be much more reliable this way. In GPRS communications, mobile operators can do anything weird.

    If you are afraid for traffic, then turn on sending at intervals of a minute for several days and then look at the traffic consumption, and if it is small, then leave it for 1-2 minutes.