![]() Server-initiated communication may only be used by 4500 devices that do not support the device-initated communication protocol. The server-initiated communication protocol requires the setup, configuration, and ongoing management of a VPN. A Virtual Private Network (VPN) is not required for devices using the device-initiated communication protocol.ĭevice communication is initiated by the host application server. Device Manager requires device-initiated communication for all devices that support it. This protocol can provide secure communication over the open Internet. Select the communication mode that is used for interactions between the server and the device: Protocolĭevices initiate all communication between the terminal and Device Manager. Click Tap Save to save your edits or click tap Cancel to dispose of them.See Device and Profile view template save options for more information.) Select one of the guided Save changes to options.It should contain the name of a template that you are editing or the unique name of the template that you are creating. Ensure that the Name field is not blank.Required fields are marked by an asterisk (*). The Communications Settings template is usually the first template configured for a new device because it is the one that is required to validate connectivity and communications between UDM Universal Device Manager manages the configuration of terminals and communication with the system. and the device.Įdit the fields in these tabs. ![]() Use the Communication Settings template to establish the communication protocol, server SSL setting, primary server and server port, primary instance ID, NetCheck interval, download retries, data collection mechanism, and device-initiated authentication. Communication settings control how the device and the Universal Device Manager (UDM) Manages the configuration of terminals and communication with the system.
0 Comments
Leave a Reply. |