Linphone on iPhone: some incoming calls may not ring in the background

Product: Warmar Communicator / supported Linphone mobile calling

Update — September 7, 2026: A server-side correction has been deployed. Follow-up validation is still in progress.

What happened

We identified an intermittent issue where an iPhone could appear registered in our system but not receive the push notification needed to wake Linphone for an incoming call. One field in the stored push registration could be missing a required service label. When that happened, the push service could skip the wake-up request and the phone would not ring.

Retained call traces show this affected some incoming-call attempts. Other phones could still answer the same call, so an affected mobile device did not always mean the entire call was missed. We have also seen other push-delivery failure patterns and are not treating this change as a fix for every possible mobile calling issue.

What we changed

We deployed a narrowly scoped server-side safeguard that restores the missing label only when it can be identified unambiguously. It applies across customers using the affected Linphone iPhone registration format and does not change passwords, phone numbers, or call routing.

No app reinstall, new QR code, or password change is required for this server-side correction.

Verification and next steps

The correction passed isolated registration and routing tests. A locked-iPhone test after deployment successfully woke, registered, rang, and answered. Longer idle and normal inbound-routing verification is continuing; one successful test does not prove every device or scenario is resolved.

If a call still does not ring, please send support the approximate time and timezone, which device/app was affected, and whether the phone was locked. Please do not post passwords, QR codes, or private call details on this public board. Service status is available at https://status.warmar.tech/.