-
By product category
-
Search by product
- SR3000-5G
- SR3000-5G-Ruggedized
- SR3000
- SR3000-lite
- T5100
- T5300
- FWR7302
- FWR9601
- FWR8102
- PR08
- LM150
- G504
- G508
- FTA1101
- FTA5102E2
- FGW4148-16S/24S/32S/48S
- FIP16
- FIP15G
- FTA5101
- FWR9502
- FWR8101
- FWR7102
- P23G
- P23GW
- P22G
- P22P
- P21/P21P
- P20/P20P/P20G
- P11W
- P10W
- P11/P11P/P11G
- P10/P10P/P10G
- FIP16Plus
- FIP15G Plus
- FIP14G
- FIP12WP-R
- FIP13G
- FIP12WP/ FIP12WP Home
- FIP11C/FIP11CP
- FIP10/FIP10P
- P11LTE
- P10LTE
- i12/i12V
- i11/i11V
- i86V-01/02
- PB01
- i86-01/02/03
- FTA5111
- HB01 & USB433
- FTA5120
- HP200
- BT50
- EHS10
- FPX9102H
- SW7R-Pro
- FRPS
- FACS
- FDC
-
Find by question type
Overview
The battery life of FIP16Plus is 120h standby time and 15h talk time. However, due to some reasons, the optimal battery life may not be achieved, and the user needs to troubleshoot and correctly configure the FIP16Plus phone. This article introduces how to correctly configure and use the FIP16Plus phone to obtain the best battery life.
Solutions to common battery life issues
If you find that the phone's battery life suddenly deteriorates, it is most likely because the phone system wakes up frequently and consumes power. There are many reasons why the phone system wakes up frequently. Finding the cause and solving it can effectively solve the problem of poor battery life.
Note: FIP16Plus’s battery testing standard is one cycle of running out of electricity and then fully charging it, 400 times. After reaching this number of times, the maximum battery capacity is still 80% of the original.
The following are common problems and solutions for your reference:
① TKIP temporary encryption algorithm affects standby time
In order to make the phone have higher wireless connection encryption security, the FIP16Plus phone is mainly recommended to use the more secure AES (Symmetric Encryption Algorithm) encryption algorithm, while the TKIP (Temporal Key Integrity Protocol) algorithm has been eliminated because of its unfriendly compatibility. Therefore, FIP16Plus cannot sleep when connected to WIFI encrypted by the TKIP algorithm, which will affect the standby time. Therefore, when connecting to WIFI, we recommend configuring the encryption algorithm of the AP to the more secure AES (symmetric encryption algorithm) encryption algorithm. FIP16Plus will have an ideal standby time when connected to this WiFi.
②SIP registration failed, the phone keeps trying to register
If the SIP account has been configured, but the registration is not successful for some reason (such as a closed intranet, wrong server address, etc.), the phone will keep trying to register again, and the battery life will be significantly shortened. If you need to find out the reason why registration cannot be successful, including network problems and server problems, please contact your administrator or SIP service provider.
③ SIP registration refresh cycle is too short
Generally, the registration period of SIP is a relatively large value, such as 1800, 3600 seconds, but in some special scenarios, a smaller value, such as 60 seconds, may be used, which will cause the phone system to wake up frequently to refresh the registration. request, please ensure that the registration period uses a relatively reasonable value.
④NAT keep -alive setting is unreasonable
SIP keep-alive settings or NAT settings: using a shorter time interval will significantly affect battery life. Please check the necessity of NAT keep-alive. Do not enable it unless necessary (set the value to 0 as shown below). If you want to use it, please use a cycle slightly lower than the NAT mapping refresh time. For example, the maintenance time of NAT mapping is 60 seconds. It is recommended. The NAT keepalive period is 55 seconds.
Server-side keep-alive scenario: For phones behind NAT, in order to ensure that the phone is reachable at any time, some servers will turn on the scheduled keep-alive function, such as sending a SIP Option keep-alive message every 20 seconds, which will also wake up the system regularly to monitor battery life. cause obvious impact. The server-side keep-alive message sending cycle can be appropriately adjusted according to the NAT mapping refresh time. Confirm the necessity of this feature and turn it off if possible.
⑤FACS/TR069 function
Enable the TR069 function or Auto provisioning fucntion on the phone will cause the phone to establish connections regularly and report the relevant status to the server, which will cause additional power consumption. The default connection cycle of the phone will cause the phone to lose power quickly. 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 will resolve DNS, resulting in 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.
⑦Storage phone without charging for a long time
If the battery continues to be stored after the battery power reaches 0%, it will overdraw the battery energy and cause over-discharge, which will damage the battery and cause its aging performance to deteriorate. Please check the battery voltage regularly. When you find that the phone is almost out of power, please recharge it in time.
⑧Power saving version requirements
In order to get a better battery life experience with the FIP16Pus phone you are using, please update to the firmware version V0.1.24.3 or later as soon as possible to ensure battery life.
Firmware version acquisition link: https://www.flyingvoice.com/download/fip16plus.html#c