Category Archives: Jitsi

Fox Sports 1 is using the video caller-based production platform from The Video Call Center (VCC) to extend its ability to bring key sports personalities and guests on the air.

Using the VCC platform, FS1 can bring guests live to air for two-way conversations using only the smartphone or other convenient devices available to the guest from anywhere in the world. Currently, the VCC platform is used throughout the week in the production of The Herd with Colin Cowherd.

The best technologies make a show better for the audience and the production team and the VCC does that remarkably well, said Fox Sports Senior Vice President of Production Whit Albohm. The video quality is excellent and the flexibility means we can put the best names in sports on-air any time with minimal preparation to talk about the most current topics of the day. Our producers and our talent appreciate the flexibility and ease of the VCC platform and that the VCC team members feel like part of our family.

The collaboration began when Colin Cowherds producers went looking for a more reliable two-way live video remote solution that would enhance, rather than impede, the show. With its ultra-low-latency, high quality, two-way video call connections, easy video call setup, and experienced video call production team, the VCC solution enables Cowherd to engage his guests in the lively back-and-forth banter that is the staple of the Herd style.

Flexibility and efficiency are the hallmarks of the VCC platform, providing FS1 with an effortless means of initiating live interviews with coaches and athletes, as well as Fox Sports correspondents. Remote participants only need a smartphone with standard mobile data or WiFi connection to appear on camera. Producers can establish first video in as little as 24 seconds via a text sent to the guest from VCCs StageDoor system. They never have to download software either, as the VCC uses standard native video calling capabilities built into all smartphones including Apple FaceTime and WebRTC-based Gruveo and Jitsi, as well as popular video call apps like Skype.

The Herd originates in LA, but during a given sports season producers need access to players and commentators spread all over the country with highly variable schedules.

The VCC service for FS1 combines VCCs expert production staff with patented technologies that together ensure long duration, stable connections with no lag that make natural, effortless conversation possible between host and guests. Monitors on the set at FS1 let the show host see their guest, while the VCCs exclusive instant return video makes sure that guests can also view the hosts on their phone, all in real-time.

We are thrilled to be supporting FS1 in creating some of the premier sports talk on the air today, said VCC CEO Larry Thaler. We think that the keys to the best live television are having access to the most relevant, recognizable voices and making it easy for them to have sustained, effortless, face-to-face conversation anytime, from anywhere. We look forward to supporting FS1 as it continues to innovate sports television.

Viewers can see VCC remotes on FS1 most weekdays, with the Herd airing as many as three live, VCC remote guest segments per show.

Link:
Fox Sports 1 Utilized Video Call Center to Extend Reach of Shows Like The Herd with Colin Cowherd - Sports Video Group

PALISADES, N.Y.Colin Cowherds guests on his Fox Sports 1 showThe Herd With Colin Cowherdare dialing in with help from the Video Call Center. VCC announced that it has provided its caller-based production platform to the sports network, which enables two-way phone/video interviews to be established using only the guests smartphone or capable device.

Remote participants can utilize the VCC platform with a smartphone that has standard mobile data or a Wi-Fi connection to conduct a video interview. FS1 producers can establish the video connection via a text with VCCs StageDoor system. VCC uses standard native video calling capabilitiesavailable in smartphones that feature Apple FaceTime, WebRTC-based Gruveo and Jitsi, as well as video call apps like Skypewithout downloading software.

VCC also provides its production staff with patented technologies that help ensure durable, stable connections with no lag, according to VCC. The videos can be displayed on the sets monitors, while VCCs instant return video enables the guest to see the host on their phone in real time.

According to VCC, The Herd uses VCC for as many as three live remote guest segments per show.

Originally posted here:
Fox Sports 1 Dials Up VCC for The Herd With Colin Cowherd - TV Technology

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.

See the original post:
Gladstone gold does club proud - Gladstone Observer

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

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 ...

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

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

See the original post:
Tsirang vegetable vendors commit to selling local chillies - Kuensel, Buhutan's National Newspaper

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

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

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