[Bug 26807] Mute interface for Channel.Type.Call

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26807

--- Comment #12 from Olivier Crête <tester at tester.ca> 2010-04-21 09:31:53 PDT ---
(In reply to comment #11)
> (In reply to comment #10)
> > I think the real question is: Does GSM have a direction=receive that's
> > different from Mute? If yes, then we need a Mute() call, if not just change the
> > direction.
> 
> On XMPP, streams can't have direction: none. So under your suggestion, the call
> would end if we both pressed mute... (Unless you're suggesting changing the
> direction locally but not on the wire?)

That's exactly why I wanted senders=none in Jingle. Can you have a call with no
contents ? (probably not?). Anyway, if XMPP is broken, we should fix it. That
also probably means that Gabble needs to be hacked to always send sound even if
the direction doesn't say it.

That said, there is the added complication of WiFi power managementm, it
buffers packets for a long time if it does not receive anything. So we have to
always be sending regularly anyway. So Mute for VoIP really has to mean "I'll
send sound buffers, they just happen to have no sound in them".

So, unless mute exists for GSM, I would suggest just changing the direction on
the TP level and have the VoIP CMs interpret that not as a change in direction,
but as a "please send no sound at all".

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.