Background call validation

• US 20060256738A1
• Filed: 04/14/2006
• Published: 11/16/2006
• Est. Priority Date: 10/15/2004
• Status: Active Grant

• Current Assignee: Lifesize, Inc. (Enghouse Systems Limited)
• Original Assignee: Lifesize, Inc. (Enghouse Systems Limited)
• Inventors: Kenoyer, Michael L., Tracey, Jonathan W.
• Granted Patent: US 8,149,739 B2
• Time in Patent Office: Days
• US Class Current: 370/260
• CPC Class Codes: H04L 12/1818 Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
• CPC Class Codes: H04L 43/0811 by checking connectivity

Abstract

A management system may test network paths prior to scheduled calls. Testing network paths may include one endpoint placing a test call to an endpoint on the other end of the path. Various characteristics of the network path may be tested. If the network path fails and/or in some way does not meet the predefined characteristics for the call, an administrator may be notified and/or alternate network path may be detected and tested. The call may be rescheduled if a satisfactory network path is not found in time.

Claims

1. A method, comprising:

providing at least two devices coupled to each other through a network path; and

testing the network path between the at least two devices using at least one protocol to be used in conducting a future call between the at least two devices.

2. The method of claim 1, wherein the at least one protocol is determined according to deducible capability numbering (DCN) assigned to at least one device of the at least two devices.

3. The method of claim 1, wherein testing the network path between the at least two devices comprises at least one of the at least two devices automatically calling at least one other device of the at least two devices.

4. The method of claim 1, wherein the at least two devices are videoconferencing devices.

5. The method of claim 1, wherein testing is performed without notifying an end user.

6. The method of claim 1, further comprising testing the network path between the at least two devices at predetermined time intervals.

7. The method of claim 6, wherein shorter predetermined time intervals are used prior to scheduled calls with more severity.

8. The method of claim 1, further comprising testing at least one alternate network path between the at least two devices.

9. The method of claim 1, further comprising notifying an administrator if a problem is detected during the testing of the network path.

10. The method of claim 9, further comprising suggesting an alternate network path to the administrator if a problem is detected while testing the network path between the at least two devices.

11. The method of claim 1, further comprising:

testing at least one alternate network path between the at least two devices;

wherein a preferred network path of the tested network paths may be determined and used for a call.

12. The method of claim 1, wherein testing the network path using at least one protocol includes testing at least one of an audio path characteristic, video path characteristic, bandwidth, packet loss, and jitter.

13. The method of claim 1, further comprising:

scheduling a call prior to testing the network path between the at least two devices; and

rescheduling the call if a problem is detected during testing of the network path.

14. The method of claim 1, wherein testing the network path comprises transmitting audio or video information to one of the at least two devices;

wherein the device then transmits the audio or video information back to the other of the at least two devices.

15. A method, comprising:

testing a primary network path between at least two devices using at least one protocol to be used in conducting a future call between the at least two devices;

determining an alternate network path between the at least two devices; and

testing the alternate network path.

16. The method of claim 15, further comprising using the alternate network path for the future call if the primary network path fails.

17. A method, comprising:

scheduling a call between at least two network devices;

testing a network path between the at least two network devices using at least one protocol to be used in conducting a future call between the at least two devices; and

wherein the call is rescheduled if the network path fails.

18. The method of claim 17, wherein testing the network path between the at least two devices comprises at least one of the at least two devices calling at least one other device of the at least two devices.

19. The method of claim 17, further comprising testing the network path between the at least two devices at predetermined time intervals.

20. The method of claim 17, further comprising testing at least one alternate network path between the at least two devices.