Network Requirements for MobiControl
If you cannot remote-control or enroll your devices (add them to MobiControl), your network might be blocking communication between the devices and the MobiControl server.
The following lists the ports and IPs that should be opened:
Ports:
80
443
5494
The above ports should be open for the following IP addresses:
40.68.196.181
40.114.220.164
13.95.171.202
57.153.35.52
57.153.34.246
20.54.221.156
ds1.mobi.taskletfactory.com
ds1.mob2.taskletfactory.com
ds2.mob2.taskletfactory.com
Architecture overview for network and data communication *WORK IN PROGRESS*
In case of concerns or questions regarding communication on these ports and IPs, we have compiled the information below to address these needs.
Operational Data and Security
The production architecture with operational data is very simple since data flows between the Mobile Device and the SOAP Endpoint over HTTP(s). The Soap webservice is located on the ERP system, either in the cloud or on-prem, and the only requirement is that the mobile devices can communicate (back and forth) with this sole endpoint. The device management platform is not part of the operational data flow; it is solely a support system.
The mobile WMS will use the authentication provided by the ERP system, and the users set up in it.
Mobile device management
Tasklet uses Soti MobiControl as its device management platform, which is a cloud-hosted solution provided and maintained by Tasklet.
Deployment and updates
To ensure the device management platform can provision devices with software and configuration updates, the following technical requirements apply to the firewall.
Purpose | Port(s) | Direction | Notes |
|---|---|---|---|
Device → Deployment Server communication (primary) | 5494/TCP (Binary) | Outbound from device | Main MobiControl device-agent protocol |
Device → Deployment Server (HTTPS fallback) | 443/TCP | Outbound from device | Alternative path for agent connectivity |
Remote control and web access (Through Soti Mobicontrol)
These rules apply to administrators using the MobiControl Web Console to remote-control a device.
Remote Control involves two communication flows:
Admin browser → Management Server (Web Console)
Management Server / Web Console → Deployment Server (remote control channel)
Purpose | Port(s) | Direction | Notes |
|---|---|---|---|
Web Console access (HTTPS UI) | 443/TCP | Inbound to Management Server | Required for all console use including RC |
Remote Control channel | 5494/TCP | Inbound to Deployment Server | Mandatory for remote control sessions; RC uses Binary 5494 inbound |
Modern setup (New server for customers)
The deployment server is at the following addresses due to redundancy:
ds1.mob2.taskletfactory.com
ds2.mob2.taskletfactory.com
The management server is at:
mob2.taskletfactory.com
There is a legacy setup on mobi.taskletfactory.com used by a small subset of old customers. If information is required, it can be obtained by opening a ticket with the service desk.