diff options
Diffstat (limited to 'spec/Call_Stream_Interface_Media.xml')
| -rw-r--r-- | spec/Call_Stream_Interface_Media.xml | 14 |
1 files changed, 1 insertions, 13 deletions
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. </tp:docstring> </tp:enumvalue> - <tp:enumvalue suffix="Pending_Mute" value="4"> - <tp:docstring> - The streaming implementation has been told to mute sending, - but it has not yet indicated that it has done so. - </tp:docstring> - </tp:enumvalue> - <tp:enumvalue suffix="Muted" value="5"> - <tp:docstring> - The streaming implementation has successfully muted sending, - and the local user's privacy is protected. - </tp:docstring> - </tp:enumvalue> </tp:enum> <property name="SendingState" tp:name-for-bindings="Sending_State" @@ -101,7 +89,7 @@ rely on reading this value and listening to <tp:member-ref>SendingStateChanged</tp:member-ref> 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 <tp:member-ref>CompleteSendingStateChange</tp:member-ref>. Failures should be reported via <tp:member-ref>ReportSendingFailure</tp:member-ref>. |