Skip to main content

How push notifications work

When a client connects to the Telnyx WebRTC platform, it maintains a WebSocket connection that receives incoming call invitations in real time. If the app moves to the background or the device terminates it, that socket closes and calls can no longer reach the device. Push notifications bridge this gap. During login the SDK registers a platform-specific push token (FCM for Android, APNS for iOS) with Telnyx. When an incoming call targets that user, Telnyx sends a push notification through the appropriate service. The device wakes the app, which reconnects to the socket and receives the actual call invitation.
Caller ──▶ Telnyx Platform ──▶ FCM / APNS ──▶ Device

                                          App wakes up

                                     Reconnects WebSocket

                                   Receives call invitation

Multidevice support

A single user can register up to 5 push tokens across iOS (APNS) and Android (FCM) devices. Each time a user logs in and provides a push token, Telnyx registers it. If a sixth token is added, the least-recently-used token is removed. This means up to five devices can receive push notifications for the same incoming call simultaneously.

Platform setup

Push notification configuration has two parts:
  1. Portal setup — Create a push credential in the Telnyx Portal and attach it to a SIP Connection.
  2. App setup — Integrate the push notification service into your application code and pass the token to the SDK on login.
Each platform has its own requirements:
PlatformPush serviceCredential typeGuide
AndroidFirebase Cloud Messaging (FCM)Android Credential (service account JSON)Android guide
iOSApple Push Notification Service (APNS)iOS Credential (cert.pem + key.pem)iOS guide
FlutterFCM (Android) + APNS (iOS)Both credentials requiredFlutter guide
React NativeFCM (Android) + APNS (iOS)Both credentials requiredReact Native guide

API reference

You can also manage push credentials programmatically through the API: