System and method for implementing a session initiation protocol feature

• US 9,088,600 B2
• Filed: 04/07/2014
• Issued: 07/21/2015
• Est. Priority Date: 06/28/2006
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Linton, Daniel P., Miller, Craig P., Panburana, Pandit, Levy, Stephen, Pearce, Christopher E.
• Primary Examiner(s): BILGRAMI, ASGHAR H
• Application Number:
  US14/246,670
• Publication Number:
  US 20140223021A1
• Time in Patent Office: 470 Days
• Field of Search: 709/228
• US Class Current: 1/1
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

A method for implementing a SIP feature includes, in particular embodiments, establishing a communication session via a communications platform between a first and second user and receiving a request from a third user to join the communication session. The second and third users are from a plurality of users using a shared line. The method further includes integrating communications of the third user into the communication session. In particular embodiments the method includes establishing a communication session between a first and second user via a communications platform. The method also includes receiving a select request that locks the communication session so that a third user cannot resume the communication session with the first user. In particular embodiments the method includes receiving a request from a first user of a shared line to enable a privacy feature that reduces call information generated by the communications platform in remote state notifications.

Claims

1. A method for implementing a Session Initiation Protocol (SIP) feature, comprising:

providing a shared line implementing a shared line protocol to serve a plurality of endpoints coupled to the shared line, the plurality of endpoints comprising at least a first endpoint and a second endpoint;

establishing a SIP communication session via a communications platform, the communication session being between the first endpoint and at least one other endpoint, the communications platform implementing the shared line protocol to serve the plurality of endpoints using the single shared line;

after establishing the SIP communication session between the first endpoint and the at least one other endpoint, receiving a request to place the SIP communication session on hold, the request identifying at that a second endpoint may pick-up the SIP communication session; and

while the SIP communication session is on hold, enabling the second endpoint to pick-up the SIP communication session while locking the SIP communication session to prevent endpoints other than the first endpoint and the second endpoint from picking-up the SIP communication session.

2. The method of claim 1, wherein:

the plurality of endpoints further comprises a third endpoint; and

locking the SIP communication session comprises preventing the third endpoint from picking-up the SIP communication session.

3. The method of claim 1, wherein the SIP communication session is between a first endpoint and a third endpoint, the third endpoint not being one of the plurality of endpoints sharing the shared line.

4. The method of claim 1, further comprising:

receiving a request from the second endpoint to pick-up the SIP communication session; and

integrating communications from the second endpoint into the SIP communication session of the first endpoint.

5. The method of claim 1, further comprising sending, via the communications platform, a remote state notification comprising call information notifying the plurality of endpoints served by the single shared line of the SIP communication session.

6. The method of claim 1, further comprising receiving from the first endpoint a remote call control line key event message specifying a privacy status.

7. The method of claim 1, further comprising:

receiving a request from the first endpoint to exit the SIP communication session; and

replacing the first endpoint with the second endpoint in the SIP communication session.

8. A system for implementing a Session Initiation Protocol (SIP) feature, comprising:

a processor configured to;

provide a shared line implementing a shared line protocol to serve a plurality of endpoints coupled to the shared line, the plurality of endpoints comprising at least a first endpoint and a second endpoint;

establish a SIP communication session via a communications platform, the communication session being between the first endpoint and at least one other endpoint, the communications platform implementing the shared line protocol to serve the plurality of endpoints using the single shared line;

after establishing the SIP communication session between the first endpoint and the at least one other endpoint, receive a request to place the SIP communication session on hold, the request identifying at that a second endpoint may pick-up the SIP communication session; and

while the SIP communication session is on hold, enabling the second endpoint to pick-up the SIP communication session while locking the SIP communication session to prevent endpoints other than the first endpoint and the second endpoint from picking-up the SIP communication session.

9. The system of claim 8, wherein:

the plurality of endpoints further comprises a third endpoint; and

the processor is operable to lock the SIP communication session to prevent the third endpoint from picking-up the SIP communication session.

10. The system of claim 8, wherein the SIP communication session is between a first endpoint and a third endpoint, the third endpoint not being one of the plurality of endpoints sharing the shared line.

11. The system of claim 8, wherein the processor is further configured to:

receive a request from the second endpoint to pick-up the SIP communication session; and

integrate communications from the second endpoint into the SIP communication session of the first endpoint.

12. The system of claim 8, wherein the processor is further configured to send, via the communications platform, a remote state notification comprising call information notifying the plurality of endpoints served by the single shared line of the SIP communication session.

13. The system of claim 8, wherein the processor is further configured to receive from the first endpoint a remote call control line key event message specifying a privacy status.

14. The system of claim 8, wherein the processor is further configured to:

receive a request from the first endpoint to exit the SIP communication session; and

replace the first endpoint with the second endpoint in the SIP communication session.

15. Logic embodied in a non-transitory computer readable medium, the non-transitory computer readable medium comprising code operable to:

provide a shared line implementing a shared line protocol to serve a plurality of endpoints coupled to the shared line, the plurality of endpoints comprising at least a first endpoint and a second endpoint;

establish a SIP communication session via a communications platform, the communication session being between the first endpoint and at least one other endpoint, the communications platform implementing the shared line protocol to serve the plurality of endpoints using the single shared line;

after establishing the SIP communication session between the first endpoint and the at least one other endpoint, receive a request to place the SIP communication session on hold, the request identifying at that a second endpoint may pick-up the SIP communication session; and

while the SIP communication session is on hold, enable the second endpoint to pick-up the SIP communication session while locking the SIP communication session to prevent endpoints other than the first endpoint and the second endpoint from picking-up the SIP communication session.

16. The logic of claim 15, wherein:

the plurality of endpoints further comprises a third endpoint; and

locking the SIP communication session comprises preventing the third endpoint from picking-up the SIP communication session.

17. The logic of claim 15, wherein the SIP communication session is between a first endpoint and a third endpoint, the third endpoint not being one of the plurality of endpoints sharing the shared line.

18. The logic of claim 15, further operable to:

receive a request from the second endpoint to pick-up the SIP communication session; and

integrate communications from the second endpoint into the SIP communication session of the first endpoint.

19. The logic of claim 15, further operable to send, via the communications platform, a remote state notification comprising call information notifying the plurality of endpoints served by the single shared line of the SIP communication session.

20. The logic of claim 15, further operable to receive from the first endpoint a remote call control line key event message specifying a privacy status.

21. The logic of claim 15, further operable to:

receive a request from the first endpoint to exit the SIP communication session; and

replace the first endpoint with the second endpoint in the SIP communication session.