IETF Logo Mail Archive

[Sipping-emergency] Re: Report on sipemergency call

Henning Schulzrinne <hgs@cs.columbia.edu> Fri, 04 April 2003 05:43 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 AAA26581 for <sipping-emergency-archive@odin.ietf.org>; Fri, 4 Apr 2003 00:43:24 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h345k2x02853 for sipping-emergency-archive@odin.ietf.org; Fri, 4 Apr 2003 00:46:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h345k1K02850 for <sipping-emergency-web-archive@optimus.ietf.org>; Fri, 4 Apr 2003 00:46:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26578 for <sipping-emergency-web-archive@ietf.org>; Fri, 4 Apr 2003 00:42:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h345k0K02841 for <sipping-emergency-web-archive@ietf.org>; Fri, 4 Apr 2003 00:46:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h345jpK02823 for <sipping-emergency@optimus.ietf.org>; Fri, 4 Apr 2003 00:45:51 -0500
Received: from jalapeno.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26575 for <sipping-emergency@ietf.org>; Fri, 4 Apr 2003 00:42:33 -0500 (EST)
Received: from cs.columbia.edu (dhcp64-134-126-202.sjcc.sjc.wayport.net [64.134.126.202]) (user=hgs10 mech=PLAIN bits=0) by jalapeno.cc.columbia.edu (8.12.8p1/8.12.8) with ESMTP id h345j1vP024408 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 4 Apr 2003 00:45:02 -0500 (EST)
Message-ID: <3E8D1B20.4050606@cs.columbia.edu>
Date: Fri, 04 Apr 2003 00:41:52 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: Emergency <sipping-emergency@ietf.org>
References: <004901c2f951$09038cd0$ee036e3f@txdwillis> <3E8B5F57.4030007@dynamicsoft.com> <3E8B7338.803@cs.columbia.edu> <3E8BB7A7.9090603@dynamicsoft.com>
In-Reply-To: <3E8BB7A7.9090603@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping-emergency] Re: Report on sipemergency call
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 mean, making sure that resources are available, whatever they may be, 
> for completing a 911 call. I have heard (again, just what I've heard) 
> that a 5E will hang up an existing non-emergency call if it is in an 
> all-circuits busy condition when it receives a 911 call. This would seem 
> to relate to the ieprep stuff, I suppose.

Never heard that mentioned, including the relevant Bellcore document.

> 
> -Jonathan R.
> 

_______________________________________________
Sipping-emergency mailing list
Sipping-emergency@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-emergency

v2.8.7 | Report a Bug | By Email