[jitsi-dev] XCAP over SSL issue


#1

Hey Emil,

It seems to me XCAP doesn't work over SSL at the moment.

When I try to connect to SSL enabled XCAP server I am getting an error
as shown here:
http://dl.dropbox.com/u/3182365/Jitsi-XCAP-SSL-Error.log

The same works just fine over plain HTTP in Jitsi and I can open
https://xcap.ssl7.net/xcap-root in the web browser on the same machine
which Jitsi runs on.
So it would seem as if Jitsi doesn't connect to SSL at the moment.

Regards,
Chris


#2

Hey,

I just checked with tcpdump what (if any) traffic on port 443 is sent
when Jitsi is configured to use XCAP over SSL, and interestingly it
only sends request on IP v6, see below:

root@dom:~# tcpdump -i any -n port 443
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
20:56:29.610294 IP6 ::1.45991 > ::1.443: Flags [S], seq 1994172625,
win 32752, options [mss 16376,sackOK,TS val 204716 ecr 0,nop,wscale
7], length 0
20:56:29.610300 IP6 ::1.443 > ::1.45991: Flags [R.], seq 0, ack
1994172626, win 0, length 0

And that is why it fails.

Any suggestions how to fix this issue very much appreciated.

Best regards,
Chris

···

On 21 June 2011 00:07, Chris Maciejewski <chris@wima.co.uk> wrote:

Hey Emil,

It seems to me XCAP doesn't work over SSL at the moment.

When I try to connect to SSL enabled XCAP server I am getting an error
as shown here:
http://dl.dropbox.com/u/3182365/Jitsi-XCAP-SSL-Error.log

The same works just fine over plain HTTP in Jitsi and I can open
https://xcap.ssl7.net/xcap-root in the web browser on the same machine
which Jitsi runs on.
So it would seem as if Jitsi doesn't connect to SSL at the moment.

Regards,
Chris


#3

Hey Chris,

How did you configure your xcap server? Is it running on your local host?

Emil

На 22.06.11 21:59, Chris Maciejewski написа:

···

Hey,

I just checked with tcpdump what (if any) traffic on port 443 is sent
when Jitsi is configured to use XCAP over SSL, and interestingly it
only sends request on IP v6, see below:

root@dom:~# tcpdump -i any -n port 443
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
20:56:29.610294 IP6 ::1.45991 > ::1.443: Flags [S], seq 1994172625,
win 32752, options [mss 16376,sackOK,TS val 204716 ecr 0,nop,wscale
7], length 0
20:56:29.610300 IP6 ::1.443 > ::1.45991: Flags [R.], seq 0, ack
1994172626, win 0, length 0

And that is why it fails.

Any suggestions how to fix this issue very much appreciated.

Best regards,
Chris

On 21 June 2011 00:07, Chris Maciejewski <chris@wima.co.uk> wrote:

Hey Emil,

It seems to me XCAP doesn't work over SSL at the moment.

When I try to connect to SSL enabled XCAP server I am getting an error
as shown here:
http://dl.dropbox.com/u/3182365/Jitsi-XCAP-SSL-Error.log

The same works just fine over plain HTTP in Jitsi and I can open
https://xcap.ssl7.net/xcap-root in the web browser on the same machine
which Jitsi runs on.
So it would seem as if Jitsi doesn't connect to SSL at the moment.

Regards,
Chris

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#4

Hey,

I am running Jitsi on Ubuntu 10.10 with both IP v4 and v6 stacks enabled.

XCAP is running on a remote server.

Perhaps what I am missing is -DpreferIPv4Stack=true

See http://download.oracle.com/javase/1.4.2/docs/guide/net/properties.html

It seems if both v4 and v6 are available Java will prefer v6?

Chris

···

On 22 June 2011 21:04, Emil Ivov <emcho@jitsi.org> wrote:

Hey Chris,

How did you configure your xcap server? Is it running on your local host?

Emil

На 22.06.11 21:59, Chris Maciejewski написа:

Hey,

I just checked with tcpdump what (if any) traffic on port 443 is sent
when Jitsi is configured to use XCAP over SSL, and interestingly it
only sends request on IP v6, see below:

root@dom:~# tcpdump -i any -n port 443
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
20:56:29.610294 IP6 ::1.45991 > ::1.443: Flags [S], seq 1994172625,
win 32752, options [mss 16376,sackOK,TS val 204716 ecr 0,nop,wscale
7], length 0
20:56:29.610300 IP6 ::1.443 > ::1.45991: Flags [R.], seq 0, ack
1994172626, win 0, length 0

And that is why it fails.

Any suggestions how to fix this issue very much appreciated.

Best regards,
Chris

On 21 June 2011 00:07, Chris Maciejewski <chris@wima.co.uk> wrote:

Hey Emil,

It seems to me XCAP doesn't work over SSL at the moment.

When I try to connect to SSL enabled XCAP server I am getting an error
as shown here:
http://dl.dropbox.com/u/3182365/Jitsi-XCAP-SSL-Error.log

The same works just fine over plain HTTP in Jitsi and I can open
https://xcap.ssl7.net/xcap-root in the web browser on the same machine
which Jitsi runs on.
So it would seem as if Jitsi doesn't connect to SSL at the moment.

Regards,
Chris

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#5

Hey,

Just found the solution :slight_smile:

in build.xml need to change line 48 from:

<property name='java.net.preferIPv6Addresses' value='true' />

to:

<property name='java.net.preferIPv6Addresses' value='false' />

And everything works fine.

Regards,
Chris

···

On 22 June 2011 21:14, Chris Maciejewski <chris@wima.co.uk> wrote:

Hey,

I am running Jitsi on Ubuntu 10.10 with both IP v4 and v6 stacks enabled.

XCAP is running on a remote server.

Perhaps what I am missing is -DpreferIPv4Stack=true

See http://download.oracle.com/javase/1.4.2/docs/guide/net/properties.html

It seems if both v4 and v6 are available Java will prefer v6?

Chris

On 22 June 2011 21:04, Emil Ivov <emcho@jitsi.org> wrote:

Hey Chris,

How did you configure your xcap server? Is it running on your local host?

Emil

На 22.06.11 21:59, Chris Maciejewski написа:

Hey,

I just checked with tcpdump what (if any) traffic on port 443 is sent
when Jitsi is configured to use XCAP over SSL, and interestingly it
only sends request on IP v6, see below:

root@dom:~# tcpdump -i any -n port 443
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
20:56:29.610294 IP6 ::1.45991 > ::1.443: Flags [S], seq 1994172625,
win 32752, options [mss 16376,sackOK,TS val 204716 ecr 0,nop,wscale
7], length 0
20:56:29.610300 IP6 ::1.443 > ::1.45991: Flags [R.], seq 0, ack
1994172626, win 0, length 0

And that is why it fails.

Any suggestions how to fix this issue very much appreciated.

Best regards,
Chris

On 21 June 2011 00:07, Chris Maciejewski <chris@wima.co.uk> wrote:

Hey Emil,

It seems to me XCAP doesn't work over SSL at the moment.

When I try to connect to SSL enabled XCAP server I am getting an error
as shown here:
http://dl.dropbox.com/u/3182365/Jitsi-XCAP-SSL-Error.log

The same works just fine over plain HTTP in Jitsi and I can open
https://xcap.ssl7.net/xcap-root in the web browser on the same machine
which Jitsi runs on.
So it would seem as if Jitsi doesn't connect to SSL at the moment.

Regards,
Chris

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#6

Hey,

I am running Jitsi on Ubuntu 10.10 with both IP v4 and v6 stacks enabled.

XCAP is running on a remote server.

The tcpdump output you pasted here seemed to indicate that both the client
and the server were running on the same machine (the one that you were doing
the capture on) and that they were connecting to each other through the lo
interface. That's why I wanted to see how the URI you used to configure XCAP
in Jitsi.

Perhaps what I am missing is -DpreferIPv4Stack=true

See http://download.oracle.com/javase/1.4.2/docs/guide/net/properties.html

It seems if both v4 and v6 are available Java will prefer v6?

Nope. If both are available Java would go for IPv4. I believe we override
this behaviour for SIP and XMPP but it should be unchanged for XCAP.

Emil

···

On Wed, Jun 22, 2011 at 10:14 PM, Chris Maciejewski <chris@wima.co.uk>wrote:

Chris

On 22 June 2011 21:04, Emil Ivov <emcho@jitsi.org> wrote:
> Hey Chris,
>
> How did you configure your xcap server? Is it running on your local
host?
>
> Emil
>
> На 22.06.11 21:59, Chris Maciejewski написа:
>> Hey,
>>
>> I just checked with tcpdump what (if any) traffic on port 443 is sent
>> when Jitsi is configured to use XCAP over SSL, and interestingly it
>> only sends request on IP v6, see below:
>>
>> root@dom:~# tcpdump -i any -n port 443
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
>> listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535
bytes
>> 20:56:29.610294 IP6 ::1.45991 > ::1.443: Flags [S], seq 1994172625,
>> win 32752, options [mss 16376,sackOK,TS val 204716 ecr 0,nop,wscale
>> 7], length 0
>> 20:56:29.610300 IP6 ::1.443 > ::1.45991: Flags [R.], seq 0, ack
>> 1994172626, win 0, length 0
>>
>> And that is why it fails.
>>
>> Any suggestions how to fix this issue very much appreciated.
>>
>> Best regards,
>> Chris
>>
>>
>> On 21 June 2011 00:07, Chris Maciejewski <chris@wima.co.uk> wrote:
>>> Hey Emil,
>>>
>>> It seems to me XCAP doesn't work over SSL at the moment.
>>>
>>> When I try to connect to SSL enabled XCAP server I am getting an error
>>> as shown here:
>>> http://dl.dropbox.com/u/3182365/Jitsi-XCAP-SSL-Error.log
>>>
>>> The same works just fine over plain HTTP in Jitsi and I can open
>>> https://xcap.ssl7.net/xcap-root in the web browser on the same machine
>>> which Jitsi runs on.
>>> So it would seem as if Jitsi doesn't connect to SSL at the moment.
>>>
>>> Regards,
>>> Chris
>>>
>>
>
> --
> Emil Ivov, Ph.D. 67000 Strasbourg,
> Project Lead France
> Jitsi
> emcho@jitsi.org PHONE: +33.1.77.62.43.30
> http://jitsi.org FAX: +33.1.77.62.47.31
>
>

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#7

Hey,

Just found the solution :slight_smile:

in build.xml need to change line 48 from:

Ah! Didn't realize you were running from sources. "ant run-v4" would have
been equivalent then.

Still. This doesn't explain the connection on localhost. Did you have the
same hostname as your server's in /etc/hosts?

Emil

···

On Wed, Jun 22, 2011 at 10:19 PM, Chris Maciejewski <chris@wima.co.uk>wrote:

<property name='java.net.preferIPv6Addresses' value='true' />

to:

<property name='java.net.preferIPv6Addresses' value='false' />

And everything works fine.

Regards,
Chris

On 22 June 2011 21:14, Chris Maciejewski <chris@wima.co.uk> wrote:
> Hey,
>
> I am running Jitsi on Ubuntu 10.10 with both IP v4 and v6 stacks enabled.
>
> XCAP is running on a remote server.
>
> Perhaps what I am missing is -DpreferIPv4Stack=true
>
> See
http://download.oracle.com/javase/1.4.2/docs/guide/net/properties.html
>
> It seems if both v4 and v6 are available Java will prefer v6?
>
> Chris
>
> On 22 June 2011 21:04, Emil Ivov <emcho@jitsi.org> wrote:
>> Hey Chris,
>>
>> How did you configure your xcap server? Is it running on your local
host?
>>
>> Emil
>>
>> На 22.06.11 21:59, Chris Maciejewski написа:
>>> Hey,
>>>
>>> I just checked with tcpdump what (if any) traffic on port 443 is sent
>>> when Jitsi is configured to use XCAP over SSL, and interestingly it
>>> only sends request on IP v6, see below:
>>>
>>> root@dom:~# tcpdump -i any -n port 443
>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
>>> listening on any, link-type LINUX_SLL (Linux cooked), capture size
65535 bytes
>>> 20:56:29.610294 IP6 ::1.45991 > ::1.443: Flags [S], seq 1994172625,
>>> win 32752, options [mss 16376,sackOK,TS val 204716 ecr 0,nop,wscale
>>> 7], length 0
>>> 20:56:29.610300 IP6 ::1.443 > ::1.45991: Flags [R.], seq 0, ack
>>> 1994172626, win 0, length 0
>>>
>>> And that is why it fails.
>>>
>>> Any suggestions how to fix this issue very much appreciated.
>>>
>>> Best regards,
>>> Chris
>>>
>>>
>>> On 21 June 2011 00:07, Chris Maciejewski <chris@wima.co.uk> wrote:
>>>> Hey Emil,
>>>>
>>>> It seems to me XCAP doesn't work over SSL at the moment.
>>>>
>>>> When I try to connect to SSL enabled XCAP server I am getting an error
>>>> as shown here:
>>>> http://dl.dropbox.com/u/3182365/Jitsi-XCAP-SSL-Error.log
>>>>
>>>> The same works just fine over plain HTTP in Jitsi and I can open
>>>> https://xcap.ssl7.net/xcap-root in the web browser on the same
machine
>>>> which Jitsi runs on.
>>>> So it would seem as if Jitsi doesn't connect to SSL at the moment.
>>>>
>>>> Regards,
>>>> Chris
>>>>
>>>
>>
>> --
>> Emil Ivov, Ph.D. 67000 Strasbourg,
>> Project Lead France
>> Jitsi
>> emcho@jitsi.org PHONE: +33.1.77.62.43.30
>> http://jitsi.org FAX: +33.1.77.62.47.31
>>
>>
>

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#8

Hello,

In this build (3558, Debian Linux) i lost my google account - it just dissapeared from the account list. And cannot configure any google talk accounts anymore neither using jabber neither the google talk account creator. Whenever i press the finish button nothing happens except the error below.
Other jabber server works.
The 3554 version has no such issues.

Please look into this.

Error message:

$ jitsi
warning: The VAD has been replaced by a hack pending a complete rewrite
23:01:21.892 SEVERE: service.protocol.AccountManager.doLoadStoredAccounts().196 Failed to load account {JINGLE_NODES_ENABLED=true, AUTO_DISCOVER_STUN=true, RESOURCE=home-desktop, RESOURCE_PRIORITY=7, ENCRYPTED_PASSWORD=TMe8pYP1o6IP8KQPPeJMTg==, IS_SERVER_OVERRIDDEN=true, SEND_KEEP_ALIVE=true, AUTO_DISCOVER_JINGLE_NODES=true, IS_PREFERRED_PROTOCOL=false, GOOGLE_CONTACTS_ENABLED=true, GMAIL_NOTIFICATIONS_ENABLED=false, UPNP_ENABLED=true, USE_DEFAULT_STUN_SERVER=true, SERVER_PORT=5222, PROTOCOL_NAME=Google Talk, SERVER_ADDRESS=talk.google.com, AUTO_GENERATE_RESOURCE=false, PROTOCOL_ICON_PATH=resources/images/protocol/googletalk, USER_ID=laszlo.kertesz@gmail.com, ACCOUNT_UID=Google Talk:laszlo.kertesz@gmail.com@talk.google.com, ACCOUNT_ICON_PATH=resources/images/protocol/googletalk/logo32x32.png, ICE_ENABLED=true}
java.lang.NullPointerException
  at net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.loadIcon(JabberStatusEnum.java:286)
  at net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.loadIcon(JabberStatusEnum.java:266)
  at net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.<init>(JabberStatusEnum.java:175)
  at net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.getJabberStatusEnum(JabberStatusEnum.java:151)
  at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initialize(ProtocolProviderServiceJabberImpl.java:1120)
  at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderFactoryJabberImpl.createService(ProtocolProviderFactoryJabberImpl.java:122)
  at net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadAccount(ProtocolProviderFactory.java:772)
  at net.java.sip.communicator.service.protocol.AccountManager.doLoadStoredAccounts(AccountManager.java:187)
  at net.java.sip.communicator.service.protocol.AccountManager.loadStoredAccounts(AccountManager.java:337)
  at net.java.sip.communicator.service.protocol.AccountManager.runInLoadStoredAccountsThread(AccountManager.java:450)
  at net.java.sip.communicator.service.protocol.AccountManager.access$100(AccountManager.java:25)
  at net.java.sip.communicator.service.protocol.AccountManager$2.run(AccountManager.java:377)


#9

Hey,

Just found the solution :slight_smile:

in build.xml need to change line 48 from:

Ah! Didn't realize you were running from sources. "ant run-v4" would have
been equivalent then.

Sorry, forgot to mention... :frowning:

Still. This doesn't explain the connection on localhost. Did you have the
same hostname as your server's in /etc/hosts?

My XCAP URL is https://xcap.local/xcap-root

/etc/resolv.conf points to internal DNS server which has A record
xcap.local resolving to v4 host 10.10.10.22, however there is no AAAA
record which would resolve to v6 address. Therefore Jitsi (Java) gets
confused somehow and tries to send to 127.0.0.1 ?? Odd...

···

On 22 June 2011 21:24, Emil Ivov <emcho@jitsi.org> wrote:

On Wed, Jun 22, 2011 at 10:19 PM, Chris Maciejewski <chris@wima.co.uk> > wrote:


#10

Oops! This seems to be due to the newly added "On the phone" status. We'll
fix it first thing tomorrow.

Thanks for the report Kertesz!
Emil

···

On Wed, Jun 22, 2011 at 10:16 PM, Kertesz Laszlo <laszlo.kertesz@gmail.com>wrote:

Hello,

In this build (3558, Debian Linux) i lost my google account - it just
dissapeared from the account list. And cannot configure any google talk
accounts anymore neither using jabber neither the google talk account
creator. Whenever i press the finish button nothing happens except the error
below.
Other jabber server works.
The 3554 version has no such issues.

Please look into this.

Error message:

$ jitsi
warning: The VAD has been replaced by a hack pending a complete rewrite
23:01:21.892 SEVERE: service.protocol.**AccountManager.**doLoadStoredAccounts().196
Failed to load account {JINGLE_NODES_ENABLED=true, AUTO_DISCOVER_STUN=true,
RESOURCE=home-desktop, RESOURCE_PRIORITY=7, ENCRYPTED_PASSWORD=**TMe8pYP1o6IP8KQPPeJMTg==,
IS_SERVER_OVERRIDDEN=true, SEND_KEEP_ALIVE=true, AUTO_DISCOVER_JINGLE_NODES=
**true, IS_PREFERRED_PROTOCOL=false, GOOGLE_CONTACTS_ENABLED=true,
GMAIL_NOTIFICATIONS_ENABLED=**false, UPNP_ENABLED=true,
USE_DEFAULT_STUN_SERVER=true, SERVER_PORT=5222, PROTOCOL_NAME=Google Talk,
SERVER_ADDRESS=talk.google.com**, AUTO_GENERATE_RESOURCE=false,
PROTOCOL_ICON_PATH=resources/**images/protocol/googletalk, USER_ID=
laszlo.kertesz@gmail.**com <laszlo.kertesz@gmail.com>, ACCOUNT_UID=Google
Talk:laszlo.kertesz@gmail.com@**talk.google.com <http://talk.google.com>,
ACCOUNT_ICON_PATH=resources/**images/protocol/googletalk/**logo32x32.png,
ICE_ENABLED=true}
java.lang.NullPointerException
       at net.java.sip.communicator.**service.protocol.**jabberconstants.*
*JabberStatusEnum.loadIcon(**JabberStatusEnum.java:286)
       at net.java.sip.communicator.**service.protocol.**jabberconstants.*
*JabberStatusEnum.loadIcon(**JabberStatusEnum.java:266)
       at net.java.sip.communicator.**service.protocol.**jabberconstants.*
*JabberStatusEnum.<init>(**JabberStatusEnum.java:175)
       at net.java.sip.communicator.**service.protocol.**jabberconstants.*
*JabberStatusEnum.**getJabberStatusEnum(**JabberStatusEnum.java:151)
       at net.java.sip.communicator.**impl.protocol.jabber.**
ProtocolProviderServiceJabberI**mpl.initialize(**
ProtocolProviderServiceJabberI**mpl.java:1120)
       at net.java.sip.communicator.**impl.protocol.jabber.**
ProtocolProviderFactoryJabberI**mpl.createService(**
ProtocolProviderFactoryJabberI**mpl.java:122)
       at net.java.sip.communicator.**service.protocol.**
ProtocolProviderFactory.**loadAccount(**ProtocolProviderFactory.java:**
772)
       at net.java.sip.communicator.**service.protocol.**AccountManager.**
doLoadStoredAccounts(**AccountManager.java:187)
       at net.java.sip.communicator.**service.protocol.**AccountManager.**
loadStoredAccounts(**AccountManager.java:337)
       at net.java.sip.communicator.**service.protocol.**AccountManager.**
runInLoadStoredAccountsThread(**AccountManager.java:450)
       at net.java.sip.communicator.**service.protocol.**
AccountManager.access$100(**AccountManager.java:25)
       at net.java.sip.communicator.**service.protocol.**
AccountManager$2.run(**AccountManager.java:377)

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#11

If it tried to connect on ::1 then someone replied to the AAAA query and
returned ::1. Otherwise it should have fallen back to the A record. Did you
check for en explanation in /etc/hosts? A look at the DNS messages that you
exchange with the server may also help. (Provided you still want to know of
course, given that it all seems to work now).

Emil

···

On Wed, Jun 22, 2011 at 10:30 PM, Chris Maciejewski <chris@wima.co.uk>wrote:

On 22 June 2011 21:24, Emil Ivov <emcho@jitsi.org> wrote:
> On Wed, Jun 22, 2011 at 10:19 PM, Chris Maciejewski <chris@wima.co.uk> > > wrote:
>>
>> Hey,
>>
>> Just found the solution :slight_smile:
>>
>> in build.xml need to change line 48 from:
>
> Ah! Didn't realize you were running from sources. "ant run-v4" would have
> been equivalent then.

Sorry, forgot to mention... :frowning:

>
> Still. This doesn't explain the connection on localhost. Did you have the
> same hostname as your server's in /etc/hosts?
>

My XCAP URL is https://xcap.local/xcap-root

/etc/resolv.conf points to internal DNS server which has A record
xcap.local resolving to v4 host 10.10.10.22, however there is no AAAA
record which would resolve to v6 address. Therefore Jitsi (Java) gets
confused somehow and tries to send to 127.0.0.1 ?? Odd...


#12

Hello,

similarly to what Kertesz wrote about the google account, I experience problems with the facebook account. After upgrading on Ubuntu 11.04 to 3558, the Facebook account was gone. It simply dissapeared from the contacts and disappeared from the account. If I want to add it again as account, Jitis tells me that the user already exists in the network. It is not possible to add the account again.

Is this the same reason why facebook does not work anymore?

Thanks,
Gerry

···

Am 22.06.2011 22:21, schrieb Emil Ivov:

Oops! This seems to be due to the newly added "On the phone" status. We'll fix it first thing tomorrow.

Thanks for the report Kertesz!
Emil

On Wed, Jun 22, 2011 at 10:16 PM, Kertesz Laszlo > <laszlo.kertesz@gmail.com <mailto:laszlo.kertesz@gmail.com>> wrote:

    Hello,

    In this build (3558, Debian Linux) i lost my google account - it
    just dissapeared from the account list. And cannot configure any
    google talk accounts anymore neither using jabber neither the
    google talk account creator. Whenever i press the finish button
    nothing happens except the error below.
    Other jabber server works.
    The 3554 version has no such issues.

    Please look into this.

    Error message:

    $ jitsi
    warning: The VAD has been replaced by a hack pending a complete
    rewrite
    23:01:21.892 SEVERE:
    service.protocol.AccountManager.doLoadStoredAccounts().196 Failed
    to load account {JINGLE_NODES_ENABLED=true,
    AUTO_DISCOVER_STUN=true, RESOURCE=home-desktop,
    RESOURCE_PRIORITY=7, ENCRYPTED_PASSWORD=TMe8pYP1o6IP8KQPPeJMTg==,
    IS_SERVER_OVERRIDDEN=true, SEND_KEEP_ALIVE=true,
    AUTO_DISCOVER_JINGLE_NODES=true, IS_PREFERRED_PROTOCOL=false,
    GOOGLE_CONTACTS_ENABLED=true, GMAIL_NOTIFICATIONS_ENABLED=false,
    UPNP_ENABLED=true, USE_DEFAULT_STUN_SERVER=true, SERVER_PORT=5222,
    PROTOCOL_NAME=Google Talk, SERVER_ADDRESS=talk.google.com
    <http://talk.google.com>, AUTO_GENERATE_RESOURCE=false,
    PROTOCOL_ICON_PATH=resources/images/protocol/googletalk,
    USER_ID=laszlo.kertesz@gmail.com
    <mailto:laszlo.kertesz@gmail.com>, ACCOUNT_UID=Google
    Talk:laszlo.kertesz@gmail.com
    <mailto:Talk%3Alaszlo.kertesz@gmail.com>@talk.google.com
    <http://talk.google.com>,
    ACCOUNT_ICON_PATH=resources/images/protocol/googletalk/logo32x32.png,
    ICE_ENABLED=true}
    java.lang.NullPointerException
           at
    net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.loadIcon(JabberStatusEnum.java:286)
           at
    net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.loadIcon(JabberStatusEnum.java:266)
           at
    net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.<init>(JabberStatusEnum.java:175)
           at
    net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.getJabberStatusEnum(JabberStatusEnum.java:151)
           at
    net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initialize(ProtocolProviderServiceJabberImpl.java:1120)
           at
    net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderFactoryJabberImpl.createService(ProtocolProviderFactoryJabberImpl.java:122)
           at
    net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadAccount(ProtocolProviderFactory.java:772)
           at
    net.java.sip.communicator.service.protocol.AccountManager.doLoadStoredAccounts(AccountManager.java:187)
           at
    net.java.sip.communicator.service.protocol.AccountManager.loadStoredAccounts(AccountManager.java:337)
           at
    net.java.sip.communicator.service.protocol.AccountManager.runInLoadStoredAccountsThread(AccountManager.java:450)
           at
    net.java.sip.communicator.service.protocol.AccountManager.access$100(AccountManager.java:25)
           at
    net.java.sip.communicator.service.protocol.AccountManager$2.run(AccountManager.java:377)

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org <mailto:emcho@jitsi.org> PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#13

Hi,

it was only 3558 with that problem, if you update to 3559 everything
will be back and normal. It was me broking things and thanks to Yana
providing so quickly the icons to fix it.

Regards
damencho

···

On Thu, Jun 23, 2011 at 9:41 AM, Gerry T. <gerry.treppel@googlemail.com> wrote:

Hello,

similarly to what Kertesz wrote about the google account, I experience
problems with the facebook account. After upgrading on Ubuntu 11.04 to 3558,
the Facebook account was gone. It simply dissapeared from the contacts and
disappeared from the account. If I want to add it again as account, Jitis
tells me that the user already exists in the network. It is not possible to
add the account again.

Is this the same reason why facebook does not work anymore?

Thanks,
Gerry

Am 22.06.2011 22:21, schrieb Emil Ivov:

Oops! This seems to be due to the newly added "On the phone" status. We'll
fix it first thing tomorrow.

Thanks for the report Kertesz!
Emil

On Wed, Jun 22, 2011 at 10:16 PM, Kertesz Laszlo <laszlo.kertesz@gmail.com> > wrote:

Hello,

In this build (3558, Debian Linux) i lost my google account - it just
dissapeared from the account list. And cannot configure any google talk
accounts anymore neither using jabber neither the google talk account
creator. Whenever i press the finish button nothing happens except the error
below.
Other jabber server works.
The 3554 version has no such issues.

Please look into this.

Error message:

$ jitsi
warning: The VAD has been replaced by a hack pending a complete rewrite
23:01:21.892 SEVERE:
service.protocol.AccountManager.doLoadStoredAccounts().196 Failed to load
account {JINGLE_NODES_ENABLED=true, AUTO_DISCOVER_STUN=true,
RESOURCE=home-desktop, RESOURCE_PRIORITY=7,
ENCRYPTED_PASSWORD=TMe8pYP1o6IP8KQPPeJMTg==, IS_SERVER_OVERRIDDEN=true,
SEND_KEEP_ALIVE=true, AUTO_DISCOVER_JINGLE_NODES=true,
IS_PREFERRED_PROTOCOL=false, GOOGLE_CONTACTS_ENABLED=true,
GMAIL_NOTIFICATIONS_ENABLED=false, UPNP_ENABLED=true,
USE_DEFAULT_STUN_SERVER=true, SERVER_PORT=5222, PROTOCOL_NAME=Google Talk,
SERVER_ADDRESS=talk.google.com, AUTO_GENERATE_RESOURCE=false,
PROTOCOL_ICON_PATH=resources/images/protocol/googletalk,
USER_ID=laszlo.kertesz@gmail.com, ACCOUNT_UID=Google
Talk:laszlo.kertesz@gmail.com@talk.google.com,
ACCOUNT_ICON_PATH=resources/images/protocol/googletalk/logo32x32.png,
ICE_ENABLED=true}
java.lang.NullPointerException
at
net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.loadIcon(JabberStatusEnum.java:286)
at
net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.loadIcon(JabberStatusEnum.java:266)
at
net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.<init>(JabberStatusEnum.java:175)
at
net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.getJabberStatusEnum(JabberStatusEnum.java:151)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initialize(ProtocolProviderServiceJabberImpl.java:1120)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderFactoryJabberImpl.createService(ProtocolProviderFactoryJabberImpl.java:122)
at
net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadAccount(ProtocolProviderFactory.java:772)
at
net.java.sip.communicator.service.protocol.AccountManager.doLoadStoredAccounts(AccountManager.java:187)
at
net.java.sip.communicator.service.protocol.AccountManager.loadStoredAccounts(AccountManager.java:337)
at
net.java.sip.communicator.service.protocol.AccountManager.runInLoadStoredAccountsThread(AccountManager.java:450)
at
net.java.sip.communicator.service.protocol.AccountManager.access$100(AccountManager.java:25)
at
net.java.sip.communicator.service.protocol.AccountManager$2.run(AccountManager.java:377)

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#14

Hello,

It works now with 3559. Both Google and Facebook.

···

On Thu, 23 Jun 2011 09:50:06 +0300, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

it was only 3558 with that problem, if you update to 3559 everything
will be back and normal. It was me broking things and thanks to Yana
providing so quickly the icons to fix it.

Regards
damencho

On Thu, Jun 23, 2011 at 9:41 AM, Gerry T. <gerry.treppel@googlemail.com> > wrote:

Hello,

similarly to what Kertesz wrote about the google account, I experience
problems with the facebook account. After upgrading on Ubuntu 11.04 to 3558,
the Facebook account was gone. It simply dissapeared from the contacts and
disappeared from the account. If I want to add it again as account, Jitis
tells me that the user already exists in the network. It is not possible to
add the account again.

Is this the same reason why facebook does not work anymore?

Thanks,
Gerry

Am 22.06.2011 22:21, schrieb Emil Ivov:

Oops! This seems to be due to the newly added "On the phone" status. We'll
fix it first thing tomorrow.

Thanks for the report Kertesz!
Emil

On Wed, Jun 22, 2011 at 10:16 PM, Kertesz Laszlo >> <laszlo.kertesz@gmail.com> >> wrote:

Hello,

In this build (3558, Debian Linux) i lost my google account - it just
dissapeared from the account list. And cannot configure any google talk
accounts anymore neither using jabber neither the google talk account
creator. Whenever i press the finish button nothing happens except the error
below.
Other jabber server works.
The 3554 version has no such issues.

Please look into this.

Error message:

$ jitsi
warning: The VAD has been replaced by a hack pending a complete rewrite
23:01:21.892 SEVERE:
service.protocol.AccountManager.doLoadStoredAccounts().196 Failed to load
account {JINGLE_NODES_ENABLED=true, AUTO_DISCOVER_STUN=true,
RESOURCE=home-desktop, RESOURCE_PRIORITY=7,
ENCRYPTED_PASSWORD=TMe8pYP1o6IP8KQPPeJMTg==, IS_SERVER_OVERRIDDEN=true,
SEND_KEEP_ALIVE=true, AUTO_DISCOVER_JINGLE_NODES=true,
IS_PREFERRED_PROTOCOL=false, GOOGLE_CONTACTS_ENABLED=true,
GMAIL_NOTIFICATIONS_ENABLED=false, UPNP_ENABLED=true,
USE_DEFAULT_STUN_SERVER=true, SERVER_PORT=5222, PROTOCOL_NAME=Google Talk,
SERVER_ADDRESS=talk.google.com, AUTO_GENERATE_RESOURCE=false,
PROTOCOL_ICON_PATH=resources/images/protocol/googletalk,
USER_ID=laszlo.kertesz@gmail.com, ACCOUNT_UID=Google
Talk:laszlo.kertesz@gmail.com@talk.google.com,
ACCOUNT_ICON_PATH=resources/images/protocol/googletalk/logo32x32.png,
ICE_ENABLED=true}
java.lang.NullPointerException
       at
net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.loadIcon(JabberStatusEnum.java:286)
       at
net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.loadIcon(JabberStatusEnum.java:266)
       at
net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.<init>(JabberStatusEnum.java:175)
       at
net.java.sip.communicator.service.protocol.jabberconstants.JabberStatusEnum.getJabberStatusEnum(JabberStatusEnum.java:151)
       at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initialize(ProtocolProviderServiceJabberImpl.java:1120)
       at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderFactoryJabberImpl.createService(ProtocolProviderFactoryJabberImpl.java:122)
       at
net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadAccount(ProtocolProviderFactory.java:772)
       at
net.java.sip.communicator.service.protocol.AccountManager.doLoadStoredAccounts(AccountManager.java:187)
       at
net.java.sip.communicator.service.protocol.AccountManager.loadStoredAccounts(AccountManager.java:337)
       at
net.java.sip.communicator.service.protocol.AccountManager.runInLoadStoredAccountsThread(AccountManager.java:450)
       at
net.java.sip.communicator.service.protocol.AccountManager.access$100(AccountManager.java:25)
       at
net.java.sip.communicator.service.protocol.AccountManager$2.run(AccountManager.java:377)

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31

--
O zi buna,

Kertesz Laszlo

Using Opera's revolutionary email client: http://www.opera.com/mail/