[Iptel] tel uri query
"Vikas Gupta" <vikasn011@gmail.com> Mon, 26 March 2007 12:47 UTC
Return-path: <iptel-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVobS-0005z9-Op; Mon, 26 Mar 2007 08:47:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVobS-0005yy-0L for iptel@ietf.org; Mon, 26 Mar 2007 08:47:14 -0400
Received: from wx-out-0506.google.com ([66.249.82.224]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVobQ-0000TF-PP for iptel@ietf.org; Mon, 26 Mar 2007 08:47:13 -0400
Received: by wx-out-0506.google.com with SMTP id h31so2156799wxd for <iptel@ietf.org>; Mon, 26 Mar 2007 05:47:12 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=VBGP9X/MrA0XVabbRZFvT9mWgpERrZTL0EpasldWkd1FEYP7aB6nAgL6ZA+OAEQnPEOCkEQP7rzY7yx3bQoX9hdO6iZ7YTXerYb3CF/T9pLrOSLNw/qCQZywHwX7K22bOzjyAYt9Z3AjdRRG0QcofNOPEVW8BNTkSMYNaKTfbU4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=GJL4sKuoD/mFt6qC0sZIF8IZlvcybVYmHIfCavOX6lT01hhLqeQCt69aJcBnwD8773s3L+cP+asAQaGbiG7XtUK0aaA+UJociITuy0EfAawhjOla/SB2a8LH6tJz4lPCc0sqqEJqtOXr9chjzTRiLQha6v3+SVt6AWd7NMTdWhc=
Received: by 10.90.116.6 with SMTP id o6mr336321agc.1174913232534; Mon, 26 Mar 2007 05:47:12 -0700 (PDT)
Received: by 10.90.104.9 with HTTP; Mon, 26 Mar 2007 05:47:12 -0700 (PDT)
Message-ID: <710fcb5d0703260547h1accfe1ey2757cec8f63f36a8@mail.gmail.com>
Date: Mon, 26 Mar 2007 13:47:12 +0100
From: Vikas Gupta <vikasn011@gmail.com>
To: sip-implementors@cs.columbia.edu, iptel@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc:
Subject: [Iptel] tel uri query
X-BeenThere: iptel@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Telephony <iptel.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/iptel>
List-Post: <mailto:iptel@ietf.org>
List-Help: <mailto:iptel-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0750129215=="
Errors-To: iptel-bounces@ietf.org
Hi, I am currently implementing the support of <tel:> URI in our existing user agent as per rfc 3966.I have some doubts regarding the same.Any inputs will be highly appreciated. 1)Is it possible to have tel: URI as request URI in methods other than INVITE and REGISTER i.e in OPTION,PRACK,ACK,CANCEL,BYE, Notify,Subscribe and REFER methods ? 2)From RFC 3396 and 3261 ,I concluded that tel: URI can be present in INVITE and REGISTER request in following headers. For INVITE tel: uri can be present in "request URI" , "From header", "TO header". >From Register tel: URI can be present in "Contact header". for privacy it can also be present in p-preferred and p-asserted header. besides this ,is it possible to have <tel:> uri in any other header(e.gRoute, record-route ,Via )? Regards, Vikas
_______________________________________________ Iptel mailing list Iptel@ietf.org https://www1.ietf.org/mailman/listinfo/iptel
- [Iptel] tel uri query Vikas Gupta