[Standards-JIG] Defining IAX transport over jingle
simon.guindon at tomahawk.ca
Wed Feb 22 16:08:35 UTC 2006
I would also like to be included in the IAX discussions. I think IAX
should be pretty easy to implement but at the same time a bit confusing.
I've thought about it quite a lot in the last while going through the
DTMF thread and I'm a bit confused as to how we are going to separate
IAX calling peers, and IAX calling Asterisk.
In a regular case where IAX is used in the same manner as Jingle Audio
(p2p) maybe we need less data (codecs etc) but we need an IP the same as
Jingle Audio to connect to. But in the case of IAX using Asterisk,
everything is basically extensions. In this case the call gets routed
via Asterisk and not a Jingle gateway.
Perhaps just adding a <extension> tag to the Jingle stanza is enough but
I'm not sure.
Thanks and take care,
Tomahawk Technologies Inc.
simon.guindon at tomahawk.ca
From: standards-jig-bounces at jabber.org
[mailto:standards-jig-bounces at jabber.org] On Behalf Of Peter Saint-Andre
Sent: Tuesday, February 21, 2006 10:35 PM
To: Jabber protocol discussion list
Subject: Re: [Standards-JIG] Defining IAX transport over jingle
-----BEGIN PGP SIGNED MESSAGE-----
Yes, this is interesting -- I was talking with someone else today who
suggested that it would be pretty easy to define an IAX transport method
for Jingle. One of the big reasons we split the "how" (transports) out
of JEP-0166 was to make this kind of thing possible.
Hopefully I'll have time to work on an IAX transport method after I get
JEP-0176 (the "ICE" method) out the door.
(I replied to Antonio at greater length off-list before I realized he
had also posted to the list, I'll try to dig that out here...)
Antonio Cano damas wrote:
> I'm working for the audio/video component into the Coccinella client.
> At first this started like a simple phone for Asterisk
> using IAX wich results really simple, lightweight and goes nice.
> After see that iax can support P2P calls, We decided to take a step
> forward and then was when comes the first version of jingle,
> We started to think how to make IAX and jingle mixed but this was
> a little difficult under our point of view (Signalling and Media goes
> but appear the 0.2 version and now we have a new approach that
> could fit fine for the mix with a transport.
> My problem is that I'm really new to all this XMMP world and some
> concepts aren't really clear.
> I understand that for defining the How (transport) for IAX, we need at
> Version: IAX or IAX2
> Public ip, could be discover using a simple call to STUN.
> Port, returned by IAX lib.
> Secure flag, by now the protocol doesn't implement TSL or any
> encrypt method for media but they are working on this.
> With this info the client can make a direct call to his friend who has
> to implements the IAX stack too.
> I don't think that the media is needed, because once the peers know
> how to be in contact, the iax protocol stack make this for us.
> Following this thoughts and after some reading of the jingle specs I
> could say that transport has to be in this way:
> <description xmlns='http:/jabber/protocol/jingle/transport/iax'>
> Is that correct? Someone told me that this is for registry definition,
> How I have to define transport for jingle?
> Other doubt I've got is related to extended presence. You define into
> Jingle-audio, but I understand that this is common stuff
> for all transports and has to be into jingle 0166, because What happen
> if I don't implement the audio spec or
> if I need a future video instead of audio?
> And one more doubt related to presence, You defined like an IQ and
> this messages are sended when someone ask for they.
> They have to be defined like message or presence extension, haven't
> Please keep in mind that I'm new to all this, I've got a lot of
> unclear ideas and I'm not able to defend if iax is
> better than jingle-audio or sip signallings.
> Thanks for all.
> Take care,
> Antonio F. Cano
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Standards