System and method for providing configuration synchronicity

• US 8,719,386 B2
• Filed: 01/08/2009
• Issued: 05/06/2014
• Est. Priority Date: 01/08/2009
• Status: Active Grant

• Current Assignee: Sangoma US, Inc. (Sangoma Technologies Corporation)
• Original Assignee: Fonality Incorporated (NetFortris, Inc.)
• Inventors: Lyman, Christopher, Kamkar, Samy
• Primary Examiner(s): Shin, Kyung H
• Application Number:
  US12/319,693
• Publication Number:
  US 20100174807A1
• Time in Patent Office: 1,944 Days
• Field of Search: 709/222, 709/221, 709/227, 717/174
• US Class Current: 709/221
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
• CPC Class Codes: H04L 41/0866 Checking the configuration

Abstract

Systems and methods for providing configuration synchronicity is provided. In exemplary embodiments, a configuration file is generated based on received configuration information. The configuration file may then be stored and queued up for download to at least one communication server to configure the communication server. Subsequently, a verification process is performed to confirm that the configuration file is correctly written to disk by the communication server.

Claims

1. A method for providing configuration synchronicity, comprising:

generating a configuration file based on received configuration information;

queuing the configuration file within a file queue at a first server;

detecting by a second server that the configuration file is in the file queue at the first server;

receiving a ping request from one or more communication servers for the configuration file;

synchronizing transfer of the configuration file by the second server to the one or more communication servers to configure the one or more communication servers;

verifying that the configuration file is correctly written by the one or more communication servers; and

removing the configuration file from the file queue upon the verification.

2. The method of claim 1 further comprising storing the configuration file in a configuration database.

3. The method of claim 2 further comprising checking by the second server for configuration files stored in the configuration database;

wherein the ping request from the one or more communication servers for the configuration file is received by the second server.

4. The method of claim 1 wherein synchronizing transfer of the configuration file comprises checking the file queue by the second server for one or more available configuration files for the one or more communication servers.

5. The method of claim 1 wherein synchronizing transfer of the configuration file comprises determining whether the one or more communication servers are available for receipt of the configuration file.

6. The method of claim 1 wherein verifying the configuration file is correctly written comprises applying a hash operation to the configuration file.

7. The method of claim 1 wherein verifying the configuration file is correctly written comprises comparing a received hash response from the one or more communication servers to local hash data.

8. The method of claim 7 further comprising generating the local hash data based on the configuration file.

9. The method of claim 1 further comprising:

detecting by a third server that the configuration file is in the file queue at the first server; and

synchronizing transfer of the configuration file by the third server to the one or more communication servers to configure the one or more communication servers.

10. A system for providing configuration synchronicity, comprising:

a configuration module, stored in a memory of a first server and executable by a processor of the first server, and configured to generate a configuration file based on received configuration information;

a synchronization module in a second server configured to synchronize transfer of the configuration file to one or more communication servers to configure the one or more communication servers, the synchronization module configured to receive a ping request from the one or more communication servers for the configuration file;

a verification module configured to verify that the configuration file is correctly written by the one or more communication servers; and

a file queue in the first server configured to queue the configuration file for delivery to the one or more communication servers.

11. The system of claim 10 further comprising a configuration database configured to store the configuration file.

12. The system of claim 11 further comprising checking by the second server for configuration files stored in the configuration database;

wherein the ping request from the one or more communication servers for the configuration file is received by the second server.

13. The system of claim 10 wherein the synchronization module is further configured to check the file queue for one or more available configuration files for the one or more communication servers.

14. The system of claim 10 wherein the synchronization module is further configured to determine whether the one or more communication servers are available for receipt of the configuration file.

15. The system of claim 10 wherein the verification module is configured to verify the configuration file is correctly written by comparing a received hash response from the one or more communication servers to local hash data.

16. The system of claim 10 wherein the verification module is further configured to remove the configuration file from a file queue when the configuration file is verified to have been correctly written to all of the one or more communication servers.

17. The system of claim 10 further comprising a web interface configured to receive the configuration information used to generate the configuration file.

18. The system of claim 10 further comprising the one or more communication servers, the one or more communication servers configured with a unique customer identifier used to identify the one or more communication servers for receipt of the configuration file.

19. The system of claim 10 wherein the synchronization module is further configured to verify whether the configuration file is in the file queue for the one or more communication servers.

20. The system of claim 19 wherein verifying whether the configuration file is in the file queue for the one or more communication servers is triggered by sending a message to web servers indicating that the one or more communication servers are online and inquiring if any configuration files are available.

21. A non-transitory machine readable medium having embodied thereon a program, the program providing instructions for a method for providing configuration synchronicity, the method comprising:

generating a configuration file based on received configuration information;

queuing the configuration file within a file queue at a first server;

detecting by a second server that the configuration file is in the file queue at the first server;

receiving a ping request from one or more communication servers for the configuration file;

synchronizing transfer of the configuration file by the second server to the one or more communication servers to configure the one or more communication servers;

verifying that the configuration file is correctly written by the one or more communication servers; and

removing the configuration file from the file queue upon the verification.

22. The non-transitory machine readable medium of claim 21, wherein the method further comprises checking by the second server for configuration files stored in a configuration database;

wherein the ping request from the one or more communication servers for the configuration file is received by the second server.