From 49a70f85af9f997478be9fdb8e8b1667485c6e71 Mon Sep 17 00:00:00 2001 From: Xavier Claessens Date: Wed, 15 Feb 2012 10:44:09 +0100 Subject: Mark Call1 spec stable Except for Call1.Interface.Mute for which we have still doubts. For now it can be done client-side by muting pulse source for example. --- spec/Call_Stream_Interface_Media.xml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'spec/Call_Stream_Interface_Media.xml') diff --git a/spec/Call_Stream_Interface_Media.xml b/spec/Call_Stream_Interface_Media.xml index 2e3af472..06c24ff4 100644 --- a/spec/Call_Stream_Interface_Media.xml +++ b/spec/Call_Stream_Interface_Media.xml @@ -20,8 +20,7 @@ 02110-1301, USA.

- + (draft 1) -- cgit v1.2.3 From 4c651366bc34ae6aab83d77e0b5f8f61f2163442 Mon Sep 17 00:00:00 2001 From: Xavier Claessens Date: Wed, 15 Feb 2012 15:29:58 +0100 Subject: Remove MUTE values from call stream/channel It is still unsure how mute should be implemented --- spec/Call_Stream_Interface_Media.xml | 14 +------------- spec/Channel_Type_Call.xml | 32 -------------------------------- 2 files changed, 1 insertion(+), 45 deletions(-) (limited to 'spec/Call_Stream_Interface_Media.xml') diff --git a/spec/Call_Stream_Interface_Media.xml b/spec/Call_Stream_Interface_Media.xml index 06c24ff4..3c9a0959 100644 --- a/spec/Call_Stream_Interface_Media.xml +++ b/spec/Call_Stream_Interface_Media.xml @@ -79,18 +79,6 @@ data, and everything is going swimmingly. - - - The streaming implementation has been told to mute sending, - but it has not yet indicated that it has done so. - - - - - The streaming implementation has successfully muted sending, - and the local user's privacy is protected. - - SendingStateChanged to determine whether it should be sending media or not. It should not - need to listen to the Mute/Hold interfaces on the Call/Content. + need to listen to the Hold interfaces on the Call/Content. Feedback on success should be given via CompleteSendingStateChange. Failures should be reported via ReportSendingFailure. diff --git a/spec/Channel_Type_Call.xml b/spec/Channel_Type_Call.xml index d151988a..e899b298 100644 --- a/spec/Channel_Type_Call.xml +++ b/spec/Channel_Type_Call.xml @@ -731,24 +731,6 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - - - The call has been muted by the local user, e.g. using the - Mute interface. This flag SHOULD only - be set if there is at least one Content, and all Contents - are locally muted (for the same reason as Locally_Held). - - - This flag exists to provide a simplified verson of MuteStateChanged, - to reduce the number of signals that need to be - listened to by a simple UI. - - - - This flag exists for observability of the @@ -1215,20 +1197,6 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - - -

The call member has muted their participation in this call. Note - that many protocols will not signal this flag, so clients should - not rely on it being set.

- - -

This is a flag per member, not a flag for the call as a whole, - because in conference calls, any member could mute their own - streams.

-
-
-
- This contact has merged this call into a conference. Note that GSM -- cgit v1.2.3