Hub based clearing house for interoperability of distinct unified communication systems
A hub-based clearing house for interoperability of distinct unified communication systems is disclosed. According to one embodiment, a system comprises a database that stores configuration information for the system; an administrator module that maintains the configuration information; a federation server that is connected to a first unified communications system and a second unified communications system. The federation server comprises a first translator that translates a first formatted message received from the first unified communications system into a common language formatted message, a second translator that translates the common language formatted message into a second formatted message, and a routing engine that routes the second formatted message to the second unified communications system.
1. A system, comprising:
a database that stores configuration information for the system;
an administrator module that maintains the configuration information; and
a federation server that is connected to a first domain and
a second domain, the federation server comprising,
a first translator that translates a first formatted message received from a first gateway of the first domain into a common language formatted message,
a second translator that translates the common language formatted message into a second formatted message, and
a routing engine that routes the second formatted message to a second gateway of the second domain, wherein the federation server allows the first domain that runs a first type of unified communications application to appear running a second type of unified communications application that federates with the second domain, wherein the second domain runs the second type of unified communications application.
2. The system of claim 1 , wherein the common language formatted message contains at least one field in the first formatted message.
3. The system of claim 1 , wherein the common language formatted message contains at least one field in the second formatted message.
4. The system of claim 1 , wherein the format of the common language formatted message is generic Session Initiation Protocol (SIP).
5. The system of claim 1 , wherein the administrator module sets enforcement policies for determining whether messages received by the federation server are acceptable.
6. The system of claim 5 , wherein the federation server further comprises a policy enforcement engine that applies the enforcement policies to the first formatted message.
7. The system of claim 1 , further comprising a load balancer that manages and directs communications traffic to the federation server to make efficient use of available system resources.
8. The system of claim 1 , further comprising a relay server that relays real-time media communications traffic between the first domain and the second domain.
9. The system of claim 1 , further comprising a transcoder that transcodes real-time media communications traffic between the first domain and the second domain.
10. The system of claim 1 , further comprising a file sharing server that relays file transfer data between the first domain and the second domain using dissimilar file transfer protocols.
11. The system of claim 1 , wherein the federation server is connected to the first domain through a first connector and is connected to the second domain through the first connector or through a second connector.
12. The system of claim 11 , wherein each of the first and second connectors are configured to connect to multiple Unified Communications (UC) systems.
13. The system of claim 1 , wherein only the administration module has direct access to the database.
14. The system of claim 1 , wherein the database is a relational database.
15. A method, comprising:
connecting a first domain and a second domain through a federation server;
receiving into the federation server a first formatted message from a first gateway of the first domain;
translating the first formatted message into a common language formatted message;
translating the common language formatted message into a second formatted message; and
routing the second formatted message from the federation server to a second gateway of the second domain, wherein the federation server allows the first domain that runs first type of unified communications application as running a second type of unified communications application that federates with the second domain, wherein the second domain runs the second type of unified communications application.
16. The method of claim 15 , wherein the common language formatted message contains at least one field in the first formatted message.
17. The method of claim 15 , wherein the common language formatted message contains at least one field in the second formatted message.
18. The method of claim 15 , wherein the format of the common language formatted message is generic Session Initiation Protocol (SIP).
19. The method of claim 15 , further comprising setting enforcement policies for determining whether messages received by the federation server are acceptable.
20. The method of claim 19 , further comprising applying the enforcement policies to the first formatted message.
21. The method of claim of claim 15 , further comprising publishing a Service (SRV) record to direct the first formatted message to the federation server.