Systems and methods for setting up a collaborative communication system
View Patent ↗A collaborative communication system comprises a highly flexible architecture that facilitates connecting communication devices and networks to establish multimedia collaboration sessions in a manner that allows distribution of various services and features throughout the collaborative communication system to provide scalability and selectable combination of cost, resource usage, and performance.
1. A method, comprising:
determining a list of services to be loaded by a media switch;
loading the services;
if it is determined that other services are to be loaded, loading the other services by the media switch and ensuring a first service of the other services to load is an authentication service that is accepted from at least one trusted endpoint address;
wherein loading the other services comprises loading a presence service which maintains information on all endpoints associated with the media switch via an endpoint locator service that is running before any of the other services are loaded;
wherein the presence service maintains information comprising at least one of entity availability that indicates a service's ability to accept connections or entity type that indicates one or more services offered by an endpoint; and
wherein the presence service is configured to publish its own presence with itself when loaded, and is further configured to attempt an additional attachment as a master presence service that is awarded to a presence service that first attempts to be the master presence service, wherein the master presence service is configured to provide synchronized access information to shared data elements.
2. The method of claim 1 , wherein loading the authentication service comprises initiating the authentication service and the authentication service attempting to publish its presence with the presence service.
3. The method of claim 2 , further comprising the authentication service receiving an indication that the attempt to publish its presence failed and the authentication service again attempting to publish its presence after the presence service is loaded.
4. The method of claim 1 , further comprising loading an additional authentication service.
5. The method of claim 1 , further comprising loading an additional presence service.
6. The method of claim 1 , wherein loading the other services comprises loading non-core services.
7. The method of claim 1 , further comprising:
reading a configuration file to determine the list of services to be loaded by the media switch; and
reading the configuration file to determine a list of the other services that should be loaded.
8. The method of claim 1 , further comprising loading the other services sequentially.
9. A system, comprising:
a media switch configured determine a list of services to be loaded by the media switch;
wherein the media switch loads the services;
wherein the media switch is configured to determine if other services are to be loaded and if so, the media switch loads the other services and ensures a first service of the other services to load is an authentication service that is accepted from at least one trusted endpoint address;
wherein the media switch loads the other services comprises a presence service being loaded which maintains information on all endpoints associated with the media switch via an endpoint locator service that is run before any of the other services are loaded;
wherein the presence service maintains information comprising at least one of entity availability that indicates a service's ability to accept connections or entity type that indicates one or more services offered by an endpoint, and wherein the presence service is configured to publish its own presence with itself when loaded, and is further configured to attempt an additional attachment as a master presence service that is awarded to a presence service that first attempts to be the master presence service, wherein the master presence service is configured to provide synchronized access information to shared data elements.
10. The system of claim 9 , wherein the authentication service to load comprises the authentication service being initiated and the authentication service attempts to publish its presence with the presence service.
11. The system of claim 10 , wherein the authentication service is configured to receive an indication that the attempt to publish its presence failed and to attempt to publish its presence after the presence service is loaded.
12. The system of claim 9 , wherein the other services being loaded comprises loading an additional authentication service.
13. The system of claim 9 , wherein the other services being loaded comprises loading an additional presence service.
14. The system of claim 9 , wherein the other services being loaded comprises loading non-core services.
15. The system of claim 9 , wherein the media switch service is configured to allow the media switch to communicate as an addressable endpoint.
16. The system of claim 9 , wherein the media switch is configured to read a configuration file to determine the list of services to be loaded by the media switch and to determine a list of the other services that should be loaded.
17. The system of claim 9 , wherein the other services are loaded sequentially.
18. A non-transitory computer readable medium comprising instructions that when read by at least one processor perform:
determining a list of services to be loaded by a media switch;
loading the services;
if it is determined that other services are to be loaded, loading the other services by the media switch and ensuring a first service of the other services to load is an authentication service that is accepted from at least one trusted endpoint address;
wherein loading the other services comprises loading a presence service which maintains information on all endpoints associated with the media switch via an endpoint locator service that is running before any of the other services are loaded;
wherein the presence service maintains information comprising at least one of entity availability that indicates a service's ability to accept connections or entity type that indicates one or more services offered by an endpoint; and
wherein the presence service is configured to publish its own presence with itself when loaded, and is further configured to attempt an additional attachment as a master presence service that is awarded to a presence service that first attempts to be the master presence service, wherein the master presence service is configured to provide synchronized access information to shared data elements.
19. The non-transitory computer readable medium of claim 18 , wherein loading the authentication service comprises initiating the authentication service and the authentication service attempting to publish its presence with the presence service.
20. The non-transitory computer readable medium of claim 19 , further comprising the authentication service receiving an indication that the attempt to publish its presence failed and the authentication service again attempting to publish its presence after the presence service is loaded.