DesignXMPP conference » History » Revision 5
Revision 4 (Adrian Georgescu, 01/22/2013 01:59 PM) → Revision 5/17 (Saúl Ibarra Corretgé, 01/29/2013 10:13 PM)
h1. SIP-XMPP Multiparty Chat This is done by bridging MUC functionality from XMPP with MSRP-Switch functionality using SIP. * SIP users can create ad-hoc conference rooms using SylkServer MSRP chat and invite users from both SIP and XMPP domains * XMPP users can create multiparty conferences using SylkServer MUC capability and invite users from both XMPP and SIP worlds h2. Joining a conference A conference room will be created if it doesn't exist previously. For joining a conference, an XMPP endpoint will send a presence stanza with the URI of the room. SylkServer handles conferences as part of the conference application, so it will create a new SIP session which will join the conference.Usually the SIP INVITE will loop in the proxy and enter SylkServer again, but this time the executed application will be "conference". The XMPP gateway application will receive SIP NOTIFY requests with [[RFC 4575]](https://tools.ietf.org/html/rfc4575) payload specifying the participants in the room, and this will be translated into presence stanza elements. Likewise, all MSRP messages received on the SIP session will be translated into _groupchat_ message stanzas. h2. Inviting new participants TODO