Digi WAN 3G User Manual page 133

Advanced remote management settings
The default settings for remote management usually work for most situations. These Advanced
settings are used in advanced situations. They are used to configure the idle timeout for the
connection between the Digi device and the remote management server, and the keep-alive settings
of the various interfaces (TCP and HTTP for mobile and Ethernet network connections). These
settings should only be changed when the defaults do not properly work.
Connection Settings: These settings configure the idle timeout for the connection

between the Digi device and the remote management server.
– Disconnect when Connectware Management is idle: Enables or disables the idle
timeout for the connection. If enabled, the connection will be dropped, or ended, after
the amount of time specified in the Idle Timeout setting.
– Idle Timeout: The amount of time to wait before timing out the connection.
Mobile Settings:

Ethernet Settings
WiFi Settings: These settings apply to client-initiated management connections over
mobile/cellular, Ethernet, and Wi-Fi networks.
– Connectware Management Protocol Keep-Alive Settings: These settings control how
often keep-alive packets are sent over the client-initiated connection to the remote
management server, and whether the device waits before dropping the connection.
Receive Interval: The number of seconds to wait for a keep-alive message from the
remote management server before assuming the connection is lost.
Transmit Interval: The number of seconds to wait between sending keep-alive
messages.
Important: It is recommended that this interval value be set as long as your
application can tolerate to reduce the amount of data traffic.
Assume connection is lost after n timeouts: How many timeouts occur before the
Digi device assumes the connection to the remote management server is lost and
drops the connection.
– Connection Method: The method for connecting to the remote management server.
TCP: Connect using TCP. This is the default connection method, and is typically
good enough for most connections. It is the most efficient method of connecting to
the remote server in terms of speed and transmitted data bytes.
Automatic: Automatically detect the connection method. This connection method
is less efficient than TCP, but it is useful in situations where a firewall or proxy may
prevent direct connection via TCP. Automatic will try each combination until a
connection is made. This connection method requires the HTTP over Proxy Settings
to be specified.
None: This value has the same effect as selecting TCP.
HTTP: Connect using HTTP.
HTTP over Proxy: Connect using HTTP.
C o n f i g u r e D i g i d e v i c e s
1 3 3