Closed Bug 911250 Opened 12 years ago Closed 12 years ago

[WAP push][Gaia] Display a WAP Push message's MSISDN as the corresponding contact

Categories

(Firefox OS Graveyard :: Gaia, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:koi+)

RESOLVED WONTFIX
blocking-b2g koi+

People

(Reporter: gsvelto, Assigned: gsvelto)

References

Details

(Whiteboard: [FT:RIL])

Currently the MSISDN of a WAP Push message is displayed as a raw number. If the number is present in the contact list the corresponding contact should be displayed instead.
Blocks: 838062
Summary: [Gaia] Display a WAP Push message's MSISDN as the corresponding contact → [WAP push][Gaia] Display a WAP Push message's MSISDN as the corresponding contact
Assignee: nobody → gsvelto
Whiteboard: [FT:RIL]
(In reply to Gabriele Svelto [:gsvelto] from comment #0) > Currently the MSISDN of a WAP Push message is displayed as a raw number. If > the number is present in the contact list the corresponding contact should > be displayed instead. Those MSISDN numbers are from carriers. Users won't add those numbers into their contacts.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
(In reply to Ken Chang from comment #1) > Those MSISDN numbers are from carriers. Users won't add those numbers into > their contacts. OK, the reason I had opened this was that sometimes vendor ship some special numbers on their SIM cards - and those usually get copied to your contacts - and I was wondering if some messages might come from those.
(In reply to Gabriele Svelto [:gsvelto] from comment #2) > (In reply to Ken Chang from comment #1) > > Those MSISDN numbers are from carriers. Users won't add those numbers into > > their contacts. > > OK, the reason I had opened this was that sometimes vendor ship some special > numbers on their SIM cards - and those usually get copied to your contacts - > and I was wondering if some messages might come from those. Good question. It might be happened. We can leave this until partners request a fix for this bug.
You need to log in before you can comment on or make changes to this bug.