From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 2/4] voicecall: add ATD support for HFP emulator
Date: Wed, 18 May 2011 11:13:54 -0500 [thread overview]
Message-ID: <4DD3F042.4050506@gmail.com> (raw)
In-Reply-To: <4DD3E6B9.7000908@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]
Hi Frederic,
>>> + if (!strncmp(number, "*31#", 4)) {
>>> + number += 4;
>>> + clir = OFONO_CLIR_OPTION_INVOCATION;
>>> + } else if (!strncmp(number, "#31#", 4)) {
>>> + number += 4;
>>> + clir = OFONO_CLIR_OPTION_SUPPRESSION;
>>> + } else
>>> + clir = OFONO_CLIR_OPTION_DEFAULT;
>>> +
>>
>> Actually this is not quite right. The clir option is determined by the
>> presence of 'I'/'i' characters at the end of the dial string. Refer to
>> 27.007 for more details.
>>
>> oFono does not actually recognize temporary forms of *31/#31
>> invocation yet.
>>
> I added *31/#31 as I found them in telephony-ofono implementation of
> BlueZ HFP AG,
> but 27.007 uses I/i,
> and HFP 1.5 does not seem to support clir option (ATDdd...dd;)
>
> Should I remove this part of code and only be compatible with HFP specs ?
>
Might as well handle the I/i and G/g part according to 27.007 since that
is pretty easy and we'll have to do it anyway. *31/#31 is really an MMI
code, it should never be sent to the modem, so please remove that for now.
>>> + err = voicecall_dial(vc, number, clir, emulator_dial_callback, vc);
>>> + switch (err) {
>>> + case DIAL_NO_ERROR:
>>> + result.type = OFONO_ERROR_TYPE_NO_ERROR;
>>> + break;
>>> +
>>> + case DIAL_NO_NETWORK:
>>> + result.error = 30;
>>> + result.type = OFONO_ERROR_TYPE_CME;
>>> + break;
>>
>> This might need to be NO CARRIER
>>
> As far as I understand, when there is no network, ATD should reply NO
> CARRIER if CMEE error mode is set to 0, or +CME ERROR: 30 if it is set
> to 1.
Not quite. CMEE controls the presentation of 'extended' CME ERROR code.
Either as ERROR, CME ERROR: <num> or CME ERROR: <str>. NO CARRIER is
not an extended error code at all, and so is only affected by ATV
setting, not CMEE.
> So, I think that voicecall should return an OFONO_ERROR_TYPE_CME 30, and
> ofono_emulator_send_final should take care of replying the right string.
>
Nope, you have to take your pick, either CME ERROR: 30, or NO CARRIER.
I'd expect most implementations to reply with a NO CARRIER in this case,
but can you check what other implementations do in reality?
Regards,
-Denis
next prev parent reply other threads:[~2011-05-18 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 14:40 [PATCH 0/4] Add dial support for HFP emulator =?unknown-8bit?q?Fr=C3=A9d=C3=A9ric?= Danis
2011-05-12 14:40 ` [PATCH 1/4] voicecall: create generic dial function =?unknown-8bit?q?Fr=C3=A9d=C3=A9ric?= Danis
2011-05-18 4:46 ` Denis Kenzior
2011-05-12 14:40 ` [PATCH 2/4] voicecall: add ATD support for HFP emulator =?unknown-8bit?q?Fr=C3=A9d=C3=A9ric?= Danis
2011-05-18 4:53 ` Denis Kenzior
2011-05-18 15:33 ` Frederic Danis
2011-05-18 16:13 ` Denis Kenzior [this message]
2011-05-19 16:16 ` Frederic Danis
2011-05-19 16:39 ` Denis Kenzior
2011-05-12 14:40 ` [PATCH 3/4] voicecall: save last dialed number =?unknown-8bit?q?Fr=C3=A9d=C3=A9ric?= Danis
2011-05-12 14:40 ` [PATCH 4/4] voicecall: add +BLDN support for HFP emulator =?unknown-8bit?q?Fr=C3=A9d=C3=A9ric?= Danis
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=4DD3F042.4050506@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox