Direct Push Timeout
When direct push sessions are longer, there are fewer HTTP round trips, less data sent and received, and less power consumed by the device.
A direct push interval that is too short defeats the purpose of direct push technology. Not only do shorter intervals reduce overall connection time, but battery life is shortened as well. Consider this: In an hourís time, a device set with a 5-minute timeout will ping the server 10 times and be connected approximately 50 minutes out of that hour. The same device set with a 15-minute timeout will ping the server 4 times and be connected for approximately 57 minutes.
The length of direct push timeout intervals has no bearing on the functions of the NotifyLink Serverís direct push component. Messages are rapidly delivered regardless of the direct push timeout interval length.
Administrators should set idle connection timeouts on outgoing firewalls to a value that equals or exceeds the direct push timeout.
Firewalls with idle connection timeouts less than the direct push timeout will close the direct push session rendering mail undeliverable until the device reconnects. The result is users who are unsynchronized for long periods of time. See Firewall Configuration Diagrams
Carrier Timeout Intervals
A second consideration is that many carriers implement timeout intervals that range from just a few minutes to almost an hour. The carrierís timeout interval may be less than the firewall timeout your administrator has set or the direct push timeout you have set on the device. In this case, your session will, again, be interrupted rendering the mail undeliverable until reconnection. Check the NotifyLink Knowledge Base article for recommendations based on carrier settings.
The direct push session length is determined by the shortest timeout in the network path. Therefore, set the deviceís direct push timeout to the longest possible interval without exceeding the shortest timeout in the network path.
Where to Change the Direct Push Timeout
From a device, select: NotifyLink Preferences > Push Settings
From the Administrative Web, select: User Administration > User IT Policies > Device Policies > Push Settings