System and method for providing data on voicemail appliance

• US 20060177014A1
• Filed: 02/07/2005
• Published: 08/10/2006
• Est. Priority Date: 02/07/2005
• Status: Abandoned Application

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Inventors: Birkhahn, Lutz, Skakkebaek, Jens
• Application Number:
  US11/053,538
• Publication Number:
  US 20060177014A1
• Time in Patent Office: Days
• US Class Current: 379/67.100
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04M 2203/4509 Unified messaging with single point of access to voicemail and other mail or messaging systems
• CPC Class Codes: H04M 2203/4536 Voicemail combined with text-based messaging
• CPC Class Codes: H04M 3/53 Centralised arrangements for recording incoming messages , i.e. mailbox systems
• CPC Class Codes: H04M 3/533 Voice mail systems

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 messaging communication server (MCS), comprising:

logic that provides services related to voice messaging including processing of voicemail messages;

a first storage for configuration information related to at least some of the services;

an interface for connection to a network that includes at least a second storage separate from the MCS; and

logic that causes configuration information received from the second storage to be loaded on the MCS and stored in the first storage on the MCS.

2. The MCS of claim 1, including logic that causes the MCS to automatically request configuration information.

3. The MCS of claim 1, including logic that causes the MCS to request configuration information in accordance with a time schedule.

4. The MCS of claim 1, including logic that causes the MCS to request configuration information after occurrence of an event.

5. The MCS of claim 1, wherein the configuration information includes a network address of an interface module coupled to the MCS.

6. The MCS of claim 1, wherein the configuration information includes a network address of the MCS.

7. The MCS of claim 1, wherein the configuration information includes telephone numbers.

8. The MCS of claim 1, wherein the configuration information includes voicemail numbers.

9. The MCS of claim 1, wherein the logic includes code.

10. The MCS of claim 1, wherein the first storage comprises volatile memory.

11. The MCS of claim 1, wherein the first storage includes a magnetic drive.

12. A method comprising:

in a messaging communication server (MCS), requesting configuration information for the MCS from a source outside of the MCS;

receiving the configuration information on the MCS;

automatically installing the received configuration information on the MCS; and

using the installed configuration information on the MCS to provide services related to voice messaging including processing of voicemail messages.

13. The method of claim 12, wherein the requesting occurs automatically.

14. The method of claim 12, wherein the requesting occurs automatically upon coupling of the MCS into a new environment.

15. The method of claim 12, wherein the requesting occurs in accordance with a time schedule.

16. The method of claim 12, wherein the requesting occurs in response to occurrence of an event.

17. The method of claim 16, including polling the environment of the MCS to determine occurrence of the event.

18. The method of claim 16, including automatically receiving notification of occurrence of the event.

19. The method of claim 16, including determining occurrence of the event by receipt of a broadcast message.

20. The method of claim 16, wherein the event comprises change of data availability.

21. The method of claim 16, wherein the event comprises addition of another MCS in a network that includes the first MCS.

22. The method of claim 16, wherein the event comprises addition of an interface module (IM) operable with the MCS.

23. The method of claim 12, including:

requesting data other than configuration information for the MCS from a source outside of the MCS;

receiving the data on the MCS;

automatically installing the data on the MCS; and

using the installed data on the MCS to provide services related to voice messaging including processing of voicemail messages.

24. The method of claim 23, wherein the data includes voicemail messages.

25. The method of claim 23, wherein the data includes user data.

26. The method of claim 23, wherein the requesting of the data and the configuration information occurs automatically upon coupling of the MCS into a new environment.

27. The method of claim 23, wherein the requesting of the data and the configuration information occurs automatically upon detection of an error.