Re: [Sip] SIPS over NAT and Firewalls

"Avasarala Ranjit-A20990" <ranjit@motorola.com> Wed, 27 February 2008 12:04 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: ietfarch-sip-archive@core3.amsl.com
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F06FB28C7B2; Wed, 27 Feb 2008 04:04:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.053
X-Spam-Level:
X-Spam-Status: No, score=-0.053 tagged_above=-999 required=5 tests=[AWL=-0.616, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRI2Ych6Nf2U; Wed, 27 Feb 2008 04:04:40 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB3B528C4B9; Wed, 27 Feb 2008 04:04:39 -0800 (PST)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A72328C4C6 for <sip@core3.amsl.com>; Wed, 27 Feb 2008 04:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id csUZfkRBugLq for <sip@core3.amsl.com>; Wed, 27 Feb 2008 04:04:37 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.179]) by core3.amsl.com (Postfix) with SMTP id 3FE0328C5D1 for <sip@ietf.org>; Wed, 27 Feb 2008 04:04:37 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: ranjit@motorola.com
X-Msg-Ref: server-3.tower-119.messagelabs.com!1204113869!50633691!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.189.100.102]
Received: (qmail 12574 invoked from network); 27 Feb 2008 12:04:29 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102) by server-3.tower-119.messagelabs.com with SMTP; 27 Feb 2008 12:04:29 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate4.mot.com (8.12.11/Motorola) with ESMTP id m1RC4TM8018482 for <sip@ietf.org>; Wed, 27 Feb 2008 05:04:29 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id m1RC4SF3000686 for <sip@ietf.org>; Wed, 27 Feb 2008 06:04:28 -0600 (CST)
Received: from ZMY16EXM66.ds.mot.com (zmy16exm66.ap.mot.com [10.179.4.26]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id m1RC4QSw000657 for <sip@ietf.org>; Wed, 27 Feb 2008 06:04:27 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 27 Feb 2008 20:04:24 +0800
Message-ID: <750BBC72E178114F9DC4872EBFF29A5B0544FF5A@ZMY16EXM66.ds.mot.com>
In-Reply-To: <22f508c20802270203h53edb4f7ib33553d745887080@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] SIPS over NAT and Firewalls
Thread-Index: Ach5KBOJXFs/0P1bSxGZR9H5AmxRZwAEMnag
From: Avasarala Ranjit-A20990 <ranjit@motorola.com>
To: PAVAN KUMAR O <acdcpavan@gmail.com>, sip@ietf.org
X-CFilter-Loop: Reflected
Subject: Re: [Sip] SIPS over NAT and Firewalls
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1952976877=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
Hi Pavan
 
For question 1) implementing sips means implementing TLS. So the SIP
stack would use SIP over TLS/TCP or DTLS over UDP. Then the URI would be
sips: Refer to RFC 3261 for more details about which flags / headers
need to changed.
I think transportation of either sip or sips messages over NAT/Firewall
remains almost same. For more details on SIP over NAT refer to RFC 3489
which explains STUN (Simple Traversal of Udp over NAT).
 
Regards 
Ranjit 

 

________________________________

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
PAVAN KUMAR O
Sent: Wednesday, February 27, 2008 3:33 PM
To: sip@ietf.org
Subject: [Sip] SIPS over NAT and Firewalls


Hi all,
 
       I am Pavan.I am working on implementing security features for SIP
on a Voip enabled phone.\
1) I am bit confused with the implementation of "sips" scheme and the
necessary changes to be made in the sip headers to make them comply with
sips scheme.
2) How to transport sip/sips messages over NAT or Firewall??
 
Any help in this regard will be greatly appreciated.
 
Thanks & Regards
Pavan Kumar O
M.E Embedded Systems
BITS Pilani
India
_______________________________________________
Sip mailing list  https://www.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