The NextPlane UC Exchange service is architected so that federating through UC Exchange is secure and extremely simple. UC Exchange is a no-touch solution for the unified communication (UC) client and is stunningly simple for the UC servers. UC Exchange does not require ANY plug-ins or software component to be installed on the federated domains' UC platforms. It appears to each UC server or gateway as if it is federating with its own kind.
Cisco UC Platforms
Federating Cisco CUPS, WebEx Messenger, or Jabber XCP with IBM Sametime, or Microsoft LCS, OCS, and Lync, does not require any changes on the Cisco side, except ensuring port 5269 is open on the perimeter network.
SIP-Based UC Platforms
In order for SIP-based domains to federate with a Cisco CUPS, WebEx Messenger, or Jabber XCP domain, the administrator for the Microsoft Lync, OCS, LCS, or IBM Sametime domain must modify the Allow List of the OCS or Lync Access Edge Server, or the Sametime Community on the Sametime Gateway to point to the NextPlane UC Exchange FQDN.
Moreover, SIP-based platforms also require that an XMPP SRV record for their domain is published to public DNS and that this record is pointing to the NextPlane UC Exchange FQDN.
The publication of the XMPP SRV record by the SIP-based domain allows UC Exchange to receive XMPP traffic from the XMPP domain(s), which is addressed to the users on the SIP-based domain, and to translate and it appropriately as SIP traffic to the Microsoft Access Edge or IBM Sametime Gateway.
The modification of the Allow List of the Microsoft Access Edge Server or the IBM Sametime Community on the Sametime Gateway enables UC Exchange to receive the SIP traffic from the SIP domain, which is addressed to the users on the Cisco XMPP domain, and to translate and route it appropriately to the Cisco XMPP domain.
Finally, the administrators of an IBM or Microsoft UC platform needs to ensure that port 5061 (TLS) or 5060 (TCP) is open on their perimeter network.
To join the UC Exchange, contact NextPlane today.