Savoir-faire Linux is proud to announce the immediate availability of SFLPhone 1.4.0. This release finally enables video by default. We have refactored the video implementation to be much more robust against a variety of conditions and made the configuration more flexible. It is also now possible to stream a variety of file types and even share your screen. Other interesting features include support for the JACK audio system used by audio industry professionals and hobbyists. Thanks to improvements in audio buffering, latency and resampling, audio quality is noticeably better. The KDE client now has much better Akonadi support. It can now act as a KAddressBook replacement for most phone related scenarios. There will probably be one final KDE4 release before officially making the switch to KF5. The SFLPhone-KDE logic backend, libqtsflphone, has been compatible with Qt5 for over a year, some of the UI dialogs have yet to be ported. As for SFLPhone in general, we plan to merge work that has been done in parallel for a while now to make the daemon more modular, easier to build, more secure and more portable to other operating systems.
Please update or comment on this ticket to add user noticeable changes and new features
Common features
- Jack support
- Video support by default
- Ability to share screen
- Ability to stream videos, images and text files
- Support GnuTLS as an alternative to OpenSSL
- Persistent camera configuration (per device)
- Switch video sources during a call
- Enable or disable video per account
- Packet loss concealment
- RTCP support
- Builds with clang
libqtsflphone
- Pluggable history storage
- Improved pluggable storage backends
- Datasource extensions support
KDE client
- Now a fully featured contact manager
- Add, edit and manage contact sources
- Delete contacts from the interface
- Attach contact sources to auto completion or presence tracker
- Basic video effects like rotate or enforce aspect ratio
- Video full screen mode
Stats
KDE client: 203 files changed, 10979 insertions, 3933 deletions, 102 commits, 36 issues closed, 19 bugs closed
Daemon: 256 files changed, 14448 insertions, 9781 deletions, 628 commits, 543 issues closed, 214 bugs closed
Get SFLPhone-KDE
Kubuntu packages are available at: https://launchpad.net/~savoirfairelinux/+archive/ubuntu/ppa
The source get be obtained from git://anongit.kde.org/sflphone-kde or from http://sflphone.org .
Things related to stuffs I want to talk about? 
Awesome, thank you!!
I just downloaded SFLPhone-kde for first time.
I tried to create a free sip account on sflphone.org via the welcome wizard. How am supposed to know if it is secured with ZRTP? I don’t even know what it is. Next in the wizard is to activate STUN if I’m behind a firewall, sure I am but I don’t know the name of the stun server so I have to leave it blank. Finally I am told to check my setting before I click finish but the page is blank – there is nothing to check – I just clicked finish anyway and the Wizard closed. It doesn’t seem like I have added an account in the account settings, there is only IP2IP.
Where do I file a bug?
First of all, are you sure you are using 1.4? I was sure I disabled the sflphone.org accounts last week. There is much better free providers out there, so giving a basic free account wasn’t really useful beyond testing purpose anymore. As for the encryption, they were not secure at all. Like most SIP account, ZRTP is not enabled directly.
ZRTP by itself is mostly useless, if the handshake (using SIP) is not itself encrypted using PKI keys, the RTP keys will be negotiated in clear. Currently, SFLPhone doesn’t generate certificate itself. First of all, generating self signed certificated is of dubious value for this kind of usage and then it require some work that will only be merged in the next version.
Very few providers actually enable full security by default. This is unfortunate and will eventually change, but most SIP hardware and software still have hard time with it. SFLPhone is actually one of the only client with SIPS+ZRTP that is working with more than 1 implementation. But security is hard, and before bragging about that, a lot of work remain to be done to actually be secure rather than “implementing security features”.
As for the other question, but can be filled at https://projects.savoirfairelinux.com/issues/
As for where to get better accounts, that all depend where you live, as some will provide a different set of features and very cheap “voice plan” to get a real local phone number for about 5% of the price an usual landline phone provider will offer. You can also use the same number on both your smartphone, desktop and physical phone with a “first to pickup the phone” answer policy.
Thanks for trying SFLPhone-KDE
I was running 1.3 since I had forgotten “apt-get update” after adding ppa.
Personally I don’t care so much about calling telephones, but it would be nice as a replacement for skype, e.g. talking to my wife. So the idea of having a wizard and getting an account easily would be great – just without being confronted with things like ZRTP and STUN server.
Perhaps make a deal with an open source friendly sip provider that will give the SFLPhone som kickback if they start making money on the users. Could be spent on motivating the development 🙂
Maybe we may do such deals eventually, some provider list us as a supported client for Linux, so we have somewhere to start with. I guess, for now, the Ekiga guys still support free SIP accounts. We technically still do, but our servers are not always up or even updated. The bug you encountered in 1.3.0 is one example among other of why we dropped official support for sip.sflphone.org. The other was the fact that there is very little active users as our main use case is to replace the phone on your desk at work (90%+ of them are SIP compatible). We also have a good user base that use SFLPhone as a SIP client for residential VoIP providers. We have plans for a Skype* like distributed, peer to peer and hard-encrypted network, but while we do have some pieces in place, most of them are not even in development yet.
As for the original question, you don’t need ZRTP and it wont really make any difference for normal users. STUN is for users with some special NAT settings to bypass the firewall, you probably don’t need one). If the account have not been created after that, then something else went wrong. As I said, sip.sflphone.org is deprecated in favor of all the much better free service provider you can find on Google/DuckDuckGo.
*The original network, not the NSA friendly replacement Microsoft switched to
Just for the backtrack: There is already a skype p2p alternative in development.
It’s called tox. https://tox.im/en
Yes, we are still evaluating if we can/want to be interoperable with them. DHT streaming is cool, but AFAIK (I am not the one working on this) there is no standardization for such use case. Beside this, our core audience and objectives are not 100% in line with tox, but there is a lot of overlap, so we will see how it goes. We still have some major work left to do before being able to properly support a 3rd protocol. While SFLPhone IAX support usually work well enough, the core code (sflphone daemon) is tied to SIP, this will soon change.
Pingback: Links 19/7/2014: CRUX 3.1 is Out, CyanogenMod Competes With Google Now | Techrights
What themes are used in the second screenshot?
The Qt theme is Oxygen with the stock dark palette, the WM is AwesomeWM with some KDE integration extensions (available in my github.com/Elv13 account) and my own theme (SciFi)
Hello admin do you need unlimited articles for your
page ? What if you could copy post from other sites, make it pass copyscape
test and publish on your website – i know the right tool for you, just type in google:
kisamtai’s article tool