Re: [Sip] SIPS over NAT and Firewalls

"Hulbut hulbut" <hulbut@gmail.com> Wed, 27 February 2008 11:54 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 1ACF428C4B7; Wed, 27 Feb 2008 03:54:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.465
X-Spam-Level: *
X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[AWL=-0.317, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, J_CHICKENPOX_24=0.6, RCVD_IN_SORBS_WEB=0.619, 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 vtt72abX-+TW; Wed, 27 Feb 2008 03:54:25 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E33A028C2CB; Wed, 27 Feb 2008 03:54:25 -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 06EB33A67E6 for <sip@core3.amsl.com>; Wed, 27 Feb 2008 03:54:24 -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 RlrX-cLdDmam for <sip@core3.amsl.com>; Wed, 27 Feb 2008 03:54:23 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by core3.amsl.com (Postfix) with ESMTP id B044C28C10A for <sip@ietf.org>; Wed, 27 Feb 2008 03:54:22 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id 16so1865126fgg.41 for <sip@ietf.org>; Wed, 27 Feb 2008 03:54:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=eQw/XLYF3ByQogfcDVIs6j7M2CeGHK3Cbt3vsRFmH7E=; b=RzkscTHqz7f+FKWb3cx76R0FJTsWTQ5iY7qwTr3zkLk7hHrskeWmrFKIqozW42oP47jkEW+/clSm7VU1zEt2i03lVHrjcJSXMgKvlY3BtI5w9Y+AiPCcH9wwygU317A4A3VCnj5ZQE13vki8klFJaEODlsimvVD1IXqLhuZNmb8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=sI3IJIFqzvfaNZGuDH1vZvx8WQddbVEpQ1r+SedYgEVLS1/xXTCSkC+ha3Swqd8cR1nRuvVtcxz5ed2NYMu0XhhT6s30lMKPq7OmnOl8emlu/Ija5Dk6iHq+7GT+eNd7jdUxfDMZU6hxUcLzl3jtdU17HjgmcZ2knEeihsunuxk=
Received: by 10.86.31.18 with SMTP id e18mr5934822fge.68.1204113255518; Wed, 27 Feb 2008 03:54:15 -0800 (PST)
Received: by 10.86.83.15 with HTTP; Wed, 27 Feb 2008 03:54:15 -0800 (PST)
Message-ID: <14b80930802270354p7298eb9fl48d234db539293b3@mail.gmail.com>
Date: Wed, 27 Feb 2008 17:24:15 +0530
From: Hulbut hulbut <hulbut@gmail.com>
To: PAVAN KUMAR O <acdcpavan@gmail.com>
In-Reply-To: <22f508c20802270203h53edb4f7ib33553d745887080@mail.gmail.com>
MIME-Version: 1.0
References: <22f508c20802270203h53edb4f7ib33553d745887080@mail.gmail.com>
Cc: sip@ietf.org
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="===============1377791045=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi Pavan,

Not sure abt the 1st part of ur questions...but regarding point 2 I have
some suggestions:
1) Not sure what you mean by how to transport ??....but here I assume that u
r concerned about how the packets will be seen in the REAL world. There are
several options
a) Clients can have STUN support, which will make clients transparent of any
NAT traversal
b) Proxies can be sip-outbound-draft compliant...this will take care of
routing based on actuall src IP:Port overriding 3261 based approach (routing
request based on Contact/Route hdr etc ..).
c) Your network can have a ALG , just outside NAT box.....this ALG needs to
be SIP aware and should do all the header re-writings. Unfortunately no
standard exists as such ..but some googling may help

rgds
  Hul

On Wed, Feb 27, 2008 at 3:33 PM, PAVAN KUMAR O <acdcpavan@gmail.com> wrote:

> 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
>
_______________________________________________
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