DesignXMPP arch
Version 4 (Anonymous, 02/29/2012 11:45 am)
| 1 | 1 | = XMPP gateway architecture = |
|
|---|---|---|---|
| 2 | 1 | ||
| 3 | 4 | The architecture of the SIP-XMPP gateway can be modeled in two different ways: |
|
| 4 | 1 | ||
| 5 | 4 | * Based on an XMPP component |
|
| 6 | 4 | * Based on an XMPP server (using server-to-server communication) |
|
| 7 | 1 | ||
| 8 | 4 | 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. |
|
| 9 | 4 | ||
| 10 | 4 | == XMPP component based architecture == |
|
| 11 | 4 | ||
| 12 | 2 | [[Image(XMPP-components.png)]] |
|
| 13 | 2 | ||
| 14 | 4 | === Elements === |
|
| 15 | 3 | ||
| 16 | 3 | * XMPP server (ejabberd) |
|
| 17 | 1 | * XMPP server plugin (divert stanzas to offline users to a given component) |
|
| 18 | 1 | * SIP Application server which is also a XMPP component |
|
| 19 | 1 | * SIP proxy (registration, AAA and routing) |
|
| 20 | 4 | ||
| 21 | 4 | == XMPP server based architecture == |
|
| 22 | 4 | ||
| 23 | 4 | TODO |
|
| 24 | 4 | ||
| 25 | 4 | === Elements === |
|
| 26 | 4 | ||
| 27 | 4 | TODO |