DesignXMPP conference » History » Version 5
Saúl Ibarra Corretgé, 01/29/2013 10:13 PM
| 1 | 2 | Adrian Georgescu | h1. SIP-XMPP Multiparty Chat |
|---|---|---|---|
| 2 | 3 | Adrian Georgescu | |
| 3 | This is done by bridging MUC functionality from XMPP with MSRP-Switch functionality using SIP. |
||
| 4 | |||
| 5 | 4 | Adrian Georgescu | * SIP users can create ad-hoc conference rooms using SylkServer MSRP chat and invite users from both SIP and XMPP domains |
| 6 | * XMPP users can create multiparty conferences using SylkServer MUC capability and invite users from both XMPP and SIP worlds |
||
| 7 | 5 | Saúl Ibarra Corretgé | |
| 8 | h2. Joining a conference |
||
| 9 | |||
| 10 | 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". |
||
| 11 | |||
| 12 | 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. |
||
| 13 | |||
| 14 | h2. Inviting new participants |
||
| 15 | |||
| 16 | TODO |