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

Jean-Louis Seguineau jean-louis.seguineau at laposte.net
Fri Jan 6 10:06:13 UTC 2006


As for JEP55 support, the XMPP does not have to store the data for the
profile. It needs to have access to it, which is slightly different. As a
very simple example in many cases profile data is held in some LDAP or DBMS
store. It is up to the server to gather this information and make it
available to the client using JEP55. The XMPP server acts as a proxy in this
case. Similarly, retrieving the information from a PBX directory is also
possible as long as the PBX exposes some sort of interfaces that the XMPP
server can query and then cache the results. It's a matter of
implementation, and in this case you may want to widen your selection of
servers outside Jabberd only.

The same applies to a gateway to the PBX (the Jingle-IAX gateway you
mentioned) Actually the XMPP server will expose the JIDs that can be
searched by JEP55 when queried through JEP30 disco. In this case the gateway
itself would have to implement the JEP55 support, but implementation wise it
is no different from having the server do it (I mean it would be the same
code, just a different service JID). Implementing the JEP55 support in the
gateway would be beneficial in your case as it would be independent of the
XMPP server (usually gateways/transports are connected as components on an
XMPP server).

Finally, if you can address "things which are not users, such as voicemail
or emergency services" through a JID you can reach them XMPP stanzas. Again
it is a matter of addressing by the gateway. In the case of a Jingle gateway
my bet is that it will implement something like phone-number at jingle.foo.bar
as an addressing scheme. 

In the end you'll have a system where any XMPP client supporting JEP55 (i.e
almost all of them) will allow to search for any phone or emergency service
number. Afterwards, it will all depend of the client capability: if it is
Jingle enabled, you may place a call directly, otherwise you would have to
use a black phone...

In short you see that you may not need DTMF extensions to Jingle to get the
result you expect ;)

Hope it helps


-----Original Message-----
Message: 2
Date: Thu, 5 Jan 2006 13:30:05 -0500
From: "Simon Guindon" <simon.guindon at tomahawk.ca>
Subject: RE: [Standards-JIG] FW: Jingle - P2P and PBX calls
To: "Jabber protocol discussion list" <standards-jig at jabber.org>
Message-ID: <3E6F9E04F4CF864DBCC3EECB90FDFB502904C6 at BART>
Content-Type: text/plain;	charset="us-ascii"


About JEP-55. This would require the XMPP server to specifically store
values that we require, which most would not I assume. Since it is the
server responding to the search and not the Jingle gateway.

For example if a IAX gateway speaks Jingle, so iax.server.com then the
IAX server is the one that knows what their phone # is, not XMPP server.

Would the proper method to be searching the main server or would it be
better to search using the same JEP but the destination JID be
iax.server.com instead of server.com?

When you say the server will communicate with the PBX to gather this
information. How does that work? Does that mean for example jabberd's
code has to be altered internally in addition of a gateway?

I think the ideal situation is if someone writes an IAX or Asterisk or
SIP gateway for Jingle, all you require is install it, and not
modifications to specific XMPP servers on top of that.

Or am I missing something?

Also about "411" or "yellow/white pages" service. What about things
which are not users, such as voicemail or emergency services etc?


More information about the Standards mailing list