[SIPForum-discussion] in REGISTER method can we use Tel URI?

[chandrasekhara.madduri at wipro.com]

Hi,



But section 10.2.1 says the following...



 The Contact header field values of the request typically consist of
   SIP or SIPS URIs that identify particular SIP endpoints (for example,
   "sip:carol at cube2214a.chicago.com"), but they MAY use any URI scheme.
   A SIP UA can choose to register telephone numbers (with the tel URL,
   RFC 2806<http://tools.ietf.org/html/rfc2806> [9<http://tools.ietf.org/html/rfc3261#ref-9>]) or email addresses (with a mailto URL, RFC 2368<http://tools.ietf.org/html/rfc2368> [32<http://tools.ietf.org/html/rfc3261#ref-32>])
   as Contacts for an address-of-record, for example.

Whích means we have an option to use the tel uri for registering.



Thanks & regards,

Chandra Madduri

________________________________
From: discussion-bounces at sipforum.org [discussion-bounces at sipforum.org] on behalf of rupandeep singh [er_rupandeep at yahoo.com]
Sent: 27 May 2013 14:51:55
To: Vijay Badola; Michael Scofield; discussion at sipforum.org
Subject: Re: [SIPForum-discussion] in REGISTER method can we use Tel URI?

Request-Uri points to the domain of the user and doesn't point to any entity so it should always be a FQDN.
>From RFC 3261


      Request-URI: The Request-URI names the domain of the location
           service for which the registration is meant (for example,
           "sip:chicago.com").  The "userinfo" and "@" components of the
           SIP URI MUST NOT be present

I think this will clear your doubt

Regards
Rupandeep Singh



________________________________
From: Vijay Badola <Vijay.Badola at onmobile.com>
To: Michael Scofield <amit.chhikara at hotmail.com>; "discussion at sipforum.org" <discussion at sipforum.org>
Sent: Thursday, April 4, 2013 5:01 PM
Subject: Re: [SIPForum-discussion] in REGISTER method can we use Tel URI?

Request URI of SIP Register Request contain domain of the location service for which the
registration is meant (for example, "sip:abc.com")  and as we know, request uri for Register request does not contain User information.
Also SIP Registrar is SIP entity and it will have a sip address.
I have not found written anywhere related to TEL URI in REGISTER request,
But from SIP RFCs, I THINK we SHOULD use SIP URI in Request Uri instead of TEL URI.

,vijay


From: discussion-bounces at sipforum.org<mailto:discussion-bounces at sipforum.org> [mailto:discussion-bounces at sipforum.org] On Behalf Of Michael Scofield
Sent: Wednesday, March 20, 2013 1:45 PM
To: discussion at sipforum.org<mailto:discussion at sipforum.org>
Subject: [SIPForum-discussion] in REGISTER method can we use Tel URI?

Hi All,

In register method request URI can we use TEL URI?

Please help me in this regard.

Thanks!!! in Advance.

Regards,
Michael

________________________________

DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.

_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org<mailto:discussion at sipforum.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130528/4a71afc5/attachment-0002.html>