phone number matching bug?

[mastabog]

Hi all,

I posted somethinig similar to this a while ago. I am using my Diamond to call VoIP numbers, i.e. call a landline then wait for a few seconds and enter the destination number followed by hash #. The landline number is the same for all destinations and only the second part differs, which is the destination number. The numbers look like:

0123456789, 00447890123456#

Now, if I store two or more such contacts in the address book, e.g.

Bar: 0123456789, 00441234567890#
Foo: 0123456789, 00447890123456#
Joe: 0123456789, 00445678901234#

the, regardless which one I call, say Foo, in the call log it will always list "Bar" as having been called. The same happens if I replace the comma with a "p". The number however is stored correctly, i.e. if I redial it, it will call the number for Foo which is what was dialed in the first place.

It appears as being a bug in WM6.1. I haven't tried WM6.5 (anyone?).

How in the world can I fix this?

Cheers for any help

[okokur]

foo? bar? linux-user? i google your text for translaiting but nothing understanding.

do you mean that the order is not correct?

(if you can give an example with more friendly-understanding/windows-user than you can get earlier response from other forum-users.)

hope, you not so much angry :-)

[misfitflt]

(if you can give an example with more friendly-understanding/windows-user than you can get earlier response from other forum-users.)


I understood perfectly. Perhaps it is a english as a second language barrier. I will try to restate the issue. (I wish I knew the answer.)

When you have a extra long number stored to a contact (as you might when you dial a AT&T toll free number with some pauses, then a passcode, then a number.) And you have more than one contact stored with this long number... they all have the same first 10 or so numbers. So regardless of which one was called last, when you look up the call history log, it displays the first one.

It would appear the call history only looks at the first 10 or so digits to find a match.

[Prewien]

I understood perfectly. Perhaps it is a english as a second language barrier. I will try to restate the issue. (I wish I knew the answer.)

When you have a extra long number stored to a contact (as you might when you dial a AT&T toll free number with some pauses, then a passcode, then a number.) And you have more than one contact stored with this long number... they all have the same first 10 or so numbers. So regardless of which one was called last, when you look up the call history log, it displays the first one.

It would appear the call history only looks at the first 10 or so digits to find a match.

if this is the case, you can use advanced config or diamond tweak (forgot which one had the option) and from there you can set how many numbers it should check

[mastabog]

@misfitflt: Thanks for rephrasing the problem .. I was just about to post. Cheers!

if this is the case, you can use advanced config or diamond tweak (forgot which one had the option) and from there you can set how many numbers it should check

I forgot to mention I already played with the number of trailing digits in AdvConfig (that's what apparently the option is called) ... I tried values from the default 6 to 20 and nothing changed. The buggy behaviour persists.

I recently tried a new dialer with address book application that replaces the TF3D dialer; it is called Inesoft Phone v4.5 (it's actually pretty cool). This one does differentiate between numbers with pauses or commas correctly!

I'll try switching off the dialer completely and use the built-in WM6.1 dialer to see if that works fine. If so then the bug is in TouchFlo (?).

Anyone knows of other good dialer software that I could try?

Cheers,

p.s. I'm surprised this hasn't surfaced until now though ... anyone out there with the same issue? Or maybe I need to give the thread a more appropriate title.

[fazalali110]

i have the same issue but learnt to live with it as i didnt want to shift to another dialer.
tried playing with the number in adv config but of no avail :(

lemme know if you find anything