Mobile softphones: background calling and emergency boundaries

Test background delivery as a separate feature

A mobile app registering in the foreground does not prove it will ring after it is backgrounded or the screen is locked. Linphone’s current FAQ distinguishes its own service from third-party SIP accounts for push. Bria describes a push service that can register on behalf of an account while the app is in the background; its current iOS and Android release notes identify separate 6.23.5 builds dated August 20, 2026.

Test the exact edition, build, server and account after the device sleeps, on Wi-Fi and mobile data, and after a restart. Observe whether an inbound call reaches voicemail, rings late or never alerts the user.

Groundwire offers push and standard registration modes. Its push architecture places SIP registration on Acrobits SIPIS rather than on the sleeping handset, so test the selected mode instead of treating a green foreground registration as background-call evidence.

The retail Acrobits Softphone uses the same documented SIPIS push boundary as Groundwire, but its feature set is separate. Review the Acrobits Softphone record before using a Groundwire feature claim in a basic-client pilot.

Sipnetic's current first-party pages do not document a push-registration relay or promise locked-screen delivery. Treat its foreground registration, Android background execution and provider reachability as separate evidence states. MizuDroid documents three distinct Android paths: server-native push, a Mizutech SIP-push gateway that creates an additional registration, or a background service. Preserve which path is active and test its revocation behavior rather than transferring a foreground result.

Review the push trust path

A push relay can handle SIP account configuration or registration state. Bria documents storage of account configuration on its push server when that service is used. Inventory the party operating the relay and review its account-security terms before provisioning a shared or sensitive extension.

Keep device screen locks and recovery controls in scope. Disable or revoke a lost handset and test that old credentials no longer place calls.

Zoiper states that its push-proxy model requires credentials in plaintext or with easily reversible encryption. Treat enabling that relay as an explicit trust decision and document revocation.

Acrobits states that Groundwire push registers the SIP account on SIPIS and that a PBX used with this mode must be reachable from the public internet; it also notes that separate push credentials may be used. Record the credential scope, permitted source addresses and revocation procedure.

Treat location as a deployment requirement

A roaming device can present a number associated with a different address. Confirm emergency call behavior and the location process with the SIP provider and client vendor. An ordinary outbound test does not validate the emergency route.

Capture the real failure

When calls fail only on cellular data, compare the registration state, transport connection and media path against the Wi-Fi case. When calls fail only in the background, inspect the push service before changing codecs or firewall rules.

For a silent microphone, the softphone microphone diagnostic preserves per-app permission, foreground or background state, Bluetooth or handset route, client capture, SDP direction and transmitted media as separate evidence.

When incoming calls arrive only while the client is open, use the background ringing diagnostic to trace push enrollment, proxy ownership, APNs or FCM delivery, application wake-up, refreshed SIP reachability and the retained INVITE before changing media settings.

If a call moves to the wrong handset, speaker or Bluetooth path, use the audio-route diagnostic to preserve the connected device, platform route change, client selection and active input/output pair separately.

Inventory temporary local export listeners

Some mobile clients can expose administrative or export services on a local network. Acrobits documents optional iOS Web Access for Acrobits Softphone and Groundwire, allowing a same-Wi-Fi browser to view history and download recordings while the app is open. Treat such a listener separately from SIP, push and media; replace documented defaults, authorize the network and export, disable it after use and verify that the data copies follow the retention policy.

Treat every network change as a new signaling path

A working foreground registration can become stale when Wi-Fi, mobile data, VPN state or address family changes. Use the network-change registration diagnostic to follow the old flow, failure detection, replacement DNS and transport, new REGISTER and later inbound route before changing codecs or media settings.

Separate Wave Android 1.0.35.7 from iOS 1.35.7

Grandstream's September 21 mobile notes identify Android 1.0.35.7 and iOS 1.35.7. The different numbers, stores, operating-system notification controls and documented iOS fixes remain separate. For Grandstream Wave, test locked-screen delivery and call continuity on each exact platform after verifying the required UCM firmware and permissions.

Trace Cloud Softphone from provisioning to background delivery

For Acrobits Cloud Softphone, keep Live or Editable portal state, external Account XML and the final incoming-call mode separate from SIPIS registration, platform push, app wake-up and RTP. The stale-provisioning diagnostic stops a delivery fault from being mistaken for a push or media fault.

Treat MizuDroid background modes as different signaling paths

MizuDroid can use direct server push, a Mizutech SIP-push gateway or an Android background service. The gateway adds its own registration and can retain an inactive binding for several days after an uninstall, so a registrar contact is not proof that the retired device can ring. Use the background-ringing diagnostic to follow binding, push, wake-up, INVITE and alert separately.

Use the Zoiper-specific background branch

For Zoiper, the background incoming-call diagnostic follows one call across foreground or locked state, registration lifetime, direct or Push Proxy ownership, device wake-up, refreshed registration and alerting. It preserves the distinction between a push wake-up and an accepted SIP call.

Keep 3CX push expiry bound to the PBX update lane

The 3CX push-expiry diagnostic distinguishes the earlier seven-day subscription lifetime from the fourteen-day V20 Update 10 behavior. Update 10 remained beta in the reviewed September 29, 2026 release record, so the installed PBX version—not a current manual sentence—controls the operational assumption.

Test PortSIP ONE background delivery as an ordered path

The PortSIP ONE mobile diagnostic preserves the PBX generation, token, X-Push, APNs or FCM, app-wake, replacement-registration and replacement-INVITE boundaries.

Trace Bria Mobile through its selected registration mode

The Bria background-call diagnostic maps the vendor's four registration modes to single- or multiple-registration SIP service behavior, then traces Contact identity, push delivery, secure wake-up and alerting without treating a foreground call as background proof.

Keep Linphone capability and provider participation separate

Linphone exposes mobile push controls, but an arbitrary third-party SIP login does not prove a matching proxy wake path. The Linphone push guide follows the token-bearing Contact, proxy request, operating-system delivery, app wake and refreshed registration without turning feature support into a reliability claim.

Control mobile-headset multipoint and call ownership

A Bluetooth headset paired to a mobile softphone and another host can switch media or controls unexpectedly. The business wireless headset category preserves the primary host, connection path, paired-device inventory and remote-audio acceptance.

Use SessionTalk to separate push wake from completed calling

The SessionTalk diagnostic follows the provider INVITE, push-server binding, APNs or FCM request, device wake, secure signaling, call interface, answer and direct media without converting an alert into an end-to-end call result.

Separate Webex mobile support from phone-service assignment

The Webex App guide preserves mobile operating-system support, assigned calling service, background state and device path separately; a Webex notification or Call on Webex session does not prove work-number reachability.