On demand capability exchange

• US 7,243,159 B1
• Filed: 03/14/2003
• Issued: 07/10/2007
• Est. Priority Date: 03/14/2003
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Jayasimha, Mysore Raghavan, Daga, Prakash
• Primary Examiner(s): Jaroenchonwanit; Bunjob
• Assistant Examiner(s): Chang; Julian
• Application Number:
  US10/388,846
• Time in Patent Office: 1,579 Days
• Field of Search: 709/237
• US Class Current: 709/237
• CPC Class Codes: H04L 65/1053 IP private branch exchange [PBX] functionality entities or arrangements circuit switched PBXs H04M3/00
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 7/0072 Speech codec negotiation H04L65/1069 takes precedence

Abstract

A network device is disclosed. The network device has a port to allow reception of an incoming call at a first endpoint and a memory to store endpoint identifiers and associated capability information. A processor in the network device is to determine an identifier for a second endpoint from the incoming call, access associated capability information for the second endpoint, if it exists, set a first field value depending upon any associated capability information available, transmit a message including a first field value and then perform a capabilities exchange with the second endpoint, if necessary, depending upon the first field value and a second field value received from the other endpoint.

Claims

1. A network device, comprising:

a port to allow reception of an incoming call at a first endpoint;

a memory to store endpoint identifiers and associated capability information; and

a processor to;

determine an identifier of a second endpoint from the incoming call;

access the associated information for the second endpoint, if it exists;

set a first field value for the first endpoint to one of status codes including unknown, known and changed, and known and unchanged, depending upon the availability of any associated capability information;

transmit a message including the first field value from the first endpoint to the second endpoint; and

perform a capabilities exchange with the second endpoint, if necessary, depending upon the first field value of the first endpoint and a second field value received from the second endpoint, where the second field value is set to one of status codes including unknown, known and changed, and known and unchanged,

wherein capabilities exchange is avoided only when the first field value is set to known and unchanged and the received second field value is known and unchanged.

2. The network device of claim 1, wherein the first endpoint is an originating endpoint and the second endpoint is a terminating endpoint.

3. The network device of claim 2, wherein the first field value is a field setup value and the second field value is a field acknowledgement value.

4. The network device of claim 2, wherein the processor is further to set the first field value to one of either known and changed or unknown and to perform the capabilities exchange.

5. The network device of claim 1, wherein the first endpoint is a terminating endpoint and the second endpoint is an originating endpoint.

6. The network device of claim 5, wherein the first field value is a field acknowledgement value and the second field value is a field setup value.

7. The network device of claim 5, wherein the processor is further to set the first field value to one of either known and changed or unknown and to perform the capabilities exchange.

8. A method, the method comprising:

receiving an incoming call at a first endpoint;

identifying a second endpoint associated with the incoming call;

accessing capability information for the second endpoint, if it exists;

determining if capability information for the first endpoint has changed;

setting a first field value for the first endpoint to one of status codes including unknown, known and changed, and known and unchanged, depending upon the capability information for at least one of the first and second endpoints;

transmitting a message to the second endpoint including the first field value; and

performing a capability exchange with the second endpoint, as necessary, depending upon the first field value of the first endpoint and a second field value received from the second endpoint, where the second field value is set to one of status codes including unknown, known and changed, and known and unchanged,

wherein capabilities exchange is avoided only when the first field value is set to known and unchanged and the received second field value is known and unchanged.

9. The method of claim 8, wherein setting a first field value further comprises setting the first field value to unknown based upon the capability information for the second endpoint.

10. The method of claim 8, wherein setting a first field value further comprises setting the first field value to known and changed based upon the capability information for the first endpoint.

11. The method of claim 8, wherein setting a first field value further comprises setting the first field value to known and unchanged based upon the capability information for the first endpoint.

12. The method of claim 8, the method further comprising receiving an acknowledgement message from the second endpoint containing the second field value.

13. The method of claim 8, the method further comprising receiving a setup message from the second endpoint containing the second field value.

14. A network device, comprising:

a means for allowing reception of an incoming call at a first endpoint;

a means for storing endpoint identifiers and associated capability information; and

a means for;

determining an identifier of a second endpoint from the incoming call;

accessing the associated information for the second endpoint, if it exists;

setting a first field value for the first endpoint to one of status codes including unknown, known and changed, and known and unchanged, depending upon the availability of any associated capability information;

transmitting a message including the first field value from the first endpoint to the second endpoint; and

performing a capabilities exchange with the second endpoint, if necessary, depending upon the first field value of the first endpoint and a second field value received from the second endpoint, where the second field value is set to one of status codes including unknown, known and changed, and known and unchanged, wherein capabilities exchange is avoided only when the first field value is set to known and unchanged and the received second field value is known and unchanged.

15. The network device of claim 14, the network device further comprising an originating endpoint.

16. The network device of claim 14, the network device further comprising a terminating endpoint.

17. An article of computer-readable code containing instructions that, when executed, cause a computer to:

receive an incoming call at a first endpoint;

identify a second endpoint associated with the incoming call;

access capability information for the second endpoint, if it exists;

determine if capability information for the first endpoint has changed;

set a first field value for the first endpoint to one of status codes including unknown, known and changed, and known and unchanged, depending upon the capability information for at least one of the first and second endpoints;

transmit a message to the second endpoint including the first field value; and

perform a capability exchange with the second endpoint, as necessary, depending upon the first field value of the first endpoint and a second field value received from the second endpoint, where the second field value is set to one of status codes including unknown, known and changed, and known and unchanged, wherein capabilities exchange is avoided only when the first field value is set to known and unchanged and the received second field value is known and unchanged.

18. The article of claim 17, the computer further comprising an originating endpoint.

19. The article of claim 17, the computer further comprising a terminating endpoint.

20. The article of claim 17, wherein the instructions that, when executed, cause the computer to set a first field value further cause the to set the first field value to unknown based upon the capability information for the second endpoint.

21. The article of claim 17, wherein the instructions that, when executed, cause the computer to set the first field value further causes the computer to set the first field value to known and changed based upon the capability information for the first endpoint.

22. The article of claim 17, wherein the instructions that, when executed, cause the computer to set the first field value further causes the computer to set the first field value to known and unchanged based upon the capability information for the first endpoint.

23. The article of claim 17, the instructions further cause the computer to receive an acknowledgement message from the second endpoint containing the second field value.

24. The article of claim 17, wherein the instructions further cause the computer to receive a setup message from the second endpoint containing the second field value.