Bug 11730 – phone number matches incorrectly when there is a pause in the phone number (calling card)

Bug 11730 - phone number matches incorrectly when there is a pause in the phone number (calling card)


Summary:	phone number matches incorrectly when there is a pause in the phone number (c...

Status:	RESOLVED WONTFIX

Product:	contacts-merger
Component:	General
Version:	unspecified
Platform:	N900 Maemo

Importance:	Unspecified enhancement (vote)
Target Milestone:	---
Assigned To:	Marco Barisione
QA Contact:	general

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-12-29 16:21 UTC by tarunkhanna
Modified:	2011-01-10 12:06 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description tarunkhanna (reporter) 2010-12-29 16:21:21 UTC

SOFTWARE VERSION: 
(Settings > General > About product) 20.2010.36-2.002

EXACT STEPS LEADING TO PROBLEM: 
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. Starts the contacts merger, with at least two contacts that are called
through a calling card. I have multiple contacts that call using a calling card
so their phone book entries contain the calling card number followed by pause
and then the correct phone number
2. 
3. 

EXPECTED OUTCOME: 
Different contacts that are called through the same calling card, shouldn't
show up as same

ACTUAL OUTCOME: 
Different contacts that are called through the same calling card, show up as
same.

REPRODUCIBILITY: 
(always, less than 1/10, 5/10, 9/10)
always

EXTRA SOFTWARE INSTALLED: 

OTHER COMMENTS: I think currently the application only matches the phone number
up to the pause and not after. If the complete phone number is matched, false
positives would go away.

Comment 1 Marco Barisione 2010-12-29 16:56:49 UTC

The digits after the pause are completely service-specific, so they cannot be
used for comparison, see
http://blog.barisione.org/2010-06/handling-phone-numbers/

WONTFIX as fixing it for your use case would break the others use cases.

Comment 2 tarunkhanna (reporter) 2010-12-29 17:13:49 UTC

(In reply to comment #1)
> The digits after the pause are completely service-specific, so they cannot be
> used for comparison, see
> http://blog.barisione.org/2010-06/handling-phone-numbers/
> 
> WONTFIX as fixing it for your use case would break the others use cases.

Thanks for looking into it. Do you think it can be added as an option?

Tarun

Comment 3 Fanis Hatzidakis 2011-01-10 12:06:12 UTC

(In reply to comment #1)
> The digits after the pause are completely service-specific, so they cannot be
> used for comparison, see
> http://blog.barisione.org/2010-06/handling-phone-numbers/
> 
> WONTFIX as fixing it for your use case would break the others use cases.

Marco, thanks for the very detailed explanation on handling phone numbers, but
I'm still not sure how pauses would break other use cases if they mattered for
comparisons. I second the Tarun's idea to have it as an option.

This is understandably a low priority issue but I'd say that for anyone who
uses calling cards with pauses those numbers indicate different contacts.