Extensible diagnostic tool

• US 8,559,605 B2
• Filed: 02/07/2005
• Issued: 10/15/2013
• Est. Priority Date: 02/07/2005
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: Forney, David, Frifeldt, Heine, Shaffer, Anthony
• Primary Examiner(s): Phan, Joseph T
• Application Number:
  US11/053,270
• Publication Number:
  US 20060177008A1
• Time in Patent Office: 3,172 Days
• Field of Search: 379/88.11, 379/88.22, 717/100
• US Class Current: 379/88.22
• CPC Class Codes: H04M 3/22 Arrangements for supervision, monitoring or testing
• CPC Class Codes: H04M 3/5307 for recording messages comprising any combination of audio and non-audio components

Abstract

An integrated messaging system for performing various types of messaging across different types of networks, including integrated user interfaces and administrator interfaces. Embodiments include a communication server that couples among networks of different types, and an interface module that couples to the communication server. The interface module may be hosted on a messaging server of a network. The interface module pulls various user information from the messaging server, including information relevant to at least the network that includes the messaging server. A cache couples to the communication server and to the interface module to hold information from the communication server and/or the user information pulled from messaging server. The interface module directs a message from the messaging server and/or the cache to at least one device on the networks using the user information.

Claims

1. A method for providing diagnostics, the method comprising:

receiving, by a CPU, identification of diagnostic compiled code;

receiving, by the CPU, identification of diagnostic source code;

compiling, by the CPU, the diagnostic source code on a target system on which the diagnostics are to be performed;

gathering, by the CPU, first information about first diagnostic methods included within the diagnostic compiled code;

gathering, by the CPU, second information about second diagnostic methods included within the compiled diagnostic source code resulting from the compiling;

based on the first and second gathered information, running, by the CPU, the first and second diagnostic methods on the target system; and

gathering, by the CPU, results of the first and second diagnostic methods.

2. The method of claim 1, including using reflection to gather information about the diagnostic methods.

3. The method of claim 1, wherein the compiled code comprises .NET framework assembly code.

4. The method of claim 1, wherein the target system comprises a voicemail system.

5. The method of claim 1, wherein the target system comprises a messaging and collaboration server.

6. The method of claim 1, wherein the diagnostic methods include a diagnostic of a greeting in a voicemail system.

7. The method of claim 1, wherein the diagnostic methods include gathering version information about the installed target system assemblies.

8. The method of claim 1, wherein the diagnostic methods include verifying that target system service account information is present in a registry.

9. The method of claim 1, wherein the diagnostic methods include checking ability to impersonate an account, including testing a password for the account.

10. The method of claim 1, wherein the diagnostic methods include checking correctness of path information in the registry for software of the target system.

11. The method of claim 1, wherein the diagnostic methods include checking correctness of installation of web software on the target system.

12. The method of claim 1, wherein the diagnostic methods include checking for presence of source configurable rules for user extensions on the target system.

13. The method of claim 1, wherein the diagnostic methods include verifying permissions of the target system service account for the target system web service software to run.

14. The method of claim 1, wherein the diagnostic methods include verifying permissions of the target system service account for the target system web application software to run.

15. The method of claim 1, wherein the diagnostic methods include verifying permissions of the target system service account for the target system email system extension software to run.

16. The method of claim 1, wherein the diagnostic methods include verifying permissions of the target system service account to access identity key of service account in a registry.

17. The method of claim 1, wherein the diagnostic methods include verifying a pin code.

18. A method for providing diagnostics, the method comprising:

a processor receiving identification of diagnostic code;

the processor gathering information about diagnostic methods included within the diagnostic code;

in software running on a target system on which the diagnostic code is to be run, the processor identifying, with the cooperation of a CPU, parameters used by code;

the processor receiving values for parameters;

the processor running diagnostic code on the target system using the parameters; and

the processor gathering results of the diagnostic code.

19. The method of claim 18, including using reflection to gather information about the diagnostic methods.

20. The method of claim 18, wherein the compiled code comprises .NET framework assembly code.

21. The method of claim 18, wherein the target system comprises a voicemail system.

22. The method of claim 18, wherein the target system comprises a messaging and collaboration server.

23. A method for providing diagnostics for a target system, the method comprising:

a processor providing diagnostic framework computer code on the target system;

the processor providing source code of diagnostic modules on the target system;

the processor providing the source code of the diagnostic modules to the framework computer code;

the processor compiling, by a CPU, the source code of the diagnostic modules; and

the processor running the compiled diagnostic modules on the target system.

24. A diagnostic tool comprising:

logic, executed by a processor, that receives identification of diagnostic compiled code;

logic, executed by a processor, that receives identification of diagnostic source code;

logic, executed by the processor, cooperating with a CPU, that causes the diagnostic source code to be compiled;

logic, executed by the processor, that gathers first information about first diagnostic methods included within the diagnostic compiled code;

logic, executed by the processor, that gathers second information about second diagnostic methods included within the compiled diagnostic source code resulting from the compiling;

logic, executed by the processor, that, based on the first and second gathered information, runs the first and second diagnostic methods; and

logic, executed by the processor, that gathers results of the first and second diagnostic methods.

25. The diagnostic tool of claim 24, wherein the logic comprises compiled assembly.

26. The diagnostic tool of claim 24, wherein the logic comprises software stored on a computer readable medium.

27. An interface module (IM) comprising:

logic, executed by a processor, to communicate with a messaging communication server (MCS) that processes voice messages;

logic, executed by the processor, to communicate with a messaging and collaboration server (MSERV) that stores voice messages and user information; and

a diagnostic tool comprising;

logic, executed by the processor, that receives identification of diagnostic compiled code;

logic, executed by the processor, that receives identification of diagnostic source code;

logic, executed by the processor, cooperating with a CPU, that causes the diagnostic source code to be compiled;

logic, executed by the processor, that gathers first information about diagnostic methods included within the diagnostic compiled code;

logic, executed by the processor, that gathers second information about second diagnostic methods included within the compiled diagnostic source code resulting from the compiling;

logic, executed by the processor, that, based on the first and second gathered information, runs the first and second diagnostic methods; and

logic, executed by the processor, that gathers results of the first and second diagnostic methods.

28. The IM of claim 27, wherein the logic comprises software.

29. The IM of claim 27, wherein the logic comprises software stored on a computer readable medium.

30. A communication system comprising:

a messaging communication server (MCS) that processes voice messages;

a messaging and collaboration server (MSERV) that stores voice messages and user information; and

a diagnostic tool that diagnoses aspects of the communication system, the diagnostic tool comprising;

logic, executed by a processor, that receives identification of diagnostic compiled code;

logic, executed by the processor, that receives identification of diagnostic source code;

logic, executed by the processor, that causes the diagnostic source code to be compiled;

logic, executed by the processor, that gathers first information about diagnostic methods included within the diagnostic compiled code;

logic, executed by the processor, that gathers second information about second diagnostic methods included within the compiled diagnostic source code resulting from the compiling;

logic, executed by the processor, that, based on the first and second gathered information, runs the first and second diagnostic methods; and

logic, executed by the processor, that gathers results of the first and second diagnostic methods.

31. The system of claim 30, wherein the diagnostic tool is included within the MSERV.