[Telepathy] Jingle Empathy with Asterisk

[Philippe Sultan]

Robert, Senko,

[...]
> Unfortunately, there are two limitations in our implementation of Jingle
> in Gabble (the XMPP backend that Empathy uses) which means it's not very
> interoperable with other Jingle implementations at the moment.
> 
> 1) The namespaces/semantics we use are from Jingle at the start of 2007,
> and we've not made any changes since then to update either to the new
> namespaces in the XEPs, or some changes to the semantics which also took
> place. This means an implementation of current Jingle won't even find us
> to be callable.

Ok, I just updated Asterisk's code to match with the temporary 
namespaces defined in the various Jingle specs that we use :
#define JINGLE_NS "urn:xmpp:tmp:jingle"
#define JINGLE_AUDIO_RTP_NS "urn:xmpp:tmp:jingle:apps:audio-rtp"
#define JINGLE_VIDEO_RTP_NS "urn:xmpp:tmp:jingle:apps:video"
#define JINGLE_ICE_UDP_NS "urn:xmpp:tmp:jingle:transports:ice-udp"
#define JINGLE_DTMF_NS "urn:xmpp:tmp:jingle:dtmf"

> 2) The only transport we support signalling at the moment is the same as
> Google uses for Google Talk calls, called "gtalk-p2p" in various places
> inside libjingle. This means you need to do the same ICE-like in-line
> STUN requests/responses that you do when establishing a GTalk call. Our
> media stack can actually do raw UDP (which we use for SIP calls too),
> and soon will add support for IETF-compliant ICE, but we've not done the
> work in our XMPP Jingle implementation to signal these types of candidates.
> 
> Senko Rasic, CC'd, is working on improving both of these things in our
> Gabble XMPP backend, so you should be able to find out from him how he's
> getting on.

Both raw UDP and "gtalk-p2p" work with Asterisk, so we should be able to 
place calls over either transport method.

[...]
> I don't really recommend that you mangle your Jingle implementation so
> that you can speak to Gabble's Jingle as it is at the moment. It's not
> something that anyone else is ever likely to implement - we're the ones
> who need to catch up here. However, in this specific circumstance, the
[...]

Ok, I'll watch the changes in Gabble, and stay in touch with Senko for 
updates on the topic.

[...]
> I actually did take some time a few weeks ago to look over the code you
> had in trunk, and decided it wouldn't work yet for the reasons I
> observed above. One other thing I noticed though - I saw that you've
> hardcoded the content names (eg "asterisk-audio-content") into your code
> which sends candidates... that really won't work when we initiate a call
> and name our streams differently, you won't be able to send any
> candidates/etc to us...

Yep, I just fixed it.

Thanks for your valuable input and hard work on the Telepathy framework. 
I look forward to testing the new Jingle code.

Regards,

Philippe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4299 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freedesktop.org/archives/telepathy/attachments/20080528/eaba5542/attachment.bin