[SIP] draft-singh-sip-h323-01.txt comments
"Schroeder, Tim" <schroeder@tri.sbc.com> Thu, 18 May 2000 22:46 UTC
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13934 for <sip-archive@odin.ietf.org>; Thu, 18 May 2000 18:46:08 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 44C374437F; Thu, 18 May 2000 18:38:34 -0400 (EDT)
Delivered-To: sip@lists.bell-labs.com
Received: from howler.tri.sbc.com (howler.tri.sbc.com [205.173.58.4]) by lists.bell-labs.com (Postfix) with ESMTP id 8241F44337 for <sip@lists.bell-labs.com>; Thu, 18 May 2000 18:38:31 -0400 (EDT)
Received: from sbctri.tri.sbc.com (sbctri [144.60.1.10]) by howler.tri.sbc.com (8.9.3/8.9.3) with ESMTP id RAA11948 for <sip@lists.bell-labs.com>; Thu, 18 May 2000 17:47:51 -0500 (CDT)
Received: from trimail2.tri.sbc.com (trimail2 [144.60.55.227]) by sbctri.tri.sbc.com (8.9.3/8.9.3) with ESMTP id RAA29955 for <sip@lists.bell-labs.com>; Thu, 18 May 2000 17:45:27 -0500 (CDT)
Received: by trimail2.tri.sbc.com with Internet Mail Service (5.5.2448.0) id <KLDB8JR3>; Thu, 18 May 2000 17:45:27 -0500
Message-ID: <4D45BA2A58A7D3119E050008C7E69E290790C9@trimail2.tri.sbc.com>
From: "Schroeder, Tim" <schroeder@tri.sbc.com>
To: sip@lists.bell-labs.com
Date: Thu, 18 May 2000 17:45:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [SIP] draft-singh-sip-h323-01.txt comments
Sender: sip-admin@lists.bell-labs.com
Errors-To: sip-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id: IETF SIP Mailing List <sip.lists.bell-labs.com>
X-BeenThere: sip@lists.bell-labs.com
5.1.3, considering the case where the IWF does not contain a registrar or a gatekeeper, says "If the destination address does not indicate the signaling protocol, a SIP proxy server has to forward all incoming requests to a local IWF, just in case the destination happens to be reachable via H.323." Is this strictly true? It would seem to me that a SIP proxy would first try to find the called party using its normal SIP mechanisms, which would work as usual for most cases (SIP-to-SIP, non-interworked calls). Only if the SIP proxy could not find the called party would it forward the call to an H.323 IWF, hoping to find the destination in the H.323 cloud before returning a 404 Not Found response. 4, requirement #2, says "the user may dial any address without actually knowing whether it belongs to the H.323 or the SIP cloud" Is 'dial' referring to a SIP request to a tel URL? Or just a request with a more general destination (perhaps an alias) than a sip URL? Tim Schroeder SBC Technology Resources _______________________________________________ SIP mailing list SIP@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/sip
- [SIP] draft-singh-sip-h323-01.txt comments Schroeder, Tim