Method for migrating or altering a messaging system

• US 6,208,717 B1
• Filed: 02/23/1998
• Issued: 03/27/2001
• Est. Priority Date: 03/03/1997
• Status: Expired due to Term

• Current Assignee: Unisys Corporation
• Original Assignee: Unisys Corporation
• Inventors: Subramanian, Murali, Yeh, Yen-Ching, Winter, Lucy
• Primary Examiner(s): WEAVER, SCOTT LOUIS
• Application Number:
  US09/027,975
• Time in Patent Office: 1,128 Days
• Field of Search: 379/88.18, 379/88.22, 379/88.27, 379/201, 379/207
• US Class Current: 379/88.18
• CPC Class Codes: H04M 1/65 Recording arrangements for recording a message from the calling party in the exchange H04M3/50
• CPC Class Codes: H04M 3/53325 Interconnection arrangements between voice mail systems
• CPC Class Codes: H04M 3/54 Arrangements for diverting calls for one subscriber to another predetermined subscriber based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; to voice mail H04M3/53308

Abstract

A method for changing or migrating a voice messaging system comprises the steps of creating a new version of a mailbox for at least one user; and using the new version for a period of time before removing an old version of the mailbox. Significantly, the change or migration is effected such that there is substantially no system interruption. The changes may include making a software upgrade; moving a logical or physical device from a first location to a second location or from a first computer system to a second computer system; and making a change from a first version of the application to a second version. The migration may be a complete migration in which all devices are migrated or a partial migration in which only selected devices are migrated. Once the change or migration begins, any new inputs or calls to a device are routed first to the new application and, if the new application is not yet ready to receive the input, then to the old application. Alternatively, the sequence may be reversed and the new input calls may be noted first to the old application and then to the new application.

Claims

1. A method for changing or migrating a voice messaging system including an application and a plurality of user mailboxes, comprising the steps of:

(A) creating a new version of a mailbox for at least one user while keeping said new version of said mailbox in a same location as an old version of said mailbox, wherein said new version of said mailbox comprises a software upgrade; and

(B) using said new version of said mailbox for a period of time before removing said old version of said mailbox;

wherein the change or migration is effected such that there is substantially no system interruption.

2. A method as recited in claim 1, wherein said changes include making a software upgrade;

moving a logical or physical device from a first location to a second location;

moving said logical or physical device from a first computer system to a second computer system; and

making a change from a first version of said application to a second version.

3. A method as recited in claim 2, wherein the migration is a complete migration in which all devices are migrated.

4. A method as recited in claim 2, wherein said migration is a partial migration in which only selected devices are migrated.

5. A method as recited in claim 2, wherein, once the change or migration begins, any new inputs or class to the device are routed first to the second version of said application and, if the second version of said application is not ready to receive the input, then to the first version of said application.

6. A method as recited in claim 2, wherein, once the change or migration begins, any new inputs or calls to a device are routed first to the first version of said application, and, if the first version of said application is not yet ready to receive the input, then to the second version of said application.

7. A method as recited in claim 2, wherein the migration comprises three phases, including a pre-migration phase, an on-line migration phase, and a post-migration phase.

8. A method as recited in claim 7, wherein said pre-migration phase comprises:

(1) system flat-file updating;

(2) data verification;

(3) dumping selected system and file variables;

(4) loading the second version of said application; and

,

(5) loading selected data sets.

9. A method as recited in claim 7, wherein said on-line migration phase comprises:

(1) selecting a scope of migration;

(2) disabling callflows and polling;

(3) initiating a multiple migration session;

(4) transferring selected devices or mailboxes from the first application to the second application;

(5) updating existing files; and

(6) finding and evaluating errors.

10. A method as recited in claim 7, wherein, in said post-migration phase, the first version of said application is deleted.

11. A method for changing or migrating a messaging system including an application and a plurality of user mailboxes, comprising the steps of:

(A) creating a new version of said messaging system while keeping said new version of said messaging system in a same location as an old version of said messaging system, wherein said new version of said messaging system comprises a software upgrade; and

(B) using said new version of said messaging system for a period of time before removing said old version of said messaging system;

wherein the change or migration is effected such that there is substantially no system interruption.

12. The method of claim 11, wherein said new version of said messaging system comprises a software upgrade to said application.

13. The method of claim 11, wherein said new version of said messaging system comprises a software upgrade to one or more of said plurality of mailboxes.

14. The method of claim 11, wherein said method is complete when all of said plurality of user mailboxes are changed or migrated.

15. The method of claim 11, wherein said method is partially complete when only selected mailboxes of said plurality of user mailboxes are changed or migrated.

16. The method of claim 11, wherein, once said changing or migrating begins, any new inputs or calls to said messaging system are routed first to said new version of said messaging system, and if said new version of said messaging system is not yet ready to receive said input, then to said old version of said messaging system.

17. The method of claim 11, wherein, once said change or migration begins, any new inputs or calls to said device are routed first to said old version of said messaging system, and if said old version of said messaging system is not yet ready to receive said input, then to said new version of said messaging system.

18. The method of claim 11, wherein said changing or migrating comprises three phases, including a pre-migration phase, an on-line migration phase, and a post-migration phase.

19. The method of claim 18, wherein said pre-migration phase comprises:

(1). updating a system flat-file;

(2). verifying data;

(3). dumping selected system and file varaiables;

(4). loading said new version of said messaging system; and

,

(5). loading selected data sets.

20. The method of claim 18, wherein said on-line migration phase comprises:

(1). selecting a scope of migration;

(2). disabling callflows and polling;

(3). initiating a multiple migration session;

(4). transferring selected mailboxes from said new version of said messaging system to said old version of said messaging system;

(5). updating existing files; and

,

(6). finding and evaluating errors.

21. The method of claim 18, wherein, in said post-migration phase, said old version of said messaging system is deleted.