DesignXMPP arch
Version 4 (Anonymous, 02/29/2012 11:45 am) → Version 5/30 (Anonymous, 02/29/2012 12:17 pm)
= XMPP gateway architecture =
The architecture of the SIP-XMPP gateway can be modeled in two different ways:
* Based on an XMPP component
* Based on an XMPP server (using server-to-server communication)
Both approaches are not mutually exclusive, they can both be implemented at the same time and decide which one to use with a configuration option to allow different deployment scenarios.
== XMPP component based architecture ==
[[Image(xmppgw-arch-component.png)]] [[Image(XMPP-components.png)]]
=== Elements required ===
* XMPP server (ejabberd for example) (ejabberd)
* XMPP server plugin (divert stanzas to offline users to a given component)
* SIP Application server which is also a XMPP component
* SIP proxy (registration, AAA and routing)
== XMPP server based architecture ==
[[Image(xmppgw-arch-server.png)]] TODO
=== Elements required ===
* SIP Application server which is also a XMPP server
* SIP proxy (registration, AAA and routing)
TODO
The architecture of the SIP-XMPP gateway can be modeled in two different ways:
* Based on an XMPP component
* Based on an XMPP server (using server-to-server communication)
Both approaches are not mutually exclusive, they can both be implemented at the same time and decide which one to use with a configuration option to allow different deployment scenarios.
== XMPP component based architecture ==
[[Image(xmppgw-arch-component.png)]] [[Image(XMPP-components.png)]]
=== Elements required ===
* XMPP server (ejabberd for example) (ejabberd)
* XMPP server plugin (divert stanzas to offline users to a given component)
* SIP Application server which is also a XMPP component
* SIP proxy (registration, AAA and routing)
== XMPP server based architecture ==
[[Image(xmppgw-arch-server.png)]] TODO
=== Elements required ===
* SIP Application server which is also a XMPP server
* SIP proxy (registration, AAA and routing)
TODO