How to change number of incoming call

[LB2064]

I have a lot of numbers with the format 0-803-xxx-xxxx.  When I roam, these incoming numbers appear as +234-803-xxx-xxxx (That is the 0 is replaced by the country code +234).  My phone then classifies this as an unknown number because it will recognize say 0-803-123-4567 as a contact but not +234-803-123-4567.  Since I have a rule to reject unknown numbers, MagiCall now rejects the number   

I have my Caller ID comparison count set to 7 so I thought this would not happen.

My questions:

1) Does the Caller ID comparison count start from just the front?

2) Is there a way to set up a rule to either recognize the 0-803 as the same as +234-803 in my contacts or is there a rule that can change an incoming call number with 0-803 to +234-803.

Thanks.
LB.
Thanks! 

[LB2064]

I think I may have found the problem with some of my incoming calls.  I use a different contact manager than pOutlook, so that contact manager was not always writing phone numbers to the pOitlook fields.  So I guess MagiCall was not seeing all my numbers.  I will adjust all my numbers to be read by pOutlook and see what happens.

In the interim, I would still like to know whether Magicall will recognize a 0803-xxxxxxx number in my contact list while roaming when the caller ID shows +234-803-xxxxxxx.

Thanks.
LB

[admin]

Contacts must be existing in pOutlook, because we use standard IMAP functions to look for matching contacts.

I think your problem is related to CallIDMatch settings, please take a look at this thread http://social.microsoft.com/Forums/en-US/windowsmobilephonesandaccessories/thread/747a9ca3-e27b-4b43-bef1-c1cf532ad692/

We can do nothing to incoming phone numbers. However I will add a registry switch to future versions to allow users to turn on legacy mechanism for finding matching contacts which compares each contact one by one. But this will greatly slow down the speed of finding a contact by MagiCall.

[LB2064]

Thanks.  I'll also try the reg tweak in the link you provided.