System And Method For Establishing A Communication Session Between Two Endpoints That Do Not Both Support Secure Media

• US 20080019381A1
• Filed: 07/21/2006
• Published: 01/24/2008
• Est. Priority Date: 07/21/2006
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Mills, David W., Jennings, Cullen F.
• Granted Patent: US 8,139,566 B2
• Time in Patent Office: Days
• US Class Current: 370/401
• CPC Class Codes: H04L 63/166 at the transport layer
• 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/0078 Security; Fraud detection; Fraud prevention

Abstract

A method for establishing a communication session between two endpoints that do not both support secure media includes receiving a registration from a first endpoint. The registration indicating the first endpoint supports secure media and non-secure media. The method also includes receiving a registration from a second endpoint. The registration indicating the second endpoint supports non-secure media. The method also includes receiving a request to establish a communication session between the first endpoint and the second endpoint using secure media. The method further includes establishing the communication session between the first endpoint and the second endpoint via the communications platform using non-secure media.

Claims

1. A method for establishing a communication session between two endpoints, comprising:

receiving a registration from a first endpoint indicating the first endpoint supports secure media and non-secure media;

receiving a registration from a second endpoint indicating the second endpoint supports non-secure media;

receiving a request to establish a communication session between the first endpoint and the second endpoint using secure media; and

establishing the communication session between the first endpoint and the second endpoint via the communications platform using non-secure media.

2. The method of claim 1, wherein:

the secure media comprises secure real-time transport protocol; and

the non-secure media comprises real-time transport protocol.

3. The method of claim 1, wherein the registration comprises a header with a tag indicating that the first endpoint supports receiving a real-time transport protocol answer to a secure real-time transport protocol offer.

4. The method of claim 3, wherein the tag comprises a proprietary fallback element.

5. The method of claim 1, wherein the request to establish a communication session between the first endpoint and the second endpoint using secure media implies the ability to also establish the communication session between the first endpoint and the second endpoint using non-secure media.

6. The method of claim 1, further comprising alerting the first endpoint that the communication session between the first endpoint and the second endpoint is using non-secure media.

7. The method of claim 1, further comprising:

sending a communication containing identification information to the first endpoint; and

receiving a communication containing identification information from the first endpoint.

8. A system for establishing a communication session between two endpoints, comprising:

an interface operable to;

receive a registration from a first endpoint indicating the first endpoint supports secure media and non-secure media;

receive a registration from a second endpoint indicating the second endpoint supports non-secure media; and

receive a request to establish a communication session between the first endpoint and the second endpoint using secure media; and

a processor coupled to the interface and operable to establish the communication session between the first endpoint and the second endpoint via the communications platform using non-secure media.

9. The system of claim 8, wherein:

the secure media comprises secure real-time transport protocol; and

the non-secure media comprises real-time transport protocol.

10. The system of claim 8, wherein the registration comprises a header with a tag indicating that the first endpoint supports receiving a real-time transport protocol answer to a secure real-time transport protocol offer.

11. The system of claim 10, wherein the tag comprises a proprietary fallback element.

12. The system of claim 8, wherein the request to establish a communication session between the first endpoint and the second endpoint using secure media implies the ability to also establish the communication session between the first endpoint and the second endpoint using non-secure media.

13. The system of claim 8, wherein the processor further comprises a processor operable to alert the first endpoint that the communication session between the first endpoint and the second endpoint is using non-secure media.

14. The system of claim 8, wherein the interface is further operable to:

send a communication containing identification information to the first endpoint; and

receive a communication containing identification information from the first endpoint.

15. Logic embodied in a computer readable medium, the computer readable medium comprising code such that when executed is operable to:

receive a registration from a first endpoint indicating the first endpoint supports secure media and non-secure media;

receive a registration from a second endpoint indicating the second endpoint supports non-secure media;

receive a request to establish a communication session between the first endpoint and the second endpoint using secure media; and

establish the communication session between the first endpoint and the second endpoint via the communications platform using non-secure media.

16. The medium of claim 15, wherein:

the secure media comprises secure real-time transport protocol; and

the non-secure media comprises real-time transport protocol.

17. The medium of claim 15, wherein the registration comprises a header with a tag indicating that the first endpoint supports receiving a real-time transport protocol answer to a secure real-time transport protocol offer.

18. The medium of claim 17, wherein the tag comprises a proprietary fallback element.

19. The medium of claim 15, wherein the request to establish a communication session between the first endpoint and the second endpoint using secure media implies the ability to also establish the communication session between the first endpoint and the second endpoint using non-secure media.

20. The medium of claim 15, wherein the code further comprises code operable to alert the first endpoint that the communication session between the first endpoint and the second endpoint is using non-secure media.

21. The medium of claim 15, wherein the code is further operable to:

send a communication containing identification information to the first endpoint; and

receive a communication containing identification information from the first endpoint.

22. A system for establishing a communication session between two endpoints that do not both support secure media, comprising:

means for receiving a registration from a first endpoint indicating the first endpoint supports secure media and non-secure media;

means for receiving a registration from a second endpoint indicating the second endpoint supports non-secure media;

means for receiving a request to establish a communication session between the first endpoint and the second endpoint using secure media; and

means for establishing the communication session between the first endpoint and the second endpoint via the communications platform using non-secure media.