Recognising incoming calls

[rsawoseyin]

I am new to this application, so forgive me if this question has been answered before: All phone numbers in my phonebook are internationally formatted, e.g. +234-803-740-2692 ( a number in Nigeria where I live). If I have an incoming local call which comes in as 08055501395 but that number exists in my phonebook as +2348055501395, Magicall does not recognise the number and so does not execute any rule (even though the phone recognises the number and shows the caller's name). Please how do I handle this?

[admin]

Hi rsawoseyin,

That depends how the rule is set. If its filter type is Specific Number, you may type just the phone number without country code and area code. If you set it to In Contacts, it will work as the same as the phone. Here are two examples:

Rule type: Phone-Inbound
Filter type: Specific Number
Phone#: 803-740-2692
Action1: Hang up

Rule type: Phone-Inbound
Filter type: In Contacts
Phone#:
Action1: Hang up

[rsawoseyin]

I have just tried it and it didn't work:

Rule type: Phone-Inbound
Filter type: In Contacts
Phone#:
Action1: Hang up

In my Contacts, the entry is +234-805-550-1395 (This is actually my 2nd mobile line)

When I called from this line to my primary line with MagiCall activated, my handset identified the caller as me, but displayed the number as 08055501395 (it replaced the country code with 0). However, MagiCall did not and so it did not hang up.

It seems to me there is need for a rule that standardised inbound phone numbers to format it as in Contacts.

[admin]

What device are you using? Is it a WM5 device or WM2003?

[rsawoseyin]

It is HTC TyTN II (Kaiser) running WM6.

[admin]

Thank you, rsawoseyin.

I think it should be a problem of filtering calls on the second line. We have not tested such cases before since the mobile operators in our country do not support the second line. Can you help us test if a rule filtering All Numbers can block the call on the second line? If it does, then this is a problem about finding a matching contact. Otherwise, it is a problem about filting the second line.

Regards.

[rsawoseyin]

I don't think you got what I meant by second line: I have 2 handsets with 2 different numbers - not that I have 2 lines on the same handset.

The issue is simple: A caller with number 0805-550-1395 calls me. I have his number in my Contacts as +234-805-550-1395. My handset sees the incoming call as being from 0805-550-1395. MagiCall is unable to match 0805-550-1395 to +234-805-550-1395. That's it.

So, the question comes down to how to get MagiCall to know that the caller whose number appears as 0805-550-1395 is actually the contact +234-805-550-1395.

[rsawoseyin]

I have just seen that this problem is covered in thread http://www.mobiion.com/forum/index.php?topic=111.0 ("Wrong definition of number") here. Simply put, one should not rely on matching of incoming calls with entries in Contacts: If numbers are stored in Contacts in international format, inbound calls without the country prefix will not be identified by MagiCall.

But I believe the developer can address this problem. Somehow, WM operating system is able to match the numbers and correctly identify the caller. So, with some work, I believe MagiCall can be made to do same.

[admin]

Not exactly the same. The problem mentioned in that thread affects "Specific Number" only.
If you use "In Contacts" or "Not in Contacts", we use the system API FindMatchingContacts to find a matching contact.

I think it should be problem of using this API. I will check it later and let you know the result.

By the way, the WM system just compares the last 6 digits while MagiCall compares all digits. This is the differece between them.

[rsawoseyin]

"By the way, the WM system just compares the last 6 digits while MagiCall compares all digits."

That's it! I strongly recommend you adopt the WM system for MagiCall as well - or if you want, make it a configuration option!

[admin]

I will add this option to the next version. Thank you.