From: Andras Domokos <andras.domokos@nokia.com>
To: ofono@ofono.org
Subject: Re: [PATCH 0/3] Long dial string support (2nd)
Date: Wed, 24 Nov 2010 11:17:19 +0200 [thread overview]
Message-ID: <4CECD81F.1030802@nokia.com> (raw)
In-Reply-To: <C681C76E0D5F1E4BB01DE79E0A80EEC702CCB78F@usrdes03.ebgroup.elektrobit.com>
[-- Attachment #1: Type: text/plain, Size: 2182 bytes --]
Hi Rajesh,
On 11/22/2010 10:58 PM, ext Rajesh.Nagaiah(a)elektrobit.com wrote:
> Hi Andras,
>
>
>> 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.
>>
>> For AT modems the long dial string can be and has to be
>> passed as is to the modem, for ISI modems the dial string
>> needs to be split into phone number (dest.
>> address sub block) and DTMF tone (post dest. address sub
>> block) before feeding it to the modem.
>>
> Sending the DTMF tone in post dest. address sub block in case of
> the ISI modem or sending as part of the dial string in case of
> AT modems, will the modem take care of DTMF postfix handling by
> itself or its only going to use that for FDN check ?
>
> If its going to be earlier case, then not all modems support
> this feature and also sending the postfix DTMF tone automatically
> by the modem without notifying to the AP, then the user neither
> wont be aware of ongoing DTMF tone sending as there will be no
> local playback of the tone nor will have any control over the
> DTMF tones sending.
>
> So we should parse the dial string and extract the DTMF postfix
> (after the FDN check, anyways we are not suppoting FDN in oFono).
> Once the call gets connected, then the postfix DTMF tones can be
> sent out and signaled to the application about the start and stop
> events of each tone, so the application can generate the
> corresponding DTMF tones using the tonegenerator for local
> playback.
>
> Also currently the "w"/"W" stop character handling is not there,
> so I am not sure if its intentionally left out or missing ?
>
I think the situation has been clarified based on the
discussion with Denis. I stop pushing these patches.
> BR,
> Rajesh
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> http://lists.ofono.org/listinfo/ofono
>
Regards,
Andras
next prev parent reply other threads:[~2010-11-24 9:17 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 [this message]
2010-11-23 17:41 ` Denis Kenzior
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=4CECD81F.1030802@nokia.com \
--to=andras.domokos@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox