[Standards-JIG] FW: Jingle - P2P and PBX calls

Simon Guindon simon.guindon at tomahawk.ca
Tue Jan 3 17:05:25 UTC 2006

Ok thanks for the clarification. I think I am understanding much better

So here are my questions then. Since a Jingle Audio client can gateway
to SIP or IAX. What is the best route to add PBX capabilities or is this
the right spot to do so.

As far as I understand Jingle Audio is RTP. So how does one do things
such as call forwarding, voicemail etc.

I don't know SIP very well but IAX can do all these things when logged
into an Asterisk box. This means the IAX client must authenticate with

Does this mean a Jingle Audio -> IAX gateway needs to exist. And that
this such gateway needs to support iq:register (off the top of my head,
might be wrong) so clients can enter their IAX login information?

If so, can we send tones? IAX I believe uses tones to handle navigating
voicemail etc.

The alternative is making IAX a session type and the jabber client
itself supporting IAX thus being able to do this all itself. This has
been my route so far in my developments as I began before I was aware of

I have an asterisk.server.com component which supports custom IQ queries
for certain things such as extension lookups, finding out what MY
extension is, etc. I would like to discuss making these things more
standard so all clients can benefit.

I think such things will make Jabber and SIP/IAX/Asterisk/others a very
strong distributed VOIP network.

Thanks and take care,

Simon Guindon
Tomahawk Technologies Inc.
simon.guindon at tomahawk.ca

-----Original Message-----
From: standards-jig-bounces at jabber.org
[mailto:standards-jig-bounces at jabber.org] On Behalf Of Hal Rottenberg
Sent: Tuesday, December 27, 2005 9:53 PM
To: Jabber protocol discussion list
Subject: Re: [Standards-JIG] FW: Jingle - P2P and PBX calls

On 12/27/05, Simon <simon at nureality.ca> wrote:
> Is this correct? So Jingle is now flexible so the client can support
> different formats either through gateways or through actual client
> supporting that session type?

Yup.  Jingle *signalling* may support different formats.  But I
wouldn't necessarily lump gateways in the same sentence there. 
Gateways will appear to a Jingle endpoint as a Jingle-supported
format.  i.e.just like when I use an AIM transport to send a message
to an AIM user, I don't have to use the AIM program or protocol, and I
don't even have to know what AIM is.  If I'm Jingle Audio and call
through a gateway to a SIP endpoint, does my client know how to talk
SIP?  The answer to that would be no.

That being said, I can't wait for the first open source SIP<->Jingle
gateway.  :)

Psi webmaster (http://psi-im.org)
im:hal at jabber.rocks.cc

More information about the Standards mailing list