I have an off-list talk with Emil, and we decided to take advantage of Google's relay services (TURN, ...) so to choose by default Google's Jingle/ICE if one peer supports it (and if the option is checked in configuration of course).
The changes is commited in SVN revision 8789, and next build (3585) will have it.
Le 21/07/11 09:27, Sebastien Vincent a écrit :
Le 21/07/11 09:17, Kertesz Laszlo a écrit :
And if the rest of the ICE options are enabled too, will be a problem or Jitsi autodetects the used protocol?
If the peer only supports Google capabilities (voice-v1, camera-v1, video-v1), it will used the Google variant.
For the moment, for a multiple logged account that have XMPP Jingle and Google caps (i.e. on Jitsi and on Gmail web client/Android phone) it will choose Jingle ones. We may change this in the future and choose either Google variant or XMPP Jingle by priorities or other things.
On Thu, 21 Jul 2011 08:47:09 +0300, Sebastien Vincent <email@example.com> >> wrote:
Yes it is supported but it needs to be explicitely enabled in your account configuration -> ICE configuration tab -> check Use Google's Jingle/ICE (experimental).
Please note that it is still experimental at this time and we need to test a little bit more to make it enabled by default.
Le 20/07/11 22:07, Kertesz Laszlo a écrit :
The changelog states:
* Adds support for RTP over TCP and Google Talk's TCP/TURN-TCP/TURN-SSLTCP candidates.
Does this mean that the Google variant of the jabber protocol is fully supported or it is work in progress?