User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.22 (KHTML, like Gecko) Ubuntu Chromium/25.0.1364.160 Chrome/25.0.1364.160 Safari/537.22 Steps to reproduce: I was on another phone call and then another number called in. The active call was put on hold while the phone automatically receives the new incoming call. After the new phone call hangs up, the other on hold is now continued. Expected results: I should have been given the option to accept or hang up the new call.
Whiteboard: [u=commsapps-user c=dialer p=0]
Is this bug vaild? I can choose whether to hold current call or to hang the incoming call. There's an user story for not able to "hang current call", but I think the incoming call isn't activated automatically. See bug 882056 for current UI.
batch update: waiting for conference call feature to be completed, then QA to verify these
Whiteboard: [u=commsapps-user c=dialer p=0] → [u=commsapps-user c=dialer p=0] [status: waiting for conf-call to be completed and then verify]
koi+ as it links to koi-comms bug
blocking-b2g: --- → koi+
As far as I could test on an Inari running Gecko and Gaia master up to date, this is working well: when on a call and a second one comes in, I get an interface to hold or hang up. So I'm marking this as INVALID. Feel free to change it if current version is not fixed for you and provide more context in this case.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.