RE: [Sip] SIP-T and BICC

ranjit.avasarala@wipro.com Fri, 30 January 2004 05:24 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13455 for <sip-archive@odin.ietf.org>; Fri, 30 Jan 2004 00:24:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmR8a-0001NR-FQ for sip-archive@odin.ietf.org; Fri, 30 Jan 2004 00:24:16 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0U5OG0B005289 for sip-archive@odin.ietf.org; Fri, 30 Jan 2004 00:24:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmR8L-0001MH-N5; Fri, 30 Jan 2004 00:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmR8C-0001Ld-WB for sip@optimus.ietf.org; Fri, 30 Jan 2004 00:23:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13336 for <sip@ietf.org>; Fri, 30 Jan 2004 00:23:49 -0500 (EST)
From: ranjit.avasarala@wipro.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AmR8A-0005Re-00 for sip@ietf.org; Fri, 30 Jan 2004 00:23:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AmR7D-0005Lr-00 for sip@ietf.org; Fri, 30 Jan 2004 00:22:52 -0500
Received: from wiproecmx1.wipro.com ([164.164.31.5]) by ietf-mx with esmtp (Exim 4.12) id 1AmR6X-00059L-00 for sip@ietf.org; Fri, 30 Jan 2004 00:22:14 -0500
Received: from ec-vwall-wd (ec-vwall-wd.wipro.com [10.200.52.125]) by wiproecmx1.wipro.com (8.12.9-20031013/8.12.9) with SMTP id i0U5LbvC018962 for <sip@ietf.org>; Fri, 30 Jan 2004 10:51:38 +0530 (IST)
Received: from blr-ec-bh2.wipro.com ([10.200.50.92]) by ec-vwall-wd with InterScan Messaging Security Suite; Fri, 30 Jan 2004 10:52:44 +0530
Received: from blr-ec-msg03.wipro.com ([10.200.52.99]) by blr-ec-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 30 Jan 2004 10:51:37 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] SIP-T and BICC
Date: Fri, 30 Jan 2004 10:51:37 +0530
Message-ID: <D00FAE91FFF6D242BA3126B63A9E35F6C86609@blr-ec-msg03.wipro.com>
Thread-Topic: [Sip] SIP-T and BICC
Thread-Index: AcPldgUpljJf0HNBRc2F1DRdqcPH6ABeqgYA
To: aartii@hotmail.com, sip@ietf.org
X-OriginalArrivalTime: 30 Jan 2004 05:21:37.0189 (UTC) FILETIME=[EEF21D50:01C3E6F0]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi
    You can refer RFC 3372 for SIP-T Context and Architecture. 

Ranjit
Ph: 8520408/16 extn: 2173




-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of Aarti
Iyengar
Sent: Wednesday, January 28, 2004 1:28 PM
To: sip@ietf.org
Subject: [Sip] SIP-T and BICC


All,
I am trying to understand SIP-T and BICC in detail.
>From my initial reading, both are essentially to seamlessly interface
the 
PSTN to broadband networks. SIP-T is specifically for SIP based IP
networks, 
whereas BICC is bearer independent and can interface with IP/ATM
networks 
well. Apart from that, SIP-T deals with ISUP translation and
encapsulation 
while BICC deals with extensions with ISUP for additional bearer
support. BICC CS3 will also enable SIP services to co-exist with BICC
based networks. My questions are - Are these the only key differences
between these protocols which essentially 
are intended perform the same function? If there are others, what are
they? Are there certain situations where one would fit in better than
the other, 
and if so what are these?
How well would these interoperate with each other if they have to
co-exist?

Also, any pointers to urls/whitepapers on the above (BICC versus SIP-T) 
would be appreciated.

thanks
Aarti

_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail


_______________________________________________
Sip mailing list  https://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  https://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