DesignXMPP im
Version 1 (Anonymous, 02/29/2012 12:34 pm) → Version 2/29 (Anonymous, 02/29/2012 03:32 pm)
= Gateway for Instant Messaging=
[[TOC(DesignXMPP_im, depth=2)]]
In XMPP there are several types of messages which lead to different semantics when exchanging XMPP ''message stanzas'' between 2 endpoints. This section focuses only on message types that allow 2 endpoints to send instant messages to each other.
Message types:
* Normal: the default message type. A reply is not expected from the recipient.
* Chat: This message type implies both parties have engaged a conversation.
* Headline: An endpoint receiving this type of message should never reply, since it's meant to be used by servers or other entities to deliver announcements.
In SIP there are currently 2 ways of doing Instant Messaging:
* SIP MESSAGE (RFC 3428)
* MSRP (RFC 4975)
The first one is session-less and the latter is session based.
The mechanisms described here follow the currently available specifications for SIP-XMPP interoperability:
* http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-im-01.html
* http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-chat-03.html
== XMPP single message <-> SIP MESSAGE ==
XMPP single messages are mapped directly to SIP MESSAGE requests and ''vice versa''.
TODO (image)
[[TOC(DesignXMPP_im, depth=2)]]
In XMPP there are several types of messages which lead to different semantics when exchanging XMPP ''message stanzas'' between 2 endpoints. This section focuses only on message types that allow 2 endpoints to send instant messages to each other.
Message types:
* Normal: the default message type. A reply is not expected from the recipient.
* Chat: This message type implies both parties have engaged a conversation.
* Headline: An endpoint receiving this type of message should never reply, since it's meant to be used by servers or other entities to deliver announcements.
In SIP there are currently 2 ways of doing Instant Messaging:
* SIP MESSAGE (RFC 3428)
* MSRP (RFC 4975)
The first one is session-less and the latter is session based.
The mechanisms described here follow the currently available specifications for SIP-XMPP interoperability:
* http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-im-01.html
* http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-chat-03.html
== XMPP single message <-> SIP MESSAGE ==
XMPP single messages are mapped directly to SIP MESSAGE requests and ''vice versa''.
TODO (image)