Health monitor for a geographically distributed voice messaging system

• US 20060239423A1
• Filed: 06/29/2005
• Published: 10/26/2006
• Est. Priority Date: 06/30/2004
• Status: Active Grant

• Current Assignee: Glenayre Electronics Incorporated (EDCI Holdings Incorporated)
• Original Assignee: Glenayre Electronics Incorporated (EDCI Holdings Incorporated)
• Inventors: Lowman, Philip L., Plotky, Jon S., Spencer, James H., Moraes, Ian M., Archer, Shafford R. Jr.
• Granted Patent: US 7,680,254 B2
• Time in Patent Office: Days
• US Class Current: 379/88.180
• CPC Class Codes: H04M 3/24 with provision for checking the normal operation
• CPC Class Codes: H04M 3/53325 Interconnection arrangements between voice mail systems

Abstract

A health monitor subsystem detects and responds to faults within a geographically disperse voice messaging system. The health monitor subsystem comprises agent, manager, interface, and common processes. The agent process monitors a respective voice messaging system component operative on the host. The manager process monitors and manages detected faults on the host. The interface process exposes a status responsive to the host. The common process monitors and manages a platform of hosts. The health monitor subsystem enables monitoring at the component, host, and platform levels.

Claims

1. A health monitor subsystem configured to detect and respond to faults within a geographically disperse voice messaging system, the subsystem comprising:

an agent process configured to monitor a respective voice messaging system component operative on a host;

a manager process coupled to the agent process and configured to monitor and manage detected faults on the host;

an interface process coupled to the manager process and configured to expose a status associated with the host;

a common process coupled to the manager process and configured to monitor and manage a platform comprising a plurality of hosts.

2. The health monitor subsystem of claim 1, wherein the agent process is further configured to restart the respective voice messaging system component.

3. The health monitor subsystem of claim 1, wherein the agent process is further configured to register with and send periodic messages that include status information to the manager process.

4. The health monitor subsystem of claim 1, wherein the agent process is configured to receive a manager process request.

5. The health monitor subsystem of claim 1, wherein the manager process communicates with a hardware mechanism to restart the host.

6. The health monitor subsystem of claim 1, wherein the manager process communicates alarm conditions.

7. The health monitor subsystem of claim 1, wherein the manager process comprises dependencies among components operative on the host.

8. The health monitor subsystem of claim 1, wherein an application programming interface is integrated with one of the agent, manager, interface, and common processes, the application programming interface configured to communicate at least one of registration, fault, and request information.

9. The health monitor subsystem of claim 8, wherein the request information is associated with an operational condition.

10. The health monitor subsystem of claim 8, wherein the request information is associated with a command operative to disable a component.

11. A method for monitoring conditions across a geographically disperse voice message system, comprising:

monitoring a first status condition responsive to a respective voice messaging system component operative on a host;

monitoring a second status condition responsive to the operation of a respective host within the voice messaging system;

monitoring a third status condition responsive to the operation of a respective platform; and

providing a network accessible mechanism for discerning the operative health of one of the platform, the host, and the voice messaging system component.

12. The method of claim 11, wherein monitoring a first status condition comprises periodically receiving information transmitted from the respective voice messaging system component.

13. The method of claim 11, wherein monitoring a first status condition comprises periodically polling the respective voice messaging system component for information.

14. The method of claim 11, wherein monitoring a first status condition comprises inserting an agent process in the respective voice messaging system component.

15. The method of claim 11, wherein monitoring a second status condition comprises inserting a manager process in the respective host.

16. The method of claim 11, wherein monitoring a third status condition comprises providing a common process operative within a computing device remote from a host coupled to the common process.

17. The method of claim 11, wherein knowledge of component dependencies is distributed across a plurality of hosts operative within the voice message system.

18. The method of claim 11, further comprising:

responding to an undesired condition within a component process by restarting the component process.

19. The method of claim 11, further comprising:

responding to an undesired condition within a host by restarting the host.

20. The method of claim 11, wherein providing a network accessible mechanism comprises generating a graphical user interface that enables an operator to view the health of the voice messaging system on the platform, host, and component levels.