Organizations with more than one unified communication (UC) platform or that are contemplating migrating to a different platform face a difficult Intra-domain federation problem, especially if they want to establish federation for users on different platforms who share the same domain name.
This problem is practically impossible to solve since each UC server would consider any traffic as its local UC traffic and thus neither system would route messages to the other one. As a result, users on one platform cannot communicate with their colleagues on the other platform because of the domain-based locality imposed by both UCs.
NextPlane solves this problem by enabling two federated UCs to share the same domain name without requiring a costly and disruptive implementation of sub-domains. NextPlane applies patented routing algorithms that use either rules or UC-specific server plug-ins to disambiguate between the two UCs in order to route messages that use the same domain name.
Single Domain Routing
For most federations, UC Exchange routes messages based upon the domain of the destination address. However, for more complex routing scenarios, UC Exchange can support enterprises that require a single (global) externally visible domain whilst having multiple internal domains (any of which can be served by different UCs or even different types of UCs) to which incoming messages must be routed.
Single or Multi-Aliasing
One major problem in migrating from one UC platform to another is the negative impact UC migration has on users. In addition to the new UC platform being incompatible with the existing UC platform, the migration usually requires employees to change their addresses. A merger or acquisition of another company is a great example of where such a situation could arise.
NextPlane's aliasing feature allows organizations to migrate internal users from one UC platform to another UC platform without affecting any of their external federated relationships.
To join the UC Exchange, contact NextPlane today.