Incoming SIP calls ring on Android and iPhone even with the app closed, from the provider or PBX you already have, with no changes on it. Ship the app under your brand, build on our native SIP SDKs, or take the full source code under a commercial licence.
Android and iOS put background apps to sleep, and a regular SIP app stops hearing calls. In push mode our server keeps your registration with the provider and wakes the phone with a push notification, so the call rings like any other. Your provider doesn't need to support push.
Your phone doesn't keep a connection to the provider open all day. Our server does that and wakes the phone only for a call, a message or a short refresh. You don't have to exempt the app from battery optimisation to get your calls.
Signalling goes over TLS and voice over SRTP. A TLS account uses SRTP by default; plain RTP is an explicit choice for providers that can't encrypt. In push mode the leg between your phone and our server is always encrypted.
In push mode the call's audio goes through our media relay. It finds the phone's real address behind carrier or home NAT on its own, so there's no STUN or port forwarding to set up.
The call carries on when you move from Wi-Fi to mobile data.
SipLife is a phone, not a carrier: we don't sell numbers or minutes. Add the account you already have with a SIP provider or an office PBX (Asterisk, FreePBX and other standard SIP systems). Several accounts can be used at once.
Incoming calls use the system call screen: Android Telecom and CallKit on iPhone. Bluetooth headsets, speaker and wired headsets work, and caller names and photos come from your contacts.
SipLife shows no ads: no banners, no videos before a call. The app is paid for by the push mode subscription.
The app's behaviour is written down as bench scenarios, about 280 in the catalogue today. Each one is judged by something outside the app (the PBX, our server, the operating system), never by a flag inside the app.
For VoIP providers and ITSPs, PBX vendors, UCaaS platforms and app developers who need a mobile softphone that rings.
Incoming calls reach a closed app: FCM on Android, PushKit and CallKit on iPhone. Our push server is a SIP push proxy: it registers with your PBX or SIP provider over plain SIP, so nothing changes on it, and the phone registers with it using standard RFC 8599 push parameters.
Ask for a white-label build, an SDK or the source code: info@free-simple-apps.com
A white-label VoIP app built under your name: app name, icon and colours, your own Google Play and App Store listing, your push project and your server address. Your users see a branded SIP app; the calling core is the same one tested here.
Take the softphone source code and build it yourself: the apps, the Android and iOS SDKs, the call core and the push server, under a commercial licence. The SIP engines come under their own terms.
A VoIP SDK for Android (Kotlin) and iOS (Swift): registration, calls on two lines, the system call screen through Android Telecom (ConnectionService) and CallKit, and push, with one call behaviour specified for both platforms.
The apps and SDKs sit on our own engine interface, with two engines behind it. Both run the same conformance suite against a test PBX and both do TLS and SRTP, Opus, G.722 and G.711, so the engine is a build choice, not a rewrite. It runs on baresip, with no third-party licence to buy. Already hold a pjsip commercial licence from Teluu? We build on pjsip instead.
Screens from the app's design; details may differ in the released app.
Free
The phone registers with your provider itself; calls arrive while the app is open.
Paid subscription
Reliable incoming calls while the app is closed.
Android and iOS stop background apps to save battery, and the app loses its connection to the provider. The reliable way to ring a closed app is a push notification: in SipLife's push mode our server keeps the registration and wakes your phone when a call comes in.
No. Our server registers with your provider over plain SIP on your behalf and sends the push itself. The provider must be reachable from the internet; a PBX on a private network works in direct mode.
Yes. SipLife speaks standard SIP and works with Asterisk, FreePBX and other PBXs and providers, over UDP, TCP or TLS, with Opus, G.722 and G.711.
Yes. On a TLS account voice is encrypted with SRTP by default. In push mode the leg between your phone and our server is always encrypted, even if your provider doesn't support encryption; from our server to the provider we use what the provider supports.
In direct mode your SIP password stays on the phone. In push mode our server stores it encrypted so it can keep your registration. Call and message history live only on the phone; the server holds an undelivered message for at most 7 days. See the privacy policy.
Not yet. SipLife handles two lines today: call waiting, hold and swap. Transfer, conference and video are not in the first version.