Bug 22031 - Answering a held call fails with NotAvailable rather than a more descriptive error.
Summary: Answering a held call fails with NotAvailable rather than a more descriptive ...
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: low minor
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on: 21996
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-02 07:01 UTC by Will Thompson
Modified: 2009-06-10 03:49 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Will Thompson 2009-06-02 07:01:07 UTC
* Alice calls Bob; Bob's Gabble sends a <ringing/> notification.
* Bob puts the call on Hold; his Gabble sends a <hold/> notification.
* Bob answers the call; his Gabble sends <active/> which cancels the <hold/>.

So now Alice thinks she's off hold, but Bob still thinks the call's on hold.

I'm inclined to say that we don't want to support answering calls while they're on hold (it's meaningless), and smcv thinks this makes sense. So maybe AddMembers should fail with o.fd.T.StreamedMedia.OnHold or something.
Comment 1 Will Thompson 2009-06-10 03:49:43 UTC
As of 0.7.29, this fails with NotAvailable.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.