<div class="gmail_extra">Let me ask you this<br><br>Just like Iñaki always says, I seem to notice that with most XCAP clients (all except for the ones AG Projects develops) they don't work perfectly with OpenXCAP.<br><br>
Examples<br><ul><li>I found a bug with Counterpath Bria and it doesn't work according to the RFC (<a href="http://opensips-open-sip-server.1449251.n2.nabble.com/OpenXCAP-user-authentication-format-td5794424.html">http://opensips-open-sip-server.1449251.n2.nabble.com/OpenXCAP-user-authentication-format-td5794424.html</a>). I told Counterpath about that almost 2 years ago and they keep telling me that the next release will fix it.</li>
<li>When a Jitsi client adds a buddy it adds a different xml format to OpenXCAP and things start to get weird and presence doesn't work when other users have a different xml schema (<a href="http://opensips-open-sip-server.1449251.n2.nabble.com/A-little-XCAP-schema-help-td7440425.html">http://opensips-open-sip-server.1449251.n2.nabble.com/A-little-XCAP-schema-help-td7440425.html</a>)</li>
</ul><p>Those are pretty much the only clients I know that support XCAP (besides Blink's Mac version. Zoiper supports XCAP Authorization but not Contact Storage).</p><p>So I guess it isn't possible to do what I asked with SIP and XMPP. Is there a possibility to have some kind of frontend to OpenXCAP that could act like OpenSIPS does and allow you to view the GETs and PUTs and edit them if need be? That way if the client doesn't follow the XCAP RFC 100% you can manipulate the GETs and PUTs. Just trying to think outside the box.</p>
<p><br></p><p><br></p><br><div class="gmail_quote">On Fri, Apr 27, 2012 at 4:18 AM, Saúl Ibarra Corretgé <span dir="ltr"><<a href="mailto:saul@ag-projects.com" target="_blank">saul@ag-projects.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Duane,<br>
<div class="im"><br>
On Apr 26, 2012, at 9:48 AM, <a href="mailto:duane.larson@gmail.com">duane.larson@gmail.com</a> wrote:<br>
<br>
> I wanted to get everyones opinion on what they think is the best way to implement Presence with an IM client. Is it possible to do the following<br>
><br>
<br>
</div>Disclaimer: I'm quite biased here, for obvious reasons :-)<br>
<div class="im"><br>
> Use SIP for VoIP (obviously) and use XMPP for IM. I would want to make sure that OpenSIPS could send Notify information to the XMPP clients telling them that someone is currently on the phone. I know you can use the pua_dialoginfo module to publish info about dialog states but I am not sure if what I am thinking (SIP with XMPP integration) is possible. So on OpenSIPS you would have a multidomain setup and the same would go for XMPP. So user bob@companyA.com would be set up on both OpenSIPS and XMPP. Bob's XMPP client (pidgin or whatever) would have buddies from companyA.com. XMPP would work as normal when it came to IM's and Presence, but I want to make it so that if alice@companyA.com calls someone OpenSIPS sends a XMPP Notify to the XMPP server and then the XMPP server notifies bob and his client shows that alice is busy or on phone or whatever.<br>
><br>
> Is this possible? If so how would Bob subscribe to Alice so that he could see her XMPP Client Presence along with her phone dialog presence and it be a single buddy on his list?<br>
><br>
<br>
</div>If you use SIP for VoIP and XMPP for IM you are effectively using 2 protocols, thus you'll have a SIP account and an XMPP account.<br>
<br>
When you login with your XMPP account you use a resource identifier, so the full JID looks something like this: user@domain.tld/resource. Now, you say you want OpenSIPS to publish presence information for this XMPP account, but how do we know to what resource it applies? This would require cooperation between your SIP proxy and your XMPP server.<br>
<br>
I think you have 2 ways to do this, depending if you go dual-stack or single-stack:<br>
<br>
Dual-stack (SIP for VoIP, XMPP for IM):<br>
- Make the client update the presence state every time you are on a call. Each client could do this and since presence is per-device it makes sense.<br>
- If you want to go this path you may want to check CUSAX (<a href="http://tools.ietf.org/html/draft-ivov-xmpp-cusax-00" target="_blank">http://tools.ietf.org/html/draft-ivov-xmpp-cusax-00</a>) from the Jitsi folks.<br>
<br>
Single stack (SIP for everything):<br>
- Use SIP for VoIP, IM and presence and a gateway to communicate with the XMPP universe<br>
- The gateway must be transparent, that is, subscribing to sip:user@x2s.domain.tld is out of the question<br>
<br>
We are currently working in a transparent XMPP gateway in order to seamlessly communicate with XMPP from a SIP client. You can find more details here: <a href="http://sipsimpleclient.com/projects/sipsimpleclient/wiki/DesignXMPP" target="_blank">http://sipsimpleclient.com/projects/sipsimpleclient/wiki/DesignXMPP</a><br>
<br>
<br>
Regards,<br>
<br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>--<br>*--*--*--*--*--*<br>Duane<br>*--*--*--*--*--*<br>--<br>
</div>