What is KEEP-ALIVE = 300 and why you are afraid when its value is increasing in your Connection history?
The first line - CWS_KEEPALIVE sets the time in seconds after which the emulator MgCamd verifies connection to the server for car***aring spelled out in the port settings. Apply in the case of using NAT router, which disconnects inactive connections or when you open encrypted channels after the transition from open to them. In the second line CWS_INCOMING_PORT given port to listen for incoming connections from the server, this line can be omitted.
CWS_KEEPALIVE = 300 means that MgCamd keep an idle connection alive for 300 seconds (5 minutes).
Simply speaking, even in idle condition (stand-by mode), your receiver sends requests to the server in order the connection to the server to be uninterrupted.
Each 5 minutes, your receiver sends a service command to the server, and the server sends response to the receiver. In such a way, this connection is kept alive.
The value 300 is an optimum value, and don't worry that in your connections history, it may increase.
The main thing in your history is the line with No violations of server rules detected! statement.
It is good that the keep-alive value is increasing, it should be so. Opposite, if it is too low, it means that your receiver is sending too frequent requests. In this case, you will be notified that some rules are violated and you need to take measures to avoid being banned.
Recommended time of delay between keepalive requests sending is 300 seconds.
Extreme value - 60 seconds.
Users sending requests more frequently than 1 time per 60 seconds, will be marked in the connection history as violating rules. They also will see warning that keep alive parameter is wrong in their settings.
The users sending requests to the server once per 1-5 seconds, most likely will be banned.
