STR 1. Go to the dialer app and make a call. 2. While the previous call is still dialing (not picked up by the other party), click on add call button and then select contact app and select a contact to dial. Expected: The newly added call should either be dialed or display some sort of notification to user in case of an error. Observed: There is no indication on the UI. 3. At this time disconnect the first ringing call. 4. Go to the contacts tab in the dialer again and try to make a call Observed: No call is made and no indication presented to the UI Note that this issue only happens if the contacts tab within the dialer is selected and not using the stand alone contacts app.

I analyzed the issue and the root cause seems to be that telephony_helper.js tries to hold a call when there is an active call. The hold call API in TelephonyCall.cpp however ignores the hold request if the call is not connected, which is the case in this scenario and so telephony_helper.js never receives the activeCall.onheld event and somehow messed up the contacts app.

We no longer allow dispatching a new call while there is a currently connecting call.

Doug, I am still able to reproduce the issue with latest Gecko/Gaia from Moz central. I am still able to click the dial button in the contacts app when a previous call is connecting but not yet connected. When you say FFOS no longer allows dispatching a new call, I was expecting some visual feedback such as perhaps disabling the dial button in the contacts app besides the phone number.

Thanks, Anshul. I'm adding this to our backlog.

Firefox OS is not being worked on