UPDATE <\/p>\n
Audio and video now works. I have also sent some patches to the Jitsi project in order to make the work of the port easier. I will update the port soon. As soon as everything is done, this page will be probably deleted. <\/p>\n
Jitsi is an open source VoIP and IM application. It supports several popular protocols (most notable SIP and XMPP), and offers encrypted chat (OTR) and encrypted voice and video calls (ZRTP). It is mostly written in Java (Swing for the GUI also) with some parts written in C because it uses a plethora of third-party libraries in order to be multiplatform (when Java fails, the third-party libraries come to the rescue). <\/p>\n
The purpose of this page is to serve as a starting and coordination point for anyone that wants to help in the process of integrating Jitsi into FreeBSD. Throughout the years, the Jitsi mailing lists have received emails from several people who were trying to port Jitsi on FreeBSD with working audio\/video calls, but as far as I know, at the moment we don't have such a thing. <\/p>\n
Jitsi 2.2 (latest stable version) exists in the Ports tree under net-im\/jitsi. <\/p>\n
Unfortunately, the new version (2.2) that exists in the Ports tree, does not solve any of the existing problems. The current problems are: <\/p>\n
I think that this is the issue with the highest priority. If we fix the audio, probably we will be able to make encrypted voice calls - one of the most useful features. <\/p>\n
Jitsi supports 3 audio systems: <\/p>\n
On a Debian GNU\/Linux system, Jitsi offers 2 audio systems: PortAudio and PulseAudio. On a Windows 7 system it also offers WASAPI (Windows only). In FreeBSD, I assume that it is possible to have both PortAudio and PulseAudio. <\/p>\n
The reason that the number of features of Jitsi differs from one platform to another is that in the lib\/native directory of the source of Jitsi, there are directories for every platform (i.e. freebsd, freebsd-64, linux, linux-64, mac, solaris, solaris-sparc, windows, windows-64). Every platform has a different number of libraries inside. For example, the freebsd directory has 5 libraries whereas the linux directory has 24 (including both the libjnportaudio.so and the libjnpulseaudio.so that are responsible for the available audio systems in Jitsi). If you are on a Debian GNU\/Linux amd64 system running Jitsi from source, and you remove the libjnportaudio.so library from the linux-64 directory, you won't be able to have the PortAudio option in the available audio systems of Jitsi. <\/p>\n
So there are 2 options (that I can see): <\/p>\n
In order to build the libjnportaudio.so library, you have to download the source of libjitsi (https:\/\/jitsi.org\/Projects\/LibJitsi<\/a>). Then, the procedure can be summarized in the following steps: <\/p>\n Download the hotplug branch of PortAudio (check src\/native\/portaudio\/README), patch it with the src\/native\/portaudio\/portaudio-hotplug-os.patch, configure and make. <\/p>\n If you follow the above procedure in an officially Jitsi supported platform (ex. Debian GNU\/Linux i386), the chances are that you will end up with a libjnportaudio.so file under the lib\/native\/linux directory of libjitsi. <\/p>\n The procedure is a lot easier than in libjnportaudio.so. It basically needs three things: <\/p>\n Some minor changes to the target pulseaudio of the src\/native\/build.xml in order to compile under FreeBSD <\/p>\n Invoke the command ant pulseaudio inside the root directory of libjitsi <\/p>\n I have produced the libjnpulseaudio.so library but when I placed it under the directory lib\/native\/freebsd-64 of Jitsi I did not get PulseAudio in the drop down menu of Audio Systems. Probably it needs some changes in the Java files in order to detect it (TODO)? <\/p>\n <\/p>\n View original post here: UPDATE Audio and video now works. I have also sent some patches to the Jitsi project in order to make the work of the port easier Continue reading
\nJitsi - FreeBSD Wiki<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"