[Standards-JIG] Defining IAX transport over jingle

Peter Saint-Andre stpeter at jabber.org
Wed Feb 22 16:17:18 UTC 2006

Hash: SHA1

Simon Guindon wrote:
> 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.

Does it matter? All Jingle says is "here is how to negotiate a session
with another party" -- the parties could be two clients, a client and a
server, two servers, etc.

> 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. 

So we might need p2p-iax and pbx-iax or whatever?

> Perhaps just adding a <extension> tag to the Jingle stanza is enough but
> I'm not sure.

I'm not familiar with the IAX protocol, so I need to read up on that...


Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060222/e9445fd3/attachment.bin>

More information about the Standards mailing list