Configurethedeviceusing theweb interface System Configuration
Digi Connect Family and ConnectPort TSFamily
107
n
Connection Settings
n
Short Messaging
n
Advanced Settings
Connection settings
TheConnection settings configure how the Remote Manager-registered device connects to Remote
Manager. These settingsallow the Remote Manager-registered device and Remote Manager to
communicates with each other.
About Remote Manager connections
You can choose how your Remote Manager-registered device connectsto and communicateswith
Remote Manager: through a device-initiated Remote Manager connection or a (device-initiated) timed
connection. To illustrate how these types of connectionswork, the following image showsa
configuration scenario featuring Remote Manager-registered devicescommunicating over a cellular
network.
You can specify addresses for Remote Manager-registered devices that are publicly known, or private
and dynamic, or handled through Network AddressTranslation (NAT). NATreduces the need for a
large amount of publicly known IPaddressesby creating a separation between publicly known and
privately known IPaddresses. NATallows a single device, such as a router, to act asan agent between
a public network, such as the Internet or a wirelessnetwork, and a private, or local, network. This
means that only one unique IPaddressisneeded to represent an entire group of computers.
Addresseshandled through NATcan accessthe rest of “the world,” but “theworld” cannot access
them.
In a device-initiated Remote Manager connection, the Remote Manager-registered device connects to
the network, and tries to establish a connection to Remote Manager. To maintain the connection, the
Remote Manager-registered device sendskeep-alive messages over theconnection. You can configure
the frequency in which keep-alive messages are sent. You can use device—initiated Remote Manager
connectionsin any cellular network, whether using public or private IPaddresses, or even if using
NAT. Note that your cellular/mobile provider may charge you, depending on your cellular/mobile
service plan, when the Remote Manager-registered device sendskeep-alivesmessages.
Aserver-initiated Remote Manager connection works the opposite way. Remote Manager opensa TCP
connection, and the Remote Manager-registered device must be listening for the connection from
Remote Manager to occur. An advantage of server-initiated Remote Manager connections is that you
are not charged for sending the keep-alive bytesthat are used in device-initiated connections. A
disadvantage is that there isno way of knowing whether the devices displayed in the Remote
Manager-registered device list areoffline or connected. The device list showsall the devicesas
disconnected until Remote Manager doessomething to interact with them. In addition, you cannot
use Remote Manager connectionsfor devices that use private IPaddresses and are behind a NAT.
(Server-initiated connectionsare not supported.)
To Next Page
Loading...
Need help?
General
