Here is the theory behind "TCP for Mobile Phones" recommendations: * tcp - keep alive is supposed to happen from the Server side (SBC) therefore * application layer can go to sleep, and firewall pin hole is kept open at the driver level * thus conserving power needed to load and wake up the application. UAC's only need to register at the SIP application layer once every 10 minutes or so. In real life however, that doesn't seem to work out all that well due to SBC limitations (both Acme and Sonus; details on request) and limited support from the various phone app vendors. Plus, if the TCP connection "gets lost" the risk interval of not receiving a phone call is just that much longer. John On 7/17/2017 16:12, jungle Boogie wrote:
On 16 July 2017 at 19:28, Colton Conor <colton.conor at gmail.com> wrote:
Overall TCP just always seems to work, and UPD depends on the situation of the network. TCP is better for battery consumption on mobile sip applications as well.
Knowing that TCP uses more overhead just by being TCP, is it really better for mobile phone batteries?