RE: [Sip] about H.323 and SIP

"Paul Long" <plong@ipdialog.com> Thu, 13 September 2001 16:33 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 MAA08092 for <sip-archive@odin.ietf.org>; Thu, 13 Sep 2001 12:33:36 -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 MAA15704; Thu, 13 Sep 2001 12:16:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15678 for <sip@ns.ietf.org>; Thu, 13 Sep 2001 12:16:15 -0400 (EDT)
Received: from ns2.austin.rr.com ([24.93.35.63]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07456 for <sip@ietf.org>; Thu, 13 Sep 2001 12:16:06 -0400 (EDT)
Received: from plong1 (cs666831-164.austin.rr.com [66.68.31.164]) by ns2.austin.rr.com (8.12.0.Beta16/8.12.0.Beta16) with SMTP id f8DGBnjd011273 for <sip@ietf.org>; Thu, 13 Sep 2001 11:11:50 -0500
From: Paul Long <plong@ipdialog.com>
To: sip@ietf.org
Subject: RE: [Sip] about H.323 and SIP
Date: Thu, 13 Sep 2001 11:15:30 -0500
Message-ID: <NEBBIELHMLDIACLLJHCNGEKHDDAA.plong@ipdialog.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <000501c13c5a$5b8412f0$b7540e3f@cxo.dec.com>
Content-Transfer-Encoding: 7bit
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: 7bit

Michael,

If the H.323 endpoint is unregistered or uses the direct call model and
pregranted ARQs, only a single message (Setup) is necessary in H.323 to
setup a call.

Paul Long
ipDialog, Inc.

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Michel
A. Maddux
Sent: Thursday, September 13, 2001 8:46 AM
To: 'Na Li'; sip@ietf.org
Subject: RE: [Sip] about H.323 and SIP


Lina writes:
>>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.

Actually, there isn't a single fundamental difference.  There are many
differences, and yet, both protocols objective at the highest level is the
same - call setup, management - teardown.  Perhaps you would like to refer
to a couple of the papers that are posted on the Columbia web-site.  There
have been several papers developed on the SIP-H.323 comparison.

To me, the fundamental difference is in the use of a single message (INVITE)
on the SIP side, compared to the multiple message traffic (e.g. ARQ, LRQ,
and so on) required to setup the calls.  There are many other differences as
well, so the challenge in mapping the two protocols is to determine from a
functional level the intent of the caller and map to the appropriate call or
sequence of calls on the other side.

>>2) Could Media gateway controller use H.323 for session creation, and
>>use Megaco to communicate with media gateway?

Well, I suppose anything is possible.  Why do you want to do it that way?

>>3) Is any standard there to map H.323 with SIP?

Check the internet drafts already available on this subject.

thanks. /m.

Michel A. Maddux
CEO and Lead Guitarist
*:  719-686-9733
*:  719-337-4727 Mobile
*  madflatpicker01@rmi.net
*  PO BOX 3087
      Colorado Springs, Colorado 80934






_______________________________________________
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