A white-label VoIP SDK is a ready-made calling engine that developers build into their own mobile or web app, so the app can make and receive internet calls under the app owner's brand. It handles the hard parts of calling: SIP or WebRTC signalling, audio codecs, network traversal, encryption, and incoming-call push notifications. Your team builds the screens and the business logic around it. You need one when calling is a feature inside a product you already have, such as a marketplace, a CRM, a telehealth app or a second-number app. If you only need a branded calling app, a ready-made white-label softphone is usually faster.
For a broader introduction to softphones, see our softphone guide.
SDK, white-label app or build from scratch?
| Option | What you get | Best for | Trade-off |
|---|---|---|---|
| White-label softphone app | A complete calling app, rebranded with your name, logo and colours | VoIP operators and resellers who want a branded app quickly | Less freedom to change the user experience |
| White-label VoIP SDK | A calling engine and components to put inside your own app | Product companies adding calling to an existing app | Your team builds and maintains the app around it |
| Build from scratch | Your own engine, based on open-source SIP or WebRTC libraries | Teams with deep VoIP experience and unusual needs | Long build, ongoing work on every OS update |
Where VoIP SDKs are used
- Marketplaces and ride or delivery apps that let buyers and sellers, or drivers and customers, talk without sharing personal numbers.
- Telehealth and education apps that need a call button inside a booked session.
- CRM and helpdesk software that adds click-to-call and call logging for sales and support teams.
- Second-number and travel apps that give users a local number for calling and texting over the internet.
- VoIP operators that want a fully custom app instead of a rebranded one.
In each case the calling feature has to feel native to the app, which is why a rebranded standalone softphone is not enough. Users should never feel they have left your app to make a call.
What a good VoIP SDK should include
- Native iOS and Android libraries, plus a WebRTC SDK for browsers, sharing one engine so calls behave the same everywhere.
- Incoming-call push. Apps are usually asleep when a call arrives, so the SDK must wake them through push notifications and show the system call screen.
- Call controls: hold, mute, transfer, speaker and Bluetooth switching, DTMF keypad, and presence.
- Codecs and network handling: support for common codecs, adaptive jitter buffers, and NAT traversal so calls connect on mobile data and office Wi-Fi.
- Security: TLS for signalling and SRTP for media.
- Themeable UI components, so you can ship a dialer and an in-call screen without designing them from nothing.
- Quality data: call-quality reports and optional recording, so support can diagnose bad calls.
- A backend to connect to: a softswitch, numbers and billing, either from the SDK provider or your own SIP platform.
The platform rules that shape your build
Mobile operating systems control how calling apps behave in the background, and an SDK must follow those rules. On iOS, Apple's PushKit documentation states that apps built with the iOS 13 SDK or later must use CallKit when handling VoIP calls. If an app cannot support CallKit, it cannot use PushKit for VoIP push notifications. In practice, every incoming VoIP push must be reported to the system as a call. Android has its own rules for background work and notifications, and these change between OS versions. A mature SDK tracks these changes for you, which is one of the main reasons not to build from scratch.
How an SDK integration usually runs
- Define the calling use case: app-to-app only, or calls to and from real phone numbers. The second needs numbers and routes behind the SDK.
- Connect the backend: point the SDK at the provider's softswitch or your own SIP server, and provision user accounts.
- Add the SDK to your iOS, Android or web project, and set up push credentials for each platform.
- Build the UI from the themeable components, or your own screens, using the SDK's call events.
- Test on real networks: mobile data, weak Wi-Fi, switching networks mid-call, and phones that are locked or in the background.
- Launch and monitor call-quality reports, and fix problems by network and device.
What it costs
SDK pricing usually combines a licence or monthly fee, sometimes per active user or per app, with usage charges for calls that reach the phone network and for any numbers you rent. Building from scratch has no licence fee, but you pay in engineering time: an engine, push handling for each platform, NAT traversal, quality monitoring, and continuing work every time iOS or Android changes the rules. For most product teams, the SDK route costs less within the first year.
Questions to ask an SDK provider
- How long has the engine been in production, and how many apps use it?
- How quickly are new iOS and Android versions supported?
- Can the SDK connect to my own SIP backend, or only to yours?
- Are numbers, routes and billing available if I need calls to the phone network?
- Can I rebrand everything, including emails and portals, and is there a monthly rental option?
If you are launching a calling service rather than adding a feature, read how to start a mobile VoIP business, and compare the SDK route with a white-label app such as MoSIP.
How Voxvalley helps
Voxvalley's calling SDK puts the engine behind MoSIP into your own app. It includes native iOS and Android SDKs, a WebRTC SDK for browsers, themeable dialer components, call controls (presence, transfer, hold and mute), incoming-call push including VoIP push on iOS, and optional recording and call-quality reports. It runs on Voxvalley's softswitch, numbers and billing, or on your own backend. The same stack powers our white-label softphones, which have served 1,800+ VoIP operators with 20M+ downloads and 1,000+ white-label builds since 2010. Everything is available white label and on monthly rental through our partner programme.