Re: [SIP] SIP Usages

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Thu, 06 July 2000 03:19 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 ESMTP id XAA23667 for <sip-archive@odin.ietf.org>; Wed, 5 Jul 2000 23:19:13 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 93CF1443AE; Wed, 5 Jul 2000 23:19:01 -0400 (EDT)
Delivered-To: sip@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51]) by lists.bell-labs.com (Postfix) with ESMTP id 519B844341 for <sip@lists.bell-labs.com>; Wed, 5 Jul 2000 23:18:58 -0400 (EDT)
Received: from dynamicsoft.com (1Cust141.tnt1.freehold.nj.da.uu.net [63.17.113.141]) by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id XAA09138; Wed, 5 Jul 2000 23:20:00 -0400 (EDT)
Message-ID: <3963FB23.C7FD1D53@dynamicsoft.com>
Date: Wed, 05 Jul 2000 23:21:07 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Pathangi N Janardhanan <janar@netlab.hcltech.com>
Cc: sip@lists.bell-labs.com
Subject: Re: [SIP] SIP Usages
References: <002401bfe65d$b6cb7f80$38c9a8c0@labs>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-admin@lists.bell-labs.com
Errors-To: sip-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id: IETF SIP Mailing List <sip.lists.bell-labs.com>
X-BeenThere: sip@lists.bell-labs.com
Content-Transfer-Encoding: 7bit


Pathangi N Janardhanan wrote:
> 
> Hi,
> 
>   Is there any document or paper which talks about the various
> applications that
> can be build for the SIP protocol.
> 
>   Some of the ones are
> 
> a) use of SIP for VoIP terminal

This is the primary application of SIP and well discussed in the
specification itself, in addition to almost any paper or presentation
you might find at:
http://www.cs.columbia.edu/~hgs/sip

> b) Use of SIP for MGC to MGC communication

See the various SIP-T drafts, of which you mention just one:

http://www.softarmor.com/sipwg/drafts/draft-zimmerer-sip-bcp-t-00.txt
http://www.softarmor.com/sipwg/drafts/draft-zimmerer-sip-isup-mime-01.txt
http://www.softarmor.com/sipwg/drafts/draft-watson-sip-isup-mime-00.txt
http://www.softarmor.com/sipwg/drafts/draft-camarillo-sip-isup-bcp-00.txt

I also have some slides on this subject:
http://www.cs.columbia.edu/~jdrosen/papers/vondev_intermgc_final.ppt

> 
> The draft "draft-ietf-sip-isup-mime" talks of carrying ISUP/QSIG
> messages in SIP messages,
> where would such a need be felt. For tunneling ISUP/QSIG messages
> would SIGTRAN not
> be a better approach?

Not if you want to derive call control from SIP itself, in order to
access features available from SIP, or talk to endpoints for which you
don't know apriori that they are another ss7 connected softswitch.

-Jonathan R.

-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
SIP mailing list
SIP@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/sip