API for WebTelephony conference calls

RESOLVED FIXED

Status

()

Core
DOM: Device Interfaces
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: overholt, Assigned: sicking)

Tracking

Trunk
x86_64
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(blocking-b2g:koi+, blocking-basecamp:-, firefox26 fixed)

Details

(Reporter)

Description

5 years ago
We need to spec the API for WebTelephony conference calls.
(Reporter)

Updated

5 years ago
blocking-basecamp: --- → ?

Updated

5 years ago
Assignee: nobody → htsai
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
Last Resolved: 5 years ago
Resolution: --- → FIXED
(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 ;).
Hah~ yes, if no body is working on this, then I'd like to take this challenge. :)
(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!)
blocking-basecamp: ? → -

Updated

4 years ago
Blocks: 772761

Updated

4 years ago
Blocks: 772765
listed as must have in v1.2 for COMM team. koi+
blocking-b2g: --- → koi+
status-firefox26: --- → fixed
You need to log in before you can comment on or make changes to this bug.