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 20:06 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 EC7183A686D for <sip@core3.amsl.com>; Thu, 18 Mar 2010 13:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.468
X-Spam-Level:
X-Spam-Status: No, score=-1.468 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 lTEV9TqC8wKU for <sip@core3.amsl.com>; Thu, 18 Mar 2010 13:06:32 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by core3.amsl.com (Postfix) with ESMTP id 0418F3A65A6 for <sip@ietf.org>; Thu, 18 Mar 2010 13:06:31 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 5so345318qwd.31 for <sip@ietf.org>; Thu, 18 Mar 2010 13:06:41 -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=PUlatxQhIqYLZ8XaFH9UvYg4933NQx8+9mHv3kl2ex8=; b=S2+RtQyAHwMd5rlZnb8U3STOWDUbkxP6Jy1/MkNSafsIAjiMxGIIdPKaGBxClV+8Ma NfU4b25A9NmHdypOa0NNwUwnyfnXxfYMbriD+YB2rR1TCZfQIINzcb2LnJytPyGzed67 ZLOAU83iQJD1wkST+ETmyLoIjZqtw1m+o2n/g=
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=Ec+NFoeAeYKQk4jUispwzcVE8s+LidAf0wiXJIeESVkAC5uvQPFNUz06MGd0wPx/H1 dWzUd/41i8UaxR5RqnN4JTmhAvMxN+DPDEkOw6PN+6XQaj9K0A+cxEVPO7o2tThKlUYX NTh8nF8HwOjA1WKrjSHduJlgZghiqjOp+CJ4A=
MIME-Version: 1.0
Received: by 10.229.230.4 with SMTP id jk4mr483109qcb.1.1268942800376; Thu, 18 Mar 2010 13:06:40 -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 16:06:39 -0400
Message-ID: <c80c92d1003181306n4fc8f4f5ia5592fc4fad3d9eb@mail.gmail.com>
From: Nitin Kapoor <nitinkapoorr@gmail.com>
To: "WORLEY, DALE R (DALE)" <dworley@avaya.com>
Content-Type: multipart/alternative; boundary=0016364ec7a8db542c048218c429
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 20:06:33 -0000

Anyhow i have resolved the issue by doing a digits manipulation.

Thanks everyone to help me on this.

Regards,
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