Edit History

DesignXMPP

Version 15 (Adrian Georgescu, 04/29/2010 08:38 am)

1 13 Adrian Georgescu 
== SIMPLE server ==
2 1 Adrian Georgescu 






    3
    15
    Adrian Georgescu
    
The goal of this project is to implement:






    4
    1
    Adrian Georgescu
    






    5
    14
    Adrian Georgescu
    
=== Multiparty Chatserver ===






    6
    14
    Adrian Georgescu
    






    7
    14
    Adrian Georgescu
    
This is a conference server that can mix Audio, MSRP and SIP MESSAGE.






    8
    14
    Adrian Georgescu
    






    9
    14
    Adrian Georgescu
    
 * MSRP ad-hoc multi-party chat sessions draft-ietf-simple-chat-05






    10
    14
    Adrian Georgescu
    
 * A Framework for Conferencing with Session Initiation Protocol (SIP) RFC4353






    11
    14
    Adrian Georgescu
    
 * Conference Event Package RFC4575






    12
    14
    Adrian Georgescu
    
 * Audio mixer






    13
    14
    Adrian Georgescu
    






    14
    13
    Adrian Georgescu
    
=== XMPP Gateway ===






    15
    13
    Adrian Georgescu
    






    16
    13
    Adrian Georgescu
    
Bidirectional gateway for Presence and IM between SIP and XMMP protocol based on the following IETF specifications:






    17
    12
    Adrian Georgescu
    






    18
    13
    Adrian Georgescu
    
 * http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-presence-02.html






    19
    8
    Adrian Georgescu
    
 * http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-im-01.html






    20
    13
    Adrian Georgescu
    
 * http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-chat-03.html






    21
    13
    Adrian Georgescu
    
 * http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-groupchat-01.html






    22
    13
    Adrian Georgescu
    






    23
    13
    Adrian Georgescu
    
==== Usage Scenario ====






    24
    13
    Adrian Georgescu
    






    25
    13
    Adrian Georgescu
    
The gateway will be used by [http://icanblink.com Blink]. End users will add a Contact in their Contact lists in the form of user@domain. Using SIP Subscribe Method the user will subscribe to the presence state of the recipient. The user should not need to know if the remote user uses SIP or XMPP protocol for IM and Presence. The SIP Proxy/Registrar of the user will decide if the remote user uses XMPP and will forward the request to the gateway.