System and method for implementing a session initiation protocol feature

• US 8,694,648 B2
• Filed: 06/30/2011
• Issued: 04/08/2014
• Est. Priority Date: 06/28/2006
• Status: Expired due to Fees

• 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:
  US13/173,655
• Publication Number:
  US 20110264814A1
• Time in Patent Office: 1,013 Days
• Field of Search: 709/227, 370/260
• US Class Current: 709/227
• 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 a third endpoint, the communications platform implementing the shared line protocol to serve a plurality of endpoints using a single shared line, the third endpoint not one of the plurality of endpoints being served by the single shared line;

after establishing the SIP communication session between the first endpoint and the third endpoint, 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;

receiving a request from the second endpoint to join the SIP communication session between the first endpoint and the third endpoint; and

integrating communications of the second endpoint into the SIP communication session between the first endpoint and the third endpoint.

2. The method of claim 1, wherein the request from the second endpoint of the plurality of endpoints comprises an invite with a join header and a call info header.

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

4. The method of claim 1, further comprising receiving a lock request from the first endpoint to invoke a select feature to lock the SIP communication session.

5. The method of claim 4, further comprising, upon receiving the lock request, locking the SIP communication session so that a fourth endpoint of the plurality of endpoints being served by the single shared line cannot resume the communication session with the second endpoint.

6. The method of claim 5, wherein:

the lock request is generated by the communications platform when the communication session is placed on hold.

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.

22. The method of claim 5, wherein the lock request is generated by the SIP communications platform when the communication session is placed on hold.

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

a processor configured to;

serve a plurality of endpoints via a shared line implementing a shared line protocol, the plurality of endpoints comprising at least a first endpoint and a second endpoint serviced by the shared line; and

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

an interface coupled to the processor and configured to;

after the establishment of the SIP communication session between the first endpoint and the third endpoint, 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; and

receive a request from a second endpoint to join the SIP communication session between the first endpoint and the third endpoint;

wherein the processor is further configured to integrate communications of the second endpoint into the SIP communication session between the first endpoint and the third endpoint.

9. The system of claim 8, wherein the request from the second endpoint of the plurality of endpoints comprises an invite with a join header and a call info header.

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

11. The system of claim 8, wherein the interface is further configured to receive a lock request from the first endpoint to invoke a select feature to lock the SIP communication session.

12. The system of claim 11, wherein, upon receiving the lock request, the processor is further configured to lock the SIP communication session so that a fourth endpoint of the plurality of endpoints being served by the shared line cannot resume the SIP communication session with the second endpoint.

13. The system of claim 12, wherein the lock request is generated by the communications platform when the SIP communication session is placed on hold.

14. The system of claim 8, wherein:

the interface is further configured to receive a request from the first endpoint to exit the SIP communication session; and

the processor is further configured to 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:

serve a plurality of endpoints via a shared line implementing a shared line protocol, the plurality of endpoints comprising at least a first endpoint and a second endpoint serviced by the shared line;

establish a Session Initiation Protocol (SIP) communication session via a communications platform, the SIP communication session being between a first endpoint and a third endpoint, the communications platform implementing the shared line protocol to serve a plurality of endpoints using a single shared line, the third endpoint not one of the plurality of endpoints being served by the shared line;

after establishing the SIP communication session between the first endpoint and the third endpoint, 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;

receive a request from the second endpoint to join the SIP communication session between the first endpoint and the third endpoint; and

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

16. The medium of claim 15, wherein the request from the second endpoint of the plurality of endpoints comprises an invite with a join header and a call info header.

17. The medium of claim 15, wherein the logic is further configured to receive from the first endpoint a remote call control line key event message specifying a privacy status.

18. The medium of claim 15, wherein the logic is further configured to receive a lock request from the first endpoint to invoke a select feature to lock the SIP communication session.

19. The medium of claim 18, wherein, upon receiving the lock request, the logic is further configured to lock the SIP communication session so that a fourth endpoint of the plurality of endpoints being served by the shared line cannot resume the SIP communication session with the second endpoint.

20. The medium of claim 19, wherein the lock request is generated by the communications platform when the SIP communication session is placed on hold.

21. The medium of claim 15, wherein the logic 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.