SYSTEM AND METHOD FOR ESTABLISHING A SIP SHARED CONTROL CHANNEL IN MULTIPLE DEVICE ENVIRONMENTS

• US 20150201024A1
• Filed: 01/14/2014
• Published: 07/16/2015
• Est. Priority Date: 01/14/2014
• Status: Abandoned Application

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Balasaygun, Mehmet, Abramson, Sandy, Lukac, Tibor
• Application Number:
  US14/154,412
• Publication Number:
  US 20150201024A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

Disclosed is a system and method for creation of a SIP session between a controlling endpoint and a controlled endpoint. The SIP shared control mechanism sets up a first party control channel between a softclient acting as a CTI application and a controlled endpoint. The use of labels associated with multiple controlled endpoints associated with a user are utilized.

Claims

1. A method for establishing a session initiation protocol shared control channel between a first endpoint and a plurality of second endpoints associated with a user, said method comprising:

providing a label and shared control support information corresponding to each of said plurality of second endpoints in a Contact header of a REGISTER message to a session initiation protocol registrar;

saving each of said labels and shared control support information in association with a registered contact address of said second endpoint;

via said first endpoint, reading each of said labels and shared control support information from a registration event NOTIFY message; and

creating a shared control session and presenting said labels of said plurality of second endpoints to said user enabling said user to select one of said plurality of endpoints.

2. The method of claim 1, wherein said first endpoint is a controlling endpoint.

3. The method of claim 1, wherein said plurality of second endpoints are a plurality of controllable endpoints.

4. The method of claim 1, wherein said first endpoint is a softclient application.

5. The method of claim 1, said method further comprising, via said first endpoint, subscribing for a registration event package.

6. A method for establishing a session initiation protocol shared control channel between a first endpoint and a plurality of second endpoints associated with a user, said method comprising:

sending a shared control INVITE request with a Request-URI set to an address of record of a user, said INVITE request comprising an indication of a desired protocol for said shared control session;

by a proxy server. Receiving said INVITE request;

by said proxy server, determining a list of registered contacts associated with said address of record;

by said proxy server, selecting from said list one or more of said contacts that support indicated shared control protocol; and

by said proxy server, forking said INVITE request to said selected contacts.

7. A method for establishing a session initiation protocol shared control channel between a controlling application and an endpoint, said endpoint comprising one of a plurality of controllable devices, said method comprising:

at said controlling application, receiving a session initiation protocol registration event notification;

at said controlling application, detecting which or one or more registered controllable devices are compatible for a shared control session;

sending a separate INVITE request for each controllable device that is deemed compatible; and

at said endpoint, enabling control by a user of said endpoint.

8. The method of claim 7, said method further comprising:

presenting a list of controllable devices to said user.

9. The method of claim 7, wherein a Request-URI of each of said separate INVITE requests uniquely identifies a registered controllable device and said INVITE request is routed by said proxy server using session initiation protocol routing logic.

10. A system for establishing a session initiation protocol shared control channel, said system comprising:

a controlling endpoint; and

a plurality of controlled endpoints associated with an end user;

wherein said controlling endpoint is enabled to subscribe to a registration event package, read labels corresponding to said plurality of controlled endpoints from a registration event NOTIFY message, and present said labels to the end user in connection with a shared control SIP session.

11. The system of claim 10, wherein said controlling endpoint is a softclient.

12. The system of claim 10, said wherein each of said plurality of controlled endpoints are enabled to prompt said user for entry of a label and provide said label in a display name portion of a Contact header of a REGISTER message to an SIP registrar.