Ubuntu phone disconnects immediately if called phone is busy & not voicemail enabled

I can't reproduce this. I get my voicemail when i call an engaged ubuntu phone from another ubuntu phone.

Confirmed. Calling my own number from my phone instantly drops the call. On maguro image 54

Status changed to 'Confirmed' because the bug affects multiple users.

This was a feature that was discussed during the phone-dations sprint earlier this month and it was decided that the behavior as described was the desired behavior for 13.10, as fully implementing call waiting and/or multi-party call was too large a feature to land.

Note, I've -re-confirmed this on a mako running image #76.

On a stock 4.4.2 Android phone, if the phone being called has CallWaiting disabled, and no VM enabled either, then the UI will show "Line Busy" and you'll hear a few busy tones, then the dialer is dismissed.

I also ran monitor-ofono when I re-created this, and it looks like the call is ending right away. Here's what I see:

root@ubuntu-phablet:/usr/share/ofono/scripts# ./monitor-ofono
{VoiceCallManager} [CallAdded] /ril_0/voicecall01 { LineIdentification = 5087339459, Name = , RemoteHeld = False, Multiparty = False, State = dialing, Emergency = False, RemoteMultiparty = False }
{NetworkRegistration} [/ril_0] Strength = 38
{VoiceCall} [/ril_0/voicecall01] State = alerting
{VoiceCall} [/ril_0/voicecall01] DisconnectReason network
{VoiceCall} [/ril_0/voicecall01] State = disconnected
{VoiceCallManager} [/ril_0/voicecall01] CallRemoved

Re-tested this with image #u144 on mako using an AT&T SIM, and I get a busy signal when calling a number that has no call-waiting nor voice-mail enabled.

Will look at this tomorrow Omer if you are about this evening and hit it before me can you confirm if it is fixed?

I just tried and the issue still happens on the latest image.

@Omer

Please include image # and device.

I again tried this using make rtm #6 and I get a busy signal.

I'm beginning to think this is operator-specific behavior and may be related to bug #1341453.

I investigated this with 208 and tried to simulate error situation with different hacks in ofono. I was suspecting that phenomena might be related to how fast call status events are coming or if some events are missing. I made such hack where call was disconnected right after it went to alerting state ( state was articially changed to disconnected state too ). Turns out that these events have nothing to do with if the alerting tone is played or not. Even if the call was disconnected

{VoiceCall} [/ril_0/voicecall01] DisconnectReason remote
{VoiceCall} [/ril_0/voicecall01] State = disconnected

Phone kept playing the busy tone.

If this bug is related to 1341453 I think it should happen in other situations too and not just when calling to busy phone. However, proposed fix for 1341453 would propably solve this too.

Per our discussion earlier, I don't think the proposed fix for bug #1341453 fixes this as the call disconnects right away.

I'm starting to this this is an operator specific bug as Omer is the only person that's able to reproduce this.

@Omer

Can you reproduce again but this time provide the following information:

1. As root on the device please capture the output of /usr/share/ofono/scripts/monitor-ofono while you run through the steps to reproduce.

2. Also as root on the device, please capture the output of /usr/share/ofono/scripts/list-modems

3. Please attach /var/log/syslog to the bug as well.

1. monitor-ofono http://paste.ubuntu.com/8178605/

2. list-modems http://paste.ubuntu.com/8178602/

3. syslog http://paste.ubuntu.com/8178648/

Just tried to reproduce this and failed on both mako ( vivid-proposed / #111 + rtm/#16 ) and krillin ( rtm/#19 ).

@Omer

Can you try again with a recent RTM image and/or vivid?