RE: [Sip] about H.323 and SIP

De Leo Walter <deleow@TELEFONICA.COM.AR> Sat, 22 September 2001 00:45 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 UAA09006 for <sip-archive@odin.ietf.org>; Fri, 21 Sep 2001 20:45:26 -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 TAA27934; Fri, 21 Sep 2001 19:56:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA27905 for <sip@optimus.ietf.org>; Fri, 21 Sep 2001 19:56:20 -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 TAA08461 for <sip@ietf.org>; Fri, 21 Sep 2001 19:56:55 -0400 (EDT)
Received: by MAIL1 with Internet Mail Service (5.5.2653.19) id <TL053ZZG>; Fri, 21 Sep 2001 20:55:36 -0300
Message-ID: <19364262E259D51198BA0008C7E6528E091AC2@MSTELEFONICA8>
From: De Leo Walter <deleow@TELEFONICA.COM.AR>
To: 'Matt Holdrege' <matt@ipverse.com>, De Leo Walter <deleow@TELEFONICA.COM.AR>, "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] about H.323 and SIP
Date: Fri, 21 Sep 2001 20:55:33 -0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
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

Yes, I think you are right. My only neurone is getting old.

Regards.


> -----Mensaje original-----
> De:	Matt Holdrege [SMTP:matt@ipverse.com]
> Enviado el:	Viernes 21 de Septiembre de 2001 17:12
> Para:	De Leo Walter; 'sip@ietf.org'
> Asunto:	RE: [Sip] about H.323 and SIP
> 
> Interworking pure ISUP and pure SIP is implementation specific. To be 
> clear, I'm referring to a call setup from an ISUP network to a Softswitch,
> 
> and the Softswitch generating a SIP/SDP setup based on policy. The same 
> goes for a call in the other direction.
> 
> However, transporting or preserving ISUP information using SIP requires a 
> standard, thus we have SIP-T modes of encapsulation and mapping. This is 
> the way to go if you do not want the Softswitch to generate the call
> details.
> 
> I hope I'm making myself clear as I'm kind of jet lagged right now.
> 
> 
> At 11:15 AM 9/18/2001, De Leo Walter wrote:
> >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 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