[Standards-JIG] Defining IAX transport over jingle
simon.guindon at tomahawk.ca
Wed Feb 22 20:33:06 UTC 2006
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.
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").
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.
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
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 Mikael Magnusson
Sent: Wednesday, February 22, 2006 2:53 PM
To: Jabber protocol discussion list
Subject: Re: [Standards-JIG] Defining IAX transport over jingle
Antonio Cano damas wrote:
> Peter Saint-Andre wrote:
>>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
>>>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
>>server, two servers, etc.
> I thought this doesn't matter. A peer is client and server at the same
> time, we don't mind if is a phone, jabber client or asterisk pbx.
> I'll try to explain, let me use Asterisk terms, for calling using IAX
> we have the next URI: 'user:password at ip:port/extension'. Now we are
> going the two cases:
The libiax2 library supports dial strings using the following format:
It's only the peer that is needed to establish an IAX call, and the
other values except port number are sent in Information Elements (IE:s)
during call setup and authentication. The default (UDP) port is 4569.
0x01 CALLED NUMBER
0x05 CALLED CONTEXT
0x07 (plaintext) PASSWORD
0x10 MD5 result
0x11 RSA result
For more information:
> 1. Calling from pc 2 pc. In that case we don't need the user and
> password because is the other user who accept or reject the call, and
> that case don't mind wich extension to use... for example we could use
> the 's' that is default extension of asterisk. The URI is like this:
Why send an extension in a CALLED NUMBER IE at all? Is it really
More information about the Standards