Download Jitsi 2.10.5550 – softpedia.com

Jitsi is an application designed to offer you a simple and fun way in which you can keep in touch with the people in your life.

It offers you chat, video and audio communication, all of which are possible through a comprehensive and good looking graphic interface. It supports protocols like XMPP, Jabber, SIP, AIM/ICQ, Yahoo, Windows Live and others.

As is characteristic to nearly all IM applications, Jitsi offers you a main window that contains your contacts list from where you can perform various tasks. You can change your status, call a friend or send a file. Everything about the application is straightforward and user-friendly.

Contacts can be placed into custom groups, renamed and relocated at any time. You can edit their info and start a secure chat with them. With Jitsi its possible to make audio and video calls, perform desktop streaming, make audio conference calls and record them, as well as encrypt all your calls.

It proves itself to be a reliable means of communication for all kinds of environments, home, school and even business.

The level of security that Jitsi offers is one you should not overlook. It provides encrypted password storage, call authentication, call encryption and DNSSEC support.

As far as instant messaging goes, Jitsi offers you a lot of functions from the chat window. You can invite more people to join in, call a certain contact, initiate a video call, send a file, start secure chatting and of course insert various types of emoticons.

In case you are busy or away from the computer, Jitsi provides auto answer and call forwarding to any other accounts that are added to the application.

In closing, if youre looking for an environment that brings together all the major chatting platforms then you can try Jitsi.

Chat client Internet phone VoIP client Communicate Chat Messenger VOIP

Excerpt from:

Download Jitsi 2.10.5550 - softpedia.com

Jitsi (Build 3132) – OnSIP

The following review was conducted inApril 2011.

Unbeknownst to many people, there are a growing number of free stand-alone VoIP clients, some of which arent half bad. Today Im going to be doing an in-depth look at one of these free downloadable clients, Jitsi, which is described as an audio/video Internet phone and instant messenger that supports some of the most popular VoIP and instant messaging protocols such as SIP, Jabber, AIM/ICQ, MSN, etc

The list is extensive, but it had me at SIP and Jabber.

Jitsi, which is written mostly in Java, is a free and open source VoIP, and instant messaging application for Windows, Mac, and Linux. Its currently in alpha. Stable releases come out every so often while nightly builds are released several times a day. When appropriate, users are automatically prompted to download and install the latest build (or you can just tell it to do this all without asking).

What separates this application from others like it is the inclusion of enterprise VoIP features such as attended and blind call transfer, call recording, call encryption, conferencing, and video calls.

This version of the application looks and feels great. The main UI is simple and clean, the pop-up call handling screen is easy to use, and the instant messaging feature is handled nicely. Jitsi certainly aims to accomplish a lot. While you can almost expect a few glitches here and there, it is certainly worth trying out.

[ Relevant Sidenote: This review was conducted on a Macbook Pro. ]

As usual, I am going to do a quick walk through of how to setup OnSIP with Jitsi. A lot of these steps apply no matter which VoIP provider youre using so I noncustomers will also find this useful. Youre going to need your user credentials. They can be found in your OnSIP admin portal under users. Here is an example of the fields you will need:

Setting Up VoIP Calling

Open up Jitsi and select +Add New Account under File. You should see a screen pop up that looks like this:

Select SIP as your choice from the options provided in the Network dropdown menu, and then hit Advanced in the lower left corner.

Youll be taken to another menu with 3 parts: Account, Connection, and Presence. Account is pretty self-explanatory. Under SIP id, youll want to input your entire SIP address. Password is your SIP password, and display name can be anything you want.

Next, in Connection, input your Proxy/Domain in the field marked Registrar, and your Auth Username into the field marked Authorization name. Youll want to uncheck Configure proxy automatically if it isnt already, and type sip.onsip.com into the field labeled Proxy if you are an OnSIP customer (Port 5060). Make sure that preferred transport is UDP and that the Keep alive method is Register.

In Presence, simply check Enable presence (SIMPLE) and leave everything else unchecked.

Hit the Next button. Youll be taken to a summary page where you can go over your settings one last time before you sign in.

Go into the Jitsi preferences. You should see a screen that looks something like the image above, with a list of all your active and inactive accounts. Select Audio and make sure that the codecs (or encodings) enabled are G722, PCMU, PCMA, and telephone-event.

Setting Up XMPP

Setting up IM is even easier. Here Ill show you how to get your my.OnSIP contacts in Jitsi. Once again, select +Add New Account under File. This time, youll want to select Jabber in the Network dropdown menu, and hit Advanced in the lower left corner. Youll be taken to another menu with 3 parts: Account, Connection, and Advanced. In Account, input your my.OnSIP login credentials. Skip the Connection section since you dont need to change anything there and uncheck the three options you see in Advanced (Use ICE, Auto discover STUN/TURN servers, and Use Jitsis STUN server in case no other servers are available). Click Next at the bottom of the menu, and then Sign In on the summary page that follows.

At Junction Networks, we put each of the phones we use through a multi-step interoperability test in which we apply ~30 test cases. An example of a test case would be the following:

Test phone calls phone B

B picks up

B puts Test phone on hold

B calls phone C

C picks up

B transfers test phone to C

Call must be transferred correctly to C. B must be released correctly after the transfer. When C picks up, audio must work in both ways between test phone and C. When test phone is on hold, there is no audio between it and phone B.

Build 3132 passed our test cases with no issues.

When I first installed Jitsi a couple of months ago, there was so much static that having an intelligible conversation was impossible. Whatever the issue was, it has since been patched and resolved.

Jitsi supports G.711 as well as the G.722 wideband codec. Narrowband calls sound about as good as a regular landline call.

High definition calls with the Jitsi sound absolutely fantastic. You can get HD VoIP calls as long as the person youre on the call is also using an HD capable device. I heavily recommend using a USB headset when making calls with a soft phone on your computer to get the optimum experience. You can pick up a good headset for less than $30.

For something that costs the end user nothing, Jitsi is a surprisingly good attempt at a unified communications client. I like to think of it as a bare-bones version of Microsoft Lync that doesnt cost me $700+ to setup, and $100 per download.

The main user interface of Jitsi looks a lot like any other IM client, except that you can have a dedicated section for voice contacts in your consolidated buddy list. Clicking on what looks like a small watch face will take you to your call history. You can conveniently redial from this screen. Right next to the watch face button is a search field, which will draw from both your contacts list and your call history. This field will also act as your dialer. Start typing in any number or SIP address, and a small green handset will appear that you can click to initiate the call.

Every contact in your buddy list and call history menus can be dragged and dropped into an ongoing call. What do I mean by that? With Jitsi, every call gets its own pop up window. Its here that youll find all of your call handling options: dialpad, create a conference call, hold, mute, record, video, desktop share, transfer, etc. Dragging and dropping people from your buddy list or call history menu into an ongoing call automatically creates a conference call. This seems to work without a hitch, and youre not just limited to a 3-way conference.

The image above shows the popup window you see during each call. You can have several calls going at once (simply call another number or SIP address using the dialer field in the main Jitsi UI and any active calls you have at the time will automatically be put on hold), and each one opens up a new window. Ill very briefly go over some of the functions of interest.

Youll notice that almost everything you can do with Jitsi is laid out in a row at the bottom. At the very left is a button that looks like an old school rotary dialer. This will append a numpad to the bottom of the window so that you can interact with attendant menus, etc. Next is your conference button. This brings up a window that you can use to invite multiple people to the call at the same time.

The next three buttons are self-explanatory: hold, mute, record (you can designate which file you want to save your recordings in the Advanced section of the application preferences).

Next is the button to turn on the video. Supported video compression formats include H.263 and H.264. Ill admit that I havent spent too much time testing out video calls on Jitsi, but the few video calls I have done (on Wifi, with just the built-in iSight camera on my Macbook and H.264 selected) were better than I was expecting. No experience-ruining frame rate or picture resolution issues here. I did try doing a video call with a coworker on her Counterpath soft phone and we werent able to get it working, despite the fact that they were using the same codec. We will do more testing and Ill update this review with our findings. Also keep in mind that a lot of factors will affect the quality of your video calls, and many of the problems you or I experience may have very little to do with the application. We plan to include video calling cases as part of JN interoperability test in the near future for applicable user agents.

According to the Jitsi development roadmap, there are tentative plans to implement multi-party video conferencing in Q1 2011.

Finally, Jitsi users can easily conduct blind and attended transfers. If only one call is active, clicking on the transfer button brings up a window where you can quickly input the transfer destination and send the caller on his/her way. If you have multiple calls active, clicking on the transfer button will open up a dropdown menu that includes all your active calls so that you can quickly conduct an attended transfer. Of course you can also choose to transfer to another number as well.

Now lets talk about some of the stuff that doesnt work quite as well.

If youre a my.OnSIP user, then you might be used to having the ability to click-to-dial and IM the same contact. You dont really get the same experience with Jitsi. My.OnSIP uses XMMP for IM and OnSIP uses SIP for voice, which means that youll have to have two separate accounts, and two separate contact lists for the same group of people. It can get especially confusing if the two types of contacts for one person look exactly the same. Long story short: Remember to use your SIP account for calling and your Jabber (XMMP) account for IM.

Adding phone numbers to the voice contacts could be better streamlined. Here is what the add contact form looks like:

Youll notice that you only get to specify the contact name. It actually works fine if youre adding a SIP address. If I type jondoe@example.onsip.com into the contact name field, Jitsi will know to use that as the SIP address, and will even cut off the domain in my contact list so that only jondoe is displayed. Adding actual telephone numbers is a little annoying since the contact name field is really the what to dial field. Sure you can go back after the contact is added and rename the number to a persons name but this seems like an unnecessary step.

Since Jitsi is a project that is literally updated several times every day, I dont think a Final Thoughts section is necessarily appropriate. The application has come a long way in a very short time, and there are big plans for the coming year. We expect a lot of updates and fine-tuning.

I would recommend giving this soft phone a download if you do not already have one on your computer, or if youre completely new to VoIP and SIP and just want a way to test out IP calling. Its free so what have you got to lose?

Continued here:

Jitsi (Build 3132) - OnSIP

Jitsi Meet (advanced) Projects

How to join Jitsi Meet video conferences over the Web

If you do not already know what Jitsi Meet is, here is the official homepage. Jitsi Meet allows you to create and join video calls over the Web (even as a simple viewer). Some of its features are: encrypted by default, no account needed, invite by pretty URL https://mysite.com/myroom

Thanks to UV4L it is possible to create or join an existing room and broadcast live video and audio to all the participants or viewers in the room from a camera and a microphone connected to the Raspberry Pi. Its also possible to automatically hear and see other participants if you have speakers and display (HDMI, touchscreen, etc) connected to the Raspberry Pi. Of course, other participants can be other Raspberry Pis. The great news is that you do not need any browser installed on the Raspberry Pi to do this.

Its necessary to install the required packages before proceeding: uv4l, uv4l-server, uv4l-webrtc, uv4l-xmpp-bridge and one video driver (e.g. uv4l-raspicam, uv4l-uvc, etc). Please refer to these installation instructions for more details.

To start and stop streaming to a particular Jitsi Meet server (called videobridge), its enough to invoke the corresponding commands by means of the UV4L Streaming Server installed on the Raspberry Pi. This can be done in two ways.

The first convenient way is through a browser by using the Jitsi Meet control page available at the URL the Streaming Server itself is listening to (e.g. http://myraspberrypi:8080), from which its possible to specify all the mandatory informations (i.e. XMPP and/or BOSH signalling server, chat room, your username and password) required to establish a connection and to click on start/stop buttons in order to join or leave the specified room respectively.

The second way is to invoke the start/stop commands via HTTP/GET requests sent to the Streaming Server from command line. For example, to start streaming to the videobridge which is at the base of the official, free-access Jitsi Meet service at meet.jit.si, type (in one line):

where raspberrypi will have to be replaced with the real hostname of your Raspberry Pi in your network (it can be localhost if you are executing the command from within your Raspberry Pi) and port will have to be replaced with the real port number the Streaming Server is listening to (8080 is the default). The above command will make the Raspberry Pi create or join a conference at http://meet.jit.si/testroom.

If the UV4L Streaming Server is providing HTTPS instead of HTTP, be careful to specify https://[] in the URL. You may also desire to add the insecure option to curl to turn off the verification of the servers certificate (see the curl manual for more details).

Please note the parameters in the URL that you are allowed to specify:

server (XMPP server hostname or ip address) port (port the XMPP server is listening to) muc (multiuser chat domain) room (desired room you want to join or create) room_password (room password, if the room is protected) username (desired username in the chat room) password (password if the server is password protected) reconnect (try to reconnect after disconnection) bosh_enable (1 if you want to use BOSH signalling, 0 otherwise) bosh_server (usually HTTP(S) server hostname for BOSH) bosh_tls (1 for HTTPS, 0 otherwise) bosh_port (typically 443 for HTTPS, 80 for HTTP) bosh_hostname (connection manager hostname, typically the same as bosh_server) action (Start or Stop streaming)

All the above settings can be optionally specified once for all in the UV4L configuration file (except action) (see the uv4l-server manual for more details).

Similarly, to stop streaming:

If you are protecting the UV4L Streaming Server with a password, then the above URL will not work. In this case, you must specify user and password in the URL as in the below example:

Continued here:

Jitsi Meet (advanced) Projects

Jitsi Download – softpedia.com

Jitsi is an application designed to offer you a simple and fun way in which you can keep in touch with the people in your life.

It offers you chat, video and audio communication, all of which are possible through a comprehensive and good looking graphic interface. It supports protocols like XMPP, Jabber, SIP, AIM/ICQ, Yahoo, Windows Live and others.

As is characteristic to nearly all IM applications, Jitsi offers you a main window that contains your contacts list from where you can perform various tasks. You can change your status, call a friend or send a file. Everything about the application is straightforward and user-friendly.

Contacts can be placed into custom groups, renamed and relocated at any time. You can edit their info and start a secure chat with them. With Jitsi its possible to make audio and video calls, perform desktop streaming, make audio conference calls and record them, as well as encrypt all your calls.

It proves itself to be a reliable means of communication for all kinds of environments, home, school and even business.

The level of security that Jitsi offers is one you should not overlook. It provides encrypted password storage, call authentication, call encryption and DNSSEC support.

As far as instant messaging goes, Jitsi offers you a lot of functions from the chat window. You can invite more people to join in, call a certain contact, initiate a video call, send a file, start secure chatting and of course insert various types of emoticons.

In case you are busy or away from the computer, Jitsi provides auto answer and call forwarding to any other accounts that are added to the application.

In closing, if youre looking for an environment that brings together all the major chatting platforms then you can try Jitsi.

Read the original post:

Jitsi Download - softpedia.com

OpenFire Jitsi as Skype(desktop sharing) and Temviewer …

Openfire Jabber/XMPP is a server written in JAVA. This is free software and is also official support. Management has a WEB panel and it works on 9090 (http) and 9091 (https) ports.It supports Plugins(extensions), SSL/TLS, can connect to the database(Oracle, MSSQL, PostgreSQL, DB2, Sybase ASE, MySQL or internal database HSQLDB) via JDBC, can connect LDAP groups and filter by groups, has the ability of users registration based on to different sources and supporting different languages. Most of the management is done via the web interface. The official website is http://www.igniterealtime.org/.

Features:

Supported client programs:

Add SRV records in your DNS server as follows:openfire IN A 94.20.81.149_jabber._tcp.jabber.unixmen.com. IN SRV 0 0 5269 jabber.unixmen.com._xmpp-client._tcp.jabber.unixmen.com. IN SRV 0 0 5222 jabber.unixmen.com._xmpp-server._tcp.jabber.unixmen.com. IN SRV 0 0 5269 jabber.unixmen.com.

Before all configuration we will create MySQL database, user and password because we will use this in next configurations:mysql -uroot -pmysql> CREATE DATABASE openfire;mysql> GRANT ALL PRIVILEGES ON openfire.* TO openfire@localhost IDENTIFIED BY 0penfire0bepassword;mysql> FLUSH PRIVILEGES;

Before the installation absolutely update the ports.cd /usr/ports/net-im/openfire Go to the port foldermake config choose the modulesmake install install

echo openfire_enable=YES >> /etc/rc.conf Add to the startup/usr/local/etc/rc.d/openfire start Start the daemon

sockstat -l | grep openfire Check for listenopenfire java 56187 26 tcp4 *:9090 *:*openfire java 56187 29 stream (not connected)

Then go to the http://openfire.unixmen.com:9090 page. You will get the following page (select English and click the continue button):

Write domain name and click the Continue button:

To select different type of database select the Standart Database Connection and click the Continue button:

The selection MySQL database. Write username, password and database URL as the following syntax and click the Continue button: jdbc:mysql://localhost:3306/openfire?rewriteBatchedStatements=true:

Select Default and click Continue button:

In the opened page add the email for administrator account, type password twice and click the continue button. Administrator login name will be admin:

Last configuration page will be as below. Go to the Login to the admin console for login:

Write admin user name and password for this user:

At the end the opened page will be as below:

Create some users as the following template:

Add group:

Then go to this group and add created users to this group:

Now configuration for client program. Download Spark client program from http://www.igniterealtime.org/downloads/download-landing.jsp?file=spark/spark_2_7_0.exe link and install.

As the following screen configuring user faxri.iskandarov:

Check monitoring service plugin (Must be installed):

Then go to the Server -> Archiving -> Archiving Settings section and select logging between our XMPP clients (as the following screen):

Even you are able to get meetings through web. For this go to the http://openfire.unixmen.com:7070/jitsi/apps/ofmeet link. This channel will not be crypted. For crypted channel go to the http://openfire.unixmen.com:7443/jitsi/apps/ofmeet link.

Note: If you are using Jitsi client program you dont need any plugin for call and any SIP number. Because Jitsi client can call with audio/video over XMPP like as Microsoft Lync and you can share your desktop like as Skype. You can download jitsi client program via https://jitsi.org/Main/Download official page. We will configure jitsi program at next sections.

In general plugin configurations under the Server tab. Also go to the Server -> Jitsi Videobridge section. Add the SIP username, password and SIP registration server and click save button:

In the Sessions -> Tools -> Send Message section you can send broadcast message to all users. As the following screen:

If we want to set SIP number for each user, before this we must add XMPP users to our system and then go to the Server -> Phone -> Add new Phone Mapping section and create SIP users(SIP and XMMP on the same server). For example we will add SIP number for existing namaz.bayramli XMPP user.

Then download Jitsi XMPP/SIP client program to your Windows machine and configure as follows (The official page: https://jitsi.org/Main/Download :File -> Add new account > XMPP -> XMPP Username Password -> Add

As you see XMPP user namaz.bayramli is ready:

Then click File -> Add contact and add the credentials as the screen, click Add button (Of course, user exists in our system):

The previous configuration we did for nurlan.farajov@jabber.unixmen.com and added to his user list namaz.bayramli@jabber.unixmen.com. At the end call from one client to another with audio/video and share your desktop:

This is desktop sharing:

And if you want to control other point from jitsi client, just select Enable desktop remote control checkbox. After that you can control other point as teamviewer.

For example if you want to use SIP configuration together XMPP, choose again Tools -> Options -> Add -> SIP and write SIP username and password (As the follows page). Just change domain name to yours:

As you see XMPP and SIP accounts is together:

Like Loading...

Related

Excerpt from:

OpenFire Jitsi as Skype(desktop sharing) and Temviewer ...

Jitsi for Mac : Free Download : MacUpdate

Jitsi (previously SIP Communicator) is an audio/video and chat communicator that supports protocols such as SIP, XMPP/Jabber, AIM/ICQ, Windows Live, Yahoo!, Bonjour, and many other useful features. Jitsi supports the ZRTP protocol stack by Phil Zimmerman for encrypted private communications.

Jitsi is Open Source / Free Software, and is available under the terms of the LGPL and performs secure video calls, conferencing, chat, desktop sharing, file transfer, support for your favorite OS, and IM network. All this, and more, in Jitsi - the most complete and advanced Open Source communicator.

No similar apps have been recommended yet. You can add your suggestions to the right.

Jitsi (previously SIP Communicator) is an audio/video and chat communicator that supports protocols such as SIP, XMPP/Jabber, AIM/ICQ, Windows Live, Yahoo!, Bonjour, and many other useful features. Jitsi supports the ZRTP protocol stack by Phil Zimmerman for encrypted private communications.

Jitsi is Open Source / Free Software, and is available under the terms of the LGPL and performs secure video calls, conferencing, chat, desktop sharing, file transfer, support for your favorite OS, and IM network. All this, and more, in Jitsi - the most complete and advanced Open Source communicator.

Read more:

Jitsi for Mac : Free Download : MacUpdate

Jitsi softphone for Windows OnSIP Support

Updated 10/26/2015

Jitsi version 2.8.5426 for Windows. Tested on Windows 7 64bit with SP1.

Each user has a set of credentials which will be needed to configure each phone. For each phone that you are configuring, obtain the following:

You can find this information in the user detail pages under the Users tab in the Phone Configuration section.

These images are based on using a Windows 7 64bit computer.

A. When you first open Jitsi after installation it will open setup wizard. DO NOT enter any data, click on Cancel to continue.

B. Click on Tools then Options

C.Click on Add

D. Choose SIP for Network then click on Advanced, DO NOT enter any user info

E. Enter User Name and SIP Password in Account page

F. In Connection page, enter the following information

G. On Encoding page, move up the following codec and uncheck all the other codec

H. Click Next, then click on Sign In. Jitsi should now beregistered and ready for use.

See our top business VoIP phone recommendations for 2017

Here is the original post:

Jitsi softphone for Windows OnSIP Support

Gladstone gold does club proud | Gladstone Observer – Gladstone Observer

MARTIAL ARTS: The Gladstone Martial Arts Academy's stocks continue to pack a punch with its latest achievements yielding more medals.

Nine students collected a total of 18 medals at the recent Queensland Brazilian Jiu-Jitsi State Titles on the Gold Coast.

The tally was made up of five gold, six silver and seven bronze in an event that attracted 515 competitors.

Among those was 13-year-old Trinity McKenzie who beat more experienced boys on her way to a gold medal for Gi and No-Gi divisions.

The teenager said enjoyment is the key to her success.

"All the people at GMAA are like my family now and it's just so much fun every class I love it, Trinity said.

What's more impressive is that she has been doing BJJ for just two years and she also trains in Mixed Martial Arts, Muay Thai and Zen Do Kai under GMAA head coach Rob McIntyre

"This was her sixth BJJ tournament, McIntyre said.

"Her favourite submission is definitely the rear naked choke and her second is the arm bar.

McIntyre said the club's athletes have excelled in the competitions they have competed in.

"It has been a big year for GMAA in Jiu Jitsu and after only three competitions, the club has earned an amazing 40 gold, 27 silver and 11 bronze medals, McIntyre said.

"The club will travel to three more tournaments this year in Rockhampton, the Sunshine Coast and the Gold Coast.

The BJJ competition is based on grappling only, with competitors earning points for take-downs, controlling top positions and reversing positions.

They can win outright with a submission making their opponent tap from chokes, arm locks or leg locks and has been made famous by its skills being used in the UFC.

People interested in BJJ can contact McIntyre on 0439739619 or visit the club's Facebook site or website http://www.gladstonemartialarts.com.au.

Visit link:

Gladstone gold does club proud | Gladstone Observer - Gladstone Observer

Jitsi | Futurist Transhuman News Blog – prometheism.net

Featured questions (hide)

How do I get the latest Jitsi source code?

You could either clone the Git repository from GitHub (see Retrieving and Building the Sources for details) or use one of the nightly source snapshots (check the Download page).

Ive discovered a bug, what can I do?

Please, report it to the developers! Take a look at the Reporting bugs guidelines page describing the steps to report bugs effectively.

Where is the user profile directory?

Jitsis user profile directory is where Jitsi keeps its configuration, logs, etc. Its location depends on the operating system.

Where do I find the log files?

The easiest way to get hold of the log files is to save them to a location of your choice using Jitsis GUI. You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Logging form. Youll see the Archive Logs button in there.

Check out the screenshot for an even better description.

Important Note: When asked for logs, please make sure that you provide the full set of logs, or better yet, the zip that Jitsi generates when following the above instructions. Please do not send separate files or file snippets as those are likely to be insufficient. If you need to provide the logs for a GitHub issue, send them to Dev Mailing List and link to the thread in the archive or create a Gist and link to it. Please DO NOT paste the log as a comment.

Otherwise, if you really want to know, the log files are located in:

Where is the configuration file?

Jitsis main configuration file is called sip-communicator.properties and is in the user profile directory.

How do you spell Jitsi and what does it mean?

The correct spelling of the application name is Jitsi (jitsi also works). The origin of the name is Bulgarian (spelled ). It means wires and the point is that the application allow you to connect to many network and people just as wires do. Of course no one other than Bulgarians is supposed to know what this means and we picked the name mainly because it was short and sounded good.

Id like to see a new feature in Jitsi, can you do that for me?

Yes, developers take feature requests into account. Send an email to the development list with a detailed description of the requested feature. After we examine its feasibility and decide whether it can be included in the Jitsi distributions you would likely be asked to open a ticket in our issue tracker. It is worth mentioning though, that handling feature requests is highly dependent of the developers availability and there is no guarantee that all requests will be satisfied.

How do I subscribe to mailing lists?

Please visit the Mailing Lists page to learn more about Jitsis mailing lists.

How do I contact the project developers?

You can ask questions concerning usage of the Jitsi on the dev mailing list (Note that the mailing lists are moderated, so, unless you subscribe to them, there may be a delay before your post shows up). For all urgent queries you could also use IRC at irc.freenode.net, channel #jitsi.

How do I send a patch?

Mail patches to the dev mailing list, with a subject line that contains the word PATCH in all uppercase, for example

A patch submission should contain one logical change; please dont mix N unrelated changes in one submission, send N separate emails instead.

The patch itself should be generated from within the project root directory using unified diff format. The following example shows one way to generate it:

You should give your patch files meaningful names. For instance if you fix a socket bug in the foo class do not call your patch file patchfile.txt but instead call it foo-socket.patch.

If the patch implements a new feature, make sure to describe the feature completely in your mail; if the patch fixes a bug, describe the bug in detail and give a reproduction recipe. An exception to these guidelines is when the patch addresses a specific issue in the issues database in that case, just make sure to refer to the issue number in your log message.

Note that unless you are describing a change rather than posting one, we would probably need you to sign our contributor agreement as either an individual or a corporation

I would like to update this wiki what can I do?

Currently, only project developers are permitted to update the wiki. Please send your suggested changes to the dev mailing list.

A wiki page can be updated by appending the string ?action=edit to the current url and refreshing the page. The page will then be displayed with an extra menu line that includes a Page Edit item.

If you click on the Page Edit item, you will be redirected to a logon page. Enter your developer username and password and you should be redirected back to the original page. Click on Page Edit again to access the source content of the page (a quick reference to wiki markup syntax is also displayed).

How do I reset my XMPP or jit.si password?

You can reset your jit.si password from within Jitsi. You can do the same for any XMPP account that allows it.

In the case of jit.si, you can also change your password via the web

Why cant I connect to ekiga.net?

NB: the problems described in this section also apply to other providers such as 1und1.de

Short Answer: The ekiga.net SIP servers are configured in a way that prevent Jitsi (and many other SIP user agents for that matter) to register with the service. Please use iptel.org or ippi.com instead.

Slightly Longer Answer: The service at ekiga.net is configured to only accept SIP REGISTER requests that contain a public IP address in their Contact header. This means that registration from Jitsi would fail unless you actually have a public IP address. The Ekiga client circumvents this by using STUN to learn the address and port that have been allocated for the current session. It then uses the pair in the SIP Contact header. This kind of use was common for the first version of the STUN protocol defined in RFC 3489 which was sometimes referred to as classic STUN.

The IETF has since significantly reviewed the way STUN should be used. The new version of the protocol is now defined in RFC 5389 which, among other things, advises against the use of STUN as a standalone NAT traversal utility:

Today STUN represents one of the tools used by complete traversal mechanisms such as SIP OUTBOUND (RFC 5626) or ICE (RFC 5245). Neither of these includes sending a STUN obtained address in a Contact header.

So, where does Jitsi currently stand on all this? At the time of writing, we support the ICE protocol but only use it with XMPP. Use with SIP is likely to come in the near future. The reason we havent implemented it yet is that most SIP servers currently open to use over the Internet, use a technique called latching. When such servers detect you are connecting from behind a NAT, they would start acting as a relay, receiving media from your peers and then forwarding it to you (and vice versa). While this is by far the most reliably way of traversing NATs, it does indeed imply some scalability constraints.

ICE on the other hand would only fall back to relaying if no other way was found to connect the two participants. This is why it is considered as a more optimal solution and why its also on our roadmap.

Note however that the constraints on ekiga.net would continue preventing Jitsi from connecting even when we do implement support for ICE.

Why do I see ICE failed errors when trying to make calls.

Jitsi implements a number of NAT traversal methods as described here. In many situations we will be able to setup a call directly between you and other users but in order to be able to reliably establish calls, your XMPP or SIP provider has to provide relaying capabilities such as TURN, Jingle Nodes or . If looking for services that support these you can try jit.si or ippi. Also note that both you and your partner need to have unhindered outgoing UDP access to the Internet or at least to your VoIP service provider. You DO NOT however need to map any port numbers on your home router. At best this is going to have no effect.

Does Jitsi support STUN? (and how about TURN, UPnP and Jingle Nodes?)

STUN, together with TURN, Jingle Nodes, IPv6 and UPnP, is one of the techniques that Jitsi uses as part of the Interactive Connectivity Establishment (ICE) protocol to handle NAT traversal for calls made over XMPP.

For its SIP calls, Jitsi currently relies on servers to relay media (a technique also known as Hosted NAT Traversal or latching, which would be the case of the majority of the SIP servers used on the Internet today. Note that in terms of reliability Hosted NAT Traversal gives the same results as use of ICE. It even works better in some ways because the connection is setup immediately and no time is waisted for gathering candidates and making connectivity checks. The only downside of HNT is that it may put a strain on SIP providers requiring more bandwidth. This could become a problem especially in environments with a high number of all IP high quality video calls.

It is likely that ICE support for SIP calls would also be added to Jitsi in 2014 especially since this would also help with WebRTC compatibility.

Standalone support for STUN is NOT going to be part of Jitsi. Check out the ekiga entry for more information on the shortcomings of STUN as a standalone NAT traversal utility.

I have a few questions regarding ZRTP, SRTP and VoIP security in general. Where can I find some answers?

Check out our ZRTP FAQ.

Why does my call stay in the Initiating Call status and I can never connect?

A common reason for providers not to respond to calls is that they simply dont get the INVITE request Jitsi sends to them. This can happen if you are using UDP. The Jitsi INVITE requests may often exceed the maximum allowed packet size (MTU) for your network or that of your server. In such cases packets may be fragmented by your IP stack and fragmentation for UDP does not always work well in certain networks. This is what happens when a client supports multiple features ;). To resolve the issue you can do one of the following:

How does on-line provisioning work?

On-line provisioning is the feature that allows Jitsi to connect to an http URI every time it starts and retrieve part or all of its configuration there. On-line provisioning is often used by providers to remotely configure the clients they maintain. It can be used to set any property in Jitsi such as the codecs used, the features that users can manually configure and even protocol accounts.

When requesting its provisioning information Jitsi can transmit any of a number of parameters to the server, like for example: the OS it is running on, user credentials, a unique ID and others. This way the provisioning server can fine-tune the parameters it sends to Jitsi.

For more information, please check our on-line provisioning manual

Are my chat sessions protected and if so, how?

Jitsi supports the OTR encryption protocol. OTR stands for Off-the-Record Messaging and once youve set it up (i.e. clicked on that padlock icon in a chat window and verified the identity of your contact) it allows you to make sure that no one other than you two can read your messages, not even your service provider. You can find more on the OTR mechanisms here:

http://en.wikipedia.org/wiki/Off-the-Record_Messaging

Should logging be disabled by default when using OTR?

By default Jitsi stores all chats so that if you need any information from them it would always be available. If you would like to disable this behavior you can currently do so by opening Jitsis Options/Preferences, selecting the General pane and then unchecking the Log chat history option near the top. It is also possible to disable chats for specific contacts, to erase their history. An indicator in the chat window makes it aware at all times whether history is on or off while chatting with someone.

OTR protected chats follow the same pattern and some users have expressed concerns that this might be incompatible with their security expectations. Our position on this is that Jitsis role is to protect your communication. We also strive to offer usability. The current defaults represent these objectives: most people would prefer for their private communication not to be readable by third parties and most of the time people use Jitsi from personal devices where they are in control of the access policy.

In some cases users may wish for their communications not to be stored locally. This can be the case when using Jitsi on devices that others may also have access to. In such cases users need to be able to easily see whether history is being logged. They would also need to easily turn this off and potentially even erase previous history.

Note however that this subject is entirely different from the encryption one. They are separate measures meant to protect you against separate attacks or problems. We dont believe that the need for one would necessarily imply the need for the other. We are hence committed to also keeping that separation in the user interface.

Force SIP Message support.

Some SIP servers (Asterisk in particular) do not announce the MESSAGE support, despite supporting it. If you enable the account property FORCE_MESSAGING, Jitsi will attempt to use MESSAGE for chats, despite your configured SIP server not explicitly announcing this support to connected clients. For example, if your SIP account is john.smith@example.com, go to property editor type that in the search field and look for something like

net.java.sip.communicator.impl.protocol.sip.acc0123456789.ACCOUNT_UID with the value SIP:john.smith@example.com

The property to add in that case would be:

net.java.sip.communicator.impl.protocol.sip.acc0123456789.FORCE_MESSAGING with the value true.

How to add/edit configuration properties.

You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Property Editor form. There you can search edit/delete or create new properties.

Is there an an Android version of Jitsi?

Yes, but it is still in an early alpha stage and further development has been put on hold until further notice. A lot of the user interface is not yet implemented. You can find the apk on the Download page.

Is there an iPhone/iPad version of Jitsi?

No. Due to the restrictions imposed by the platform it is highly unlikely this answer is going to change.

The cc-buildloop target of ant fails with the following error message: Could not create task or type of type: junitreport.

On some Linux distributions such as Debian, the ant package is actualy subdivided into multiple packages. So when you chose to install junit and ant with the distribution specific package system, dont forget to install ant-optional too.

The cc-buildloop target of ant fails with the following error message: No test with id=IcqProtocolProviderSlick.

Have you created your own accounts.properties file in the lib directory? Youll need to define two ICQ test accounts at least, and preferably some test accounts for the other supported protocols.

Read the original:

FAQ | Jitsi

. Bookmark the

.

See original here: FAQ | Jitsi | Futurist Transhuman News Blog

See original here:

FAQ | Jitsi | Futurist Transhuman News Blog | Prometheism.net

. Bookmark the

.

Continue reading here: Jitsi | Futurist Transhuman News Blog euvolution.com

Continue reading here:

Jitsi | Futurist Transhuman News Blog - prometheism.net

FAQ | Jitsi | Prometheism.net euvolution.com | Futurist

Featured questions (hide)

How do I get the latest Jitsi source code?

You could either clone the Git repository from GitHub (see Retrieving and Building the Sources for details) or use one of the nightly source snapshots (check the Download page).

Ive discovered a bug, what can I do?

Please, report it to the developers! Take a look at the Reporting bugs guidelines page describing the steps to report bugs effectively.

Where is the user profile directory?

Jitsis user profile directory is where Jitsi keeps its configuration, logs, etc. Its location depends on the operating system.

Where do I find the log files?

The easiest way to get hold of the log files is to save them to a location of your choice using Jitsis GUI. You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Logging form. Youll see the Archive Logs button in there.

Check out the screenshot for an even better description.

Important Note: When asked for logs, please make sure that you provide the full set of logs, or better yet, the zip that Jitsi generates when following the above instructions. Please do not send separate files or file snippets as those are likely to be insufficient. If you need to provide the logs for a GitHub issue, send them to Dev Mailing List and link to the thread in the archive or create a Gist and link to it. Please DO NOT paste the log as a comment.

Otherwise, if you really want to know, the log files are located in:

Where is the configuration file?

Jitsis main configuration file is called sip-communicator.properties and is in the user profile directory.

How do you spell Jitsi and what does it mean?

The correct spelling of the application name is Jitsi (jitsi also works). The origin of the name is Bulgarian (spelled ). It means wires and the point is that the application allow you to connect to many network and people just as wires do. Of course no one other than Bulgarians is supposed to know what this means and we picked the name mainly because it was short and sounded good.

Id like to see a new feature in Jitsi, can you do that for me?

Yes, developers take feature requests into account. Send an email to the development list with a detailed description of the requested feature. After we examine its feasibility and decide whether it can be included in the Jitsi distributions you would likely be asked to open a ticket in our issue tracker. It is worth mentioning though, that handling feature requests is highly dependent of the developers availability and there is no guarantee that all requests will be satisfied.

How do I subscribe to mailing lists?

Please visit the Mailing Lists page to learn more about Jitsis mailing lists.

How do I contact the project developers?

You can ask questions concerning usage of the Jitsi on the dev mailing list (Note that the mailing lists are moderated, so, unless you subscribe to them, there may be a delay before your post shows up). For all urgent queries you could also use IRC at irc.freenode.net, channel #jitsi.

How do I send a patch?

Mail patches to the dev mailing list, with a subject line that contains the word PATCH in all uppercase, for example

A patch submission should contain one logical change; please dont mix N unrelated changes in one submission, send N separate emails instead.

The patch itself should be generated from within the project root directory using unified diff format. The following example shows one way to generate it:

You should give your patch files meaningful names. For instance if you fix a socket bug in the foo class do not call your patch file patchfile.txt but instead call it foo-socket.patch.

If the patch implements a new feature, make sure to describe the feature completely in your mail; if the patch fixes a bug, describe the bug in detail and give a reproduction recipe. An exception to these guidelines is when the patch addresses a specific issue in the issues database in that case, just make sure to refer to the issue number in your log message.

Note that unless you are describing a change rather than posting one, we would probably need you to sign our contributor agreement as either an individual or a corporation

I would like to update this wiki what can I do?

Currently, only project developers are permitted to update the wiki. Please send your suggested changes to the dev mailing list.

A wiki page can be updated by appending the string ?action=edit to the current url and refreshing the page. The page will then be displayed with an extra menu line that includes a Page Edit item.

If you click on the Page Edit item, you will be redirected to a logon page. Enter your developer username and password and you should be redirected back to the original page. Click on Page Edit again to access the source content of the page (a quick reference to wiki markup syntax is also displayed).

How do I reset my XMPP or jit.si password?

You can reset your jit.si password from within Jitsi. You can do the same for any XMPP account that allows it.

In the case of jit.si, you can also change your password via the web

Why cant I connect to ekiga.net?

NB: the problems described in this section also apply to other providers such as 1und1.de

Short Answer: The ekiga.net SIP servers are configured in a way that prevent Jitsi (and many other SIP user agents for that matter) to register with the service. Please use iptel.org or ippi.com instead.

Slightly Longer Answer: The service at ekiga.net is configured to only accept SIP REGISTER requests that contain a public IP address in their Contact header. This means that registration from Jitsi would fail unless you actually have a public IP address. The Ekiga client circumvents this by using STUN to learn the address and port that have been allocated for the current session. It then uses the pair in the SIP Contact header. This kind of use was common for the first version of the STUN protocol defined in RFC 3489 which was sometimes referred to as classic STUN.

The IETF has since significantly reviewed the way STUN should be used. The new version of the protocol is now defined in RFC 5389 which, among other things, advises against the use of STUN as a standalone NAT traversal utility:

Today STUN represents one of the tools used by complete traversal mechanisms such as SIP OUTBOUND (RFC 5626) or ICE (RFC 5245). Neither of these includes sending a STUN obtained address in a Contact header.

So, where does Jitsi currently stand on all this? At the time of writing, we support the ICE protocol but only use it with XMPP. Use with SIP is likely to come in the near future. The reason we havent implemented it yet is that most SIP servers currently open to use over the Internet, use a technique called latching. When such servers detect you are connecting from behind a NAT, they would start acting as a relay, receiving media from your peers and then forwarding it to you (and vice versa). While this is by far the most reliably way of traversing NATs, it does indeed imply some scalability constraints.

ICE on the other hand would only fall back to relaying if no other way was found to connect the two participants. This is why it is considered as a more optimal solution and why its also on our roadmap.

Note however that the constraints on ekiga.net would continue preventing Jitsi from connecting even when we do implement support for ICE.

Why do I see ICE failed errors when trying to make calls.

Jitsi implements a number of NAT traversal methods as described here. In many situations we will be able to setup a call directly between you and other users but in order to be able to reliably establish calls, your XMPP or SIP provider has to provide relaying capabilities such as TURN, Jingle Nodes or . If looking for services that support these you can try jit.si or ippi. Also note that both you and your partner need to have unhindered outgoing UDP access to the Internet or at least to your VoIP service provider. You DO NOT however need to map any port numbers on your home router. At best this is going to have no effect.

Does Jitsi support STUN? (and how about TURN, UPnP and Jingle Nodes?)

STUN, together with TURN, Jingle Nodes, IPv6 and UPnP, is one of the techniques that Jitsi uses as part of the Interactive Connectivity Establishment (ICE) protocol to handle NAT traversal for calls made over XMPP.

For its SIP calls, Jitsi currently relies on servers to relay media (a technique also known as Hosted NAT Traversal or latching, which would be the case of the majority of the SIP servers used on the Internet today. Note that in terms of reliability Hosted NAT Traversal gives the same results as use of ICE. It even works better in some ways because the connection is setup immediately and no time is waisted for gathering candidates and making connectivity checks. The only downside of HNT is that it may put a strain on SIP providers requiring more bandwidth. This could become a problem especially in environments with a high number of all IP high quality video calls.

It is likely that ICE support for SIP calls would also be added to Jitsi in 2014 especially since this would also help with WebRTC compatibility.

Standalone support for STUN is NOT going to be part of Jitsi. Check out the ekiga entry for more information on the shortcomings of STUN as a standalone NAT traversal utility.

I have a few questions regarding ZRTP, SRTP and VoIP security in general. Where can I find some answers?

Check out our ZRTP FAQ.

Why does my call stay in the Initiating Call status and I can never connect?

A common reason for providers not to respond to calls is that they simply dont get the INVITE request Jitsi sends to them. This can happen if you are using UDP. The Jitsi INVITE requests may often exceed the maximum allowed packet size (MTU) for your network or that of your server. In such cases packets may be fragmented by your IP stack and fragmentation for UDP does not always work well in certain networks. This is what happens when a client supports multiple features ;). To resolve the issue you can do one of the following:

How does on-line provisioning work?

On-line provisioning is the feature that allows Jitsi to connect to an http URI every time it starts and retrieve part or all of its configuration there. On-line provisioning is often used by providers to remotely configure the clients they maintain. It can be used to set any property in Jitsi such as the codecs used, the features that users can manually configure and even protocol accounts.

When requesting its provisioning information Jitsi can transmit any of a number of parameters to the server, like for example: the OS it is running on, user credentials, a unique ID and others. This way the provisioning server can fine-tune the parameters it sends to Jitsi.

For more information, please check our on-line provisioning manual

Are my chat sessions protected and if so, how?

Jitsi supports the OTR encryption protocol. OTR stands for Off-the-Record Messaging and once youve set it up (i.e. clicked on that padlock icon in a chat window and verified the identity of your contact) it allows you to make sure that no one other than you two can read your messages, not even your service provider. You can find more on the OTR mechanisms here:

http://en.wikipedia.org/wiki/Off-the-Record_Messaging

Should logging be disabled by default when using OTR?

By default Jitsi stores all chats so that if you need any information from them it would always be available. If you would like to disable this behavior you can currently do so by opening Jitsis Options/Preferences, selecting the General pane and then unchecking the Log chat history option near the top. It is also possible to disable chats for specific contacts, to erase their history. An indicator in the chat window makes it aware at all times whether history is on or off while chatting with someone.

OTR protected chats follow the same pattern and some users have expressed concerns that this might be incompatible with their security expectations. Our position on this is that Jitsis role is to protect your communication. We also strive to offer usability. The current defaults represent these objectives: most people would prefer for their private communication not to be readable by third parties and most of the time people use Jitsi from personal devices where they are in control of the access policy.

In some cases users may wish for their communications not to be stored locally. This can be the case when using Jitsi on devices that others may also have access to. In such cases users need to be able to easily see whether history is being logged. They would also need to easily turn this off and potentially even erase previous history.

Note however that this subject is entirely different from the encryption one. They are separate measures meant to protect you against separate attacks or problems. We dont believe that the need for one would necessarily imply the need for the other. We are hence committed to also keeping that separation in the user interface.

Force SIP Message support.

Some SIP servers (Asterisk in particular) do not announce the MESSAGE support, despite supporting it. If you enable the account property FORCE_MESSAGING, Jitsi will attempt to use MESSAGE for chats, despite your configured SIP server not explicitly announcing this support to connected clients. For example, if your SIP account is john.smith@example.com, go to property editor type that in the search field and look for something like

net.java.sip.communicator.impl.protocol.sip.acc0123456789.ACCOUNT_UID with the value SIP:john.smith@example.com

The property to add in that case would be:

net.java.sip.communicator.impl.protocol.sip.acc0123456789.FORCE_MESSAGING with the value true.

How to add/edit configuration properties.

You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Property Editor form. There you can search edit/delete or create new properties.

Is there an an Android version of Jitsi?

Yes, but it is still in an early alpha stage and further development has been put on hold until further notice. A lot of the user interface is not yet implemented. You can find the apk on the Download page.

Is there an iPhone/iPad version of Jitsi?

No. Due to the restrictions imposed by the platform it is highly unlikely this answer is going to change.

The cc-buildloop target of ant fails with the following error message: Could not create task or type of type: junitreport.

On some Linux distributions such as Debian, the ant package is actualy subdivided into multiple packages. So when you chose to install junit and ant with the distribution specific package system, dont forget to install ant-optional too.

The cc-buildloop target of ant fails with the following error message: No test with id=IcqProtocolProviderSlick.

Have you created your own accounts.properties file in the lib directory? Youll need to define two ICQ test accounts at least, and preferably some test accounts for the other supported protocols.

Read this article: FAQ | Jitsi

Read the original:

FAQ | Jitsi | Prometheism.net

. Bookmark the

.

View original post here: FAQ | Jitsi | Prometheism.net euvolution.com

Read more from the original source:

FAQ | Jitsi | Prometheism.net euvolution.com

. Bookmark the

.

Go here to read the rest: FAQ | Jitsi | Prometheism.net euvolution.com | Futurist

More here:

FAQ | Jitsi | Prometheism.net euvolution.com | Futurist

Jitsi Meet (advanced) Projects | Prometheism.net

How to join Jitsi Meet video conferences over the Web

If you do not already know what Jitsi Meet is, here is the official homepage. Jitsi Meet allows you to create and join video calls over the Web (even as a simple viewer). Some of its features are: encrypted by default, no account needed, invite by pretty URL https://mysite.com/myroom

Thanks to UV4L it is possible to create or join an existing room and broadcast live video and audio to all the participants or viewers in the room from a camera and a microphone connected to the Raspberry Pi. Its also possible to automatically hear and see other participants if you have speakers and display (HDMI, touchscreen, etc) connected to the Raspberry Pi. Of course, other participants can be other Raspberry Pis. The great news is that you do not need any browser installed on the Raspberry Pi to do this.

Its necessary to install the required packages before proceeding: uv4l, uv4l-server, uv4l-webrtc, uv4l-xmpp-bridge and one video driver (e.g. uv4l-raspicam, uv4l-uvc, etc). Please refer to these installation instructions for more details.

To start and stop streaming to a particular Jitsi Meet server (called videobridge), its enough to invoke the corresponding commands by means of the UV4L Streaming Server installed on the Raspberry Pi. This can be done in two ways.

The first convenient way is through a browser by using the Jitsi Meet control page available at the URL the Streaming Server itself is listening to (e.g. http://myraspberrypi:8080), from which its possible to specify all the mandatory informations (i.e. XMPP and/or BOSH signalling server, chat room, your username and password) required to establish a connection and to click on start/stop buttons in order to join or leave the specified room respectively.

The second way is to invoke the start/stop commands via HTTP/GET requests sent to the Streaming Server from command line. For example, to start streaming to the videobridge which is at the base of the official, free-access Jitsi Meet service at meet.jit.si, type (in one line):

where raspberrypi will have to be replaced with the real hostname of your Raspberry Pi in your network (it can be localhost if you are executing the command from within your Raspberry Pi) and port will have to be replaced with the real port number the Streaming Server is listening to (8080 is the default). The above command will make the Raspberry Pi create or join a conference at http://meet.jit.si/testroom.

If the UV4L Streaming Server is providing HTTPS instead of HTTP, be careful to specify https://[] in the URL. You may also desire to add the insecure option to curl to turn off the verification of the servers certificate (see the curl manual for more details).

Please note the parameters in the URL that you are allowed to specify:

server (XMPP server hostname or ip address) port (port the XMPP server is listening to) muc (multiuser chat domain) room (desired room you want to join or create) room_password (room password, if the room is protected) username (desired username in the chat room) password (password if the server is password protected) reconnect (try to reconnect after disconnection) bosh_enable (1 if you want to use BOSH signalling, 0 otherwise) bosh_server (usually HTTP(S) server hostname for BOSH) bosh_tls (1 for HTTPS, 0 otherwise) bosh_port (typically 443 for HTTPS, 80 for HTTP) bosh_hostname (connection manager hostname, typically the same as bosh_server) action (Start or Stop streaming)

All the above settings can be optionally specified once for all in the UV4L configuration file (except action) (see the uv4l-server manual for more details).

Similarly, to stop streaming:

If you are protecting the UV4L Streaming Server with a password, then the above URL will not work. In this case, you must specify user and password in the URL as in the below example:

Go here to read the rest: Jitsi Meet (advanced) Projects

Original post:

Jitsi Meet (advanced) Projects | Prometheism.net

FAQ | Jitsi | Futurist Transhuman News Blog | Prometheism.net

Featured questions (hide)

How do I get the latest Jitsi source code?

You could either clone the Git repository from GitHub (see Retrieving and Building the Sources for details) or use one of the nightly source snapshots (check the Download page).

Ive discovered a bug, what can I do?

Please, report it to the developers! Take a look at the Reporting bugs guidelines page describing the steps to report bugs effectively.

Where is the user profile directory?

Jitsis user profile directory is where Jitsi keeps its configuration, logs, etc. Its location depends on the operating system.

Where do I find the log files?

The easiest way to get hold of the log files is to save them to a location of your choice using Jitsis GUI. You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Logging form. Youll see the Archive Logs button in there.

Check out the screenshot for an even better description.

Important Note: When asked for logs, please make sure that you provide the full set of logs, or better yet, the zip that Jitsi generates when following the above instructions. Please do not send separate files or file snippets as those are likely to be insufficient. If you need to provide the logs for a GitHub issue, send them to Dev Mailing List and link to the thread in the archive or create a Gist and link to it. Please DO NOT paste the log as a comment.

Otherwise, if you really want to know, the log files are located in:

Where is the configuration file?

Jitsis main configuration file is called sip-communicator.properties and is in the user profile directory.

How do you spell Jitsi and what does it mean?

The correct spelling of the application name is Jitsi (jitsi also works). The origin of the name is Bulgarian (spelled ). It means wires and the point is that the application allow you to connect to many network and people just as wires do. Of course no one other than Bulgarians is supposed to know what this means and we picked the name mainly because it was short and sounded good.

Id like to see a new feature in Jitsi, can you do that for me?

Yes, developers take feature requests into account. Send an email to the development list with a detailed description of the requested feature. After we examine its feasibility and decide whether it can be included in the Jitsi distributions you would likely be asked to open a ticket in our issue tracker. It is worth mentioning though, that handling feature requests is highly dependent of the developers availability and there is no guarantee that all requests will be satisfied.

How do I subscribe to mailing lists?

Please visit the Mailing Lists page to learn more about Jitsis mailing lists.

How do I contact the project developers?

You can ask questions concerning usage of the Jitsi on the dev mailing list (Note that the mailing lists are moderated, so, unless you subscribe to them, there may be a delay before your post shows up). For all urgent queries you could also use IRC at irc.freenode.net, channel #jitsi.

How do I send a patch?

Mail patches to the dev mailing list, with a subject line that contains the word PATCH in all uppercase, for example

A patch submission should contain one logical change; please dont mix N unrelated changes in one submission, send N separate emails instead.

The patch itself should be generated from within the project root directory using unified diff format. The following example shows one way to generate it:

You should give your patch files meaningful names. For instance if you fix a socket bug in the foo class do not call your patch file patchfile.txt but instead call it foo-socket.patch.

If the patch implements a new feature, make sure to describe the feature completely in your mail; if the patch fixes a bug, describe the bug in detail and give a reproduction recipe. An exception to these guidelines is when the patch addresses a specific issue in the issues database in that case, just make sure to refer to the issue number in your log message.

Note that unless you are describing a change rather than posting one, we would probably need you to sign our contributor agreement as either an individual or a corporation

I would like to update this wiki what can I do?

Currently, only project developers are permitted to update the wiki. Please send your suggested changes to the dev mailing list.

A wiki page can be updated by appending the string ?action=edit to the current url and refreshing the page. The page will then be displayed with an extra menu line that includes a Page Edit item.

If you click on the Page Edit item, you will be redirected to a logon page. Enter your developer username and password and you should be redirected back to the original page. Click on Page Edit again to access the source content of the page (a quick reference to wiki markup syntax is also displayed).

How do I reset my XMPP or jit.si password?

You can reset your jit.si password from within Jitsi. You can do the same for any XMPP account that allows it.

In the case of jit.si, you can also change your password via the web

Why cant I connect to ekiga.net?

NB: the problems described in this section also apply to other providers such as 1und1.de

Short Answer: The ekiga.net SIP servers are configured in a way that prevent Jitsi (and many other SIP user agents for that matter) to register with the service. Please use iptel.org or ippi.com instead.

Slightly Longer Answer: The service at ekiga.net is configured to only accept SIP REGISTER requests that contain a public IP address in their Contact header. This means that registration from Jitsi would fail unless you actually have a public IP address. The Ekiga client circumvents this by using STUN to learn the address and port that have been allocated for the current session. It then uses the pair in the SIP Contact header. This kind of use was common for the first version of the STUN protocol defined in RFC 3489 which was sometimes referred to as classic STUN.

The IETF has since significantly reviewed the way STUN should be used. The new version of the protocol is now defined in RFC 5389 which, among other things, advises against the use of STUN as a standalone NAT traversal utility:

Today STUN represents one of the tools used by complete traversal mechanisms such as SIP OUTBOUND (RFC 5626) or ICE (RFC 5245). Neither of these includes sending a STUN obtained address in a Contact header.

So, where does Jitsi currently stand on all this? At the time of writing, we support the ICE protocol but only use it with XMPP. Use with SIP is likely to come in the near future. The reason we havent implemented it yet is that most SIP servers currently open to use over the Internet, use a technique called latching. When such servers detect you are connecting from behind a NAT, they would start acting as a relay, receiving media from your peers and then forwarding it to you (and vice versa). While this is by far the most reliably way of traversing NATs, it does indeed imply some scalability constraints.

ICE on the other hand would only fall back to relaying if no other way was found to connect the two participants. This is why it is considered as a more optimal solution and why its also on our roadmap.

Note however that the constraints on ekiga.net would continue preventing Jitsi from connecting even when we do implement support for ICE.

Why do I see ICE failed errors when trying to make calls.

Jitsi implements a number of NAT traversal methods as described here. In many situations we will be able to setup a call directly between you and other users but in order to be able to reliably establish calls, your XMPP or SIP provider has to provide relaying capabilities such as TURN, Jingle Nodes or . If looking for services that support these you can try jit.si or ippi. Also note that both you and your partner need to have unhindered outgoing UDP access to the Internet or at least to your VoIP service provider. You DO NOT however need to map any port numbers on your home router. At best this is going to have no effect.

Does Jitsi support STUN? (and how about TURN, UPnP and Jingle Nodes?)

STUN, together with TURN, Jingle Nodes, IPv6 and UPnP, is one of the techniques that Jitsi uses as part of the Interactive Connectivity Establishment (ICE) protocol to handle NAT traversal for calls made over XMPP.

For its SIP calls, Jitsi currently relies on servers to relay media (a technique also known as Hosted NAT Traversal or latching, which would be the case of the majority of the SIP servers used on the Internet today. Note that in terms of reliability Hosted NAT Traversal gives the same results as use of ICE. It even works better in some ways because the connection is setup immediately and no time is waisted for gathering candidates and making connectivity checks. The only downside of HNT is that it may put a strain on SIP providers requiring more bandwidth. This could become a problem especially in environments with a high number of all IP high quality video calls.

It is likely that ICE support for SIP calls would also be added to Jitsi in 2014 especially since this would also help with WebRTC compatibility.

Standalone support for STUN is NOT going to be part of Jitsi. Check out the ekiga entry for more information on the shortcomings of STUN as a standalone NAT traversal utility.

I have a few questions regarding ZRTP, SRTP and VoIP security in general. Where can I find some answers?

Check out our ZRTP FAQ.

Why does my call stay in the Initiating Call status and I can never connect?

A common reason for providers not to respond to calls is that they simply dont get the INVITE request Jitsi sends to them. This can happen if you are using UDP. The Jitsi INVITE requests may often exceed the maximum allowed packet size (MTU) for your network or that of your server. In such cases packets may be fragmented by your IP stack and fragmentation for UDP does not always work well in certain networks. This is what happens when a client supports multiple features ;). To resolve the issue you can do one of the following:

How does on-line provisioning work?

On-line provisioning is the feature that allows Jitsi to connect to an http URI every time it starts and retrieve part or all of its configuration there. On-line provisioning is often used by providers to remotely configure the clients they maintain. It can be used to set any property in Jitsi such as the codecs used, the features that users can manually configure and even protocol accounts.

When requesting its provisioning information Jitsi can transmit any of a number of parameters to the server, like for example: the OS it is running on, user credentials, a unique ID and others. This way the provisioning server can fine-tune the parameters it sends to Jitsi.

For more information, please check our on-line provisioning manual

Are my chat sessions protected and if so, how?

Jitsi supports the OTR encryption protocol. OTR stands for Off-the-Record Messaging and once youve set it up (i.e. clicked on that padlock icon in a chat window and verified the identity of your contact) it allows you to make sure that no one other than you two can read your messages, not even your service provider. You can find more on the OTR mechanisms here:

http://en.wikipedia.org/wiki/Off-the-Record_Messaging

Should logging be disabled by default when using OTR?

By default Jitsi stores all chats so that if you need any information from them it would always be available. If you would like to disable this behavior you can currently do so by opening Jitsis Options/Preferences, selecting the General pane and then unchecking the Log chat history option near the top. It is also possible to disable chats for specific contacts, to erase their history. An indicator in the chat window makes it aware at all times whether history is on or off while chatting with someone.

OTR protected chats follow the same pattern and some users have expressed concerns that this might be incompatible with their security expectations. Our position on this is that Jitsis role is to protect your communication. We also strive to offer usability. The current defaults represent these objectives: most people would prefer for their private communication not to be readable by third parties and most of the time people use Jitsi from personal devices where they are in control of the access policy.

In some cases users may wish for their communications not to be stored locally. This can be the case when using Jitsi on devices that others may also have access to. In such cases users need to be able to easily see whether history is being logged. They would also need to easily turn this off and potentially even erase previous history.

Note however that this subject is entirely different from the encryption one. They are separate measures meant to protect you against separate attacks or problems. We dont believe that the need for one would necessarily imply the need for the other. We are hence committed to also keeping that separation in the user interface.

Force SIP Message support.

Some SIP servers (Asterisk in particular) do not announce the MESSAGE support, despite supporting it. If you enable the account property FORCE_MESSAGING, Jitsi will attempt to use MESSAGE for chats, despite your configured SIP server not explicitly announcing this support to connected clients. For example, if your SIP account is john.smith@example.com, go to property editor type that in the search field and look for something like

net.java.sip.communicator.impl.protocol.sip.acc0123456789.ACCOUNT_UID with the value SIP:john.smith@example.com

The property to add in that case would be:

net.java.sip.communicator.impl.protocol.sip.acc0123456789.FORCE_MESSAGING with the value true.

How to add/edit configuration properties.

You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Property Editor form. There you can search edit/delete or create new properties.

Is there an an Android version of Jitsi?

Yes, but it is still in an early alpha stage and further development has been put on hold until further notice. A lot of the user interface is not yet implemented. You can find the apk on the Download page.

Is there an iPhone/iPad version of Jitsi?

No. Due to the restrictions imposed by the platform it is highly unlikely this answer is going to change.

The cc-buildloop target of ant fails with the following error message: Could not create task or type of type: junitreport.

On some Linux distributions such as Debian, the ant package is actualy subdivided into multiple packages. So when you chose to install junit and ant with the distribution specific package system, dont forget to install ant-optional too.

The cc-buildloop target of ant fails with the following error message: No test with id=IcqProtocolProviderSlick.

Have you created your own accounts.properties file in the lib directory? Youll need to define two ICQ test accounts at least, and preferably some test accounts for the other supported protocols.

Read the original:

FAQ | Jitsi

. Bookmark the

.

See original here: FAQ | Jitsi | Futurist Transhuman News Blog

See original here:

FAQ | Jitsi | Futurist Transhuman News Blog | Prometheism.net

FAQ | Jitsi | Prometheism.net euvolution.com

Featured questions (hide)

How do I get the latest Jitsi source code?

You could either clone the Git repository from GitHub (see Retrieving and Building the Sources for details) or use one of the nightly source snapshots (check the Download page).

Ive discovered a bug, what can I do?

Please, report it to the developers! Take a look at the Reporting bugs guidelines page describing the steps to report bugs effectively.

Where is the user profile directory?

Jitsis user profile directory is where Jitsi keeps its configuration, logs, etc. Its location depends on the operating system.

Where do I find the log files?

The easiest way to get hold of the log files is to save them to a location of your choice using Jitsis GUI. You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Logging form. Youll see the Archive Logs button in there.

Check out the screenshot for an even better description.

Important Note: When asked for logs, please make sure that you provide the full set of logs, or better yet, the zip that Jitsi generates when following the above instructions. Please do not send separate files or file snippets as those are likely to be insufficient. If you need to provide the logs for a GitHub issue, send them to Dev Mailing List and link to the thread in the archive or create a Gist and link to it. Please DO NOT paste the log as a comment.

Otherwise, if you really want to know, the log files are located in:

Where is the configuration file?

Jitsis main configuration file is called sip-communicator.properties and is in the user profile directory.

How do you spell Jitsi and what does it mean?

The correct spelling of the application name is Jitsi (jitsi also works). The origin of the name is Bulgarian (spelled ). It means wires and the point is that the application allow you to connect to many network and people just as wires do. Of course no one other than Bulgarians is supposed to know what this means and we picked the name mainly because it was short and sounded good.

Id like to see a new feature in Jitsi, can you do that for me?

Yes, developers take feature requests into account. Send an email to the development list with a detailed description of the requested feature. After we examine its feasibility and decide whether it can be included in the Jitsi distributions you would likely be asked to open a ticket in our issue tracker. It is worth mentioning though, that handling feature requests is highly dependent of the developers availability and there is no guarantee that all requests will be satisfied.

How do I subscribe to mailing lists?

Please visit the Mailing Lists page to learn more about Jitsis mailing lists.

How do I contact the project developers?

You can ask questions concerning usage of the Jitsi on the dev mailing list (Note that the mailing lists are moderated, so, unless you subscribe to them, there may be a delay before your post shows up). For all urgent queries you could also use IRC at irc.freenode.net, channel #jitsi.

How do I send a patch?

Mail patches to the dev mailing list, with a subject line that contains the word PATCH in all uppercase, for example

A patch submission should contain one logical change; please dont mix N unrelated changes in one submission, send N separate emails instead.

The patch itself should be generated from within the project root directory using unified diff format. The following example shows one way to generate it:

You should give your patch files meaningful names. For instance if you fix a socket bug in the foo class do not call your patch file patchfile.txt but instead call it foo-socket.patch.

If the patch implements a new feature, make sure to describe the feature completely in your mail; if the patch fixes a bug, describe the bug in detail and give a reproduction recipe. An exception to these guidelines is when the patch addresses a specific issue in the issues database in that case, just make sure to refer to the issue number in your log message.

Note that unless you are describing a change rather than posting one, we would probably need you to sign our contributor agreement as either an individual or a corporation

I would like to update this wiki what can I do?

Currently, only project developers are permitted to update the wiki. Please send your suggested changes to the dev mailing list.

A wiki page can be updated by appending the string ?action=edit to the current url and refreshing the page. The page will then be displayed with an extra menu line that includes a Page Edit item.

If you click on the Page Edit item, you will be redirected to a logon page. Enter your developer username and password and you should be redirected back to the original page. Click on Page Edit again to access the source content of the page (a quick reference to wiki markup syntax is also displayed).

How do I reset my XMPP or jit.si password?

You can reset your jit.si password from within Jitsi. You can do the same for any XMPP account that allows it.

In the case of jit.si, you can also change your password via the web

Why cant I connect to ekiga.net?

NB: the problems described in this section also apply to other providers such as 1und1.de

Short Answer: The ekiga.net SIP servers are configured in a way that prevent Jitsi (and many other SIP user agents for that matter) to register with the service. Please use iptel.org or ippi.com instead.

Slightly Longer Answer: The service at ekiga.net is configured to only accept SIP REGISTER requests that contain a public IP address in their Contact header. This means that registration from Jitsi would fail unless you actually have a public IP address. The Ekiga client circumvents this by using STUN to learn the address and port that have been allocated for the current session. It then uses the pair in the SIP Contact header. This kind of use was common for the first version of the STUN protocol defined in RFC 3489 which was sometimes referred to as classic STUN.

The IETF has since significantly reviewed the way STUN should be used. The new version of the protocol is now defined in RFC 5389 which, among other things, advises against the use of STUN as a standalone NAT traversal utility:

Today STUN represents one of the tools used by complete traversal mechanisms such as SIP OUTBOUND (RFC 5626) or ICE (RFC 5245). Neither of these includes sending a STUN obtained address in a Contact header.

So, where does Jitsi currently stand on all this? At the time of writing, we support the ICE protocol but only use it with XMPP. Use with SIP is likely to come in the near future. The reason we havent implemented it yet is that most SIP servers currently open to use over the Internet, use a technique called latching. When such servers detect you are connecting from behind a NAT, they would start acting as a relay, receiving media from your peers and then forwarding it to you (and vice versa). While this is by far the most reliably way of traversing NATs, it does indeed imply some scalability constraints.

ICE on the other hand would only fall back to relaying if no other way was found to connect the two participants. This is why it is considered as a more optimal solution and why its also on our roadmap.

Note however that the constraints on ekiga.net would continue preventing Jitsi from connecting even when we do implement support for ICE.

Why do I see ICE failed errors when trying to make calls.

Jitsi implements a number of NAT traversal methods as described here. In many situations we will be able to setup a call directly between you and other users but in order to be able to reliably establish calls, your XMPP or SIP provider has to provide relaying capabilities such as TURN, Jingle Nodes or . If looking for services that support these you can try jit.si or ippi. Also note that both you and your partner need to have unhindered outgoing UDP access to the Internet or at least to your VoIP service provider. You DO NOT however need to map any port numbers on your home router. At best this is going to have no effect.

Does Jitsi support STUN? (and how about TURN, UPnP and Jingle Nodes?)

STUN, together with TURN, Jingle Nodes, IPv6 and UPnP, is one of the techniques that Jitsi uses as part of the Interactive Connectivity Establishment (ICE) protocol to handle NAT traversal for calls made over XMPP.

For its SIP calls, Jitsi currently relies on servers to relay media (a technique also known as Hosted NAT Traversal or latching, which would be the case of the majority of the SIP servers used on the Internet today. Note that in terms of reliability Hosted NAT Traversal gives the same results as use of ICE. It even works better in some ways because the connection is setup immediately and no time is waisted for gathering candidates and making connectivity checks. The only downside of HNT is that it may put a strain on SIP providers requiring more bandwidth. This could become a problem especially in environments with a high number of all IP high quality video calls.

It is likely that ICE support for SIP calls would also be added to Jitsi in 2014 especially since this would also help with WebRTC compatibility.

Standalone support for STUN is NOT going to be part of Jitsi. Check out the ekiga entry for more information on the shortcomings of STUN as a standalone NAT traversal utility.

I have a few questions regarding ZRTP, SRTP and VoIP security in general. Where can I find some answers?

Check out our ZRTP FAQ.

Why does my call stay in the Initiating Call status and I can never connect?

A common reason for providers not to respond to calls is that they simply dont get the INVITE request Jitsi sends to them. This can happen if you are using UDP. The Jitsi INVITE requests may often exceed the maximum allowed packet size (MTU) for your network or that of your server. In such cases packets may be fragmented by your IP stack and fragmentation for UDP does not always work well in certain networks. This is what happens when a client supports multiple features ;). To resolve the issue you can do one of the following:

How does on-line provisioning work?

On-line provisioning is the feature that allows Jitsi to connect to an http URI every time it starts and retrieve part or all of its configuration there. On-line provisioning is often used by providers to remotely configure the clients they maintain. It can be used to set any property in Jitsi such as the codecs used, the features that users can manually configure and even protocol accounts.

When requesting its provisioning information Jitsi can transmit any of a number of parameters to the server, like for example: the OS it is running on, user credentials, a unique ID and others. This way the provisioning server can fine-tune the parameters it sends to Jitsi.

For more information, please check our on-line provisioning manual

Are my chat sessions protected and if so, how?

Jitsi supports the OTR encryption protocol. OTR stands for Off-the-Record Messaging and once youve set it up (i.e. clicked on that padlock icon in a chat window and verified the identity of your contact) it allows you to make sure that no one other than you two can read your messages, not even your service provider. You can find more on the OTR mechanisms here:

http://en.wikipedia.org/wiki/Off-the-Record_Messaging

Should logging be disabled by default when using OTR?

By default Jitsi stores all chats so that if you need any information from them it would always be available. If you would like to disable this behavior you can currently do so by opening Jitsis Options/Preferences, selecting the General pane and then unchecking the Log chat history option near the top. It is also possible to disable chats for specific contacts, to erase their history. An indicator in the chat window makes it aware at all times whether history is on or off while chatting with someone.

OTR protected chats follow the same pattern and some users have expressed concerns that this might be incompatible with their security expectations. Our position on this is that Jitsis role is to protect your communication. We also strive to offer usability. The current defaults represent these objectives: most people would prefer for their private communication not to be readable by third parties and most of the time people use Jitsi from personal devices where they are in control of the access policy.

In some cases users may wish for their communications not to be stored locally. This can be the case when using Jitsi on devices that others may also have access to. In such cases users need to be able to easily see whether history is being logged. They would also need to easily turn this off and potentially even erase previous history.

Note however that this subject is entirely different from the encryption one. They are separate measures meant to protect you against separate attacks or problems. We dont believe that the need for one would necessarily imply the need for the other. We are hence committed to also keeping that separation in the user interface.

Force SIP Message support.

Some SIP servers (Asterisk in particular) do not announce the MESSAGE support, despite supporting it. If you enable the account property FORCE_MESSAGING, Jitsi will attempt to use MESSAGE for chats, despite your configured SIP server not explicitly announcing this support to connected clients. For example, if your SIP account is john.smith@example.com, go to property editor type that in the search field and look for something like

net.java.sip.communicator.impl.protocol.sip.acc0123456789.ACCOUNT_UID with the value SIP:john.smith@example.com

The property to add in that case would be:

net.java.sip.communicator.impl.protocol.sip.acc0123456789.FORCE_MESSAGING with the value true.

How to add/edit configuration properties.

You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Property Editor form. There you can search edit/delete or create new properties.

Is there an an Android version of Jitsi?

Yes, but it is still in an early alpha stage and further development has been put on hold until further notice. A lot of the user interface is not yet implemented. You can find the apk on the Download page.

Is there an iPhone/iPad version of Jitsi?

No. Due to the restrictions imposed by the platform it is highly unlikely this answer is going to change.

The cc-buildloop target of ant fails with the following error message: Could not create task or type of type: junitreport.

On some Linux distributions such as Debian, the ant package is actualy subdivided into multiple packages. So when you chose to install junit and ant with the distribution specific package system, dont forget to install ant-optional too.

The cc-buildloop target of ant fails with the following error message: No test with id=IcqProtocolProviderSlick.

Have you created your own accounts.properties file in the lib directory? Youll need to define two ICQ test accounts at least, and preferably some test accounts for the other supported protocols.

Read this article: FAQ | Jitsi

Read the original:

FAQ | Jitsi | Prometheism.net

. Bookmark the

.

View original post here: FAQ | Jitsi | Prometheism.net euvolution.com

Read more from the original source:

FAQ | Jitsi | Prometheism.net euvolution.com

Tsirang vegetable vendors commit to selling local chillies – Kuensel, Buhutan’s National Newspaper

Going by the trend followed these days, Tsirang could soon become a chilli sufficient dzongkhag.

It has been more than a month that vegetable vendors in Tsirang have stopped buying chillies the youth business cooperative (YBC) imports from Kolkata and distributes to vegetable vendors across the country.

Tsirang residents have been consuming local chillies, which is grown abundantly. Farmers grow both local and the native Indian chillies grown in Bhutan, commonly known as jitsi ema.

Vendors in Tsirang say imported chilli gets damaged faster and is also expensive, whereas fresh chillies are available in the local market.

A vendor, Jyoti Nepal, said that importing chilli is not necessary when locally grown chillies are available.

She said when vendors buy chilli from the YBC, they have to buy in bulk, at least 200kgs to 300kgs and it rots before it reaches the destination. We have to throw more than half.

Jyoti also said the price for imported chilli was comparatively cheaper last year but ever since it was imported from Kolkata, the price hiked. We could instead buy and promote our local chilli at that price.

The initiative that vendors took by not buying importing chilli has come as a blessing for local chilli growers.

Most of the farmers, who brought locally grown jitsi ema to the Sunday market yesterday were from Gosarling gewog.

Sonam Choden, 52, has been selling chillies for last five weeks.

She said she brings at least 30kgs of jitsi ema grown in her garden every week and sells it for Nu 80 to Nu 130 a kilogramme.

Jitsi ema fetch a better price than any other variety of chillies we grow, she said. All we need is something hot on our plate.

Another farmer, Lhasang Dolma, sells her produce to vendors who supply chilli to Thimphu. She said she sold 49kgs in two weekends at Nu 100 a kg.

The price for Bhutanese chilli was Nu 30 a kg yesterday and the highest vendors fetched was Nu 300 a kg.

Vegetable vendors say farmers should grow more jitsi ema, as both require the same hard work in the fields.

Vendors say they decided that until the local chilli finishes in the market, they would not sell imported chillies.

Nirmala Pokhrel | Tsirang

Read the original here:

Tsirang vegetable vendors commit to selling local chillies - Kuensel, Buhutan's National Newspaper

FAQ | Jitsi | Prometheism.net

Featured questions (hide)

How do I get the latest Jitsi source code?

You could either clone the Git repository from GitHub (see Retrieving and Building the Sources for details) or use one of the nightly source snapshots (check the Download page).

Ive discovered a bug, what can I do?

Please, report it to the developers! Take a look at the Reporting bugs guidelines page describing the steps to report bugs effectively.

Where is the user profile directory?

Jitsis user profile directory is where Jitsi keeps its configuration, logs, etc. Its location depends on the operating system.

Where do I find the log files?

The easiest way to get hold of the log files is to save them to a location of your choice using Jitsis GUI. You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Logging form. Youll see the Archive Logs button in there.

Check out the screenshot for an even better description.

Important Note: When asked for logs, please make sure that you provide the full set of logs, or better yet, the zip that Jitsi generates when following the above instructions. Please do not send separate files or file snippets as those are likely to be insufficient. If you need to provide the logs for a GitHub issue, send them to Dev Mailing List and link to the thread in the archive or create a Gist and link to it. Please DO NOT paste the log as a comment.

Otherwise, if you really want to know, the log files are located in:

Where is the configuration file?

Jitsis main configuration file is called sip-communicator.properties and is in the user profile directory.

How do you spell Jitsi and what does it mean?

The correct spelling of the application name is Jitsi (jitsi also works). The origin of the name is Bulgarian (spelled ). It means wires and the point is that the application allow you to connect to many network and people just as wires do. Of course no one other than Bulgarians is supposed to know what this means and we picked the name mainly because it was short and sounded good.

Id like to see a new feature in Jitsi, can you do that for me?

Yes, developers take feature requests into account. Send an email to the development list with a detailed description of the requested feature. After we examine its feasibility and decide whether it can be included in the Jitsi distributions you would likely be asked to open a ticket in our issue tracker. It is worth mentioning though, that handling feature requests is highly dependent of the developers availability and there is no guarantee that all requests will be satisfied.

How do I subscribe to mailing lists?

Please visit the Mailing Lists page to learn more about Jitsis mailing lists.

How do I contact the project developers?

You can ask questions concerning usage of the Jitsi on the dev mailing list (Note that the mailing lists are moderated, so, unless you subscribe to them, there may be a delay before your post shows up). For all urgent queries you could also use IRC at irc.freenode.net, channel #jitsi.

How do I send a patch?

Mail patches to the dev mailing list, with a subject line that contains the word PATCH in all uppercase, for example

A patch submission should contain one logical change; please dont mix N unrelated changes in one submission, send N separate emails instead.

The patch itself should be generated from within the project root directory using unified diff format. The following example shows one way to generate it:

You should give your patch files meaningful names. For instance if you fix a socket bug in the foo class do not call your patch file patchfile.txt but instead call it foo-socket.patch.

If the patch implements a new feature, make sure to describe the feature completely in your mail; if the patch fixes a bug, describe the bug in detail and give a reproduction recipe. An exception to these guidelines is when the patch addresses a specific issue in the issues database in that case, just make sure to refer to the issue number in your log message.

Note that unless you are describing a change rather than posting one, we would probably need you to sign our contributor agreement as either an individual or a corporation

I would like to update this wiki what can I do?

Currently, only project developers are permitted to update the wiki. Please send your suggested changes to the dev mailing list.

A wiki page can be updated by appending the string ?action=edit to the current url and refreshing the page. The page will then be displayed with an extra menu line that includes a Page Edit item.

If you click on the Page Edit item, you will be redirected to a logon page. Enter your developer username and password and you should be redirected back to the original page. Click on Page Edit again to access the source content of the page (a quick reference to wiki markup syntax is also displayed).

How do I reset my XMPP or jit.si password?

You can reset your jit.si password from within Jitsi. You can do the same for any XMPP account that allows it.

In the case of jit.si, you can also change your password via the web

Why cant I connect to ekiga.net?

NB: the problems described in this section also apply to other providers such as 1und1.de

Short Answer: The ekiga.net SIP servers are configured in a way that prevent Jitsi (and many other SIP user agents for that matter) to register with the service. Please use iptel.org or ippi.com instead.

Slightly Longer Answer: The service at ekiga.net is configured to only accept SIP REGISTER requests that contain a public IP address in their Contact header. This means that registration from Jitsi would fail unless you actually have a public IP address. The Ekiga client circumvents this by using STUN to learn the address and port that have been allocated for the current session. It then uses the pair in the SIP Contact header. This kind of use was common for the first version of the STUN protocol defined in RFC 3489 which was sometimes referred to as classic STUN.

The IETF has since significantly reviewed the way STUN should be used. The new version of the protocol is now defined in RFC 5389 which, among other things, advises against the use of STUN as a standalone NAT traversal utility:

Today STUN represents one of the tools used by complete traversal mechanisms such as SIP OUTBOUND (RFC 5626) or ICE (RFC 5245). Neither of these includes sending a STUN obtained address in a Contact header.

So, where does Jitsi currently stand on all this? At the time of writing, we support the ICE protocol but only use it with XMPP. Use with SIP is likely to come in the near future. The reason we havent implemented it yet is that most SIP servers currently open to use over the Internet, use a technique called latching. When such servers detect you are connecting from behind a NAT, they would start acting as a relay, receiving media from your peers and then forwarding it to you (and vice versa). While this is by far the most reliably way of traversing NATs, it does indeed imply some scalability constraints.

ICE on the other hand would only fall back to relaying if no other way was found to connect the two participants. This is why it is considered as a more optimal solution and why its also on our roadmap.

Note however that the constraints on ekiga.net would continue preventing Jitsi from connecting even when we do implement support for ICE.

Why do I see ICE failed errors when trying to make calls.

Jitsi implements a number of NAT traversal methods as described here. In many situations we will be able to setup a call directly between you and other users but in order to be able to reliably establish calls, your XMPP or SIP provider has to provide relaying capabilities such as TURN, Jingle Nodes or . If looking for services that support these you can try jit.si or ippi. Also note that both you and your partner need to have unhindered outgoing UDP access to the Internet or at least to your VoIP service provider. You DO NOT however need to map any port numbers on your home router. At best this is going to have no effect.

Does Jitsi support STUN? (and how about TURN, UPnP and Jingle Nodes?)

STUN, together with TURN, Jingle Nodes, IPv6 and UPnP, is one of the techniques that Jitsi uses as part of the Interactive Connectivity Establishment (ICE) protocol to handle NAT traversal for calls made over XMPP.

For its SIP calls, Jitsi currently relies on servers to relay media (a technique also known as Hosted NAT Traversal or latching, which would be the case of the majority of the SIP servers used on the Internet today. Note that in terms of reliability Hosted NAT Traversal gives the same results as use of ICE. It even works better in some ways because the connection is setup immediately and no time is waisted for gathering candidates and making connectivity checks. The only downside of HNT is that it may put a strain on SIP providers requiring more bandwidth. This could become a problem especially in environments with a high number of all IP high quality video calls.

It is likely that ICE support for SIP calls would also be added to Jitsi in 2014 especially since this would also help with WebRTC compatibility.

Standalone support for STUN is NOT going to be part of Jitsi. Check out the ekiga entry for more information on the shortcomings of STUN as a standalone NAT traversal utility.

I have a few questions regarding ZRTP, SRTP and VoIP security in general. Where can I find some answers?

Check out our ZRTP FAQ.

Why does my call stay in the Initiating Call status and I can never connect?

A common reason for providers not to respond to calls is that they simply dont get the INVITE request Jitsi sends to them. This can happen if you are using UDP. The Jitsi INVITE requests may often exceed the maximum allowed packet size (MTU) for your network or that of your server. In such cases packets may be fragmented by your IP stack and fragmentation for UDP does not always work well in certain networks. This is what happens when a client supports multiple features ;). To resolve the issue you can do one of the following:

How does on-line provisioning work?

On-line provisioning is the feature that allows Jitsi to connect to an http URI every time it starts and retrieve part or all of its configuration there. On-line provisioning is often used by providers to remotely configure the clients they maintain. It can be used to set any property in Jitsi such as the codecs used, the features that users can manually configure and even protocol accounts.

When requesting its provisioning information Jitsi can transmit any of a number of parameters to the server, like for example: the OS it is running on, user credentials, a unique ID and others. This way the provisioning server can fine-tune the parameters it sends to Jitsi.

For more information, please check our on-line provisioning manual

Are my chat sessions protected and if so, how?

Jitsi supports the OTR encryption protocol. OTR stands for Off-the-Record Messaging and once youve set it up (i.e. clicked on that padlock icon in a chat window and verified the identity of your contact) it allows you to make sure that no one other than you two can read your messages, not even your service provider. You can find more on the OTR mechanisms here:

http://en.wikipedia.org/wiki/Off-the-Record_Messaging

Should logging be disabled by default when using OTR?

By default Jitsi stores all chats so that if you need any information from them it would always be available. If you would like to disable this behavior you can currently do so by opening Jitsis Options/Preferences, selecting the General pane and then unchecking the Log chat history option near the top. It is also possible to disable chats for specific contacts, to erase their history. An indicator in the chat window makes it aware at all times whether history is on or off while chatting with someone.

OTR protected chats follow the same pattern and some users have expressed concerns that this might be incompatible with their security expectations. Our position on this is that Jitsis role is to protect your communication. We also strive to offer usability. The current defaults represent these objectives: most people would prefer for their private communication not to be readable by third parties and most of the time people use Jitsi from personal devices where they are in control of the access policy.

In some cases users may wish for their communications not to be stored locally. This can be the case when using Jitsi on devices that others may also have access to. In such cases users need to be able to easily see whether history is being logged. They would also need to easily turn this off and potentially even erase previous history.

Note however that this subject is entirely different from the encryption one. They are separate measures meant to protect you against separate attacks or problems. We dont believe that the need for one would necessarily imply the need for the other. We are hence committed to also keeping that separation in the user interface.

Force SIP Message support.

Some SIP servers (Asterisk in particular) do not announce the MESSAGE support, despite supporting it. If you enable the account property FORCE_MESSAGING, Jitsi will attempt to use MESSAGE for chats, despite your configured SIP server not explicitly announcing this support to connected clients. For example, if your SIP account is john.smith@example.com, go to property editor type that in the search field and look for something like

net.java.sip.communicator.impl.protocol.sip.acc0123456789.ACCOUNT_UID with the value SIP:john.smith@example.com

The property to add in that case would be:

net.java.sip.communicator.impl.protocol.sip.acc0123456789.FORCE_MESSAGING with the value true.

How to add/edit configuration properties.

You can do so by clicking on ToolsOptions (JitsiPreferences on OS X), then selecting the Advanced tab and opening the Property Editor form. There you can search edit/delete or create new properties.

Is there an an Android version of Jitsi?

Yes, but it is still in an early alpha stage and further development has been put on hold until further notice. A lot of the user interface is not yet implemented. You can find the apk on the Download page.

Is there an iPhone/iPad version of Jitsi?

No. Due to the restrictions imposed by the platform it is highly unlikely this answer is going to change.

The cc-buildloop target of ant fails with the following error message: Could not create task or type of type: junitreport.

On some Linux distributions such as Debian, the ant package is actualy subdivided into multiple packages. So when you chose to install junit and ant with the distribution specific package system, dont forget to install ant-optional too.

The cc-buildloop target of ant fails with the following error message: No test with id=IcqProtocolProviderSlick.

Have you created your own accounts.properties file in the lib directory? Youll need to define two ICQ test accounts at least, and preferably some test accounts for the other supported protocols.

Read this article: FAQ | Jitsi

Read the original:

FAQ | Jitsi | Prometheism.net

Provisioning | Jitsi

Intro

Provisioning is the feature that allows network and provider administrators to remotely configure Jitsi instances that they are responsible for.

Jitsis provisioning module uses http. This means that, based on a few parameters like an IP or a mac layer address, or a user name and a password, a simple script on a web server or an advanced provisioning system like JitsiProvS can feed to a freshly installed Jitsi all the details that it needs in order to start making calls, downloading updates or configure codec preferences.

Of course, in order for this to work, Jitsi would first need to find out where the provisioning web server is. This can happen either automatically, using discovery protocols like DHCP or mDNS (a.k.a. Bonjour), or by manually entering a provisioning URI in Jitsis configuration form.

The easiest way to have Jitsi connect to a provisioning server is to configure the provisioning URL in its configuration form. Jitsi also supports automatic provisioning discovery via DHCP and Bonjour both of which are discussed later in this document. To do so, go to options => advanced => provisioning and check Enable provisioning (if not already checked), then select Manually specify provisioning URI and enter a URI.

A provisioning URI is an HTTP or HTTPS URL optionally followed by several parameters. The URI would most often point to a provisioning server-side script (e.g. PHP, CGI, servlet, ). Please note that we strongly recommend you only use HTTPS unless you have very good reasons not to. Provisioning POST requests generally contain sensitive information like passwords and you definitely dont want that being sent in clear text.

Here is an example of a provisioning URI:

Note that in the above URI the names of the parameters to the left of an equal (=) sign only depend on you and the web script that you are using in your provisioning environment. Those to the right however are parameters supported by Jitsi and they always come surrounded by accolades and prefixed with a dollar sign (e.g. ${param_value} )

Currently, Jitsi supports the following parameters:

See Configure Jitsi With Provisioning for a list of parameters that allow for hiding various menu entries from the UI.

A provisioning script is something that you write and run on your web server. It handles incoming provisioning requests and it serves configuration properties to Jitsi according to the parameters that these requests contain.

A provisioning script MUST always return content formatted as a valid properties file. Thats pretty much the only limitation and other than that, you can have almost anything in it. You can certainly use the output to configure absolutely any aspect of Jitsi.

Quite often, a provisioning script would use the parameters from the provisioning URI to determine the exact properties that it is going to return. A common example is the provisioning of a SIP account that often depends on either the hardware address or the user name and password entered by the user.

In order to retrieve its configuration properties from the provisioning script, Jitsi would use an HTTP POST request. All the parameters that are present in the provisioning URL (e.g. username, password, osname, ) would then be encoded as parameters of that POST request. This is important to note and may be a bit confusing since the request makes it look as if we would be doing a GET.

JitsiProvS is one example of a Jitsi provisioning server written in python. You can use it as is or extend it to fit your needs. You are of course also free to create your own versions.

Following is a simple PHP provisioning file:

You can use the special property value ${null} when youd like to remove (unset) all properties beginning with the specified prefix. Note that properties are processed in the order that the provisioning script returns them. It is therefore possible to use ${null} in the beginning of a provisioning file, have it remove a group of properties like a SIP account for example, and then feed a new SIP account in the same provisioning file.

The property provisioning.ALLOW_PREFIX tells Jitsi that through the rest of the provisioning file, it should ignore any properties that do not match the specified prefixes. The value of the property would hence contain a number of strings separated by the | (pipe) character.

The provisioning.ENFORCE_PREFIX is somewhat similar to ALLOW_PREFIX. Jitsi would use this property to make sure that your Jitsis configuration file only contains properties matching the specified prefixes and it would remove all those that dont, regardless of whether they were provisioned through a provisioning script or were set by the user.

Important note: Your provisioning script should indicate authentication problems (e.g. wrong password) using a 401 HTTP error response. After receiving such a response, Jitsi would prompt the user to enter the credentials again.

DHCP is one way for Jitsi to discover a provisioning URI without user interaction. To make Jitsi use DHCP provisioning, go to options => advanced => provisioning, check Enable provisioning and then select the DHCP radio button.

In order to get the provisioning URL via DHCP, somewhere on the network a DHCP server has to be running on port 6767. This means that if you already have a DHCP server in your network, you would probably need to install a second one (although this one would be extremely simple to configure so dont worry 🙂 ).

We expect to find our provisioning URI in option 224 so thats where your server needs to serve it.

Following is a sample dhcpd.conf file that you can use almost as is in your own network. Youd probably only need to adjust the subnet and the URI itself:

Note: the provisioning DHCP server does not need to provide IP addresses to machines. All it does is return the provisioning URI to whoever asks.

To configure provisioning via Bonjour, go to options => advanced => provisioning, check Enable provisioning, and then select Bonjour.

In order to get the provisioning URI via Bonjour, you would need to make sure that an mDNS server is running somewhere on your network and that it is configured to advertise the provisioning URI.

Avahi is one of the most popular mDNS servers. Heres what you need to do in order to make it provision Jitsi

On Unix/Linux:

Note that name MUST not be changed since Jitsi will look for the service name Provisioning URL. The host-name is not a FQDN and has to be suffixed by .local, next step will tell avahi about the IP address of this host name. The URL parameters is added in this way paramname=$paramname.

match the one in parameter of provisioning.service file.

would become something like

More:

Provisioning | Jitsi

Provisioning | Jitsi | Prometheism.net

Intro

Provisioning is the feature that allows network and provider administrators to remotely configure Jitsi instances that they are responsible for.

Jitsis provisioning module uses http. This means that, based on a few parameters like an IP or a mac layer address, or a user name and a password, a simple script on a web server or an advanced provisioning system like JitsiProvS can feed to a freshly installed Jitsi all the details that it needs in order to start making calls, downloading updates or configure codec preferences.

Of course, in order for this to work, Jitsi would first need to find out where the provisioning web server is. This can happen either automatically, using discovery protocols like DHCP or mDNS (a.k.a. Bonjour), or by manually entering a provisioning URI in Jitsis configuration form.

The easiest way to have Jitsi connect to a provisioning server is to configure the provisioning URL in its configuration form. Jitsi also supports automatic provisioning discovery via DHCP and Bonjour both of which are discussed later in this document. To do so, go to options => advanced => provisioning and check Enable provisioning (if not already checked), then select Manually specify provisioning URI and enter a URI.

A provisioning URI is an HTTP or HTTPS URL optionally followed by several parameters. The URI would most often point to a provisioning server-side script (e.g. PHP, CGI, servlet, ). Please note that we strongly recommend you only use HTTPS unless you have very good reasons not to. Provisioning POST requests generally contain sensitive information like passwords and you definitely dont want that being sent in clear text.

Here is an example of a provisioning URI:

Note that in the above URI the names of the parameters to the left of an equal (=) sign only depend on you and the web script that you are using in your provisioning environment. Those to the right however are parameters supported by Jitsi and they always come surrounded by accolades and prefixed with a dollar sign (e.g. ${param_value} )

Currently, Jitsi supports the following parameters:

See Configure Jitsi With Provisioning for a list of parameters that allow for hiding various menu entries from the UI.

A provisioning script is something that you write and run on your web server. It handles incoming provisioning requests and it serves configuration properties to Jitsi according to the parameters that these requests contain.

A provisioning script MUST always return content formatted as a valid properties file. Thats pretty much the only limitation and other than that, you can have almost anything in it. You can certainly use the output to configure absolutely any aspect of Jitsi.

Quite often, a provisioning script would use the parameters from the provisioning URI to determine the exact properties that it is going to return. A common example is the provisioning of a SIP account that often depends on either the hardware address or the user name and password entered by the user.

In order to retrieve its configuration properties from the provisioning script, Jitsi would use an HTTP POST request. All the parameters that are present in the provisioning URL (e.g. username, password, osname, ) would then be encoded as parameters of that POST request. This is important to note and may be a bit confusing since the request makes it look as if we would be doing a GET.

JitsiProvS is one example of a Jitsi provisioning server written in python. You can use it as is or extend it to fit your needs. You are of course also free to create your own versions.

Following is a simple PHP provisioning file:

You can use the special property value ${null} when youd like to remove (unset) all properties beginning with the specified prefix. Note that properties are processed in the order that the provisioning script returns them. It is therefore possible to use ${null} in the beginning of a provisioning file, have it remove a group of properties like a SIP account for example, and then feed a new SIP account in the same provisioning file.

The property provisioning.ALLOW_PREFIX tells Jitsi that through the rest of the provisioning file, it should ignore any properties that do not match the specified prefixes. The value of the property would hence contain a number of strings separated by the | (pipe) character.

The provisioning.ENFORCE_PREFIX is somewhat similar to ALLOW_PREFIX. Jitsi would use this property to make sure that your Jitsis configuration file only contains properties matching the specified prefixes and it would remove all those that dont, regardless of whether they were provisioned through a provisioning script or were set by the user.

Important note: Your provisioning script should indicate authentication problems (e.g. wrong password) using a 401 HTTP error response. After receiving such a response, Jitsi would prompt the user to enter the credentials again.

DHCP is one way for Jitsi to discover a provisioning URI without user interaction. To make Jitsi use DHCP provisioning, go to options => advanced => provisioning, check Enable provisioning and then select the DHCP radio button.

In order to get the provisioning URL via DHCP, somewhere on the network a DHCP server has to be running on port 6767. This means that if you already have a DHCP server in your network, you would probably need to install a second one (although this one would be extremely simple to configure so dont worry ).

We expect to find our provisioning URI in option 224 so thats where your server needs to serve it.

Following is a sample dhcpd.conf file that you can use almost as is in your own network. Youd probably only need to adjust the subnet and the URI itself:

Note: the provisioning DHCP server does not need to provide IP addresses to machines. All it does is return the provisioning URI to whoever asks.

To configure provisioning via Bonjour, go to options => advanced => provisioning, check Enable provisioning, and then select Bonjour.

In order to get the provisioning URI via Bonjour, you would need to make sure that an mDNS server is running somewhere on your network and that it is configured to advertise the provisioning URI.

Avahi is one of the most popular mDNS servers. Heres what you need to do in order to make it provision Jitsi

On Unix/Linux:

Note that name MUST not be changed since Jitsi will look for the service name Provisioning URL. The host-name is not a FQDN and has to be suffixed by .local, next step will tell avahi about the IP address of this host name. The URL parameters is added in this way paramname=$paramname.

match the one in parameter of provisioning.service file.

would become something like

Go here to see the original: Provisioning | Jitsi

View original post here:

Provisioning | Jitsi | Prometheism.net

Jitsi PediaView.com | Prometheism.net

Jitsi Original author(s) Emil Ivov Developer(s) Jitsi Team and Contributors Initial release 2003; 14years ago Stable release 2.10 (build.5550) (February5, 2017; 3 months ago) Preview release 2.11 (nightly) Development status Active Written in Java Operating system Linux, Mac OS X, Windows (all Java supported) Size 52.4 MB Windows (bundles its own private JRE)[1] 78.8MB Mac OS X (includes private JRE)[2] 22MB Linux 65MB source code[3] Available in Asturian, English, French, German, Bulgarian, Japanese, Spanish, Italian, Romanian, Greek and 25 more Type Voice over Internet Protocol / instant messaging / videoconferencing License Apache 2.0[4] Website jitsi.org

Jitsi (formerly SIP Communicator) is a free and open source multiplatform[5]voice (VoIP), videoconferencing and instant messaging application for Windows, Linux, Mac OS X and Android. It supports several popular instant-messaging and telephony protocols, including open recognised encryption protocols for chat (OTR) and voice/video/streaming and voice/video conferencing (SIP/RTP/SRTP/ZRTP), as well as built-in IPv6, NAT traversal and DNSSEC. Jitsi and its source code are released under the terms of the Apache Software Licence.[6]

Work on Jitsi (then SIP Communicator) started in 2003 in the context of a student project by Emil Ivov at the University of Strasbourg.[7] It was originally released as an example video phone in the JAIN-SIP stack and later spun off as a standalone project.[8]

Originally the project was mostly used as an experimentation tool because of its support for IPv6.[9][10] Through the years, as the project gathered members, it also added support for protocols other than SIP.

Jitsi has received support from various institutions such as the NLnet Foundation,[11][12] the University of Strasbourg and the Region of Alsace[13] and it has also had multiple participations in the Google Summer of Code program.[14][15]

In 2009, Emil Ivov founded the BlueJimp company which has employed some of Jitsis main contributors[16][17] in order to offer professional support and development services[18] related to the project.

In 2011, after successfully adding support for audio/video communication over XMPPs Jingle extensions, the project was renamed to Jitsi since it was no longer a SIP only Communicator.[19][20] This name originates from the Bulgarian (wires).[21]

On November 4, 2014, Jitsi + Ostel scored 6 out of 7 points on the Electronic Frontier Foundations secure messaging scorecard. They lost a point because there has not been a recent independent code audit.[22]

On February 1, 2015, Hristo Terezov, Ingo Bauersachs and the rest of the team released[23] version 2.6 from their stand at the Free and Open Source Software Developers European Meeting 2015 event in Brussels. This release includes security fixes, removes support of the deprecated MSN protocol, along with SSLv3 in XMPP. Among other notable improvements, the OS X version bundles a Java 8 runtime, enables echo cancelling by default, and uses the CoreAudio subsystem. The Linux build addresses font issues with the GTK+ native LookAndFeel, and fixes some long standing issues about microphone level on call setup when using the PulseAudio sound system. This release also adds the embedded Java database Hyper SQL Database to improve performance for users with huge configuration files, a feature which is disabled by default. A full list of changes is[24] available on the project web site.

Jitsis conference call window on Mac OS X

Jitsi supports multiple operating systems, including Windows as well as Unix-like systems such as Linux, Mac OS X and BSD. Beta packages built for Android are available[25] but the projects roadmap describes the porting to Android as on hold.[26] It also includes:[27]

The following protocols are currently supported by Jitsi:[5]

Jitsi is mostly written in Java[32] which helps reuse most of the same code over the various operating systems it works on. Its GUI is based upon Swing. The project also uses native code for the implementation of platform specific tasks such as audio/video capture and rendering, IP address selection, and access to native popup notification systems such as Growl.

The project uses the Apache Felix OSGi implementation[33] for modularity.

Among others Jitsi uses the JAIN-SIP protocol stack for SIP support and the Jive Software Smack library[34] for XMPP.[35]

As Jitsi can handle IPv6 it is especially interesting for direct PC-to-PC (peer-to-peer) communication, for instance, if both sides were trapped behind NAT routers, but could obtain a reachable IPv6 address via a tunnel-broker.

The Jitsi community has also completed an ICE implementation called ice4j.org, which it uses to provide NAT traversal capabilities, and assist IPv4 to IPv6 transition.[36]

Audio systems supported are PortAudio, PulseAudio and WASAPI (Windows Audio Session API).

Content is authored by an open community of volunteers and is not produced by or in any way affiliated with or reviewed by PediaView.com. Licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License, using material from the Wikipedia article Jitsi, which is available in its original form here:

Original post: Jitsi PediaView.com

Follow this link:

Jitsi PediaView.com | Prometheism.net

How to Configure and Set-Up Jitsi – Liberty Under Attack

Download a PDF version of this article.

By: Shane Radliff

May 25, 2015

Jitsi is an open source platform similar to Skype and handles messaging, audio calls, and video calls. In addition to that, Jitsi comes stock with Off the Record (OTR) and Zimmerman Real Time Protocol (ZRTP) to provide secure communications.

OTR is the program used to encrypt messaging, while ZRTP is what encrypts VoIP (Voice over Internet Protocol) calls.

Since Jitsi comes stock with OTR and ZRTP, the install is quite simple; but to ensure simplicity and accuracy, I have decided to do a tutorial for the configuration and use of Jitsi on a Windows OS.

Note: I dont think the set-up for Windows vs. Mac is much different, so its possible you could use this for Mac OS too.

Downloading Jitsi and Setting up the XMPP Server

1. The first step is to download Jitsi.

2. While youre waiting for Jitsi to download, youll need to set-up an XMPP server. Head over to DuckDuckGo and sign-up. Note: make sure to remember your email (xxxx@dukgo.com) and password as you will need that to log-in.

3. After you have set-up your XMPP server through DuckDuckGo, youll need to open Jitsi.

4. Once Jitsi is open, youll click File and then Add New Account. It will give you a few options but youll want to login through the XMPP Server option (near the bottom of the list). Youll use the log-in information that you signed up with on DuckDuckGo. Note: the email will be something like: xxxx@dukgo.com.

Setting up Off the Record (OTR)

5. Next, find a buddy and add them. Youll do this by selecting the File dropdown and clicking the Add contact button.

6. Once you two are friends, youll need to highlight their name and click the message icon to start a conversation. Next, youll click the lock in the top right of the chat box. A dialogue should appear that states: John Doe is contacting you from an unrecognized computer. You should authenticate Youll then click the hyperlink to authenticate your buddy.

7. Once you click the link, a new window will appear. It will show your fingerprint and also the purported fingerprint of your buddy. At this point, you will have to use a separate channel to authenticate. That can be done by a VoIP call, phone call, or in person. Youll read your fingerprint and then your buddy will read theirs. If they match, then you will click Authenticate Buddy.

8.After you click Authenticate Buddy, check the chat window and make sure the lock is green and has no further warning messages. If its green, youre now using Off the Record encryption in your messages with the buddy you verified. Note: keep in mind, youll have to do it separately for everyone you chat with, but you will only have to do it once for each.

Setting up Zimmerman Real Time Protocol (ZRTP)

9. Highlight your friends name and click either the audio or video call button. It will take a few seconds for it to connect and then it should start ringing.

10.At that point, you will see a button in the middle of the call window that says connected with an unlatched lock. That is indicating that ZRTP is not connected.

11. After a few seconds, there will be window that opens up at the bottom of the call window.

12. At this point, the call is still not secure, and you will need to verify the key with your friend as an additional security measure. If the codes match, then you will click confirm and close out of that window. ZRTP should be connected and you can verify that by making sure the lock is now closed and green.

If you made it through all the steps and followed the instructions, you should have Jitsi, ZRTP, and OTR configured. If not, and youre having some problems or technical difficulties, please take a look at these two videos and they should be able to answer any questions. Alternatively, view the tutorial made by the Pillow Fortress blog by clicking here.

If for some reason those do not work, please email me or call me at 309-533-7857 and I will assist you with getting it configured properly.

Youve just taken a great step in ensuring private communications and have also began implementing a security culture.

I would further recommend encrypting your email as well. A colleague put together a great tutorial on setting up Pretty Good Privacy (PGP), which you can find here.

Lastly, if you feel like there is something missing in the tutorial or that something needs to be explained better, please let me know. This will be updated as needed when I get feedback.

Shane is the founder of Liberty Under Attack Radio, The Vonu Podcast, and LUA Publications, an independent publishing company. He has been a guest on many podcasts and radio shows and his work has appeared on sites all over the alternative media. When he's not producing content (which isn't often), he enjoys riding four wheelers, reading, and drumming.

See the original post here:

How to Configure and Set-Up Jitsi - Liberty Under Attack

Jitsi for Mac OS X Secure instant messaging and VoIP

Posted10 August 2016

Jitsi is cross-platform, free and open-source software for Instant Messaging (IM), Voice over IP (VoIP) and video chat. It is compatible with many popular IM and telephony services and provides reliable end-to-end encryption for text chats (and somewhat experimental end-to-end encryption for voice chats).

Jitsi is cross-platform, free and open-source software for Instant Messaging (IM), Voice over IP (VoIP) and video chat. It is compatible with many popular IM and telephony protocols, including Jabber/XMPP, Facebook Messenger, AIM, ICQ, MSN, Yahoo! Messenger and SIP. It provides end-to-end encryption for text chats through the Off-the-Record (OTR) protocol. It also supports end-to-end encrypted voice chat using ZRTP over SIP, though it tends to be somewhat unstable when used in this way.

Important: If you and those with whom you communicate use OTR encryption for text chats and ZRTP encryption for voice chats, Jitsi will protect the content of your conversations from service providers like Google and Facebook. However, these providers can still monitor certain metadata about the conversations you have through Jitsi. Examples include:

They can share this information with third parties, including other companies and governments. For conversations where such metadata could be sensitive, you and those with whom you communicate should consider using a trusted, independent service provider.

Jitsi allows you to use your existing accounts to communicate securely through the use of end-to-end encryption. This not only makes the content of your communication inaccessible to various third parties, such as government or corporate surveillance platforms, it also protects your conversations from those who operate the chat services themselves (such as Facebook, if you are using Facebook Messenger, or Google, if you are using Google Talk).

Note: Jitsi was written in the Java programming language. As such, Java must be installed on your computer in order for it to work. Though Java itself does not represent a significant security risk, Java browser extensions are often found to contain vulnerabilities that allow malicious websites to assume control of your computer or install malware. If your browser has a Java plugin installed, we strongly recommend that you disable it.

Jitsi is available for Mac OS, GNU Linux, and MS Windows. It can be used to communicate with other XMPP or SIP clients that support end-to-end encryption through OTR (for text chat) or ZRTP (for voice chat). Examples are recommended below:

To install the latest stable version of Jitsi, follow the steps below:

Step 1. Go to the Jitsi download page.

Tip: Make sure you're on the secure version of the Jitsi download page before you download anything. (The 'https' part encrypts the connection between your browser and the website, thus making it harder for an attacker to modify the file you're going to download.)

Step 2. Select the appropriate Jitsi Mac OS X Package for your computers operating system.

Figure 1: Jitsis Download Page

If you are using OS X versions 10.8 and above, click on the main Mac OS X Packages link directly below the apple icon. If you are using versions 10.6 or 10.7, click on the No-JRE Packages Mac OS X 10.6/10.7 link. Most users with up-to-date operating systems will click on the main Mac OS X Packages link.

Tip: If you are unsure of which version your operating system is, click on the apple icon in the menu at the top of your screen, then scroll down to select About This Mac. A window will appear that includes the current version number of your operating system.

Step 3. Click to download the appropriate version of Jitsi. Save it to your Downloads folder.

Figure 2: Downloading Jitsi

To install Jitsi, follow the steps below:

Step 1. Navigate to the folder in which you saved the Jitsi package (titled jitsi-latest.dmg' or jitsi-no-jre-latest.dmg). In this example, we saved it in the Downloads file.

Figure 1: The Downloads folder containing the Jitsi .dmg file

Step 2. Double-click the Jitsi .dmg file to mount it as a disk image. It should show up in a new window (Figure 2, below) and under Devices in the left-hand sidebar of a normal Finder window.

Figure 2: Inside the mounted Jitsi disk image

Step 3. Drag the Jitsi.app into the Applications folder.

Figure 3: Dragging the mounted Jitsi.app into the Applications folder

It will then copy over into Applications.

Step 4. Before we start using Jitsi, we should unmount (or 'eject') the Jitsi disk image. Find Jitsi under Devices in the Finder sidebar. Click on the {eject} icon next to it in the sidebar to unmount the disk image.

Figure 4: Unmounting (or ejecting) the Jitsi disk image

Jitsi is written in the Java programming language andat the time of writingrequires an older, 'legacy' version of Java in order to run on Mac OS X.

Therefore, the first time you run Jitsi, you will probably see a message (as seen in Figure 1, below) informing you that you need to install the legacy Java SE 6 runtime in order to open and use Jitsi. (This same legacy version of Java is also called 'Java for OS X 2015-001' by Apple, as seen in Figure 2, below.)

To install this required legacy version of Java, follow the steps below:

Step 1. Locate Jitsi in your Applications folder and double-click to open it.

Step 2. If you need to install the legacy Java SE 6 runtime, the alert in Figure 1 will pop up.

Figure 1: Alert window notifying the user to install the legacy Java SE 6 runtime for Jitsi

If you already have this version of Java installed, Jitsi will open without this installation message, and you can skip to Section 3, Adding accounts to Jitsi.

Step 3. Click on More Info in the alert window. This will open up a webpage in your browser where you can download the required legacy version of Java 6 from Apple.

Figure 2: Apple support page for legacy Java 6

Step 4. To download the legacy version of Java 6, click on the [Download] button at the top of the webpage. Save the file to your Downloads file.

Figure 3: Download progress bar in Firefox

Step 5. Navigate to the folder in which you saved the Jitsi file (titled JavaForOSX.pkg). In this example, we saved it in the Downloads file.

Figure 4: The Downloads folder containing the Jitsi .pkg file

Step 6. Double-click the Java .pkg file to mount it as a disk image. It should show up in a new window (Figure 5, below) and under Devices in the left-hand sidebar of a normal Finder window.

Figure 5: Inside the mounted Jitsi disk image

Step 7. Double-click JavaForOSX.pkg in the mounted disk image. It will open the installer for the legacy version of Java for OS X 2015-001.

Figure 6: Installer for Java

Step 8. There is no special installation details for Java. Click [Continue] through the Read Me section, then review and agree to the License agreement. To install Java in the default location for installation (Macintosh HD), input an admin-level password to authorize the installation of Java.

Figure 7: Java installation complete

When you are finished, the installer will show that the installation was successful.

Step 9. Click [Close] to exit the Installer.

Step 10. Before we continue, we should unmount (or 'eject') the Java disk image. Find Java for OS X 2015-001 under Devices in the Finder sidebar. Click on the {eject} icon next to it in the sidebar to unmount the disk image.

Figure 8: Unmounting (or ejecting) the Java disk image

When you have the newest version of Jitsi and the legacy version of Java SE 6 installed, you can open Jitsi for the first time. Depending on your System Preferences for Mac OS X, you may see a few messages when you run Jitsi for the first time.

To navigate these and run Jitsi for the first time, follow the steps below:

Step 1. As with most Mac OS X apps downloaded from sources other than those downloaded from Apples official App Store, youll see a confirmation alert the first time you open Jitsi.

Navigate to your Applications folder, locate the Jitsi app, and double-click to open it.

Step 2. Youll see the pop-up in Figure 1 below, asking you if youre sure you want to open Jitsi. Click [Open].

Figure 1: Confirmation alert when opening Jitsi for the first time

Step 3. Depending on what your Firewall settings are in the Security & Privacy section of System Preferences, you may also see a second alert as Jitsi opens.

Figure 2: Authorization alert for Jitsi to accept incoming connections

The alert window will ask you if you want the application Jitsi.app to accept incoming network connections? Click [Allow].

Jitsi supports many different services and protocols for text chat. The first time you launch Jitsi, you will see the window shown in Figure 1, which allows you to add the accounts you want to access through Jitsi.

Figure 1: Jitsi's initial account configuration screen

You can use this screen to enter a username and password for each of the services displayed, for a total of four accounts. But you must already have accounts for these services before configuring them for use here in the Jitsi client. The sections below describe how to set up accounts for various IM and VoIP service providers.

Note: Both Google Talk and Facebook may require that you change certain account settings before you can access their text chat services through Jitsi. To learn how, see the following two sections:

As shown in Figure 1 of the previous section, the first time you launch Jitsi, you will see an account configuration screen that allows you to add various chat services to the application. After you have added at least one account, this screen will no longer appear. In order to add additional accounts, follow the steps below.

Step 1. Click File in Jitsi's menu and scroll down to select Add new account... to choose the service or protocol you want to use.

Figure 1: Add New Account screen

Step 2. Select Google Talk from the Network drop-down list.

Figure 2: Entering Google Talk account details into the Add New Account screen

Step 3. Type your Google username

Step 4. Type your Google passphrase

Step 5. (Optional) Uncheck the Remember Password box.

Important: If you want Jitsi to remember your Google Talk account password for you, you should first enable its Master Password feature.

Step 6. Click [Add]

You can now use Jitsi to communicate through the Google Talk account you have added.

Note: If you are using 2-step verification to protect access to your Gmail account, you may see an error like the one shown in Figure 3 when Jitsi tries to access your account. (It will also display the same error if you get your passphrase wrong.)

Figure 3: Google Talk authentication failed (possibly as a result of "2-step verification" settings)

To access Google Talk using Jitsi, you will need to generate an "application-specific password". To learn how, see Google's instructions. When you have generated an app password for Jitsi within your Google account, you will enter that password within Jitsi as the main password for your Google Talk account.

There are two settings that you may need to change on the Facebook website first before Jitsi can use Facebook for chat: - Create a username for your Facebook account. - Turn on Facebooks application platform.

Step 1. Assign a username to your Facebook account on the Facebook website.

Before Jitsi can connect to Facebook to use its chat functionality, you must assign a username to your Facebook account. Unlike most Web services, Facebook does not require you to select a username when you create your account, but it does allow you to create one if you wish. You can confirm your username by signing into your Facebook account.

Your username is what appears in the address bar of your browser after https://www.facebook.com/ when you view your Timeline or Page. So, if your username is elena.katerina, you should see https://www.facebook.com/elena.katerina in your browser's address bar when viewing your Timeline. Your username is also part of your Facebook email address (elena.katerina@facebook.com, for example).

If you do not have a Facebook username, you can choose one by signing into your Facebook account and selecting Settings > General or by navigating to https://www.facebook.com/username.

Facebook may need you verify your account before allowing you to select a username. This could require giving Facebook a mobile phone number at which you can receive a text message. For more details see Facebooks explanation of usernames.

Step 2. Turn on Facebooks application platform in order to give Jitsi access to your Facebook account. To do this, sign in to Facebook, select Settings > Apps, then confirm that the Apps, Websites and Plugins setting is Enabled.

Note: Turning on Facebooks application platform opens up some of your Facebook data to third-party application developers. This data is available not only to the Facebook applications that you choose to use, but also to the Facebook applications used by your friends. After turning on Facebooks Apps, Websites and Plugins, be sure to check the settings under Apps others use. This setting allows you to hide some personal information from applications used by your friends. Unfortunately, Facebook does not offer settings to hide all personal information. As long as the application platform is Enabled, certain categories of data (including your friend list, your gender, and any information you have made public) are accessible to apps used by others. If this is unacceptable, you should disable Apps, Websites and Plugins and avoid using Jitsi with Facebook Messenger.

Once have chosen a Facebook username and enabled the application platform, you can add your Facebook account to Jitsi.

As shown in Figure 1 of the Add accounts to Jitsi section, the first time you launch Jitsi, you will see an account configuration screen that allows you to add various chat services to the application. After you have added at least one account, this screen will no longer appear. In order to add additional accounts, follow the steps below to add your Facebook account to Jitsi.

Step 3. Click File in Jitsi's menu bar and select Add new account... to choose the service or protocol you want to use.

Figure 1: Add New Account screen

Step 4. Select Facebook from the Network list to enter your username and passphrase

Figure 2: Entering a username and password into the Add New Account screen

Step 5. Type your Facebook username

Step 6. Type your Facebook passphrase.

Step 7. (Optional) Uncheck the Remember password box

Important: If you want Jitsi to remember your account passwords (or passphrases) for you, you should enable its Master Password feature.

Step 8. Click [Add]

You can now use Jitsi to communicate using your Facebook account.

XMPP and Jabber are different names for the same instant messaging (IM) protocol. It is an open standard, and there are many providers who offer free Jabber/XMPP accounts that you can use with Jitsi. The IM Observatory allows you to evaluate some security properties of public Jabber/XMPP services.

If you have experience running online services, you can also install a Jabber/XMPP server (such as ejabberd or Prosody IM) on your own server and provide accounts to members of a particular community or organization.

Below, we recommend a few services that have a great deal of experience protecting their users' privacy.

Excerpt from:

Jitsi for Mac OS X Secure instant messaging and VoIP