Number rewrite not always working

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Add rewrite rule for Call Mobile: Rewrite Is Exactly 905 Replace Match By 443
2.Add Directly Call rule for Call Mobile (below the other one) Is Exactly 443
3.Dial 905 on phone's dialler.

What is the expected output? What do you see instead?
The phone should dial 443 (giffgaff.com voicemail number). Instead, 905 is 
directly dialled (which doesn't work).

What version of the product are you using? On what operating system?
Version 0.04-01 r1841 running on Android 2.3.6 (Huawei Ascend G300)

Please provide any additional information below.
The phone was locked to Vodafone UK. Unlocked and running on giffgaff (MVNO on 
O2 UK). Vodafone's voicemail settings file incorrectly makes the phone use O2's 
voicemail number 905 and the setting is locked so it cannot be changed. What 
I'm trying to do is if 905 is dialled (either keyed in or using the voicemail 
button), the rewrite rules cause the number to be changed to 443 and dialled.

If I DON'T enter the second rule (or I place it above the rewrite rule), I get 
the choice to call 905 via VoIP or 443 via Call Mobile, and selecting Call 
Mobile works.  If I have the second rule to directly dial 443, dialling 905 
tries to call 905 directly.

Original issue reported on code.google.com by soru...@gmail.com on 28 Aug 2012 at 9:22

[GoogleCodeExporter]

Issue also exists with r1848.

Original comment by soru...@gmail.com on 28 Aug 2012 at 10:52

[GoogleCodeExporter]

Thanks for the bug report.

Original comment by r3gis...@gmail.com on 28 Aug 2012 at 9:51

• Changed state: Accepted

[GoogleCodeExporter]

This issue was closed by revision r1852.

Original comment by r3gis...@gmail.com on 28 Aug 2012 at 9:57

• Changed state: Fixed

[GoogleCodeExporter]

I've fixed it in r1852, it will be produced in about 30 minutes. The bug was 
normally localized to gsm account (that has dedicated optimization to try to 
try to directly launch the call if possible). If you observe same kind of thing 
elsewhere don't hesitate to report :)
Thanks

Original comment by r3gis...@gmail.com on 28 Aug 2012 at 9:59