[Rtcomm] [Rtcomm] [Bug 7195] Please allow non-digits in phone numbers

[From: bugzilla-daemon at maemo.org]

https://bugs.maemo.org/show_bug.cgi?id=7195


fozzy at zip.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fozzy at zip.com.au




------- Comment #2 from fozzy at zip.com.au  2010-01-03 13:57 GMT+3 -------
I believe this should be re-opened.

Two additional cases where it's used:

1. Entries can be imported with brackets, spaces and hyphens.  All these are
used to add to the readability of a number, e.g. (02) 1234-5678.  That should
be valid.

2. My Carrier (Optus Australia) provides what they call a "dual sim" facility. 
The SIM I have works with two numbers.  In my case one number is my personal
number and the other one is my work number.  When I want to make a call and
have it billed to the alternate number, I simply precede the phone number with
"#1".  In my case, all these calls are billed directly to work.  Thus all my
work contacts are stored in my phone with hash one at the start of the number. 
Numbers that were in my previous phone (Nokia 6110 Navigator), still have the
hash one and dial correctly.  However, if I try and add a hash one to the start
of a new number I can't type the hash.

It would appear this is actually a problem with the phone number entry edit
check code, rather than with the back end processing code.


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=7195
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.