In brief: 3CX’s mobile apps have improved substantially in recent releases, but getting them to work reliably on iOS — particularly for background call reception — requires understanding both the platform constraints and the 3CX configuration options. This guide covers what works, what doesn’t, and how to configure mobile apps correctly for SA clients.
Why Mobile App Reliability Matters for SA Deployments
South African businesses adopted remote and hybrid work rapidly from 2020 onwards, and mobile softphone apps became critical infrastructure rather than a convenience feature. A staff member who can receive their business extension calls on their smartphone while working from home, at a client site, or during load shedding can maintain professional communication regardless of their physical location.
However, 3CX’s iOS app has historically been one of the more challenging aspects of managing a 3CX deployment, primarily because of Apple’s restrictions on background app activity. iOS aggressively suspends apps running in the background to preserve battery life, which can cause the 3CX app to miss incoming calls when not actively in use. This issue has been a source of significant client frustration and support tickets for SA resellers.
3CX has continuously worked to address this through a combination of push notification architecture and iOS-specific configuration changes, and the situation has improved substantially in V20 Update 2 and later releases.
How 3CX Push Notifications Work on iOS
On iOS 15 and later, 3CX uses Apple Push Notification Service (APNs) to deliver incoming call notifications to iOS devices. When a call arrives at a 3CX extension, the server sends a push notification via Apple’s infrastructure to the device, which wakes the 3CX app to handle the incoming call — even if the app has been suspended by iOS.
This architecture is more reliable than the previous approach, which attempted to maintain a persistent SIP connection from the background. However, it requires:
- The 3CX server must have outbound internet access on the required ports to reach Apple’s APNs servers
- The iOS device must have internet connectivity (WiFi or mobile data) to receive the push
- The 3CX iOS app must have notifications enabled in iOS Settings — users who deny notification permission will not receive calls
- The device must not be in a “Do Not Disturb” or Focus mode that blocks the app’s notifications
Configuring 3CX Mobile Apps: Step-by-Step
Server-side (3CX admin console):
- Verify that push notifications are enabled in System → Push Notification. The APNs certificate status should show “Valid” with a current expiry date.
- Ensure the 3CX server can reach push.3cx.com on port 443. If a firewall is blocking this, push notifications will fail for iOS and Android both.
- In the extension’s Mobile App configuration, confirm that “Enable Push Notification” is ticked. This is on by default for new extensions but worth verifying on older configurations.
iOS device setup:
- Install 3CX from the App Store — use the QR code provisioning from the admin console to avoid manual configuration errors.
- When prompted, allow notifications. This is critical — without it, the app cannot wake up for incoming calls.
- Grant microphone permission when prompted.
- Test with a call from another extension while the screen is off and the app is in the background. The phone should ring normally.
- If calls are missed when the screen is off, check iOS Settings → 3CX → Notifications and verify all notification categories are enabled.
Known iOS Limitations and Workarounds
Background call receipt after reboot: After an iOS device restarts, apps do not receive push notifications until they have been opened at least once. Staff who reboot their phones (or after an iOS update which restarts the device) need to open the 3CX app once before they’ll receive calls. This is a documented iOS limitation, not a 3CX bug.
Focus modes blocking calls: iOS Focus modes (Do Not Disturb, Personal, Work modes) can block notifications from apps not on the “allowed” list. If a client complains of missed calls on their personal phone, check whether a scheduled Focus mode is active during business hours. Adding the 3CX app to the Focus mode’s allowed apps list resolves this.
Low Power Mode: iOS Low Power Mode restricts background activity. Devices in Low Power Mode may miss 3CX call notifications. Advise clients not to rely on 3CX as their primary contact method when their phone is in Low Power Mode.
Poor mobile data: In areas with weak mobile signal, push notifications may be delayed by seconds. If a client reports that their 3CX app rings briefly then stops (the call has already been answered elsewhere in the queue), the push notification delivery latency may be causing the desk phone or another device to answer first.
Android vs iOS: Behavioural Differences
3CX’s Android app generally behaves more reliably for background call reception than iOS, primarily because Android provides more flexibility for persistent background connections. However, Android has its own quirks:
Battery optimisation: Most Android manufacturers (Samsung, Huawei, Oppo, Xiaomi) implement aggressive battery optimisation that can kill background apps. The 3CX Android documentation includes manufacturer-specific instructions for disabling battery optimisation for the 3CX app. This step is often missed in deployments.
Samsung-specific: Samsung devices with “Adaptive Battery” enabled sometimes aggressively restrict 3CX. In Settings → Battery → Adaptive Battery → Apps not optimised, adding 3CX typically resolves this.
The key diagnostic question when a client reports missed calls on mobile: “What phone model are they using?” The answer almost always points to the right manufacturer-specific fix.
Best Practice: Parallel Ring Configuration
For critical extensions where call reception reliability is non-negotiable (receptionists, sales leads, business owners), configure parallel ring with the desktop phone as primary and the mobile app as secondary — or vice versa. This way, a call rings on both devices simultaneously, and the mobile app backing up the desk phone means calls are unlikely to be missed even if one device is temporarily offline or in a missed state.
What This Means for SA Telecoms Resellers
Mobile app configuration is one of the most common sources of post-installation support calls for SA 3CX resellers. Building a comprehensive mobile app setup checklist — including iOS notification permissions, battery optimisation exceptions for Android, and a post-setup test call — into your standard installation process reduces these support calls substantially.
Providing clients with a one-page “3CX Mobile App Setup and Troubleshooting Guide” tailored to the phone models they commonly use is a value-added touchpoint that demonstrates professionalism and reduces support burden. Most clients would rather troubleshoot a missed call notification issue themselves with clear guidance than log a support ticket.
About the Author
Mechelle Gindra
Mechelle Gindra is the managing editor and lead content strategist at Telecoms-Channel, South Africa's dedicated intelligence platform for telecoms resellers, ICT distributors, and channel partners. She oversees the editorial team's AI-assisted content production pipeline, ensuring vendor news, market analysis, and regulatory updates are accurate, timely, and actionable for the SA telecoms channel community. With deep expertise in the South African telecoms reseller ecosystem, Mechelle directs coverage of vendor partner programmes, ICASA regulatory developments, wholesale market dynamics, and channel business strategy. She is responsible for maintaining Telecoms-Channel's editorial standards, fact-checking processes, and corrections policy.
