Re: [Sipping-emergency] Emergency Scenarios Document
Tom Taylor <taylor@nortelnetworks.com> Tue, 27 May 2003 16:48 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19355
for <sipping-emergency-archive@odin.ietf.org>;
Tue, 27 May 2003 12:48:45 -0400 (EDT)
Received: (from mailnull@localhost)
by www1.ietf.org (8.11.6/8.11.6) id h4RGmK102476
for sipping-emergency-archive@odin.ietf.org; Tue, 27 May 2003 12:48:20 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4RGmKB02473
for <sipping-emergency-web-archive@optimus.ietf.org>;
Tue, 27 May 2003 12:48:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19332
for <sipping-emergency-web-archive@ietf.org>;
Tue, 27 May 2003 12:48:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 19Khb1-00065Y-00
for sipping-emergency-web-archive@ietf.org; Tue, 27 May 2003 12:46:43 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 19Khb0-00065V-00
for sipping-emergency-web-archive@ietf.org; Tue, 27 May 2003 12:46:42 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4RGmJB02465
for <sipping-emergency-web-archive@ietf.org>; Tue, 27 May 2003 12:48:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4RGluB02433
for <sipping-emergency@optimus.ietf.org>; Tue, 27 May 2003 12:47:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19318
for <sipping-emergency@ietf.org>; Tue, 27 May 2003 12:47:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 19Khad-00065G-00
for sipping-emergency@ietf.org; Tue, 27 May 2003 12:46:19 -0400
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
by ietf-mx with esmtp (Exim 4.12) id 19Khac-00065C-00
for sipping-emergency@ietf.org; Tue, 27 May 2003 12:46:18 -0400
Received: from zcard307.ca.nortel.com (americasm03.nt.com [47.129.242.67])
by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
h4RGlHc24208; Tue, 27 May 2003 12:47:17 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by
zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service
Version 5.5.2653.13) id KRLF6T21; Tue, 27 May 2003 12:47:17 -0400
Received: from nortelnetworks.com (acart1ct.ca.nortel.com [47.129.129.69]) by
zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service
Version 5.5.2653.13) id JQNA0M0D; Tue, 27 May 2003 12:47:17 -0400
Message-ID: <3ED3968C.9060601@nortelnetworks.com>
Date: Tue, 27 May 2003 12:47:08 -0400
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.3) Gecko/20030312
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: "McCalmont, Patti" <PMcCalmont@intrado.com>
CC: sipping-emergency@ietf.org, Patrick.Emery@aca.gov.au,
dick.rr.knight@bt.com, "Mary Barnes" <mbarnes@nortelnetworks.com>,
"James McEachern" <jmce@nortelnetworks.com>, steve.norreys@bt.com
Subject: Re: [Sipping-emergency] Emergency Scenarios Document
References: <19B3D8818B23554581D1E8C65C2964392DB8B2@jaguar.scc911.com>
In-Reply-To: <19B3D8818B23554581D1E8C65C2964392DB8B2@jaguar.scc911.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-emergency-admin@ietf.org
Errors-To: sipping-emergency-admin@ietf.org
X-BeenThere: sipping-emergency@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>,
<mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Id: <sipping-emergency.ietf.org>
List-Post: <mailto:sipping-emergency@ietf.org>
List-Help: <mailto:sipping-emergency-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>,
<mailto:sipping-emergency-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
I'll be replying to Henning's comments, but since this note is relatively short I'll address it first. McCalmont, Patti wrote: > Section 3.3 > > >> In the legacy network ....mapping database. > > > The term "mapping database is used a few times within the document. Is mapping > database trying to refer to a selective routing database that is used to > determine how to route the call based on the location of the caller to the PSAP? > If so, a better term would be location database or selective routing database > (term used in US/Canada. Or, is it trying to refer to the phone number to > location information, Automatic Location Identification (ALI) database, or both? > Some clarification is needed. [PTT] I'll clarify. In North American terms I'm referring to the ALI database. > > For PBX operation, an additional issue is that telephone number assignments are > under control of the private network operator. PBXs without > direct-inward-dialing (DID) introduce an additional challenge. Typically, the > calling number is used as a unique reference to identify the caller's location. > > Without CAMA or PRI connections for emergency calls, those PBX locations cannot > convey the caller's identity (even with DID). What is typically used is the > Billing Number or Main Directory number for the PBX when they don't have the > CAMA/PRI. There may need some clarification as connections required in order to > provide the DID stations or is that what was trying to be said with > "administrative arrangements"? [PTT] I seem to have gotten this wrong, as you and Henning point out. I'll have to extend the discussion. > > > A special arrangement at the switch serving the ECC allows the emergency operator > to hold open the voice path back to the caller as long as necessary, even if the > caller goes on-hook. It should be noted that this functionality is not supported > for ISDN. Thus, the operator can also ring the caller's line in this situation or > others where it might be necessary. > > Call Hold applies globally to Basic 911 and is an option for Enhanced 9-1-1 so > which type of "legacy network" is described in this section. If Enhanced 9-1-1, > then Call Hold (as stated later) is an optional feature. > > Henning wrote: I would qualify this as "In analog switches, ....". Most switches > today are effectively ISDN (or equivalent), so this feature is likely only > available to a tiny fraction of end systems. > > Most switches today are digital so I don't like the term "analog switches". It > would be better to talk about the interfaces into the switch as being analog or > digital (ISDN). [PTT] Yes, that's right. In North America, there aren't many ISDN lines, but in Europe there are. In both places, most switches are digital. > > > Section 4.3.1 > >> There is still the problem of distinguishing between voice and text emergency >> calls. If the user enters an actual emergency number, that can be the one that >> serves the user's needs. If the configuration is by DHCP or SIP registrar, it >> may be that selection of the appropriate number is based on pre-configuration >> of the SIP phone as voice or text bas > > > Henning wrote: Unless I'm really off my rocker, the number is the same for TDD > calls. See http://www.nena.org/PR_Pubs/9-1-1QandA.htm for evidence. > > He is correct. It's the equipment at the PSAP that detects the call as TDD > nothing in how the user dials. [PTT] That's in North America. It's different in Australia. I suppose I should modify the discussion to make it clear that the requirement is only present in some countries. > > Patti McCalmont > > _______________________________________________ Sipping-emergency mailing list > Sipping-emergency@ietf.org > https://www1.ietf.org/mailman/listinfo/sipping-emergency > _______________________________________________ Sipping-emergency mailing list > Sipping-emergency@ietf.org > https://www1.ietf.org/mailman/listinfo/sipping-emergency > _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency
- [Sipping-emergency] Emergency Scenarios Document Tom Taylor
- [Sipping-emergency] [Fwd: RE: Emergency Scenarios… Tom Taylor
- Re: [Sipping-emergency] Emergency Scenarios Docum… Henning Schulzrinne
- Re: [Sipping-emergency] Emergency Scenarios Docum… Henning Schulzrinne
- RE: [Sipping-emergency] Emergency Scenarios Docum… McCalmont, Patti
- Re: [Sipping-emergency] Emergency Scenarios Docum… Tom Taylor
- RE: [Sipping-emergency] Emergency Scenarios Docum… dick.rr.knight
- Re: [Sipping-emergency] Emergency Scenarios Docum… Tom Taylor