Push notifications

Push notifications are required for reliable inbound call delivery when the app is backgrounded or killed.

Step-by-step breakdown

1. Register onCallInvite listener — Before anything else, your app must register the onCallInvite listener. This ensures the callback is in place when a push arrives.

2. Incoming call — A caller initiates a call that targets your user. The Vonage API resolves the destination and determines the user's device needs a push notification.

3. Push invite payload — The Vonage API sends the call invite payload to the platform push service (APNs for iOS, FCM for Android).

4. Deliver push — The push service delivers the notification to the device's OS. On iOS this arrives via PushKit (VoIP push). On Android this arrives via FCM's data message.

5. Push callback — The OS delivers the push payload to your app's push handler:

   • iOS: Call processCallInvitePushData inside the PushKit delegate callback.
   • Android: Call processPushCallInvite inside onMessageReceived.

6. onCallInvite callback fires — The SDK processes the push payload and fires onCallInvite. Present the incoming call UI with caller information and answer/reject actions.

Prerequisites

Before implementation, complete Vonage dashboard push setup for your application credentials:

• Vonage iOS push setup
• Vonage Android push setup

Platform Guides

For comprehensive implementation walkthroughs including full code samples, flow diagrams, error handling, and production checklists, see the platform-specific guides:

• iOS Push Notifications Guide — PushKit, CallKit, audio session handoff, and common pitfalls
• Android Push Notifications Guide — FCM, Telecom framework, ConnectionService, and foreground service requirements

Web support

Web SDK does not use native mobile-style push notifications for incoming voice invites. Invites are delivered over the WebSocket session while it is active.