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.
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 voicecall01] State = disconnected
{VoiceCall} [/ril_0/
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.