History

« Previous - Version 23/30 (diff) - Next » - Current version
Adrian Georgescu, 03/07/2012 09:35 am

= Gateway Architecture =

<acronym title="DesignXMPP, DesignXMPP_analysis, DesignXMPP_arch, DesignXMPP_im, , DesignXMPP_conference, DesignXMPP_presence, DesignXMPP_jingle, depth=2">TOC</acronym>

Due to the dedicated server architecture of XMPP and requirement for public DNS entries for the target domain, is not possible to position the gateway between two clients. The architecture of the SIP-XMPP gateway can be modeled in two ways, both deponent on the way XMPP server is deployed:

  • Based on an XMPP server (using server-to-server communication)
  • Based on an XMPP component connected to an existing XMPP server

These approaches are not mutually exclusive, they could potentially be implemented and decide which one to use by setting a configuration option.

XMPP Server Based Architecture

Image(xmppgw-arch-server.png, 700px, center)

  • SIP Application server which is also a XMPP server
  • SIP proxy (registration, AAA and routing)
XMPP Component Based Architecture

Image(xmppgw-arch-component.png, 700px, center)

  • XMPP server (ejabberd for example)
  • 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)
Chosen Architecture

After experimenting with both models the chosen model to be implemented first is the '''XMPP server based architecture'''. The component based approach could be added at a later time.

The server based architecture model has a number of advantages / disadvantages:

  • Advantages * Less network elements involved * Full control over XMPP routing since the server is customized * No need for developing plugins for any XMPP server
  • Disadvantages: * Inability to use an XMPP client in the local domain

The critical factor when making this choice is the fact that if a custom XMPP server is built all the routing logic can be customized without the need of running an extra XMPP server and writing a plugin for it. Thus, this approach is more sustainable over time.

The aforementioned disadvantage would also disappear if the chosen library implemented accepting XMPP client connections, which is likely to happen in the future.

xmppgw-arch-component.png (80.3 kB) , 03/07/2012 04:56 pm

xmppgw-arch-server.png (75.9 kB) , 03/07/2012 04:58 pm