Skip to main content

Deployment Overview

Context​

The MindLink XMPP Gateway is deployed as a standalone trusted application as part of Skype for Business (SfB) on-premise topology, as illustrated below. It acts as a protocol gateway between an SfB deployment (which uses the SIP protocol) and an external XMPP deployment, as illustrated below.

Example Topology

Above: An example deployment topology, showing the gateway situated within the Skype for Business topology

Architecture​

Further to the overall context of the above diagram, the Gateway service is broken down into the following internal components:

  • A single "adapter" which handles bidirectional communication between the gateway and an SfB deployment. (Referred to elsewhere in this documentation as the "SIP adapter".)
  • A single "adapter" which handles bidirectional communication between the gateway and an XMPP deployment. (Referred to elsewhere in this documentation as the "XMPP adapter".)
  • A central publish-subscribe mechanism, providing a common event-based interface for adapters to publish any data they receive, and handle any data which they must forward to their federated deployment.
  • A persistence and state management layer to maintain continuous and reliable presence subscription behavior.