"Julien Favre-Bulle" <[email protected]> writes:
> Supporting push notifications has become compulsory since iOS 10 and on most > recent Android phones to receive incoming calls and messages when the app is > not active in foreground. > > To wake up a VoIP app when an incoming call or an incoming message is > received, the server must send a push notification request to Apple/Google's > PN server. For security reasons, Apple/Google doesn't allow everybody to > send push notifications to their servers. There are private keys and > certificates to protect the whole process. On Android, there is also Unified Push https://unifiedpush.org/ which does the same thing, but in a way that respects software freedom and decentralization. There is a small library one can include so that e.g. Linphone could subscribe via UP. > We have decided not to share Linphone’s push notification ID with third > party services, and this is why the stock Linphone app can only receive push > notifications sent from our sip.linphone.org service. Sure, but the bug is that there is a centralized id and the monopoly concept that the app developers are in the middle of push. Also, other services have a push gateway (with rate limits), so that other servers can send wakeups. An example is Home Assistant (server) and Home Assistant Companion (iOS and Android app). On iOS, the app registers for apple push, and sends the tokens to the Home Assistant server (the user's own computer). When the server wants to send a notification, it contacts a push gateway run by Nabu Casa (the publisher of the mobile app), and subject to reasonable rate limits, Nabu Casa's servers make the notification call to Apple's servers. In practice this works very well. _______________________________________________ Linphone-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/linphone-users
