Push notification using ip 74.119.146.37

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Push notification using ip 74.119.146.37

linphone-users mailing list

Hi

I am using linphone for Android ver 4.1.1.

My VoIP provider is VoIP. ms and when logging into my portal on VoIP. ms it showed a connection from 74.119.146.37 instead of my public IP address. My VoIP provider informed me that this is because of "push notification" used by linphone.

I would appreciate if you can confirm the IP address is correct and perhaps clarify how push notification functions on linphone.

Thanks

Mr Ellis



_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Push notification using ip 74.119.146.37

Greg Troxel
Secure Mails via Linphone-users <[hidden email]> writes:

> I am using linphone for Android ver 4.1.1.
>
> My VoIP provider is VoIP. ms and when logging into my portal on
> VoIP. ms it showed a connection from 74.119.146.37 instead of my
> public IP address. My VoIP provider informed me that this is because
> of "push notification" used by linphone.
>
> I would appreciate if you can confirm the IP address is correct and perhaps clarify how push notification functions on linphone.

That doesn't sound quite right.

As I understand it, push as most people mean it* is about the client
disconnecting at the SIP level while remaining logically connected, and
the server doing some out-of-band usually proprietary thing to wake up
linphone which then reconnects at the SIP level.  I see no reason why
this would involve different IP addresses.

* In SIP as specified, if the client remains functional, INVITE sent
  from the server will arrive promptly.   But because this is normal,
  does not involve the client stopping running SIP, and perhaps because
  it doesn't involve any proprietary centralized services, people don't
  call this "push".


There are also a number of NAT traversal schemes, going by names such as
ICE and STUN.  Some of these seem, in particular STUN, seem likely to
route your traffic via a proxy.


If you do figure this out precisely, please post what you find out.


_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Push notification using ip 74.119.146.37

linphone-users mailing list
'Doze mode' and other aggressive android application shutdown have increased the importance of using Google's push messaging solution (https://en.wikipedia.org/wiki/Firebase_Cloud_Messaging) over long lived connections. As I understand it, certain SIP softphones will register with additional parameters indicating how to send messages to Firebase specifically to you phone so the SIP server can send a "wake up" message to your SIP app if there is incoming data for the SIP connection such as an incoming call.

Gory details of PUSH options are: https://tools.ietf.org/html/rfc8599

I have not seen a solution which registers your SIP account on your behalf, but that would be handy to have if the upstream SIP server doesn't have push notification features.

On Wed, Oct 23, 2019 at 2:42 PM Greg Troxel <[hidden email]> wrote:
Secure Mails via Linphone-users <[hidden email]> writes:

> I am using linphone for Android ver 4.1.1.
>
> My VoIP provider is VoIP. ms and when logging into my portal on
> VoIP. ms it showed a connection from 74.119.146.37 instead of my
> public IP address. My VoIP provider informed me that this is because
> of "push notification" used by linphone.
>
> I would appreciate if you can confirm the IP address is correct and perhaps clarify how push notification functions on linphone.

That doesn't sound quite right.

As I understand it, push as most people mean it* is about the client
disconnecting at the SIP level while remaining logically connected, and
the server doing some out-of-band usually proprietary thing to wake up
linphone which then reconnects at the SIP level.  I see no reason why
this would involve different IP addresses.

* In SIP as specified, if the client remains functional, INVITE sent
  from the server will arrive promptly.   But because this is normal,
  does not involve the client stopping running SIP, and perhaps because
  it doesn't involve any proprietary centralized services, people don't
  call this "push".


There are also a number of NAT traversal schemes, going by names such as
ICE and STUN.  Some of these seem, in particular STUN, seem likely to
route your traffic via a proxy.


If you do figure this out precisely, please post what you find out.


_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users

_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Push notification using ip 74.119.146.37

Greg Troxel
Adam Chasen via Linphone-users <[hidden email]> writes:

> 'Doze mode' and other aggressive android application shutdown have
> increased the importance of using Google's push messaging solution (
> https://en.wikipedia.org/wiki/Firebase_Cloud_Messaging) over long lived
> connections. As I understand it, certain SIP softphones will register with
> additional parameters indicating how to send messages to Firebase
> specifically to you phone so the SIP server can send a "wake up" message to
> your SIP app if there is incoming data for the SIP connection such as an
> incoming call.

Yes, that's what I meant by out-of-band proprietary thing.

> Gory details of PUSH options are: https://tools.ietf.org/html/rfc8599

Yes, and that also seems to describe an IETF approach that isn't
actually used.

> I have not seen a solution which registers your SIP account on your behalf,
> but that would be handy to have if the upstream SIP server doesn't have
> push notification features.

Previous messages on this list have talked about using flexisip as a
proxy to deal with push, in front of asterisk which doesn't have push
support.

But, I don't know of clients that start using a proxy you didn't
configure.


There is also the notion of fixing your phone to not have doze problems,
or choosing a phone that runs an OS where you can configure things
(e.g. Lineage) and then using a client which sleeps and can still get
incoming messages.  As I understand it baresip works just fine in this
mode.  In non-SIP, Conversations (XMPP) and K-9 (IMAP) similarly work
well.

_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users