[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ecrit] emergency call termination
Henning,
Yes, accidental disconnects is one case including where the caller thinks he had given enough info but the call taker does not.
Drastic actions such as the one you mentioned are indeed a challenge. For the PSTN phone though, if there is more than one phone in the house (as it is usually the case), the other sets could be used to re-invite the calFrom ecrit-bounces at ietf.org Thu Jul 10 14:41:41 2008
Return-Path: <ecrit-bounces at ietf.org>
X-Original-To: ecrit-archive at megatron.ietf.org
Delivered-To: ietfarch-ecrit-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id BF6663A6AB3;
Thu, 10 Jul 2008 14:41:41 -0700 (PDT)
X-Original-To: ecrit at core3.amsl.com
Delivered-To: ecrit at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 7A5483A69BD
for <ecrit at core3.amsl.com>; Thu, 10 Jul 2008 14:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level:
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,
BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id z2i5ERX4m3FN for <ecrit at core3.amsl.com>;
Thu, 10 Jul 2008 14:41:39 -0700 (PDT)
Received: from mail70.messagelabs.com (mail70.messagelabs.com
[193.109.255.115])
by core3.amsl.com (Postfix) with ESMTP id BE9943A6ABE
for <ecrit at ietf.org>; Thu, 10 Jul 2008 14:41:11 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: g.caron at bell.ca
X-Msg-Ref: server-8.tower-70.messagelabs.com!1215726083!111653036!4
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [206.47.0.173]
Received: (qmail 23719 invoked from network); 10 Jul 2008 21:41:25 -0000
Received: from dm1c8f.bell.ca (HELO TLS.Exchange.Bell.ca) (206.47.0.173)
by server-8.tower-70.messagelabs.com with RC4-SHA encrypted SMTP;
10 Jul 2008 21:41:25 -0000
Received: from hub03-wyn.bell.corp.bce.ca (142.182.199.49) by
dm1c8f.exchange1.bell.ca (198.235.102.112) with Microsoft SMTP Server
id 8.1.278.0; Thu, 10 Jul 2008 17:41:26 -0400
Received: from toroondc550.bell.corp.bce.ca (142.182.84.162) by
hub03-wyn.bell.corp.bce.ca (142.182.199.49) with Microsoft SMTP Server
id 8.1.278.0; Thu, 10 Jul 2008 17:41:24 -0400
Received: from toroondc254.bell.corp.bce.ca ([142.182.4.53]) by
toroondc550.bell.corp.bce.ca with Microsoft SMTPSVC(6.0.3790.1830);
Thu, 10 Jul 2008 17:41:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 10 Jul 2008 17:41:23 -0400
Message-ID: <2DE9A51895931C4CBCAEFA9306AE480E848BCD at toroondc254.bell.corp.bce.ca>
In-Reply-To: <67A83811-40C2-48F3-B22F-B58A83779286 at cs.columbia.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Ecrit] emergency call termination
Thread-Index: Acji0r/Zcx99cZvNQ+WN+oZnsWVr3gAABrCg
References: <2DE9A51895931C4CBCAEFA9306AE480E848B68 at toroondc254.bell.corp.bce.ca>
<C49BCCAE.A3F0%mlinsner at cisco.com>
<2DE9A51895931C4CBCAEFA9306AE480E848BAC at toroondc254.bell.corp.bce.ca>
<67A83811-40C2-48F3-B22F-B58A83779286 at cs.columbia.edu>
From: <g.caron at bell.ca>
To: <hgs at cs.columbia.edu>
X-OriginalArrivalTime: 10 Jul 2008 21:41:24.0400 (UTC)
FILETIME=[B34AE300:01C8E2D5]
Cc: nena-i2_5 at listserv.neustar.biz, ecrit at ietf.org
Subject: Re: [Ecrit] emergency call termination
X-BeenThere: ecrit at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>,
<mailto:ecrit-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ecrit>
List-Post: <mailto:ecrit at ietf.org>
List-Help: <mailto:ecrit-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>,
<mailto:ecrit-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ecrit-bounces at ietf.org
Errors-To: ecrit-bounces at ietf.org
Henning,
Yes, accidental disconnects is one case including where the caller thinks he had given enough info but the call taker does not.
Drastic actions such as the one you mentioned are indeed a challenge. For the PSTN phone though, if there is more than one phone in the house (as it is usually the case), the other sets could be used to re-invite the caller inler into a conversation since it is the "line" that is kept alive.
Thanks,
Guy Caron
-----Message d'origine-----
De : Henning Schulzrinne [mailto:hgs at cs.columbia.edu]
Envoyé : 10 juillet 2008 17:20
À : Caron, Guy (A162859)
Cc : mlinsner at cisco.com; ecrit at ietf.org; nena-i2_5 at listserv.neustar.biz
Objet : Re: [Ecrit] emergency call termination
I assume that preventing BYE from the caller side is mainly meant to
deal with accidental disconnect. Nothing prevents a caller from
turning off the cell phone, removing its battery or unplugging the
land-line phone (or simply muting the microphone).
On Jul 10, 2008, at 3:42 PM, <g.caron at bell.ca> <g.caron at bell.ca> wrote:
> Certainly Marc.
>
> It is also my understanding that current cellular voice services
> have not implemented the network capabilities to enable PSAP control
> over call termination even if the jurisdiction requires/mandates it.
> The reasons for this are still obscure to me. I note however that
> those PSAPs using it are very disappointed of this situation in
> wireless and would like not to repeat it for Next Generation services.
>
> The situation I was referring to was more in line with PSAP
> requirements than with technical limitations. In that sense, if a
> PSAP assumes a certain behavior for devices operating in its
> jurisdiction, it would be up to the device to adjust accordingly.
>
> Thanks,
_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit
to a conversation since it is the "line" that is kept alive.
Thanks,
Guy Caron
-----Message d'origine-----
De : Henning Schulzrinne [mailto:hgs at cs.columbia.edu]
Envoyé : 10 juillet 2008 17:20
À : Caron, Guy (A162859)
Cc : mlinsner at cisco.com; ecrit at ietf.org; nena-i2_5 at listserv.neustar.biz
Objet : Re: [Ecrit] emergency call termination
I assume that preventing BYE from the caller side is mainly meant to
deal with accidental disconnect. Nothing prevents a caller from
turning off the cell phone, removing its battery or unplugging the
land-line phone (or simply muting the microphone).
On Jul 10, 2008, at 3:42 PM, <g.caron at bell.ca> <g.caron at bell.ca> wrote:
> Certainly Marc.
>
> It is also my understanding that current cellular voice services
> have not implemented the network capabilities to enable PSAP control
> over call termination even if the jurisdiction requires/mandates it.
> The reasons for this are still obscure to me. I note however that
> those PSAPs using it are very disappointed of this situation in
> wireless and would like not to repeat it for Next Generation services.
>
> The situation I was referring to was more in line with PSAP
> requirements than with technical limitations. In that sense, if a
> PSAP assumes a certain behavior for devices operating in its
> jurisdiction, it would be up to the device to adjust accordingly.
>
> Thanks,
_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit