Subject: Re: [dispatch] SIP Action Referral charter proposal

From: Leon Portman <[email-masked]>
Date: Mon, 7 Feb 2011 13:05:45 +0200

I see additional use cases where mechanism like this can be used in Contact Center environment where agent's phone is controlled by CRM application in order to answer, transfer or conference other agents and experts.

Regards

Leon

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf Of Shekh-Yusef, Rifaat (Rifaat)
Sent: Friday, January 21, 2011 3:09 AM
To: [email-masked]
Subject: [dispatch] SIP Action Referral charter proposal

Hi,

The following is a charter proposal for the SIP Action Referral WG.
While the SPLICES WG seems like a possible place for this work, the SIP Action Referral has a wider scope than the Loosely Coupled UAs use case.
We would appreciate any thoughts and comments on the charter proposal and on the SPLICES idea as a WG for this work.

We would also appreciate any ideas for a name for the WG.

Regards,
 Rifaat

-----------------------------

Charter Proposal (version 1)

Possible WG Names: Open for ideas 

Hard phones often work in conjunction with software on other device, such as a soft phone on a PC. For example, a soft phone on the PC might want to answer a phone call but use the user's speakerphone on their desk for the call instead of the soft phone. To do this, it would need to signal to the speakerphone to answer the call.

This working group will define a SIP extension that allows a SIP User Agent to instruct another SIP User Agent to perform an action. An action is an event or a series of events that modify the state of a UA at different levels, e.g. SIP state, UI, etc. An action can be triggered either in the context of an existing dialog or outside the context of any existing dialog. An action is not necessarily tied to a SIP request.

The following is a list example actions: Answer a call, mute or unmute a call, put the call on hold or take off, add or remove the call to conference bridge. 

The Working group will be a very short lived working group that will use frequent phone calls and IETF meetings to quickly progress a single specification. This working group will closely coordinate with the SPLICES working group as this work seems to be applicable to their work. 

Deliverables

Nov 2011     Use Cases and Requirements to IESG as Informational RFC Feb 2012     Protocol specification to IESG as PS

_______________________________________________
dispatch mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/dispatch