The Host URL setting of the iTrac device determines where the host web service is located. For use that is only within the building accessing via a wireless connection, this address can be the local IP address of the server. However, if the device is a phone and the user leaves the wireless area, the phone will change to the cellular network. If this happens, the local address will no longer work.
If the Host URL setting of the iTrac cell phone device is set to the public IP address, then the router will require a port forwarding from the Internet modem to the server hosting the web service. However, if the cell phone moves into the building and is allowed to jump onto the wireless network, then the public IP will no longer work because it will be looking outside of your network.
If you need to support both inside and outside access with the ability to move between either, then a DNS needs to be set up. For example, you would use a Host URL such as “iTrac.mycompany.com”, which is then translated into the public IP from a DNS service. A free DNS service is available at www.no-ip.com. Whether inside the wireless network or originating from the public cellular network, the address goes out to the public network to resolve to your public IP and then back into your modem to be routed to the server.
The iTrac device must have a solid connection to the network when the employee initially logs in. However after login, the network connection could be intermittent because the device holds the transactions until a network connection is made.
When an iTrac transaction is made, the transaction is entered into the History log in red text to indicate that the transaction is pending and has not yet been sent to the host. After the transaction has been sent to the host, the text color is changed to black. This allows the user to easily see if there are pending transactions that need to be sent. When the device comes back into network, all pending transactions are automatically sent.
It is important that the device be brought back into network at the end of the work period so that the End Day transaction can be sent. If the End Day event is not sent by the time a TracManager user attempts to approve the timesheet then the TracManager software may automatically end the employee’s day so that the timesheet can be processed.