[jitsi-dev] Jingle compatibility.


#1

Hi all. I'm testing compatibility of voice calls between different
Jabber clients. I noticed that Jitsi have a lot of compatibility
problems, so I decided to post my results here.

Jitsi version 1.0-beta1-nightly.build.3565 (01-Jul-2011) on WinXP was
used. Other clients was run on a computer with ArchLinux. There were
no NATs or firewalls, direct connections were possible.

Calling from Jitsi to Psi+ (ver. 0.15.4113) was impossible, there was
no "Call" button near a contact. Jitsi thought that Psi+ doesn't
supports voice calls.

Call from Psi+ to Jitsi wasn't successful too. Jitsi showed a call
window and wrote "Connected" in it, but Psi+ was showing only
"Calling..." for more than a minute, I manually stopped a call. There
were no sound from both sides.

Calling from Jitsi to Gajim (0.14.3) worked once, but generally
Jitsi doesn't show a "Call" button in this case.

Call from Gajim to Jitsi wasn't impossible - Jitsi immediately dropped a
call.

Call from Pidgin (2.9.0) to Jitsi wasn't successful - they tried to make
a connection for some time, but couldn't.

Call from Jitsi to Pidgin was successful, but I could hear a voice only
at a Pidgin side, Jitsi played nothing.

Call from Google Talk (browser module ver. 2.1.6.0) to Jitsi and vice
versa wasn't possible, calling button was inactive in both cases.

If problem was caused by another client, not a Jitsi, tell me about it.
Thank for you attention!


#2

Hi Artyom,

Last december, I also tested other OSS with Jingle support and I gather the same results.

I investigate a little bit at the time and that's what I found:
- For Gajim to Jitsi call, Gajim did not support "ringing" stanza and send an error IQ (that's why Jitsi closes the call).

- For Pidgin, I don't know if they update their Jingle/ICE support recently but I think it is not compatible with the latest Jingle/ICE specifications. Somebody on the list mentionned that if you disable ICE (in Jitsi's account configuration) Jitsi could establish successfully calls to Pidgin.

FYI, empathy works perfectly with Jitsi.

Regards,

···

--
Seb

Le 03/07/11 22:03, Artyom Aleksuk a �crit :

Hi all. I'm testing compatibility of voice calls between different
Jabber clients. I noticed that Jitsi have a lot of compatibility
problems, so I decided to post my results here.

Jitsi version 1.0-beta1-nightly.build.3565 (01-Jul-2011) on WinXP was
used. Other clients was run on a computer with ArchLinux. There were
no NATs or firewalls, direct connections were possible.

Calling from Jitsi to Psi+ (ver. 0.15.4113) was impossible, there was
no "Call" button near a contact. Jitsi thought that Psi+ doesn't
supports voice calls.

Call from Psi+ to Jitsi wasn't successful too. Jitsi showed a call
window and wrote "Connected" in it, but Psi+ was showing only
"Calling..." for more than a minute, I manually stopped a call. There
were no sound from both sides.

Calling from Jitsi to Gajim (0.14.3) worked once, but generally
Jitsi doesn't show a "Call" button in this case.

Call from Gajim to Jitsi wasn't impossible - Jitsi immediately dropped a
call.

Call from Pidgin (2.9.0) to Jitsi wasn't successful - they tried to make
a connection for some time, but couldn't.

Call from Jitsi to Pidgin was successful, but I could hear a voice only
at a Pidgin side, Jitsi played nothing.

Call from Google Talk (browser module ver. 2.1.6.0) to Jitsi and vice
versa wasn't possible, calling button was inactive in both cases.

If problem was caused by another client, not a Jitsi, tell me about it.
Thank for you attention!


#3

hi,everyone,
I want to know which design pattern did the sip operationset used? and there
are some operations extend the MethodProcessor,some do not, Can you explain
the reasons?
thanks in advance.

···

--
姜春雨
生活就是这样子
Beijing University of Posts and Telecommunications


#4

And one small question. How Jitsi detects that client supports Jingle?

···

Hi Artyom,

Last december, I also tested other OSS with Jingle support and I
gather the same results.

I investigate a little bit at the time and that's what I found:
- For Gajim to Jitsi call, Gajim did not support "ringing" stanza and
send an error IQ (that's why Jitsi closes the call).

- For Pidgin, I don't know if they update their Jingle/ICE support
recently but I think it is not compatible with the latest Jingle/ICE
specifications. Somebody on the list mentionned that if you disable
ICE (in Jitsi's account configuration) Jitsi could establish
successfully calls to Pidgin.

FYI, empathy works perfectly with Jitsi.

Regards,
--
Seb


#5

- For Pidgin, I don't know if they update their Jingle/ICE support
recently but I think it is not compatible with the latest Jingle/ICE
specifications. Somebody on the list mentionned that if you disable
ICE (in Jitsi's account configuration) Jitsi could establish
successfully calls to Pidgin.

Yes, if ICE is disabled, call is being successful, but with the same
problem - I could hear a voice only at a Pidgin side.

FYI, empathy works perfectly with Jitsi.

When calling from Jitsi to Empathy all works well. When calling from
Empathy to Jitsi I can hear a voice only at a Jitsi side.


#6

Hi,

Jitsi looks in discovery info for:
- urn:xmpp:jingle
- urn:xmpp:jingle:apps:rtp
- urn:xmpp:jingle:apps:rtp:audio (for audio call)
- urn:xmpp:jingle:apps:rtp:video (for video support)

If remote client does not have them, it will not show call button (and video call button).

···

--
Seb

Le 04/07/11 17:42, Artyom Aleksuk a �crit :

And one small question. How Jitsi detects that client supports Jingle?

Hi Artyom,

Last december, I also tested other OSS with Jingle support and I
gather the same results.

I investigate a little bit at the time and that's what I found:
- For Gajim to Jitsi call, Gajim did not support "ringing" stanza and
send an error IQ (that's why Jitsi closes the call).

- For Pidgin, I don't know if they update their Jingle/ICE support
recently but I think it is not compatible with the latest Jingle/ICE
specifications. Somebody on the list mentionned that if you disable
ICE (in Jitsi's account configuration) Jitsi could establish
successfully calls to Pidgin.

FYI, empathy works perfectly with Jitsi.

Regards,
--
Seb


#7

A couple of months ago Julius Schwartzenberg reported the Psi+ issue. I
remember looking at the traces back than and it seemed to me that all
the necessary urn-s were present in Psi's disco info. I didn't have the
time to see exactly what it was that we didn't like about them though.

We'd have to have a look.

Emil

На 04.07.11 17:47, Sebastien Vincent написа:

···

Hi,

Jitsi looks in discovery info for:
- urn:xmpp:jingle
- urn:xmpp:jingle:apps:rtp
- urn:xmpp:jingle:apps:rtp:audio (for audio call)
- urn:xmpp:jingle:apps:rtp:video (for video support)

If remote client does not have them, it will not show call button (and
video call button).

--
Seb

Le 04/07/11 17:42, Artyom Aleksuk a écrit :

And one small question. How Jitsi detects that client supports Jingle?

Hi Artyom,

Last december, I also tested other OSS with Jingle support and I
gather the same results.

I investigate a little bit at the time and that's what I found:
- For Gajim to Jitsi call, Gajim did not support "ringing" stanza and
send an error IQ (that's why Jitsi closes the call).

- For Pidgin, I don't know if they update their Jingle/ICE support
recently but I think it is not compatible with the latest Jingle/ICE
specifications. Somebody on the list mentionned that if you disable
ICE (in Jitsi's account configuration) Jitsi could establish
successfully calls to Pidgin.

FYI, empathy works perfectly with Jitsi.

Regards,
--
Seb


#8

Jitsi looks in discovery info for:
- urn:xmpp:jingle
- urn:xmpp:jingle:apps:rtp
- urn:xmpp:jingle:apps:rtp:audio (for audio call)
- urn:xmpp:jingle:apps:rtp:video (for video support)

Psi+ uses "urn:xmpp:jingle:1" and "urn:xmpp:jingle:apps:rtp:1". I
patched Psi+ to make it announce also "urn:xmpp:jingle"
"urn:xmpp:jingle:apps:rtp", but this didn't changed anything.


#9

Hello All,
   I have finished the arabic translation online. I hope to see the results soon.Regards

Amer

···

Date: Mon, 4 Jul 2011 22:06:35 +0400
From: h31mail@yandex.ru
To: dev@jitsi.java.net
Subject: [jitsi-dev] Re: Jingle compatibility.

> Jitsi looks in discovery info for:
> - urn:xmpp:jingle
> - urn:xmpp:jingle:apps:rtp
> - urn:xmpp:jingle:apps:rtp:audio (for audio call)
> - urn:xmpp:jingle:apps:rtp:video (for video support)

Psi+ uses "urn:xmpp:jingle:1" and "urn:xmpp:jingle:apps:rtp:1". I
patched Psi+ to make it announce also "urn:xmpp:jingle"
"urn:xmpp:jingle:apps:rtp", but this didn't changed anything.


#10

Hi,

Sorry I had a bad copy/paste, Jitsi announces "urn:xmpp:jingle:1" and "urn:xmpp:jingle:apps:rtp:1".

What about "urn:xmpp:jingle:apps:rtp:audio" ? is it announced by Psi+ ?

Regards,

···

--
Seb

Le 04/07/11 20:06, Артём Алексюк a écrit :

Jitsi looks in discovery info for:
- urn:xmpp:jingle
- urn:xmpp:jingle:apps:rtp
- urn:xmpp:jingle:apps:rtp:audio (for audio call)
- urn:xmpp:jingle:apps:rtp:video (for video support)

Psi+ uses "urn:xmpp:jingle:1" and "urn:xmpp:jingle:apps:rtp:1". I
patched Psi+ to make it announce also "urn:xmpp:jingle"
"urn:xmpp:jingle:apps:rtp", but this didn't changed anything.


#11

Hi Amer,

Your translations are now part of the latest build (3569)!

It's also ack-ed on our Team&Contributors page.

Thank you!
Yana

···

On Jul 5, 2011, at 12:51 AM, Amer C wrote:

Hello All,

   I have finished the arabic translation online. I hope to see the results soon.
Regards

Amer

> Date: Mon, 4 Jul 2011 22:06:35 +0400
> From: h31mail@yandex.ru
> To: dev@jitsi.java.net
> Subject: [jitsi-dev] Re: Jingle compatibility.
>
> > Jitsi looks in discovery info for:
> > - urn:xmpp:jingle
> > - urn:xmpp:jingle:apps:rtp
> > - urn:xmpp:jingle:apps:rtp:audio (for audio call)
> > - urn:xmpp:jingle:apps:rtp:video (for video support)
>
> Psi+ uses "urn:xmpp:jingle:1" and "urn:xmpp:jingle:apps:rtp:1". I
> patched Psi+ to make it announce also "urn:xmpp:jingle"
> "urn:xmpp:jingle:apps:rtp", but this didn't changed anything.


#12

What about "urn:xmpp:jingle:apps:rtp:audio" ? is it announced by
Psi+ ?

Yes.