From: Rafael Ignacio Zurita <rafael.zurita@profusion.mobi>
To: ofono@ofono.org
Subject: Re: [RFC PATCH 0/3] Long phone numbers
Date: Tue, 18 Jan 2011 06:39:09 -0300 [thread overview]
Message-ID: <20110118093908.GA20108@nodo3> (raw)
In-Reply-To: <AANLkTi=ZBdVALq+n4EOBMh-nMN2zkMbrzqOFvOor0ZhQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Mon, Jan 17, 2011 at 11:18:51PM +0200, Pekka Pessi wrote:
> Hi Rafael,
>
> 2011/1/17 Rafael Ignacio Zurita <rafael.zurita@profusion.mobi>:
> > This is a proposal for the "long phone number" task (80 digits max length).
> > It changes OFONO_MAX_PHONE_NUMBER_LENGTH and splits
> > common:valid_phone_number_format(), to make sure long numbers are handled
> > appropriately for functions that need manage shorter numbers, like
> > numbers written to the SIM, or sms SCA.
>
> Perhaps a validator and type for long phone numbers is better than for
> short numbers? I guess long numbers are mostly used when reporting an
> outgoing call back to oFono.
No completely sure if it is better. Maybe it is the same?. With a new
type for long number we will have modifications on other parts of the code
which use OFONO_MAX_PHONE_NUMBER_LENGTH. The first idea could be simpler
because we just have one type and would check for the format and length on the
proper places.
> BTW, with call forwarding you could have numbers up to 16 digits or if
> longForwardedToNumber is supported (by modem and both home and visited
> networks) even 28 digits. See TS 29.002 for merry details.
Thanks for that. I am checking, and going to add an extra validator
surely.
Rafael Zurita
next prev parent reply other threads:[~2011-01-18 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 14:59 [RFC PATCH 0/3] Long phone numbers Rafael Ignacio Zurita
2011-01-17 14:59 ` [RFC PATCH 1/3] types: change OFONO_MAX_PHONE_NUMBER_LENGTH value to 80 Rafael Ignacio Zurita
2011-01-17 14:59 ` [RFC PATCH 2/3] common: split valid_phone_number_format and adapt atoms Rafael Ignacio Zurita
2011-01-17 14:59 ` [RFC PATCH 3/3] smart-messaging: Adapt to use new validation function Rafael Ignacio Zurita
2011-01-17 21:18 ` [RFC PATCH 0/3] Long phone numbers Pekka Pessi
2011-01-18 9:39 ` Rafael Ignacio Zurita [this message]
2011-01-19 4:27 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110118093908.GA20108@nodo3 \
--to=rafael.zurita@profusion.mobi \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox