Telephone stations with independent backup/restore feature

• US 8,862,553 B2
• Filed: 06/07/2007
• Issued: 10/14/2014
• Est. Priority Date: 06/07/2006
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: Soltes, John W., Penning, Randall J., Mitchell, Robert L.
• Primary Examiner(s): FILIPCZYK, MARCIN R
• Application Number:
  US11/759,899
• Publication Number:
  US 20080082594A1
• Time in Patent Office: 2,686 Days
• Field of Search: 370/352, 455/414.2, 707/1, 707/2, 707/10, 707/100, 707/103.X, 707/200, 707/202, 707/203, 707/204, 707/999.2, 707/999.202, 707/999.203, 707/999.204, 707/622, 707/623, 707/647, 707/659, 707/610, 707/640, 707/653, 707/655, 707/661, 707/671, 707/674, 709/203, 709/217, 709/219
• US Class Current: 707/653
• CPC Class Codes: G06F 16/10 File systems; File servers

Abstract

A method, system, and computer-readable medium for backing up and/or restoring user-specific settings for one or more IP telecommunications terminals. A backup process is initiated through a user interface of the IP telecommunications terminal. A file name and a backup file are supplied from the telecommunication terminal during a backup process. The backup file is transferred to an HTTP server and the backup file is transferred to the IP telecommunications terminal or other terminals in response to an HTTP GET message received from an IP telecommunications terminal connected to the HTTP server. Accordingly, multiple users can enjoy customized user-interfaces at multiple locations and across multiple platforms.

Claims

1. A method for backing up user-specific settings for an IP telecommunications terminal, the method comprising:

initiating a backup process through a user interface of the IP telecommunications terminal, wherein a file name and a backup file are supplied from the telecommunication terminal;

transferring the backup file to an HTTP server via an HTTP PUT message; and

determining if the backup file has been successfully transferred to the HTTP server, wherein determining includes receiving an indication of a successful transfer or a failed file transfer.

2. The method according to claim 1, wherein the backup file comprises settings relating to at least one of the following parameters from the group consisting of call log settings, bridged call settings, accessory gain control settings, audio path settings, button click settings, error tone settings, ring tones, user interface settings, visual alert settings, call timer settings, and redial settings.

3. The method according to claim 2, wherein the backup file includes at least two of the parameters consisting of call log settings, bridged call settings, accessory gain control settings, audio path settings, button click settings, error tone settings, ring tones, user interface settings, visual alert settings, call timer settings, and redial settings.

4. The method according to claim 3, wherein the backup file includes call log settings, bridged call settings, accessory gain control settings, audio path settings, button click settings, error tone settings, ring tones, user interface settings, visual alert settings, call timer settings, and redial settings.

5. The method according to claim 4, wherein the backup file comprises user-specific data, user-specific contacts, user-generated call appearance features, and/or user-generated button or softkey features.

6. The method according to claim 1, wherein the backup file comprises user-specific data, user-specific contacts, user-generated call appearance features, and/or user-generated button or softkey features.

7. The method according to claim 1, providing a uniform resource identifier (URI) designated for backup and restoration of user data from the HTTP server.

8. The method according to claim 7, wherein the URI identifies the HTTP server and a directory path for the backup file.

9. The method according to claim 8, further comprising restoring user-specific settings to the IP telecommunication terminal, wherein the backup file is transferred from the HTTP server to the IP telecommunication terminal.

10. The method according to claim 8, further comprising restoring user-specific settings to a second IP telecommunication terminal, wherein the backup file is transferred from the HTTP server to the second IP telecommunication terminal in response.

11. The method according to claim 1, further comprising:

transferring an HTTP GET message to the HTTP server; and

transferring the backup file to the IP telecommunications terminal in response to the HTTP GET message.

12. A system for backing up and/or restoring user-specific settings for an IP telecommunications terminal, the system comprising:

a plurality of IP telecommunications terminals, each IP telecommunications terminal including a user interface configured to initiate a backup process and a restore process; and

at least one HTTP server configured to store a backup file for user-specific settings for each user among a plurality of users associated with the telecommunications terminals, wherein the IP telecommunications terminals are configured to transfer each backup file to the HTTP server via an HTTP PUT message and to receive each backup file in response to an HTTP GET message.

13. The system according to claim 12, wherein each IP telecommunication terminal is configured to receive an indication of a successful transfer or failed transfer of a respective backup file sent to the HTTP server.

14. The system according to claim 13, wherein each IP telecommunication terminal is configured to modify a backup file comprising user-specific settings relating to at least one of the following parameters from the group consisting of call log settings, bridged call settings, accessory gain control settings, audio path settings, button click settings, error tone settings, ring tones, user interface settings, visual alert settings, call timer settings, and redial settings.

15. The system according to claim 14, wherein the backup file includes at least two of the parameters consisting of call log settings, bridged call settings, accessory gain control settings, audio path settings, button click settings, error tone settings, ring tones, user interface settings, visual alert settings, call timer settings, and redial settings.

16. The system according to claim 15, wherein the backup file includes call log settings, bridged call settings, accessory gain control settings, audio path settings, button click settings, error tone settings, ring tones, user interface settings, visual alert settings, call timer settings, and redial settings.

17. The system according to claim 16, wherein the backup file comprises user-specific data, user-specific contacts, user-generated call appearance features, and/or user-generated button or softkey features.

18. The system according to claim 14, wherein the backup file comprises user-specific data, user-specific contacts, user-generated call appearance features, and/or user-generated button or softkey features.

19. The system according to claim 12, wherein each IP telecommunications terminal is configured to replace a current backup file with a backup file associated with another user logging into the IP telecommunications terminal through PSA/IP login/logoff.

20. A non-transitory computer-readable medium having computer-executable instructions contained therein for a method for backing up and restoring user-specific settings for an IP telecommunications terminal, the method comprising:

initiating a backup process through a user interface of the IP telecommunications terminal, wherein a file name and a backup file are supplied from the telecommunication terminal;

transferring the backup file to an HTTP server via an HTTP PUT message;

determining if the backup file has been successfully transferred to the HTTP server, wherein determining includes receiving an indication of a successful transfer or a failed file transfer;

transferring an HTTP GET message to the HTTP server; and

transferring the backup file to the IP telecommunications terminal in response to the HTTP GET message.