Methods and systems for processing calls in a packet network using peer call servers

• US 6,775,277 B1
• Filed: 02/18/2000
• Issued: 08/10/2004
• Est. Priority Date: 06/04/1999
• Status: Expired due to Fees

• Current Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Li, Xuewen, Ress, David P., Hinchey, Allan Jeffrey
• Primary Examiner(s): NGUYEN, BRIAN D
• Application Number:
  US09/507,277
• Time in Patent Office: 1,635 Days
• Field of Search: 370/389, 370/352, 370/353, 370/392, 370/395.3, 370/395.31, 370/395.32, 370/395.5, 370/395.52, 370/400, 370/401, 370/465, 370/466, 370/475, 370/355, 370/356, 370/410, 370/522, 709/200, 709/201, 709/203, 709/223, 709/227, 709/238
• US Class Current: 370/389
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/401 wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42

Abstract

A method for processing calls in a packet network using peer call servers includes receiving a setup message from a first gateway in the packet network. The setup message includes a first address for a called endpoint. The call server that receives the setup message translates the message into a call server ID and an endpoint ID specifying the remote call server corresponding to the called party. The call server sends the call server ID and the endpoint ID to the remote call server. The remote call server obtains a call signaling transport address to the called end user based in the endpoint ID.

Claims

1. A method for correlating call signaling messages associated with multiple calls and sent over a single network connection, the method comprising:

(a) at a first call agent, formulating a first call signaling message associated with the first call, the fist call signaling message having a first half call ID including a first allocation parameter for indicating a call originator and a first call counter for identifying the first call;

(b) setting the first allocation parameter to a first value for identifying the first call agent as originator of the first call and the first call counter to a first count value for identifying the first call;

(c) transmitting the first call signaling message to a second call agent over a first network connection;

(d) at the second call agent, in response to receiving the first message, formulating a second call signaling message including a second half call ID having a second allocation parameter and a second call counter;

(e) setting the second allocation parameter to a second value for identifying the second call agent as non-originator of the first call and setting the second call counter to the first count value; and

(f) transmitting the second call signaling message to the first call agent over the first network connection.

2. The method of claim 1 wherein the first network connection is a transport control protocol (TCP) connection.

3. The method of claim 2 wherein the TCP connection is a multi-user TCP connection encapsulated in a multi-user signaling channel object.

4. The method of claim 1 comprising, at the first call agent, formulating a third call signaling message relating to a second call, the third call signaling message including a call reference parameter having a third allocation parameter and a third call counter, setting the third allocation parameter to the first value for identifying the first call agent as originator of the second call and setting the third call counter to a second count value for identifying the second call.

5. The method of claim 4 comprising transmitting the third call signaling message to the second call agent over the first network connection.

6. The method of claim 5 comprising, at the second call agent, in response to receiving the third call signaling message, formulating a fourth call signaling message including a call reference parameter having a fourth allocation parameter and a fourth call counter and setting the fourth allocation parameter to the second value and setting the fourth call counter to the second count value.

7. The method of claim 6 comprising transmitting the third call signaling message to the first call agent over the first network connection.