Google opens system dialer to third-party VoIP apps with Jetpack Telecom v1.1.0

At a glance:

• Google's Jetpack Telecom v1.1.0 lets third-party VoIP apps surface call logs and callbacks inside Phone by Google and other system dialers.
• The feature rolls out first to Google Meet on Android 16.1 (SDK 36.1) and higher, with a phased rollout for end users.
• Developers also get a Call Log Exclusion API so they can keep specific VoIP calls out of the native dialer history.

What changed

Google's Android team has released Jetpack Telecom v1.1.0, a library update that gives developers of third-party Voice over IP applications native-level integration with the platform's system dialers. The headline capability is integrated call logging: apps such as Phone by Google can now surface call logs directly from third-party VoIP apps, so users no longer have to open each app individually to check their VoIP call history or return a missed call.

In practice, a VoIP contact can appear alongside cellular entries in the Home tab of Phone by Google. Google's blog post shows Google Meet listed in that tab next to regular phone calls, and users can initiate a callback to a VoIP contact straight from the native system dialer. The company says the integrated logging and callback features are available for devices running Android 16.1 (SDK 36.1) and higher.

Why it matters for developers and users

The change removes a longstanding friction point for Android users who juggle multiple communication apps. Previously, a missed VoIP call in an app like Skype or WhatsApp required opening that app to see who called and to call back. With Jetpack Telecom v1.1.0, the system dialer becomes a single place to view and act on both cellular and VoIP calls.

Google is also giving developers a new Call Log Exclusion capability. This API lets app makers prevent specific calls from being logged into the system call logs, addressing privacy concerns or app-specific behavior where not every VoIP call should be visible in the native dialer history. The company notes that reasons can range from privacy to ephemeral communication to app design choices.

To guard against spam, native dialers use secure package allowlists to control which VoIP apps are displayed. This means only vetted VoIP packages can appear in the system dialer, keeping the experience clean for end users.

What to watch next

Google says it is rolling out system dialer integration in phases, starting with Google Meet. That phased approach suggests the company wants to validate the integration with its own app before opening the door wider to third-party developers. For end users, the feature will land gradually rather than all at once, and it is currently gated behind Android 16.1 (SDK 36.1), so older devices will not see the changes immediately.

Developers building VoIP apps on Android should check the Jetpack Telecom v1.1.0 release notes for implementation details and the Call Log Exclusion API documentation. As more VoIP providers integrate, the system dialer could become a universal call hub on Android — but the package allowlist mechanism means Google will retain editorial control over which apps get that privilege.