PHONELIB

An open source VoIP framework developed by Coffee IT in collaboration with Spindle devhouse.

THE CASE

PhoneLib makes it easier to implement VoIP functionality in an app. The framework ensures that the deploying app has no dependencies on the underlying SIP framework and provides a set of features that reduce the need for the deploying developer to have SIP knowledge.

Currently, PhoneLib depends on Linphone. The deploying app has no knowledge of this. This keeps the framework flexible to switch to another underlying SIP framework in the future.

Library

A library developed by Coffee IT. Native techniques with the SIP library Linphone. The Gradle framework is used for Android and Cocoapod for iOS.

VoIP communication

Incoming/outgoing calls, hold, mute, speakerphone, various audio codecs, conference calls, video calling, call waiting and transfer.

Open source

By making the technology public, Spindle and Coffee IT stimulate innovation development in VoIP technology.

ABOUT PHONELIB

Together with Spindle, we have worked to make developing VoIP apps easier. With the PhoneLib framework, parties and developers without VoIP-specific knowledge can use the technology. This reduces the barrier for solving complex VoIP issues for medium-sized companies. In addition, Spindle is no longer dependent on the underlying SIP framework 'PJSP'.

PhoneLib can be implemented by apps like Vailer. Vailer is one VoIP app of VoIPGrid what we have been working on.

THE TECHNICAL SUPPORT

The techniques are native, with Linphone as the SIP library. For Android we have for one Gradle framework chosen, for iOS cocopods. The code is made available Open Source via Github. This allows anyone to use the code.

We have done extensive research into the best SIP framework. We weighed up PJSIP, Linphone and PortSIP against each other. In the end, we chose Linphone because of its better technical performance.

THE TECHNICAL CHALLENGE

The techniques used for this framework are Linphone, Gradle and Cocoapods.

One of the spearheads when developing the framework was to ensure that the apps that will eventually implement the framework have no reference whatsoever to the underlying SIP framework. This ensures flexibility. If it turns out that Linphone does not sufficiently meet the wishes, we can easily change this.