With my implementation of Hold, we can put the other participant on hold, but we can't tell him we've done so, and neither can we see when he's put us on hold.
Prerequisite: update Jingle compatibility to XEP-0166 >= 0.25 (bug #15907).
Setting as enhancement. It is.
We should also react to the a received hold notification by calling "SetSending(false)".
(In reply to comment #2)
> We should also react to the a received hold notification by calling
I'd much rather make this a separate signal. Maybe there should be a RemoteHeldState/SetRemoteHeldState method/signal pair on StreamHandler, matching HoldState/SetHoldState?
Why make it yet another signal? It really is the same thing as far as the streaming implementation is concerned.
Implemented, including emitting SetSending() as Olivier said.