[Standards-JIG] Defining IAX transport over jingle

Antonio F. Cano antonio at igestec.com
Wed Feb 22 23:11:09 UTC 2006

Hi Steve,

After take a little walk. I agree with you, is better to keep simple :)


-----Original Message-----
From: Steve Kann <stevek at stevek.com>
Date: Wed, 22 Feb 2006 17:34:09 
To:Jabber protocol discussion list <standards-jig at jabber.org>
Subject: Re: [Standards-JIG] Defining IAX transport over jingle

I've read over all of this, and I still don't understand why we'd want (or think we need) multiple "ways" to establish an IAX call via XMPP?
 Can't it be as simple as this (not in XML):
 Romeo->Juliet:  Hey, I'd like to talk to you, do you support Jingle-IAX?
 Juliet->Romeo: Sure! My IAX address is montague.com/juliet
 It would be juliet's responsibility to decide whether juliet wants to advertise the address of her client, or the address of a PBX that would forward to her client, or lie entirely and give Romeo the address of Joe's pizza shop.
 Juliet's client might have a UI like this:
 VoIP [IAX] Setup
 [X] accept peer-to-peer calls
 [ ] accept calls via server _____________ extension ________
 Register for calls via server ________ Username ______ Password _______
 So here, the first radio group decides whether she wants her client to accept calls directly, or direct calls to her through a PBX.
 The registration line would make her chat client also be a more traditional VoIP extension from a server.
 Simon Guindon wrote:   I see in my scenario an asterisk gateway mostly just being an information hub. Replying to DISCO/Jingle queries but then the IAX client just simply calls the extension. When I wish to call you how do I distinguish which 2 of the IAX methods you support? I believe in the Jingle Signaling JEP has a feature section is that correct? Maybe we need 2 features for IAX/SIP being IP to IP or through a PBX. I think I'm a bit in the same boat as you. I know what I need out of this but confused which solution is best and most clean. The way I see it is, there might be multiple gateways on 1 server for Asterisk. One might be a chan_jingleaudio which connects Jingle Audio capable clients Asterisk. Another would be an Asterisk gateway that doesn't do Jingle Audio but supports DISCO queries for asking how do I contact Antonio. Like I said I know what I need but ensure at which route to take. You could DISCO the asterisk.server.com for Antonio's extension #, or do you query for his VCard to find it? Etc etc.. Many JEP's I think could be used but which is best? Thanks, Simon ------------------------------------------------------- Simon Guindon Tomahawk Technologies Inc. simon.guindon at tomahawk.ca www.tomahawk.ca ------------------------------------------------------- -----Original Message----- From: standards-jig-bounces at jabber.org [mailto:standards-jig-bounces at jabber.org] On Behalf Of Antonio Cano damas Sent: Wednesday, February 22, 2006 5:03 PM To: Jabber protocol discussion list Subject: Re: [Standards-JIG] Defining IAX transport over jingle Simon Guindon wrote:         I'm not sure if I'm misunderstanding your post or not but I think sending IAX call format (extension, maybe we need to include server/context as well?) is a very important thing. I don't believe         it's         a requirement though. As said previously there are 2 manners which IAX Jabber aware clients will want to call. 1. P2P 2. PBX In #1 we don't need to pass extension, context etc. But if we are a Telco running Asterisk maybe we want all the calls to go through the         PBX         and call records go into the CDR etc. In the sense Jabber is now just         an         easy way to call without having to dial. (IE just clicking on a roster item and clicking "call").          hmmmmm three points goes to Simon :) I'm not sure about this, maybe this has to be implemented by a chan_jingle_iax into the Asterisk. Maybe Asterisk (PBX) box could have his roster mapped with extensions, and connected to the Jabber server like a bot  :-/ Ohhhh I can see the scenario, sorry is really late and a long day. I promise to think slowly tomorrow morning with a cleaner mind ;)         Now that aside I think theres more integration that needs to happen for XMPP/VoIP to really take off. It may be outside of the Jingle spec though and more in the discovery or Vcard spec. I've been trying to think of ways Jingle/Disco or can discover many things automatically so the user doesn't have to enter phone numbers.  For example: When I click "Call Mikael at xmpp.com" how do we discover Mikael's extension. How do we discover his voicemail box to leave him a msg. How do we discover our own voicemail box so we can go there in 1 click? How do we discover tech support number so we can call via 1 button click. I guess the idea is the number system is there, but Jabber can have a much more seamless integration with the PBX so the user is just clicks away from everything he needs. This is all stuff later though, first we need to figure out how do we tie IAX into Jingle but allow IAX to do what IAX can do if that makes sense ;)          Yes you're right, maybe all this stuff is related to the entities implementation and not to the specification :-/ Thinking a little (only a little), not seems to be necesary to include the extension we want to call into the transport because this goes into the dial string of the IAX library. Take care,   
Antonio F. Cano
iGesTec Tecnología Digital - Grupo Ikusnet
antonio at igestec.com
953 892 970 - 667 697 521 - 2335
C/ Manuel Caballero nº 20, 2º
23600 Martos (Jaén)

More information about the Standards mailing list