Good Afternoon Jitsi Developers,
Thank you for the email. I was trying to open the tickets today but
couldnt find the link to create a new ticket on jira. Can you please
point me to the right site? Thanks.
Also I had couple of more questions.
I was testing jitsi today and found out that something goes wrong with
the config files because it will not let me reopen jitsi after I closed
it the first time using quit. I checked that all the jitsi processes are
killed. To reopen jitsi I had to delete the .jitsi directory and than it
would let me open jitsi again. I also attached the warnings I get when I
The second question is that when I use command line argument jitsi sip:,
it calls the person but when we disconnect it doesn't quit jitsi
correctly. I attached the output from the terminal. I always have to
kill the process when I do this.
My last question is, if there is an easy way to change the accept call
interfece or any documentation that would help me do that . Thanks you
very much for the help. I look forward to your reply. Thanks.
On Thu, Sep 22, 2011 at 2:54 PM, Lyubomir Marinov <firstname.lastname@example.org > <mailto:email@example.com>> wrote:
On Thu, Sep 22, 2011 at 7:41 PM, Leonid Nayer <firstname.lastname@example.org > <mailto:email@example.com>> wrote:
> First you need to use libjnportaudio with librt
> linked in. Damian provided it to me.
Please open an issue in our issue tracker for it (and mention in the
description that you've been authorized on the dev mailing list to do
so) so that we can get it done as soon as we have the time.
> Also I found out yesterday that Enable
> support to encrypt calls doesnt work on red hat. So All I did is set
> DEFAULT_ENCRYPTION to false in the properties file and jitsi works
> both side can hear.
> I was wondering if jitsi can have DEFAULT_ENCRYPTION set to false as a
Secure calls is one of the major features of Jitsi so I'd rather think
that we'd like to fix any issue related to it than disable it. You may
open a new issue for it as well but please notice that we have a lot
on our todo lists so we may not be able to handle it in the very near
> Also I was wondering if a feature can be added to make calls from
> command line.
Well, Jitsi was supposed to already handle protocol URIs/addresses on
the command line by establishing calls to them. Have you already tried
a command line like "jitsi sip:firstname.lastname@example.org
<mailto:sip%3Aecho@iptel.org>"? Could you please
elaborate on your experience and expectations with respect to making
calls from the command line?