The NextPlane Federation Server is designed to address the complexities faced by today’s large organizations to deliver the benefits of federation across corporate or network boundaries.
| Hi-Fidelity Federation | |
| Hi-Fidelity Federation | Takes full advantage of each clients’ rich features when communicating with federated contacts, such as showing show custom presence messages, tagging, supporting special European characters, and using emoticons. |
| Custom Disclaimer Messages | Enable display of customizable disclaimer messages to be displayed at the start of a federate chat session on both client end-points. |
| Support for concurrently opened and active UC clients | Tracks a user’s presence across concurrently open XMPP clients. |
| Multi-party (n-way) chat Federation | |
| OCS hosted multi-party chat federation | Allows any OCS user to initiate and invite participants on federated UCs. |
| CUPS hosted multi-party chat federation | Allows any CUPS user to initiate and invite participants on federated UCs. |
| WebEx hosted multi-party chat federation | Allows any WebEx user to initiate and invite participants on federated UCs. |
| OpenFire hosted multi-party chat federation | Allows any OpenFire user to initiate and invite participants on federated supported UCs. |
| Google Apps hosted multi-party chat federation | Allows any Google Apps user to initiate and invite participants on federated UCs. |
| Jabber hosted multi-party chat federation | Allows any Jabber user to initiate and invite participants on federated UCs. |
| Rich client (hi-fidelity) support for multi-party chat | Allows users on CUPS, WebEx, OpenFire, Jabber, OCS, Google Apps to take full advantage of their clients’ rich features when participating in multi-user chat sessions hosted on a dissimilar UC platform. For example, a Google user can see the list of all the participants (including OCS users) and be aware of those who join or leave the session. |
| Advanced Routing | |
| Domain Overlap | Allows two or more incompatible UC servers to be federated (internally or externally) while sharing the same domain name. This feature is mostly used by organizations that need to maintain two UC solutions, or are in the process of migrating from one to another. |
| Single Domain Routing | Routes messages addressed to a single external domain to the appropriate internal UC servers. |
| Multi-Aliasing | Allows internal users to be migrated from one UC solution to another without affecting the externally federated colleagues. |
| Policy Enforcement | |
| Instant Messaging and Presence | Controls which types of messages are allowed to pass across network boundaries and manages white-lists and blacklists of both internal and external addresses and domains, as well as internal groups. |
| Presence Obfuscation | Enforces policies related to dissemination of employees presence with partner organizations based on context, activity, business processes, or location. |
| Security | |
| TLS over SIP and XMPP support | Supports secure TLS over both SIP and XMPP connections. |
| Automatic certificate retrieval | Automates the certificate retrieval of the federated domain and eliminates the need to receive certificates via email. |
| Automatic domain validation | Monitors federated domains and send alarms when there is a problem. |
| Centralized certificate management | Monitors certificate expiration dates and sends alarms before they are about to expire. |
| Automatic domain validation | Monitors federated domains and send alarms when there is a problem |
| Centralized certificate management | Monitors certificate expiration dates and sends alarms before they are about to expire. |
