Web Phone

Edit Package linphone

Linphone is a Web phone with a GNOME interface. It lets you make
two-party calls over IP networks such as the Internet. It uses the IETF
protocols SIP (Session Initiation Protocol) and RTP (Realtime TransporT
Protocol) to make calls, so it should be able to communicate with other
SIP-based Web phones. With several codecs available, it can be used
with high speed connections as well as 28k modems.

Build with ALL features enabled.

Source Files (show merged sources derived from linked package)
Filename Size Changed
liblinphone-5.2.98.tar.bz2 0020416906 19.5 MB
linphone-build-jsoncpp.patch 0000000889 889 Bytes
linphone-build-readline.patch 0000007041 6.88 KB
linphone-fix-pkgconfig.patch 0000001236 1.21 KB
linphone.changes 0000043185 42.2 KB
linphone.spec 0000013389 13.1 KB
openldap-bc.tar.bz2 0005050810 4.82 MB
reproducible.patch 0000001494 1.46 KB
set_current_version.patch 0000000374 374 Bytes
Comments 2

Ki Mi's avatar

Hello Sergey!

I tried to remove some of the compiling errors by linking from your project to here. Fedora 35 almost compiles, but there is a linking error somewhere that I can't see how to resolve. The log.

Maybe you can reuse some of the patch for Fedora 35.

Have you by any chance tried to get it to work for Debian/Ubuntu too? It would be awseome if it worked on everything so that people can call each other no matter what OS they are on. Most of the code is already ported to Debian/Ubuntu, it is just the last bit liblinphone and linphone-desktop gui app left.

One issue that I saw was that limeon OpenSUSE installs to /usr/lib64. The same code on Fedora 35 installs to /usr/lib, which then makes an issue for liblinphone to find it, when it expects it to be in /usr/lib64.

Bare cloning of code that compiles on OpenSUSE to a new package makes it fail and it is difficult to know why. It should just compile when just cloned to a new package. CMake is missing some files when package is cloned, and very difficult to know why that happens. It is the same system... Also noted that it depends which worker that is compiling as if it is not the same system on every worker.

I hope you find it helpful that I let you know that your code, with patches, is now 99% compiling. Maybe a joint effort can make it work on all the major linux OS systems, as some machines can only run a specific type of linux distribution due to hardware limits (semi-working hardware), but people still want to call each other no matter what they are using.

Sergey Kondakov's avatar

Sorry, I've missed the notification. To be honest, I'm better versed in Gentoo's ebuild system than RPM spec and whatever Debian uses. To figure out build errors one have to be well versed in exact toolchain workings of the target distro, so I can't even attempt to write universally compatible scripts. All SIP clients usually have ridiculous amount of dependencies, some of which are incompatible forks of more common packages and some are statically-linked bundled libraries which depend on more common shared libraries of one particular version (sometimes not even being versioned correctly, so it tries to compile with an incompatible version and errors out weirdly). It's a glorious mess.

And I also stopped actively maintaining this package after ending my experiments with SIP chatting, concluding that Linphone might be the most stable feature-complete client and Ring/SFLphone/Jami is the most ambitious yet perpetually broken. It's probably easier and more secure to get equivalent opus/vp9-based audiovisual chats in something like a Tox-protocol P2P client.

openSUSE Build Service is sponsored by