RE: [Sip] about H.323 and SIP
De Leo Walter <deleow@TELEFONICA.COM.AR> Wed, 19 September 2001 22:48 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12063 for <sip-archive@odin.ietf.org>; Wed, 19 Sep 2001 18:48:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA22025; Wed, 19 Sep 2001 18:13:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA21932 for <sip@optimus.ietf.org>; Wed, 19 Sep 2001 18:13:10 -0400 (EDT)
Received: from mail1.telefonica.com.ar (mail.telefonica.com.ar [168.226.49.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11784 for <sip@ietf.org>; Wed, 19 Sep 2001 18:13:08 -0400 (EDT)
Received: by MAIL1 with Internet Mail Service (5.5.2653.19) id <THR8M1WT>; Wed, 19 Sep 2001 19:11:08 -0300
Message-ID: <19364262E259D51198BA0008C7E6528E091AB4@MSTELEFONICA8>
From: De Leo Walter <deleow@TELEFONICA.COM.AR>
To: "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] about H.323 and SIP
Date: Tue, 18 Sep 2001 15:15:16 -0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
Matt, Applying your reasoning to the ISUP-SIP interface, you cannot understand why is that interface being defined, and perhaps becoming an standar? Do you think it should be left implementation specific? I don't. Regards. Walter. > -----Mensaje original----- > De: Matt Holdrege [SMTP:matt@ipverse.com] > Enviado el: Jueves 13 de Septiembre de 2001 14:04 > Para: Na Li; sip@ietf.org > Asunto: Re: [Sip] about H.323 and SIP > > It's perfectly simple in concept that an MGC would speak H.323 on one > interface and SIP on another. In fact some MGC's or Softswitches do this > today. So if an MGC receives a call setup from an H.323 Gatekeeper which > is > intended for a SIP network, it would simply send a call setup to the SIP > proxy that has reachability for the destination and upon receipt of an RTP > > address would instruct the H.323 Gatekeeper or gateway to open up an RTP > connnection. > > A similar action would take place if a call was destined for the PSTN and > the MGC needed use SIP-T to contact another MGC to setup the call at the > remote PSTN network. The far end MGC would speak MGCP or MEGACO/H.248 to > control the trunking gateway to the PSTN. > > Since such protocol interworking occurs internal to a given platform/MGC, > there is no standard nor should there be. It is implementation specific as > > there is no interworking with other elements. > > > At 05:15 PM 9/12/2001, Na Li wrote: > >Hello, > > > >I have several questions relating to H.323 > > > >1) What's the fundamental difference between H.323 (including fast > >setup) and SIP? I don't mean the text encoding or ANS.1 encoding. > >2) Could Media gateway controller use H.323 for session creation, and > >use Megaco to communicate with media gateway? > >3) Is any standard there to map H.323 with SIP? > > > >Thanks, have a nice day > > > >Lina > > > >_______________________________________________ > >Sip mailing list http://www1.ietf.org/mailman/listinfo/sip > >This list is for NEW development of the core SIP Protocol > >Use sip-implementors@cs.columbia.edu for questions on current sip > >Use sipping@ietf.org for new developments on the application of sip > > > _______________________________________________ > Sip mailing list http://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use sip-implementors@cs.columbia.edu for questions on current sip > Use sipping@ietf.org for new developments on the application of sip _______________________________________________ Sip mailing list http://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] about H.323 and SIP Na Li
- RE: [Sip] about H.323 and SIP Michel A. Maddux
- FW: [Sip] about H.323 and SIP Na Li
- RE: [Sip] about H.323 and SIP Cullen Jennings
- RE: [Sip] about H.323 and SIP Paul Long
- RE: [Sip] about H.323 and SIP Paul Long
- Re: [Sip] about H.323 and SIP Matt Holdrege
- RE: [Sip] about H.323 and SIP Henry Sinnreich
- RE: [Sip] about H.323 and SIP Paul Long
- RE: [Sip] about H.323 and SIP Henry Sinnreich
- RE: [Sip] about H.323 and SIP Agboh, Charles
- RE: [Sip] about H.323 and SIP Peter.Gajdos
- RE: [Sip] about H.323 and SIP Michel A. Maddux
- RE: [Sip] about H.323 and SIP Paul Long
- RE: [Sip] about H.323 and SIP Rosen, Brian
- Re: [Sip] about H.323 and SIP Suheel Hussain
- RE: [Sip] about H.323 and SIP Naidu, Venkata
- Re: [Sip] about H.323 and SIP Henning G. Schulzrinne
- RE: [Sip] about H.323 and SIP Naidu, Venkata
- RE: [Sip] about H.323 and SIP Paul Long
- RE: [Sip] about H.323 and SIP De Leo Walter
- RE: [Sip] about H.323 and SIP Matt Holdrege
- RE: [Sip] about H.323 and SIP De Leo Walter