RE: [Sip] From Header

ranjit.avasarala@wipro.com Tue, 24 February 2004 05:06 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13968 for <sip-archive@odin.ietf.org>; Tue, 24 Feb 2004 00:06:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvUlq-0001ml-U2 for sip-archive@odin.ietf.org; Tue, 24 Feb 2004 00:06:15 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1O56EPc006800 for sip-archive@odin.ietf.org; Tue, 24 Feb 2004 00:06:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvUle-0001ku-Bx; Tue, 24 Feb 2004 00:06:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvUlN-0001jU-ER for sip@optimus.ietf.org; Tue, 24 Feb 2004 00:05:47 -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 AAA13921 for <sip@ietf.org>; Tue, 24 Feb 2004 00:05:41 -0500 (EST)
From: ranjit.avasarala@wipro.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvUlL-0005xC-00 for sip@ietf.org; Tue, 24 Feb 2004 00:05:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvUkP-0005rv-00 for sip@ietf.org; Tue, 24 Feb 2004 00:04:46 -0500
Received: from wiproecmx2.wipro.com ([164.164.31.6]) by ietf-mx with esmtp (Exim 4.12) id 1AvUje-0005hx-00 for sip@ietf.org; Tue, 24 Feb 2004 00:03:59 -0500
Received: from ec-vwall-wd (ec-vwall-wd.wipro.com [10.200.52.125]) by wiproecmx2.wipro.com (8.12.9-20031013/8.12.9) with SMTP id i1O53QqA004817 for <sip@ietf.org>; Tue, 24 Feb 2004 10:33:26 +0530 (IST)
Received: from blr-ec-bh3.wipro.com ([10.200.50.93]) by ec-vwall-wd with InterScan Messaging Security Suite; Tue, 24 Feb 2004 10:34:26 +0530
Received: from blr-ec-msg03.wipro.com ([10.200.52.99]) by blr-ec-bh3.wipro.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 24 Feb 2004 10:33:25 +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] From Header
Date: Tue, 24 Feb 2004 10:33:25 +0530
Message-ID: <D00FAE91FFF6D242BA3126B63A9E35F6D81F3F@blr-ec-msg03.wipro.com>
Thread-Topic: [Sip] From Header
Thread-Index: AcP6QYpFb0302AXqSp6JDD6/9myKwQAUt4qQ
To: ABollineni@netscreen.com, boyliangxt@yahoo.com
Cc: sip@ietf.org, sip-implementors@cs.columbia.edu
X-OriginalArrivalTime: 24 Feb 2004 05:03:25.0353 (UTC) FILETIME=[887CE990:01C3FA93]
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=AWL, 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 Anil,

If I understand you correctly then I think you want to know the sender's
IP and port number. This information can be obtaine from the SDP. Via
header gives information of Proxy not of sender's.

Ranjit

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of Anil
Bollineni
Sent: Tuesday, February 24, 2004 12:43 AM
To: 'xiao'tong liang'
Cc: 'sip@ietf.org'; 'sip-implementors@cs.columbia.edu'
Subject: RE: [Sip] From Header


The Via header tells that IP address/port where the response should be
sent. It does not specify from where the request has been come, as the
ports for sending request and receiving responses can be different. I
think the only way we can tell is by seeing the sending ip and port in
IP header of the packet. Please correct if I am wrong.

Thanks,
Anil


This email contains material that is confidential. The content of this
email is for the sole use of the intended recipient(s). Any review or
distribution by persons other than the intended recipient(s) without the
express permission of NetScreen Technologies, Inc. is strictly
prohibited. If you are not the intended recipient, please contact the
sender and delete/destroy all copies of this email and any related
attachments. NetScreen does not guarantee the accuracy or completeness
of third party materials or information.


-----Original Message-----
From: xiao'tong liang [mailto:boyliangxt@yahoo.com] 
Sent: Sunday, February 22, 2004 6:07 PM
To: Anil Bollineni
Subject: Re: [Sip] From Header

Via header.

--
xiaotong


--- Anil Bollineni <ABollineni@netscreen.com> wrote:
> Hi All,
> 
>  
> 
>       I understand from the following statement in
> RFC, that From header
> SHOULD not contain IP addresses/ports from whom the
> request has come. If it
> is so, I can't assume that the information is not
> used to assume from where
> (IP address/port) the request has come. Appreciate
> your response to clarify
> the point.
> 
>  
> 
>   As such, it is very important that the From URI
> not contain IP addresses
> or the FQDN
> 
>    of the host on which the UA is running, since
> these are not logical
> 
>    names.
> 
>  
> 
> Thank you,
> 
> Anil
> 
>  
> 
> This email contains material that is confidential.
> The content of this email
> is for the sole use of the intended recipient(s).
> Any review or distribution
> by persons other than the intended recipient(s)
> without the express
> permission of NetScreen Technologies, Inc. is
> strictly prohibited. If you
> are not the intended recipient, please contact the
> sender and delete/destroy
> all copies of this email and any related
> attachments. NetScreen does not
> guarantee the accuracy or completeness of third
> party materials or
> information.
> 
>  
> 
> 


__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools

_______________________________________________
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