[VoiceOps] TCP Signaling for SIP Signaling

Colton Conor colton.conor at gmail.com
Tue Jul 18 09:51:31 EDT 2017


This is true. I still worry about the NAT issue when using UDP. Most all
wireless carrier do not assign public facing IPv4 addresses to the phone
only IPv6.



On Tue, Jul 18, 2017 at 3:56 AM, Nikolay Shopik <shopik+lists at nvcube.net>
wrote:

> On 18/07/17 00: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?
> >
>
> Some mobile clients (on both iOS and android) allow you to use push
> notification. Thus mobile client only keep TCP connection when app is
> open. And push server keep connection/registration, when app closed only
> to wake it up when need to accept call.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170718/4ac0b423/attachment.html>


More information about the VoiceOps mailing list