[jitsi-dev] Android Interoperability


#1

Hello.

I haven't been following the project for a while, sorry. I've been
focusing on my new (first) job.

I'm glad to hear that Jitsi now supports the more widespread Google
variant of Jingle. (Although I still hope other clients start adopting
standard XSF Jingle.)

So in theory it should now be possible to make calls to one of the
'GTalk compatible' clients for Android. In practice though, it looks
like there's a little more work.

I've tried making a call to/from Crolix Communicator, Talkonaut, Vtok
and Nimbuzz. None of which I got to work. They all seemed to cause
different errors, suggesting that some or all of the clients have not
implemented the protocol correctly. ('call ended by remote', one
client hanging the while the other disconnected, ICE failure despite
both being on the same LAN, persistent calling but not ringing on the
other client, and some others...)

It would be very nice to get at least one of these clients working
with Jitsi, and make Jingle calls from Android. Could you check if
this is partly due to Jitsi's young Gingle implementation? (If you
have Android that is, otherwise I'll collect info for you when I can.)

Thank you to all contributors for the progress!
James.


#2

Hi James,

Do you use nightly builds or stable ones because we add support to vtok
(both in 3G and WiFi) recently. For other programs we will need logs to
investigate.

Regards,

···

----
Seb

Le lundi 31 octobre 2011, James Haigh <james.r.haigh@gmail.com> a écrit :

Hello.

I haven't been following the project for a while, sorry. I've been
focusing on my new (first) job.

I'm glad to hear that Jitsi now supports the more widespread Google
variant of Jingle. (Although I still hope other clients start adopting
standard XSF Jingle.)

So in theory it should now be possible to make calls to one of the
'GTalk compatible' clients for Android. In practice though, it looks
like there's a little more work.

I've tried making a call to/from Crolix Communicator, Talkonaut, Vtok
and Nimbuzz. None of which I got to work. They all seemed to cause
different errors, suggesting that some or all of the clients have not
implemented the protocol correctly. ('call ended by remote', one
client hanging the while the other disconnected, ICE failure despite
both being on the same LAN, persistent calling but not ringing on the
other client, and some others...)

It would be very nice to get at least one of these clients working
with Jitsi, and make Jingle calls from Android. Could you check if
this is partly due to Jitsi's young Gingle implementation? (If you
have Android that is, otherwise I'll collect info for you when I can.)

Thank you to all contributors for the progress!
James.


#3

Forgot to mention, tested on:
Ubuntu 11.04 i386
Jitsi 3689

Hi James,

Do you use nightly builds or stable ones because we add support to vtok
(both in 3G and WiFi) recently. For other programs we will need logs to
investigate.

I didn't realise there's now stable as well.

So 3689 is the latest stable, and 3756 is the latest nightly
(according to jitsi.org). I still have:
deb http://download.jitsi.org/deb unstable/
which I've had since the rename to Jitsi. My repos can't seem to see
the nightlies.

It seems that what was the nightly repo has become the new 'stable'
repo. So where is the /new/ nightly repo?

"we add support to vtok"

Are you developing Vtok? Or do you mean 'for Vtok'?

Thank you.
James.

···

On 31/10/2011, Sebastien Vincent <seb@jitsi.org> wrote:

Regards,
----
Seb

Le lundi 31 octobre 2011, James Haigh <james.r.haigh@gmail.com> a écrit :

Hello.

I haven't been following the project for a while, sorry. I've been
focusing on my new (first) job.

I'm glad to hear that Jitsi now supports the more widespread Google
variant of Jingle. (Although I still hope other clients start adopting
standard XSF Jingle.)

So in theory it should now be possible to make calls to one of the
'GTalk compatible' clients for Android. In practice though, it looks
like there's a little more work.

I've tried making a call to/from Crolix Communicator, Talkonaut, Vtok
and Nimbuzz. None of which I got to work. They all seemed to cause
different errors, suggesting that some or all of the clients have not
implemented the protocol correctly. ('call ended by remote', one
client hanging the while the other disconnected, ICE failure despite
both being on the same LAN, persistent calling but not ringing on the
other client, and some others...)

It would be very nice to get at least one of these clients working
with Jitsi, and make Jingle calls from Android. Could you check if
this is partly due to Jitsi's young Gingle implementation? (If you
have Android that is, otherwise I'll collect info for you when I can.)

Thank you to all contributors for the progress!
James.


#4

Hi James,

Forgot to mention, tested on:
Ubuntu 11.04 i386
Jitsi 3689

Hi James,

Do you use nightly builds or stable ones because we add support to vtok
(both in 3G and WiFi) recently. For other programs we will need logs to
investigate.

I didn't realise there's now stable as well.

So 3689 is the latest stable, and 3756 is the latest nightly
(according to jitsi.org). I still have:
deb http://download.jitsi.org/deb unstable/
which I've had since the rename to Jitsi. My repos can't seem to see
the nightlies.

It seems that what was the nightly repo has become the new 'stable'
repo. So where is the /new/ nightly repo?

For nightly deb, change your existing "deb ..." line by "deb http://download.jitsi.org/nightly/deb unstable/".
You can also remove the existing jitsi package and download/install a nightly ones (at http://download.jitsi.org/jitsi/nightly/debian/).

"we add support to vtok"

Are you developing Vtok? Or do you mean 'for Vtok'?

Sorry, I mean "for Vtok".

Regards,

···

Le 01/11/11 22:42, James Haigh a écrit :

On 31/10/2011, Sebastien Vincent<seb@jitsi.org> wrote:

--
Seb

Thank you.
James.

Regards,
----
Seb

Le lundi 31 octobre 2011, James Haigh<james.r.haigh@gmail.com> a écrit :

Hello.

I haven't been following the project for a while, sorry. I've been
focusing on my new (first) job.

I'm glad to hear that Jitsi now supports the more widespread Google
variant of Jingle. (Although I still hope other clients start adopting
standard XSF Jingle.)

So in theory it should now be possible to make calls to one of the
'GTalk compatible' clients for Android. In practice though, it looks
like there's a little more work.

I've tried making a call to/from Crolix Communicator, Talkonaut, Vtok
and Nimbuzz. None of which I got to work. They all seemed to cause
different errors, suggesting that some or all of the clients have not
implemented the protocol correctly. ('call ended by remote', one
client hanging the while the other disconnected, ICE failure despite
both being on the same LAN, persistent calling but not ringing on the
other client, and some others...)

It would be very nice to get at least one of these clients working
with Jitsi, and make Jingle calls from Android. Could you check if
this is partly due to Jitsi's young Gingle implementation? (If you
have Android that is, otherwise I'll collect info for you when I can.)

Thank you to all contributors for the progress!
James.


#5

Thank you.

I can confirm that on Ubuntu 11.04 i386, Jitsi 3758, Vtok calls are
mostly successful although quite choppy at times.

Even video from laptop to phone works on minimum resolution. In fact
video works very well and is very responsive at about 100ms of latency
over WiFi which is better than the audio at about a second of latency
over WiFi.

I notice that Vtok only seems to support the PCMU/8000 encoding.

Phone to laptop doesn't work because I don't have Android 2.3 and Vtok
doesn't specifically support the front-cam on my Optimus 3D with
2.2.2. Clearly not Jitsi's problem, so I've contacted Vtok. :wink:

I can also confirm that Crolix Communicator, Talkonaut and Nimbuzz can
not have calls with Jitsi. Not that I care, I only need 1 to work, but
just letting you know.

Thanks again for getting Jitsi to work with Vtok, allowing me to make
calls to/from Android. :slight_smile:

...

For nightly deb, change your existing "deb ..." line by "deb
http://download.jitsi.org/nightly/deb unstable/".

I did browse around a bit, but http://download.jitsi.org/ (parent dir
of http://download.jitsi.org/deb/) redirects to
http://jitsi.org/index.php/Main/Download so I could not see 'nightly'.

You can also remove the existing jitsi package and download/install a
nightly ones (at http://download.jitsi.org/jitsi/nightly/debian/).

So are the packages slightly different depending on whether they are
in /nightly/deb or /deb, or are they bit-for-bit identical. How does a
package know which repo to add?

For example, jitsi_1.0-beta1-nightly.build.3689_i386.deb must have
once been in /nightly/deb. If I installed it from /nightly/deb or /deb
how would it know whether to add 'deb
http://download.jitsi.org/nightly/deb unstable/' or 'deb
http://download.jitsi.org/deb unstable/' to my repos?

/etc/apt/sources.list.d/jitsi.list:
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb http://download.jitsi.org/deb unstable/

So what is this automatically configured /by/? Jitsi? And so what is
the persistent way of changing this?

Thanks,
James.

···

On 02/11/2011, Sebastien Vincent <seb@jitsi.org> wrote:


#6

Hi James,

Thank you for feedback.

I will try Crolix, Talkonaut and Nimbuzz in the following weeks but if you have full logs (log + pcap traces) of failed calls with these applications, maybe you can send them to us so that I can see if the problem is like Vtok ones (Vtok seems to failed the call if it receive IPv6 addresses in ICE candidates).

Regards,

···

--
Seb

Le 06/11/11 15:35, James Haigh a écrit :

Thank you.

I can confirm that on Ubuntu 11.04 i386, Jitsi 3758, Vtok calls are
mostly successful although quite choppy at times.

Even video from laptop to phone works on minimum resolution. In fact
video works very well and is very responsive at about 100ms of latency
over WiFi which is better than the audio at about a second of latency
over WiFi.

I notice that Vtok only seems to support the PCMU/8000 encoding.

Phone to laptop doesn't work because I don't have Android 2.3 and Vtok
doesn't specifically support the front-cam on my Optimus 3D with
2.2.2. Clearly not Jitsi's problem, so I've contacted Vtok. :wink:

I can also confirm that Crolix Communicator, Talkonaut and Nimbuzz can
not have calls with Jitsi. Not that I care, I only need 1 to work, but
just letting you know.

Thanks again for getting Jitsi to work with Vtok, allowing me to make
calls to/from Android. :slight_smile:

On 02/11/2011, Sebastien Vincent<seb@jitsi.org> wrote:
...

For nightly deb, change your existing "deb ..." line by "deb
http://download.jitsi.org/nightly/deb unstable/".

I did browse around a bit, but http://download.jitsi.org/ (parent dir
of http://download.jitsi.org/deb/) redirects to
http://jitsi.org/index.php/Main/Download so I could not see 'nightly'.

You can also remove the existing jitsi package and download/install a
nightly ones (at http://download.jitsi.org/jitsi/nightly/debian/).

So are the packages slightly different depending on whether they are
in /nightly/deb or /deb, or are they bit-for-bit identical. How does a
package know which repo to add?

For example, jitsi_1.0-beta1-nightly.build.3689_i386.deb must have
once been in /nightly/deb. If I installed it from /nightly/deb or /deb
how would it know whether to add 'deb
http://download.jitsi.org/nightly/deb unstable/' or 'deb
http://download.jitsi.org/deb unstable/' to my repos?

/etc/apt/sources.list.d/jitsi.list:
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb http://download.jitsi.org/deb unstable/

So what is this automatically configured /by/? Jitsi? And so what is
the persistent way of changing this?

Thanks,
James.


#7

Hi,

Thank you.

I can confirm that on Ubuntu 11.04 i386, Jitsi 3758, Vtok calls are
mostly successful although quite choppy at times.

Even video from laptop to phone works on minimum resolution. In fact
video works very well and is very responsive at about 100ms of latency
over WiFi which is better than the audio at about a second of latency
over WiFi.

I notice that Vtok only seems to support the PCMU/8000 encoding.

Phone to laptop doesn't work because I don't have Android 2.3 and Vtok
doesn't specifically support the front-cam on my Optimus 3D with
2.2.2. Clearly not Jitsi's problem, so I've contacted Vtok. :wink:

I can also confirm that Crolix Communicator, Talkonaut and Nimbuzz can
not have calls with Jitsi. Not that I care, I only need 1 to work, but
just letting you know.

Thanks again for getting Jitsi to work with Vtok, allowing me to make
calls to/from Android. :slight_smile:

...

For nightly deb, change your existing "deb ..." line by "deb
http://download.jitsi.org/nightly/deb unstable/".

I did browse around a bit, but http://download.jitsi.org/ (parent dir
of http://download.jitsi.org/deb/) redirects to
http://jitsi.org/index.php/Main/Download so I could not see 'nightly'.

You can also remove the existing jitsi package and download/install a
nightly ones (at http://download.jitsi.org/jitsi/nightly/debian/).

So are the packages slightly different depending on whether they are
in /nightly/deb or /deb, or are they bit-for-bit identical. How does a
package know which repo to add?

The packages are identical.

For example, jitsi_1.0-beta1-nightly.build.3689_i386.deb must have
once been in /nightly/deb. If I installed it from /nightly/deb or /deb
how would it know whether to add 'deb
http://download.jitsi.org/nightly/deb unstable/' or 'deb
http://download.jitsi.org/deb unstable/' to my repos?

/etc/apt/sources.list.d/jitsi.list:
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb http://download.jitsi.org/deb unstable/

So what is this automatically configured /by/? Jitsi? And so what is
the persistent way of changing this?

You have to change it by hand in this file or add the repository in
other file. As nightly builds are for developers or impatient users :slight_smile:
its not done automatically.

Regards
damencho

···

On Sun, Nov 6, 2011 at 4:35 PM, James Haigh <james.r.haigh@gmail.com> wrote:

On 02/11/2011, Sebastien Vincent <seb@jitsi.org> wrote: