System and method for providing configuration synchronicity

• US 20100174807A1
• Filed: 01/08/2009
• Published: 07/08/2010
• Est. Priority Date: 01/08/2009
• Status: Active Grant

• Current Assignee: Sangoma US, Inc. (Sangoma Technologies Corporation)
• Original Assignee: Fonality Incorporated (Sangoma Technologies Corporation)
• Inventors: Lyman, Christopher, Kamkar, Samy
• Granted Patent: US 8,719,386 B2
• Time in Patent Office: Days
• 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;

sending the configuration file to one or more communication servers to configure the one or more communication servers; and

verifying the configuration file is correctly written by the one or more communication servers.

2. The method of claim 1 further comprising queuing the configuration file in a file queue for delivery to the one or more communication servers.

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

4. The method of claim 1 wherein sending the configuration file comprises checking a file queue for one or more available configuration files for the one or more communication servers.

5. The method of claim 1 wherein sending 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 generated configuration file.

9. The method of claim 1 further comprising removing the configuration file from a file queue when the configuration file is verified to have been correctly written by all of the one or more communication servers.

10. The method of claim 1 further comprising receiving a ping request from the communication server for the configuration file.

11. A system for providing configuration synchronicity, comprising:

a configuration module configured to generate a configuration file based on received configuration information;

a synchronization module configured to send the configuration file to one or more communication servers to configure the one or more communication servers; and

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

12. The system of claim 11 further comprising a file queue configured to queue the configuration file for delivery to the one or more communication servers.

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

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

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

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

17. The system of claim 11 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.

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

19. The system of claim 11 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.

20. A 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;

sending the configuration file to one or more communication servers to configure the one or more communication servers; and

verifying the configuration file is correctly written by the one or more communication servers.