Twilio Voice SDK: Mobile Voice Calls Integration

The user taps the call button — but the call doesn't go through. Or an incoming call arrives with a 10-second delay. Most often the problem lies in incorrect Twilio Voice integration: Access Token expired, PushKit not configured, CallKit invoked in the wrong order. Let's break down how to avoid these errors.

Twilio Programmable Voice SDK is an industrial platform that eliminates the hassle of TURN servers and media servers. Twilio handles media transport (Opus/DTLS/SRTP) and global routing through 90+ data centers. The developer is left with: signaling through Twilio, managing the audio session on the mobile platform, and integration with system call interfaces (CallKit on iOS, ConnectionService on Android). We have 5+ successful Twilio Voice projects under our belt, guaranteeing stable operation in production.

Server-Side Setup: Access Token

Twilio Voice SDK authenticates via short-lived Access Tokens generated by your backend using the Twilio Helper Library. The token contains a VoiceGrant — permissions for incoming and outgoing calls. Typical configuration:

from twilio.jwt.access_token import AccessToken
from twilio.jwt.access_token.grants import VoiceGrant

token = AccessToken(
    account_sid=ACCOUNT_SID,
    signing_key_sid=API_KEY_SID,
    private_key=API_KEY_SECRET,
    identity=user_id,
    ttl=3600
)
token.add_grant(VoiceGrant(
    outgoing_application_sid=TWIML_APP_SID,
    incoming_allow=True
))
return token.to_jwt()

The mobile client fetches the token on launch and renews it before expiry. The Twilio SDK notifies via the delegate accessTokenInvalidOrExpired — at this point you need to request a new token and call updateAccessToken. We recommend a TTL of 3600 seconds — a balance between security and refresh frequency. Twilio official documentation confirms this approach.

Steps to generate an Access Token on the server:

1. Create an API Key in Twilio Console.
2. Configure a TwiML Application with a webhook URL.
3. Write an endpoint in Node.js/Python that returns a JWT with VoiceGrant.

Why PushKit is Mandatory for Incoming Calls on iOS

PushKit is the only reliable way to deliver an incoming call in any application state. The APNs VoIP channel guarantees priority delivery. Without PushKit, the app won't receive the signal in the background.

func pushRegistry(_ registry: PKPushRegistry,
                  didUpdate credentials: PKPushCredentials,
                  for type: PKPushType) {
    TwilioVoice.register(accessToken: token,
                         deviceToken: credentials.token) { error in }
}

func pushRegistry(_ registry: PKPushRegistry,
                  didReceiveIncomingPushWith payload: PKPushPayload,
                  for type: PKPushType,
                  completion: @escaping () -> Void) {
    TwilioVoice.handleNotification(payload.dictionaryPayload,
                                   delegate: self,
                                   delegateQueue: nil)
    // MUST call CallKit reportNewIncomingCall before completion
}

Violating the rule of calling CallKit before completion in the PushKit delegate results in forced app termination by iOS. This is not a warning, it's a crash. Integration with CallKit via TVODefaultAudioDevice — Twilio provides a ready-made AVAudioSession manager that correctly interacts with CallKit.

How to Connect ConnectionService on Android

Dependency: com.twilio:voice-android:6.x.x. The SDK works on top of WebRTC but provides a high-level API.

// Initialization
Voice.initialize(context, LogLevel.DEBUG)

// Outgoing call
val connectOptions = ConnectOptions.Builder(accessToken)
    .params(mapOf("To" to phoneNumber))
    .build()

val call = Voice.connect(context, connectOptions, object : Call.Listener {
    override fun onConnected(call: Call) { /* call established */ }
    override fun onDisconnected(call: Call, error: CallException?) { /* ended */ }
    override fun onConnectFailure(call: Call, error: CallException) { /* error */ }
})

Incoming calls come via FCM. The Twilio SDK handles FCM payload through Voice.handleMessage():

override fun onMessageReceived(message: RemoteMessage) {
    if (Voice.handleMessage(context, message.data, object : MessageListener {
        override fun onCallInvite(callInvite: CallInvite) {
            // show incoming call notification
            showIncomingCallNotification(callInvite)
        }
        override fun onCancelledCallInvite(cancelledInvite: CancelledCallInvite, ...) {
            // call cancelled before answer
        }
    })) { /* this is a Twilio push */ }
}

Answering a call: callInvite.accept(context, callListener). To work correctly with ConnectionService, you must specify the correct android:name in the manifest — otherwise the system won't be able to activate the service.

TwiML and Server-Side Routing

Note: when a mobile client calls via Twilio, the request hits your TwiML Application webhook. The backend responds with TwiML — XML instructions for Twilio:

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Dial callerId="+1234567890">
    <Client>recipient_user_id</Client>
  </Dial>
</Response>

For calls to regular phone numbers, use <Number> instead of <Client>. Twilio acts as an intermediary, your server controls routing logic.

Call Recording and Analytics

Recording via TwiML <Record> or programmatically via REST API — available without SDK changes. Twilio stores recordings on its servers, providing a download URL. Call analytics (duration, quality, statuses) — via Twilio Console or REST API. We configure automatic notification of recordings to your CRM.

Twilio Voice vs. Custom WebRTC

When to Choose Custom WebRTC?

Twilio Voice adds latency through relay — all media streams go through Twilio data centers, not P2P. For most tasks this is negligible (< 50 ms additional latency at the closest PoP), but in regions without a nearby Twilio data center (Central Asia, parts of Africa) latency may be noticeable. Cost: at high volumes (10,000+ minutes/day) custom WebRTC + TURN is cheaper, but more expensive in development and maintenance. If you need P2P communication without intermediaries — contact us, we'll help you choose the architecture.

Integration Process

Full integration timeline — 1–3 weeks. Infrastructure savings — up to $50,000 in the first year.

What's Included

• Backend development and setup: Access Token generation, TwiML webhook (Node.js or Python).
• Twilio Voice SDK integration on iOS (Swift, CallKit) and Android (Kotlin, ConnectionService).
• PushKit (iOS) and FCM (Android) configuration for incoming calls.
• Testing on real devices, bug fixing.
• Integration documentation and operations manual.
• Team training (up to 2 hours online).

Contact us for a consultation on architecture and pricing. Order Twilio Voice integration from us – get stable calls in 2 weeks.

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.