[SIP] Interworking Between SIP/SDP and H.323
"Fairlie-Cuninghame, Robert" <rfairlie@nuera.com> Fri, 02 February 2001 01:54 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 SMTP id UAA16963 for <sip-archive@odin.ietf.org>; Thu, 1 Feb 2001 20:54:53 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 76B304433E; Thu, 1 Feb 2001 19:55:06 -0500 (EST)
Delivered-To: sip@lists.bell-labs.com
Received: from exchange1.nuera.com (igate.nuera.com [204.216.240.98]) by lists.bell-labs.com (Postfix) with ESMTP id E6A424433A for <sip@lists.bell-labs.com>; Thu, 1 Feb 2001 19:54:35 -0500 (EST)
Received: by exchange1.nuera.com with Internet Mail Service (5.5.2650.21) id <1DWCS31T>; Thu, 1 Feb 2001 17:54:12 -0800
Message-ID: <E79883AEA37FD411A58C00508BAC5F4B710103@exchange1.nuera.com>
From: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
To: "'Henning G. Schulzrinne'" <hgs@cs.columbia.edu>, "'kns10@cs.columbia.edu'" <kns10@cs.columbia.edu>
Cc: sip@lists.bell-labs.com
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C08CBB.0A1F2480"
Subject: [SIP] Interworking Between SIP/SDP and H.323
Sender: sip-admin@lists.bell-labs.com
Errors-To: sip-admin@lists.bell-labs.com
X-BeenThere: sip@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:sip-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:sip@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/sip>, <mailto:sip-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SIP Mailing List <sip.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/sip>, <mailto:sip-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/sip/
Date: Thu, 01 Feb 2001 17:54:12 -0800
Hi Henning & Kundan, I have a query with regards to draft-singh-sip-h323-01.txt. The draft states that the destination information from the H.323 call be derived from the To URL in a new INVITE (see A.1.2). It seems that the request-URI is ignored entirely (despite the fact that some of the call flows are annotated with "INVITE sip:kns10@cs.columbia.edu"). I do not see how this will work when a SIP UA or proxy redirects (or proxies with updating the request) call to a H.323 device. For example: INVITE sip:rfairlie@nuera.com SIP/2.0 To: "Robert Fairlie-Cuninghame" <sip:rfairlie@nuera.com> is sent to the proxy at nuera.com which responds with a SIP/2.0 302 Temp Moved Contact: <sip:1000@h323-gatekeeper.nuera.com;maddr=h323-iwf.nuera.com> How will this work if the IWF ignores the Request-URI ? If the IWF instead uses the request URI in the H323 SETUP destinationInfo, is there anythign wrong with it using the display name from the To? Unless a 380 Alternate Service is issued then the display name should still be correct. On a related note in the base SIP spec, if a 380 Alternate Service is issued (which requires user interaction), the spec needs to be clarified whether the new call attempt will use a new call-leg with the To field changed apprpriately. Cheers, Robert.
- RE: [SIP] Interworking Between SIP/SDP and H.323 Fairlie-Cuninghame, Robert
- [SIP] Interworking Between SIP/SDP and H.323 Fairlie-Cuninghame, Robert
- Re: [SIP] Interworking Between SIP/SDP and H.323 Kundan Singh
- RE: [SIP] Interworking Between SIP/SDP and H.323 Fairlie-Cuninghame, Robert