From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 0/3] Long dial string support (2nd)
Date: Tue, 23 Nov 2010 11:41:40 -0600 [thread overview]
Message-ID: <4CEBFCD4.80204@gmail.com> (raw)
In-Reply-To: <cover.1290436058.git.Andras.Domokos@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On 11/22/2010 10:36 AM, Andras Domokos wrote:
> Dial strings can now be as long as 120 digits (not counting '+'). This feature
> is going to be needed by the FDN feature.
>
> An FDN may consist of a phone number plus a DTMF string. In order to have the
> call succeed when FDN is enabled, both parts need to be provided when making a
> call, as a single dial string.
So as mentioned previously, oFono does not support FDN. So why are we
doing this again?
>
> For AT modems the long dial string can be and has to be passed as is to the
Most AT modems have serious limitations on how many characters are
supported in the dial string. Not to mention that the pause character
doesn't really always work.
I can understand supporting long dialing numbers, but supporting dial
strings is something else entirely...
Regards,
-Denis
next prev parent reply other threads:[~2010-11-23 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 16:36 [PATCH 0/3] Long dial string support (2nd) Andras Domokos
2010-11-22 16:36 ` [RFC PATCH 1/3] common: add long dial string support Andras Domokos
2010-11-22 16:36 ` [RFC PATCH 2/3] voicecall: " Andras Domokos
2010-11-22 16:36 ` [RFC PATCH 3/3] isimodem/voicecall: " Andras Domokos
2010-11-22 20:58 ` [PATCH 0/3] Long dial string support (2nd) Rajesh.Nagaiah
2010-11-24 9:17 ` Andras Domokos
2010-11-23 17:41 ` Denis Kenzior [this message]
2010-11-23 18:19 ` Andras Domokos
2010-11-23 22:04 ` Denis Kenzior
2010-11-24 9:14 ` Andras Domokos
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=4CEBFCD4.80204@gmail.com \
--to=denkenz@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.