FW: [Sip] about H.323 and SIP

"Na Li" <lina@ashleylaurent.com> Thu, 13 September 2001 15:36 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 LAA05981 for <sip-archive@odin.ietf.org>; Thu, 13 Sep 2001 11:36:10 -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 LAA13290; Thu, 13 Sep 2001 11:11:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13256 for <sip@ns.ietf.org>; Thu, 13 Sep 2001 11:11:43 -0400 (EDT)
Received: from voyager.ashleylaurent.com (goodhope.vpcom.com [207.207.28.147]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05353 for <sip@ietf.org>; Thu, 13 Sep 2001 11:11:29 -0400 (EDT)
content-class: urn:content-classes:message
Subject: FW: [Sip] about H.323 and SIP
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Thu, 13 Sep 2001 10:11:57 -0500
Message-ID: <387DCE97A6A6CC40B4A6E090A955B5E0256467@voyager.ashleylaurent.com>
Thread-Topic: [Sip] about H.323 and SIP
Thread-Index: AcE8MWTS6SQnMTwQSwaC1nbutCX/EwANQBdg
From: Na Li <lina@ashleylaurent.com>
To: sip@ietf.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA13258
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
Content-Transfer-Encoding: 8bit

 
 
-----Original Message-----
From: Peter.Gajdos@proin.com [mailto:Peter.Gajdos@proin.com] 
Sent: Thursday, September 13, 2001 3:51 AM
To: Na Li
Subject: Re: [Sip] about H.323 and SIP
 

Hi Lina, 

to your questions: 

1) The fundamental difference is in the model these two use - as you
probably know the SIP uses the Internet model - transaction oriented
(IETF) while H.323 uses "old-style" circtuit switched thinking (ITU-T). 

2) This is implementation specific. I can say that they are vendors
whose equipment can do exactly what you write (incl. the situation when
H.323 is replaced by SIP). 

3) There's no standard, but as far as I remember there is a draft
dealing with this: draft-agrawal-sip-h323-interworking-01.txt 

Kind regards 

--Peter 



 
"Na Li" <lina@ashleylaurent.com> 
Sent by: sip-admin@ietf.org 
09/13/2001 02:15 AM 
        
        To:        <sip@ietf.org> 
        cc:         
        Subject:        [Sip] about H.323 and SIP



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