Overview
The battery life of the FIP16Plus is 120 hours in standby and 15 hours in conversation. However, for various reasons, optimal battery life may not be achieved, and the user must troubleshoot and properly configure the FIP16Plus phone. This article explains how to correctly configure and use the FIP16Plus phone to achieve the best possible battery life.
Solutions to common battery life issues
If you notice that the phone’s battery life suddenly deteriorates, it’s most likely because the phone’s system wakes up frequently and consumes power. Many reasons can explain these frequent wake‑ups. Identifying the cause and resolving it effectively addresses the battery life issue.
Note: The FIP16Plus battery test standard consists of a full discharge cycle followed by a full recharge, repeated 400 times. After this number of cycles, the maximum battery capacity remains at 80% of the original capacity.
Here are common problems and their solutions for reference:
① The temporary TKIP encryption algorithm affects sleep time
To improve the security of the phone’s wireless connection encryption, the FIP16Plus phone is primarily recommended to use the AES encryption algorithm (symmetric encryption algorithm) for greater security, while the TKIP algorithm (Temporal Key Integrity Protocol) has been eliminated due to its limited compatibility. As a result, the FIP16Plus cannot enter sleep mode when connected to a Wi‑Fi encrypted with the TKIP algorithm, which affects battery life. Therefore, when connecting to Wi‑Fi, we recommend configuring the access point’s encryption algorithm to the more secure AES algorithm. The FIP16Plus will enjoy optimal battery life when connected to this Wi‑Fi.
②SIP registration failure, the phone keeps trying to register
If the SIP account has been configured, but registration fails for some reason (e.g., a closed intranet, incorrect server address, etc.), the phone will continue to try to register, which will significantly shorten battery life. If you need to identify the reason for registration failure, including network and server issues, please contact your administrator or SIP service provider.
③ The SIP registration refresh cycle is too short
In general, the SIP registration period is a relatively large value, such as 1800 or 3600 seconds, but in some special scenarios, a smaller value, such as 60 seconds, can be used, which forces the telephone system to wake up frequently to refresh the registration request. Please ensure that the registration period uses a reasonable value.

④ The NAT keep‑alive parameter is unreasonable
SIP keep‑alive or NAT settings: using a shorter interval will significantly affect battery life. Please check the need for NAT keep‑alive. Do not enable it unless necessary (set the value to 0 as shown below). If you wish to use it, choose a cycle slightly less than the NAT mapping refresh time. For example, the NAT mapping maintenance time is 60 seconds. It is recommended that the NAT keep‑alive period be 55 seconds.

Server‑side keep‑alive scenario: for phones behind NAT, to ensure the phone is reachable at all times, some servers enable scheduled keep‑alive, e.g., by sending a SIP Option keep‑alive every 20 seconds, which also wakes the system regularly to monitor battery life, resulting in a noticeable impact. The server‑side keep‑alive message cycle can be adjusted based on the NAT mapping refresh time. Confirm the need for this function and disable it if possible.
⑤FACS/TR069 function
Enabling the TR069 function or automatic provisioning on the phone will establish regular connections and report the relevant status to the server, increasing power consumption. The phone's default connection cycle will cause rapid battery drain. To ensure battery life, please disable the FACS and TR069 functions or set the connection period to a longer value.


⑥ The phone cannot access the external network
When the phone cannot access the external network, it resolves DNS, which leads to rapid power consumption. Please contact your network administrator to ensure that the network environment is properly configured to use an internal DNS server. The test method is as follows:

0 % packet loss means the phone can access the external network.
⑦Phone storage without charge for a long period
If the battery continues to be stored after the battery voltage reaches 0 %, it will overconsume the battery energy and cause excessive discharge, damaging the battery and degrading its aging performance. Please regularly check the battery voltage. When you notice the phone is almost out of power, recharge it promptly.
⑧Low power version requirements
To achieve better battery life with the FIP16Pus phone you use, please upgrade to firmware version V0.1.24.3 or later as soon as possible to ensure battery longevity.
Firmware version acquisition link: flyingvoice.com
