IETF Logo Mail Archive

Re: [Sip] [Sip-implementors] Request URI and TO heasder "user" part is different

Nitin Kapoor <nitinkapoorr@gmail.com> Thu, 18 March 2010 18:02 UTC

Return-Path: <nitinkapoorr@gmail.com>
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 AC9EE3A67E5 for <sip@core3.amsl.com>; Thu, 18 Mar 2010 11:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-1.032, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, J_CHICKENPOX_62=0.6]
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 YU0hJd9kbTnY for <sip@core3.amsl.com>; Thu, 18 Mar 2010 11:02:06 -0700 (PDT)
Received: from mail-qy0-f177.google.com (mail-qy0-f177.google.com [209.85.221.177]) by core3.amsl.com (Postfix) with ESMTP id A08273A6869 for <sip@ietf.org>; Thu, 18 Mar 2010 11:02:06 -0700 (PDT)
Received: by qyk7 with SMTP id 7so49908qyk.17 for <sip@ietf.org>; Thu, 18 Mar 2010 11:02:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=RmhOjCP5ME0w311TbL/TLyT57Hkovsgb60JuLRph7dI=; b=OzP0w2lb1+JwT8o2J5rzghPz9IbumUZ4UtmRDrXRM3BvJXcbycNBND7/LfrcrSS2jC zzGRs5OADjcu6CNPnJWyLwyJzUsBUzuQz86JWhZnUyZKNWMQ87ZgIPQXtUYBzH5segQO SNfvrreIEvX02Xb/QrNIJ3C0yy5G8fAejA5z4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=mKmLzyUJYt4LUG8q9Kf7P5uItAnYgCA9ZAn3QTq7+bzWhxIVGYvqnSJC59u84CHrnc ZBV9htSyyyHAHWmtxB3Znp935IeFO8FUpeKuP/foICcUcMBlpm5xbfwjRp7vlfvHxRo8 BfkHBBD3GHpoHQ2M7h1IdmxAiKoMG5M8LOgo4=
MIME-Version: 1.0
Received: by 10.229.184.132 with SMTP id ck4mr934957qcb.45.1268935333892; Thu, 18 Mar 2010 11:02:13 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B21F6E96F5A@DC-US1MBEX4.global.avaya.com>
References: <c80c92d1003180741s31691d6cg7d7f41ebe8bd2c6f@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B21F6E96F5A@DC-US1MBEX4.global.avaya.com>
Date: Thu, 18 Mar 2010 14:02:13 -0400
Message-ID: <c80c92d1003181102v35e25439t83b8326b0b1b2ed4@mail.gmail.com>
From: Nitin Kapoor <nitinkapoorr@gmail.com>
To: "WORLEY, DALE R (DALE)" <dworley@avaya.com>
Content-Type: multipart/alternative; boundary=0016364eca7ad1fe1304821707d7
Cc: "sip@ietf.org" <sip@ietf.org>, "sip-implementors@lists.cs.columbia.edu" <sip-implementors@lists.cs.columbia.edu>
Subject: Re: [Sip] [Sip-implementors] Request URI and TO heasder "user" part is different
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-Archive: <http://www.ietf.org/mail-archive/web/sip>
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>
X-List-Received-Date: Thu, 18 Mar 2010 18:02:07 -0000

Dale,

I guess its looks different in sip forum..

Because i have not seen a single packet in original format who is taking
"%3A" in userpart..However i am again sending you the Request line which is
actually quested in uri's.


Request-Line: INVITE
sip:17139229867@64.245.120.88<sip%3A17139229867@64.245.120.88>SIP/2.0
Request-URI: sip:17139229867@64.245.120.88 <sip%3A17139229867@64.245.120.88>

Whereby in TO header(of the same INVITE) I do not have the “1” in user part
as below.

To: sip:7139229867@64.245.120.88 <sip%3A7139229867@64.245.120.88>

Thanks,
Nitin Kapoor

On 18 March 2010 13:52, WORLEY, DALE R (DALE) <dworley@avaya.com> wrote:

> _______________________________________
> From: sip-implementors-bounces@lists.cs.columbia.edu [
> sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of Nitin Kapoor
> [nitinkapoorr@gmail.com]
>
> To: sip:7139229867@64.245.120.88 <sip%3A7139229867@64.245.120.88> <
> sip%3A7139229867@64.245.120.88 <sip%253A7139229867@64.245.120.88>>
>
> _______________________________________________
>
> In general, a SIP element should not consider the value of the To header.
>  However, the To header is required to conform to a specific syntax, and
> this To header does not.  The basic structure for this type of To header is
> "display-name <SIP-URI>".  However, if display-name is not quoted, it is
> restricted to being a "token", and "token" may not contain ":" or "@".  The
> text between <...> is supposed to be a SIP URI, but the ":" is replaced by
> "%3A", and there is no escaping defined for that position.  See section 25.1
> of RFC 3261 for the details.
>
> So until you correct the To header (who is generating it?) there is no
> reason to expect any SIP element to accept the request.
>
> Dale
>

v2.8.7 | Report a Bug | By Email