From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Terminating emergency calls
Date: Fri, 13 Aug 2010 14:05:51 -0500 [thread overview]
Message-ID: <4C65978F.4000601@gmail.com> (raw)
In-Reply-To: <AANLkTiktt2fgxpRyg__p+f__K2gYx3kVLEXM30sfCFQf@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
Hi Sjur,
>>> I have to verify this with some of my colleagues, but I am pretty sure
>>> emergency calls cannot be applied to the AT+CHLD command. i.e. they
>>> cannot be part of mpty.
>
> Initial testing on STE modem indicates that emergency call cannot
> participate in multi call or be put on hold.
What about a somewhat backdoor of putting call on hold on some modems:
If a call is active, and you dial another call, the active call is
automatically put on hold. So if an emergency call is active and we
dial another number, what happens?
>
>>
>> If emergency calls cannot be part of mpty call, we can use either hangup_all or
>> hangup_active as Denis said. However, your suggested fix will break multiparty call
>> scenario since multiparty_hangup calls voicecall_release_next as well.
>
> Yes, you're right using hangup_active will terminate all active calls
> participating in a multi call.
> So my proposal will not work as is. Maybe we need to know if
> release_next was called for multi call?
I have commited a fix for this that I think should work just fine. Can
you please check bab23b39767b664061ac2bcba747fe2b96561ca7 and let me
know if it solves the issue?
Regards,
-Denis
next prev parent reply other threads:[~2010-08-13 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 17:39 Terminating emergency calls Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2010-08-12 18:23 ` Denis Kenzior
2010-08-12 23:10 ` Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2010-08-13 2:45 ` Zhang, Zhenhua
2010-08-13 13:44 ` Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2010-08-13 19:05 ` Denis Kenzior [this message]
2010-08-16 12:55 ` Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
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=4C65978F.4000601@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