-----Original Message----- From: users-bounces@lists.kamailio.org [mailto:users-bounces@lists.kamailio.org] On Behalf Of Iñaki Baz Castillo Sent: Wednesday, 07. October 2009 16:48 To: Juha Heinanen Cc: users@lists.kamailio.org Subject: Re: [Kamailio-Users] SIMPLE vs XMPP: The Resolution
2009/10/7 Juha Heinanen jh@tutpro.com:
yes and one pragmatic solution might be to add a xmmp server to the infrastructure so that user can use the same uri both as a
sip uri and
xmmp uri depending on client's capabilities.
noooooo!!!
SIP & XMPP integration is a hack!! It's just a dirty workaround, nothing else. It requires management and maintenance of two different protocols, two different QoS, two authentication mechanims... what about dialog subscriptions for call pickup and so? dialgo presence with SIP and user presence with XMPP? oh nooo please....
Hi Inaki You could include the presence of a SIP endpoint (your phone) as another resource into your XMPP state. If one of your SIP phones is in a call, the XMPP resource will be e.g. busy.
If you "set DND on the SIP phone", it could be easily mapped to a XMPP state, i.e. somehow trigger the resource to become busy as well.
I think also integration at this level is something worth to consider. Not "SIMPLE users interact with XMPP users" but to let each protocol do what its good at (chat through XMPP and call through SIP). I have not met too many SIMPLE users to chat with yet anyways :) The user could have a single URI and there would be no confusion.
Sebastian
Yes, it's true that until now the only feasible IM and presence solution is XMPP, but we are in SIP side! and we must extend the usage of SIP for IM and presence (even if implementations are not mature yet...). We must help in the adoption of SIMPLE/XCAP under feasible specs (OMA?). If we insist on using XMPP then we are not helping at all :(
-- Iñaki Baz Castillo ibc@aliax.net