Method and apparatus for merging call components during call reconstruction

• US 20060067274A1
• Filed: 01/27/2005
• Published: 03/30/2006
• Est. Priority Date: 09/30/2004
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Technology Corporation Miami Lakes FLA US
• Inventors: Velamala, Vivekananda, Gillespie, Donald E., Marwah, Manish
• Granted Patent: US 7,366,110 B2
• Time in Patent Office: Days
• US Class Current: 370/331
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1083 In-session procedures
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

The present invention is directed to a secondary communication server 216 for assuming control of a communication formerly controlled by a primary communication server 212 in the event of a failure, comprising:

• • (a) an input operable to (i) receive, from a first communication node 204a, first communication information, wherein the first communication information is associated with the communication and comprises a first node identifier 236a and/or a communication identifier 240a, the first node identifier 236a is associated with a second communication node 204b, the communication identifier is associated with the communication, and the second communication node 204b comprises second communication information associated with the communication and (ii) thereafter receive, from the second communication node 204b, the second communication information; and
  • (b) a reconstruction agent 228 operable to identify the second communication information based on the first node identifier 236a and/or communication identifier 240a.

Claims

1. A method for migrating a communication from a first to a second communication server, comprising:

(a) determining that at least one communication is to be controlled by a second communication server, wherein the at least one communication was formerly controlled by a first communication server;

(b) receiving, from a first communication node, first communication information, wherein the first communication information is associated with the at least one communication and comprises at least one of a first node identifier and a communication identifier, the communication identifier is associated with the at least one communication, the second communication node comprises second communication information associated with the at least one communication and/or second node, and the first node identifier is associated with second communication information;

(c) thereafter receiving, from a second communication node, the second communication information; and

(d) identifying the second communication information based on the at least one of a first node identifier and communication identifier.

2. The method of claim 1, wherein the at least one of a first node identifier and communication identifier is the first node identifier.

3. The method of claim 1, wherein the at least one of a first node identifier and communication identifier is the communication identifier.

4. The method of claim 1, wherein the at least one communication spans at least two media gateways and wherein step (a) is in response to detection by the at least two media gateways of a failure in a signaling channel with the primary communication server.

5. The method of claim 2, wherein third communication information is received from a third communication node, wherein at least the second, third, and fourth communication nodes are involved in at least a second communication, and wherein the identifying step (d) comprises:

(e) determining whether the third communication information comprises a third node identifier associated with the fourth communication node;

(f) when the third communication information comprises the third node identifier, determining whether fourth communication information has been received from the fourth communication node associated with the third node identifier;

(g) when the fourth communication information has not been received, determining whether any of the first and second communication information comprise the third node identifier; and

(h) when the fourth communication information has been received or when any of the first and second communication information comprises the third node identifier, associating the at least a second communication with the third communication node.

6. The method of claim 5, wherein the third information comprises a communication identifier identifying the at least a second communication and further comprising:

(g) when the fourth communication information has been not received and when any of the first and second communication information do not comprise the third node identifier, determining whether the fourth communication information comprises the communication identifier; and

(h) when the fourth communication identifier comprises the communication identifier, performing step (h).

7. The method of claim 1, wherein the first and second communication information each comprise a common communication identifier, the first and second communication information each comprise, respectively, first and second node identifiers, and the first and second node identifiers are different.

8. The method of claim 1, wherein the first node identifier is at least one of an electronic address of the second communication node, an identifier of a data structure in the second communication node, and an identifier of at least one resource of the second communication node and wherein the data structure and at least one resource are associated with the at least one communication.

9. The method of claim 8, wherein the first node identifier comprises an resource identifier associated with a second ephemeral termination involved in the at least one communication and a context identifier associated with second context involved in the at least one communication and wherein the second ephemeral termination and second context are each in the second communication information.

10. The method of claim 9, wherein the first node identifier is saved by the first communication node as a property of a first context stored by the first communication node, the first context being associated with the at least one communication.

11. A computer readable medium comprising instructions to perform the steps of claim 1.

12. A logic circuit operable to perform the steps of claim 1.

13. A secondary communication server for assuming control of at least one communication formerly controlled by a primary communication server in the event of a failure, comprising:

(a) an input operable to (i) receive, from a first communication node, first communication information, wherein the first communication information is associated with the at least one communication and comprises at least one of a first node identifier and a communication identifier, the first node identifier is associated with a second communication node, the communication identifier is associated with the at least one communication, and the second communication node comprises second communication information associated with the at least one communication and/or second node and (ii) thereafter receive, from the second communication node, the second communication information; and

(b) a reconstruction agent operable to identify the second communication information based on the at least one of a first node identifier and communication identifier.

14. The server of claim 13, wherein the at least one of a first node identifier and communication identifier is the first node identifier and wherein the first node identifier is associated with the second communication information.

15. The server of claim 13, wherein the at least one of a first node identifier and communication identifier is the communication identifier.

16. The server of claim 13, wherein the at least one communication spans at least two media gateways.

17. The server of claim 14, wherein third communication information is received from a third communication node, wherein at least the second, third, and fourth communication nodes are involved in at least a second communication, and wherein the identifying operation comprises the sub-operations of:

determining whether the third communication information comprises a third node identifier associated with the fourth communication node;

when the third communication information comprises the third node identifier, determining whether fourth communication information has been received from the fourth communication node associated with the third node identifier;

when the fourth communication information has not been received, determining whether any of the first and second communication information comprise the third node identifier; and

when the fourth communication information has been received or when any of the first and second communication information comprises the third node identifier, associating the at least a second communication with the third communication node.

18. The server of claim 17, wherein the third information comprises a communication identifier identifying the at least a second communication and the agent is further operable to:

when the fourth communication information has been not received and when any of the first and second communication information do not comprise the third node identifier, determine whether the fourth communication information comprises the communication identifier; and

when the fourth communication identifier comprises the communication identifier, associate the at least a second communication with the third communication node.

19. The server of claim 13, wherein the first and second communication information each comprise a common communication identifier, the first and second communication information each comprise, respectively, first and second node identifiers, and the first and second node identifiers are different.

20. The server of claim 14, wherein the first node identifier is at least one of an electronic address of the second communication node, an identifier of a data structure in the second communication node, and an identifier of at least one resource of the second communication node and wherein the data structure and at least one resource are associated with the at least one communication.

21. The server of claim 20, wherein the first node identifier comprises an resource identifier associated with a second ephemeral termination involved in the at least one communication and a context identifier associated with second context involved in the at least one communication and wherein the second ephemeral termination and second context are each in the second communication information.

22. The server of claim 21, wherein the first node identifier is saved by the first communication node as a property of a first context stored by the first communication node, the first context being associated with the at least one communication.

23. A first media gateway, comprising:

a first node identifier associated with a second media gateway, the first and second media gateways handling a common communication, the common communication involving an inter gateway connection between the first and second media gateways, and the first node identifier being further associated with the common communication.

24. The gateway of claim 23, wherein the first node identifier is at least one of an electronic address of the second gateway, an identifier of a data structure in the second gateway, and an identifier of at least one resource of the second gateway and wherein the data structure and at least one resource are associated with the common communication.

25. The gateway of claim 24, wherein the first node identifier comprises an resource identifier associated with a second ephemeral termination involved in the common communication and a context identifier associated with second context involved in the common communication and wherein the second ephemeral termination and second context are each stored in the second gateway.

26. The gateway of claim 25, wherein the first node identifier is saved by the first gateway as a property of a first context stored by the first gateway, the first and second context each being associated with the common communication.