VoIP Call Development for Mobile Apps: iOS & Android Implementation

Your client can't answer a call while the phone is locked. Or there's echo that annoys both speakers. Sometimes the call drops when an SMS arrives. These bugs are typical consequences of a poorly integrated VoIP. We solve them at the architecture level, leveraging experience in telemedicine, logistics, and corporate communications.

Implementing VoIP calls in a mobile app isn't a single task — it's several interconnected technical layers: signaling protocol, media transport, audio session management, and integration with system call APIs. Skipping or simplifying any of these layers means a call that works in a demo but breaks in production: echo, audio loss on incoming notification, inability to answer a call from the lock screen.

How CallKit works

On iOS, VoIP without CallKit is technically possible, but the app won't get an audio session for an incoming call when the screen is locked, the system won't show the system incoming call screen, and since iOS 13, apps without CallKit won't receive PushKit notifications for VoIP. CallKit is a system framework that displays the system incoming call screen, manages audio sessions, supports Bluetooth/AirPods, and displays calls in the call history.

import CallKit

class CallManager: NSObject {
    let provider: CXProvider
    let callController = CXCallController()

    init() {
        let config = CXProviderConfiguration()
        config.supportsVideo = false
        config.maximumCallsPerCallGroup = 1
        config.supportedHandleTypes = [.phoneNumber, .emailAddress]
        provider = CXProvider(configuration: config)
        super.init()
        provider.setDelegate(self, queue: nil)
    }

    func reportIncomingCall(uuid: UUID, callerName: String) {
        let update = CXCallUpdate()
        update.remoteHandle = CXHandle(type: .generic, value: callerName)
        update.hasVideo = false
        provider.reportNewIncomingCall(with: uuid, update: update) { error in
            // start answering call after system approval
        }
    }
}

PushKit for incoming calls in background. Unlike regular APNs push, PushKit wakes the app instantly with high priority. But since iOS 13, Apple requires immediately calling reportNewIncomingCall upon receiving a VoIP push — otherwise the app crashes. No network request before CallKit.

Android: ConnectionService and Telecom API

The Android counterpart to CallKit is ConnectionService from the android.telecom package. It allows the app to become a "phone account" in the system, show calls on the lock screen, and manage audio routing. For incoming calls in background — FCM push with priority: high. On Android 14+, background services are restricted, but ForegroundService of type phoneCall (added in Android 14) solves exactly this task — no startup restrictions for incoming calls.

Audio session management via AudioManager:

val audioManager = context.getSystemService(Context.AUDIO_SERVICE) as AudioManager
audioManager.mode = AudioManager.MODE_IN_COMMUNICATION
audioManager.isSpeakerphoneOn = false
// on call end:
audioManager.mode = AudioManager.MODE_NORMAL

Bluetooth headsets are a separate headache. BluetoothHeadset profile, SCO connection for voice (not A2DP!), BroadcastReceiver for ACTION_SCO_AUDIO_STATE_UPDATED. Without explicit SCO management, audio goes through the speaker even when a Bluetooth headset is connected.

Why a TURN server matters

If you use WebRTC on its own (rather than through Twilio/Vonage), you need a TURN server for NAT traversal. Without it, calls only work within one network — a classic demo bug that breaks when the client is behind a corporate NAT. A TURN server also helps with symmetric NATs where standard STUN doesn't work.

coturn is an open source TURN server, deployable on a VPS in a few hours. ICE configuration:

// Android WebRTC SDK
val iceServers = listOf(
    PeerConnection.IceServer.builder("stun:stun.example.com:3478").createIceServer(),
    PeerConnection.IceServer.builder("turn:turn.example.com:3478")
        .setUsername("user")
        .setPassword("password")
        .createIceServer()
)

Codecs: Opus for audio (adaptive bitrate 6–510 kbps, works well with up to 20% packet loss). WebRTC SDK includes it by default.

Approach comparison: Managed SDK vs WebRTC

Managed SDKs are simpler, but WebRTC can save up to 80% on call costs with your own TURN infrastructure. At high volumes (over 10,000 minutes per month), the difference becomes significant.

Common mistakes and solutions

What's included in the work

• Requirements analysis and optimal stack selection (WebRTC, Twilio, Agora, or custom SIP).
• Signaling channel design (WebSocket, SIP, or custom protocol).
• TURN server deployment (coturn) and ICE candidate configuration.
• CallKit (iOS) and ConnectionService (Android) integration with PushKit/FCM.
• Testing on 20+ real devices with different OS versions and network conditions.
• Audio quality optimization: AEC, adaptive jitter buffer, packet loss concealment.
• Documentation and client team training.
• Post-launch support (monitoring, bug fixes, enhancements).

VoIP call development process

1. Requirements analysis and stack selection (managed SDK vs WebRTC).
2. Signaling and media channel design.
3. TURN server deployment and ICE configuration.
4. CallKit/ConnectionService and PushKit/FCM integration.
5. Testing on real devices with various network conditions.
6. Audio quality optimization and artifact elimination.
7. Deployment and monitoring.

Contact us to discuss your VoIP solution architecture. Order development and we guarantee stable calls without echo or drops. Get a consultation from our engineer — we're ready to help.

How to Start Integrating API into a Mobile App?

The request goes out, the response doesn't come, timeout — 30 seconds. The user stares at the spinner. No network — mobile card in the subway. Or the network is there, but the server returns 200 with an HTML error page instead of JSON — and the app crashes on JSONDecoder.decode(). We see such cases on every second project. So integrating API into a mobile app is not just calling an endpoint, but designing a reliable network layer: error handling, caching, offline mode, certificate pinning. Order an audit of your current network layer — we will evaluate the project in 1 day. Our team guarantees a thorough analysis and provides a detailed roadmap.

Standard libraries like URLSession and OkHttp provide basic HTTP clients, but for production you need retries with exponential backoff, status code validation, typed deserialization, and network state monitoring. Without this, the app loses data and users. We have been doing mobile development for 5 years and implemented more than 30 projects with API integration on iOS, Android, and Flutter — from startups to enterprise solutions.

How to Choose a Protocol for API Integration?

REST remains the standard for most projects. But when a profile screen needs 5 fields out of 40, GraphQL eliminates over-fetching and reduces traffic by 30–60%. gRPC is justified for thousands of requests per minute (trading, IoT) — binary serialization is 3–5 times faster than JSON. WebSocket is the only choice for real-time without polling (messages, notifications).

Practical example: For a fintech app, we replaced REST (40 fields) with GraphQL — response size dropped from 12 KB to 2.5 KB, screen render time decreased by 70%. Traffic savings were significant. Our certified iOS and Android developers have deep experience with all these protocols — you can rely on proven solutions.

How to Ensure Reliable Connection and Offline-First?

Users lose network in the subway, elevator, tunnel. A mobile app must work without internet — at least in read-only mode. We implement the offline-first pattern:

1. On screen open, first show data from the local cache (Core Data / Room).
2. Simultaneously perform a network request, update UI after response.
3. If network is unavailable — show cached data and a 'no connection' label.
4. When network is restored, automatically synchronize changes.

For HTTP response caching we use URLCache (iOS) and OkHttp Cache (Android) with Cache-Control support. For structured data — SwiftData / Room. NWPathMonitor / ConnectivityManager.NetworkCallback monitor network state and trigger updates.

REST and Client Library Selection

Alamofire (iOS) — de facto standard for Swift projects. On top of URLSession it adds request chaining, response validation, automatic retry, certificate pinning via ServerTrustManager. AF.request() with .validate() returns an error for any status code outside 200–299. Without .validate(), Alamofire considers 404 and 500 as successful responses. With Swift Concurrency — async version via serializingDecodable.

Retrofit (Android) — annotation-based HTTP client on top of OkHttp. An interface with annotations compiles into implementation. @GET, @POST, @Path, @Query, @Body — declarative API description. OkHttp under the hood: connection pooling, transparent gzip, HTTP/2 multiplex. HttpLoggingInterceptor — logging in debug builds. Authenticator — automatic token refresh on 401.

Ktor (KMM/Flutter) — multiplatform HTTP client. On iOS it works via Darwin engine (URLSession), on Android — via OkHttp. Single code for both platforms with KMM architecture.

GraphQL: When REST Falls Short

REST returns a fixed structure. A profile screen needs name, avatar, email — the server sends 40 fields. Over-fetching. GraphQL solves this: the client requests exactly the needed fields. This is critical for mobile where traffic and parsing time are real constraints. Apollo iOS and Apollo Kotlin generate typed classes from schema: schema.graphql + query files → strict types at compile time. Subscriptions via WebSocket — real-time without polling. Limitation: GraphQL is harder to cache at the HTTP level. Apollo uses a normalized in-memory cache InMemoryNormalizedCache — requests with overlapping data update the cache without duplication.

WebSocket: Real-Time Without Extra Traffic

Polling (setInterval every 5 seconds) — battery and traffic waste. WebSocket is a persistent bidirectional connection. iOS: URLSessionWebSocketTask (native, iOS 13+). Android: OkHttp WebSocket. Mandatory reconnect handling: on onFailure — exponential backoff (1s → 2s → 4s → 8s → max 60s). Socket.IO is an overlay with automatic reconnect, but for new projects native WebSocket is preferable (fewer dependencies).

gRPC: For High-Load Services

gRPC with protobuf — binary serialization: smaller size, faster parsing. grpc-swift for iOS, grpc-kotlin for Android. The protobuf schema compiles to typed classes. Streaming (server-side, client-side, bidirectional) is a native feature. Application threshold: high request frequency (trading, IoT) or critical latency. For regular CRUD, REST is simpler to debug and monitor.

Certificate Pinning and Security

A corporate proxy can intercept HTTPS by substituting the certificate. Certificate pinning prevents this: the app accepts only a specific certificate or public key. Alamofire: ServerTrustManager with PinnedCertificatesTrustEvaluator. OkHttp: CertificatePinner with SHA-256 hash. Apple's App Transport Security documentation recommends pinning certificates for sensitive data. Operational complexity: on certificate rotation, older app versions stop working. Solution — pinning to the CA public key or support multiple pins with a grace period.

What Is Included in the Work

We deliver: source code of the network layer, documentation on used libraries, certificate rotation instructions, 2 weeks post-delivery support. Our experience guarantees that the solution will be stable and maintainable.

Timeline and Cost

Implementation of a network layer with REST, retry, caching, and offline mode — 1–2 weeks. Adding GraphQL or WebSocket — another 1–2 weeks. gRPC — 2–3 weeks, including code generation. The cost is calculated individually after analyzing the API and offline behavior requirements. We will evaluate the project in 1 day — contact us for a consultation. Get a reliable API integration with guaranteed quality.