Closed
Bug 768925
Opened 12 years ago
Closed 12 years ago
API for WebTelephony conference calls
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox26 | --- | fixed |
People
(Reporter: overholt, Assigned: sicking)
References
Details
We need to spec the API for WebTelephony conference calls.
Reporter | ||
Updated•12 years ago
|
blocking-basecamp: --- → ?
Updated•12 years ago
|
Assignee: nobody → htsai
Assignee | ||
Comment 1•12 years ago
|
||
Me and Bent talked through this and came up with an API: https://wiki.mozilla.org/WebAPI/WebTelephony#DOM_API I wanted to keep things simple for now since GSM doesn't support multiple simultaneous conference groups as far as we could tell. So there's a static mozTelephony.conferanceGroup property which contains the one group that you can use. Adding and removing calls to that group is straight-forward by calling group.add and group.remove. Only quirk is that the group can't contain just one call (since then it's not a group), so the first time you have to call .add and provide two call objects. Swiching between a group and a call on hold, or simply between two different calls, is done by calling .resume on the group/call that you want to switch to. That will automatically put the currently active group/call on hold. So now we just need someone to implement :)
Assignee: htsai → jonas
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 2•12 years ago
|
||
(In reply to Jonas Sicking (:sicking) from comment #1) > Me and Bent talked through this and came up with an API: > > https://wiki.mozilla.org/WebAPI/WebTelephony#DOM_API > > I wanted to keep things simple for now since GSM doesn't support multiple > simultaneous conference groups as far as we could tell. So there's a static > mozTelephony.conferanceGroup property which contains the one group that you > can use. Is "conferance" just a typo of "conference" or an actual word? *playing the ESL card* > So now we just need someone to implement :) I thought this was the point of this bug? At least it seemed like Hsin-Yi was volunteering ;).
Comment 3•12 years ago
|
||
Hah~ yes, if no body is working on this, then I'd like to take this challenge. :)
Comment 4•12 years ago
|
||
(In reply to Philipp von Weitershausen [:philikon] from comment #2) > > > > So now we just need someone to implement :) > > I thought this was the point of this bug? At least it seemed like Hsin-Yi > was volunteering ;). (In reply to Hsin-Yi Tsai [:hsinyi] from comment #3) > Hah~ yes, if no body is working on this, then I'd like to take this > challenge. :) Hi, I am studying conference calls and gonna file two bugs for implementing this API. One focuses on DOM implementation and the other on RIL. Right before I file and take the new bugs, I wanna ask again, if anyone is working on the implementation? If no, then may I take them? Thanks. :)
(In reply to Philipp von Weitershausen [:philikon] from comment #2) > (In reply to Jonas Sicking (:sicking) from comment #1) > Is "conferance" just a typo of "conference" or an actual word? typo!
(In reply to Hsin-Yi Tsai [:hsinyi] from comment #4) > Right before I file and take the new bugs, I wanna ask again, if anyone is > working on the implementation? If no, then may I take them? All yours! (Fair warning, though: this may prove to be a tricky first DOM bug!)
Updated•12 years ago
|
blocking-basecamp: ? → -
Updated•11 years ago
|
status-firefox26:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•