Why the store app doesn’t work
Linphone from the App Store or Google Play doesn’t work with pgw, because pushes to that app need Belledonne Communications’ push credentials. Build the open-source app with your own bundle ID or package name and your own credentials instead.Build Linphone with your credentials
- iOS
- Android
- In
linphone.xcodeproj, set your team and a bundle ID under your prefix for the app target and each extension target. - Change the app group IDs to your own.
- Turn on the Push Notifications capability, and the Voice over IP and Remote notifications background modes.
Set the Firebase project number
Linphone for Android sends the Firebase project number inpn-param, not the project ID. Create its app record with --fcm-project-number. Without it, Linphone’s REGISTERs get 555 Push Notification Service Not Supported.
Provision the SIP account
Add the account with the settings in the step “Add the SIP account in the app” of Configure apps for pgw. To provision it in a Linphone configuration file instead, use these keys. Key names can change between Linphone releases.push_notification_allowed turns on VoIP pushes for calls. remote_push_notification_allowed turns on the remote pushes that pgw uses for missed calls and registration refreshes.
In managed mode, pgw sends two digest challenges, SHA-256 and MD5. Linphone answers both, and pgw checks the SHA-256 answer.
Test with a self-signed certificate
When pgw serves a self-signed certificate, as in the quickstart, Linphone connects only if you build it to skip certificate checks. Before you build Linphone, add these settings to its default settings file,linphonerc_default on Android. Replace pbx.example.com with the SIP domain that the app registers to.
Next steps
Try it on the Android emulator
Build Linphone, run pgw on your computer, and receive a call through a real FCM push.
Configure an Android app
Create the Firebase service account and project number that the build needs.
Configure an iOS app
Create the APNs key that the build needs.