Management and diagnosis of telephonic devices

• US 9,032,079 B2
• Filed: 06/26/2007
• Issued: 05/12/2015
• Est. Priority Date: 06/26/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Appiah, Madan Mohan R., Chandrasekaran, Subramanian
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US11/768,809
• Publication Number:
  US 20090003533A1
• Time in Patent Office: 2,877 Days
• Field of Search: 709/220, 709/223, 709/224
• US Class Current: 709/227
• CPC Class Codes: H04M 2203/052 software update
• CPC Class Codes: H04M 3/08 Indicating faults in circuits or apparatus
• CPC Class Codes: H04M 3/22 Arrangements for supervision, monitoring or testing
• CPC Class Codes: H04M 3/28 Automatic routine testing ; Fault testing; Installation testing; Test methods, test equipment or test arrangements therefor
• CPC Class Codes: H04M 3/42178 by downloading data to substation equipment

Abstract

Systems and methods of managing and diagnosing enterprise telephonic devices are disclosed. A provisioning request can be received from an enterprise telephonic device. The provisioning request can include a domain name system lookup request. An enterprise network address of a device management server can be provided to the enterprise telephonic device. A voice data link can be established with the enterprise telephonic device so as to permit the enterprise telephonic device to communicate over a data network with endpoint telephonic devices. The device management server can periodically receive heartbeat data from the enterprise telephonic device. The heartbeat can be indicative of a status of at least one functionality of the enterprise telephonic device. The enterprise telephonic device can provide diagnostic logs when requested by the device management server. In addition, the enterprise telephonic device can be configured to periodically request software updates.

Claims

1. A method of managing self-provisioned enterprise telephonic devices, comprising:

receiving a self-provisioning request from an enterprise telephonic device, the enterprise telephonic device being non-provisioned, at a device management server in an enterprise network, wherein the enterprise network does not have previous data associated with the enterprise telephonic device, the self-provisioning request including a domain name system lookup request and a request to register as an element of the enterprise network;

providing to the enterprise telephonic device an enterprise network address that permits the enterprise telephonic device to communicate with the device management server;

establishing a voice data link with the enterprise telephonic device so as to permit the enterprise telephonic device to communicate over a data network with endpoint telephonic devices; and

periodically receiving at the device management server heartbeat data from the enterprise telephonic device, the heartbeat data being indicative of a status of at least one functionality of the enterprise telephonic device, including a voice communication function.

2. The method of claim 1, further comprising receiving a diagnostic log if requested by the device management server.

3. The method of claim 1, wherein the domain name system lookup request includes a service record that requests authentication by the device management server.

4. The method of claim 1, wherein establishing the voice data link with the enterprise telephonic device includes dynamically providing an IP address to the enterprise telephonic device.

5. The method of claim 1, further comprising querying an update software database to determine if there are any software updates available.

6. The method of claim 1, further comprising filtering diagnostic data received in the diagnostic log from the enterprise telephonic device, and providing the filtered diagnostic data to an update service for determination as to whether software updates are necessary or available.

7. The method of claim 1, further comprising:

receiving, at the device maintenance server, event data from the enterprise telephonic device, the event data being associated with an occurrence of an event;

analyzing, at the device maintenance server, the heartbeat data and the event data received from the enterprise telephonic device to determine whether there is a voice communication malfunction in the enterprise telephonic device; and

if it is determined that there is a voice communication malfunction in the enterprise telephonic device, requesting from the enterprise telephonic device a diagnostic log indicative of the occurrence of the event.

8. The method of claim 7, further comprising filtering diagnostic data received in the diagnostic log from the enterprise telephonic device, and providing the filtered diagnostic data to an update service for determination as to whether software updates are necessary or available.

9. The method of claim 7, further comprising providing software updates to the enterprise telephonic device if there is a voice communication malfunction in the enterprise telephonic device.

10. The method of claim 7, further comprising checking an update software database to determine whether there are software updates available.

11. A device management server apparatus comprising:

a processing unit;

a communication device;

a memory containing instructions, that when executed by the processing unit, cause the apparatus to;

receive a self-provisioning request from an enterprise telephonic device, the enterprise telephonic device being non-provisioned, at the device management server in an enterprise network via the communication device, wherein the enterprise network does not have previous data associated with the enterprise telephonic device, the self-provisioning request including a domain name system lookup request and a request to register as an element of the enterprise network;

provide to the enterprise telephonic device an enterprise network address that permits the enterprise telephonic device to communicate with the device management server;

establish a voice data link with the enterprise telephonic device so as to permit the enterprise telephonic device to communicate over a data network with endpoint telephonic devices; and

periodically receive, at the device management server, heartbeat data from the enterprise telephonic device, the heartbeat data being indicative of a status of at least one functionality of the enterprise telephonic device, including a voice communication function.

12. The device management server apparatus of claim 11, the memory further comprising instructions that when executed by the processing unit, cause the apparatus to:

receive a request from the enterprise telephonic device at the device management server to determine whether a software update is available;

request, from an update service that is separate from the device management server, an indication of whether an update service software is available for downloading;

request the update service software from the update service when the update service provides the indication to the device management service that update service software is available; and

provide, to the enterprise telephonic device, an indication that a software update is available when the enterprise telephonic device has not previously received the update service software.

13. The device management server apparatus of claim 12, the memory further comprising instructions that when executed by the processing unit, cause the apparatus to:

store the update service software in an update software database.

14. The device management server apparatus of claim 13, the memory further comprising instructions that when executed by the processing unit, cause the apparatus to:

receive, at the device maintenance server, event data from the enterprise telephonic device, the event data being associated with an occurrence of an event;

analyze, at the device maintenance server, the heartbeat data and the event data received from the enterprise telephonic device to determine whether there is a voice communication malfunction in the enterprise telephonic device; and

request, from the enterprise telephonic device, a diagnostic log indicative of the occurrence of the event when it is determined that there is a voice communication malfunction in the enterprise telephonic device.

15. The device management server apparatus of claim 14, wherein at least one of the update service software and the diagnostic log is stored on a share point server, the memory further comprising instructions that when executed by the processing unit, cause the apparatus to:

communicate with the share point server to receive at least one of the diagnostic log and update service software.