[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-users] Push notification using ip

From: Greg Troxel
Subject: Re: [Linphone-users] Push notification using ip
Date: Wed, 23 Oct 2019 13:01:06 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix)

Secure Mails via Linphone-users <address@hidden> 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 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]