Liblinphone is a high level library integrating all the SIP video calls feature into a single easy to use API. Usually telecommunications is made of two things: media (transport of voice or video, encoding and decoding...), and signaling (routing calls, ringing, accepting a call etc...).
Liblinphone aims at combining the two things together and doing most things automatically. This makes it easier to the programmer to implement video calls in any application, without being an expert in VoIP and telecommunications. Liblinphone is an open source library based on Mediastreamer2 for voice/video streaming, and belle-sip for SIP signaling.
Liblinphone in Linphone architecture
Linphone and linphonec are directly based on Liblinphone.
- SIP user agent compliant with RFC 3261
- SIP/UDP, SIP/TCP, SIP/TLS
- IPv6 dual stack or v6-only mode
- Digest authentication
- Supports multiple calls simultaneously with call management features: hold on with music, resume, transfer...
- Multiple SIP proxy support: registrar, proxies, outbound proxies
- Text instant messaging with delivery and "is typing" notification
- Presence using list subscription to presence server, or in peer to peer mode
- DTMF (telephone tones) support using SIP INFO or RFC 2833
- Generic SUBSCRIBE/NOTIFY and PUBLISH
Liblinphone leverages on mediastreamer2 engine for rendering audio & video streams, and as such takes advantages of all features implemented in mediastreamer2.
Liblinphone is available on the following platforms:
- GNU/Linux: x86, x86-64, ARM v5, v7, arm64 ; Debian 7/8, Centos 6/7
- Windows Desktop: x86 (works also on x86_64) Vista and later
- Mac OS X: x86_64 ; 10.7 and later.
- GNU/Linux embedded: Linphonec or liblinphone are good candidates to provide the software stack of an hardware phone or hardware communication system.
- Apple iOS 8 to 10 (ARM v7, ARM 64)
- Google Android 4.1 to 7 (ARM v5 to v7, x86)
- BlackBerry OS10 (ARM v7)
- Windows Phone 8 and 8.1 (ARM v7)
- Session Initiation Protocol, RFC 3261
- 8. General User Agent behaviour
- 9. Cancelling a request
- 10. Registrations
- 12. Dialogs
- 13. Initiating a session
- 14. Modifying an existing session
- 15. Terminating a session
- 17. Transactions
- 18. Transports
- 22.4 The Digest Authentication Scheme
- Session Description Protocol, RFC 4566
- An Offer/Answer Model with the Session Description Protocol (SDP), RFC 3264
- An Extension to the Session Initiation Protocol (SIP), RFC 3581 (use of rport parameter)
- Session Initiation Protocol (SIP) INFO Method and Package Framework, RFC 6086
- 4. The INFO Method
- The Session Initiation Protocol (SIP) Refer Method, RFC 3515
- 2. The REFER Method
- Session Description Protocol (SDP) Security Descriptions for Media Streams, RFC 4568
- Managing Client-Initiated Connections in the Session Initiation Protocol (+sip.instance parameter), RFC 5626
- Connection reuse in the Session Initiation Protocol (alias parameter), RFC 5923
- Correct Transaction Handling for 2xx Response to Session Initiation Protocol (SIP) INVITE Requests, RFC 6026
- A privacy mechanism for the Session Initiation Protocol, RFC 3323
- Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks, RFC 3325
- Indication of message composition in instant messaging, RFC 3994
- Interactive Connectivity Establishment (ICE), RFC 5245
- Re-INVITE and Target-Refresh Request Handling, RFC 6141, chpt. 5 only
Presence and Instant Messaging
- Session Initiation Protocol (SIP)-Specific Event Notification, RFC 3265
- A Presence Event Package for the Session Initiation Protocol (SIP), RFC 3856
- Session Initiation Protocol (SIP) Extension for Instant Messaging, RFC 3428 (only text/plain messages)
- Session Initiation Protocol (SIP) Extension for Event State Publication, RFC 3903 (Creation of PUBLISH requests)
- A Data Model for Presence, RFC 4479
- RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF), RFC 4480
- Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP), RFC 5367
- SIP-specific event notification, RFC 6665
- SIP body compression, RFC 1951
- Message Body Handling in the Session Initiation Protocol, RFC 5621
Liblinphone is dual licensed. It can be licensed and distributed:
- under GNU GPLv2 license - for free (open source)
- under proprietary and commercial license to be used in closed source applications. Contact Belledonne Communications for costs and other service information.
Liblinphone Android version:
Liblinphone iOS version:
Liblinphone win32 SDK version:
Liblinphone macos SDK version:
Please see Linphone Source code section.
The Liblinphone wiki gives good hints to start programming with liblinphone.
The API reference documentations are available in various formats depending on the target programming language:
Liblinphone C API documentation (used for Linux, Windows, Mac and iOS) documented with Doxygen.
Liblinphone's Java wrapper for Android applications.