On 11/18/13 11:31 PM, Vivek Gupta wrote:
> RFC section 10.2.1 says below:
>
> The Contact header field values of the request typically consist of SIP or
> SIPS URIs that identify particular SIP endpoints (for example, “
> sip:ca...@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
> [8]) or email addresses (with a mailto URL, RFC 2368 [32]) as Contacts for
> an address-of-record, for example.*
>
> I would be interested to know the practical use cases where SIP UA would
> make use of Tel URL in the Contact header when registering.
A UA that is registering isn't necessarily registering contacts that
identify itself. It may register contacts that identify something else.
You could potentially register a TEL uri in order to get incoming calls
redirected to some arbitrary phone number.
Thanks,
Paul
> Vivek Gupta | Sr. Consultant Engineering
> GlobalLogic
> P +91.120.406.2953 M +91.987.390.4358 S vivek.gupta_globallogic.com
> www.globallogic.com
> <http://www.globallogic.com/>
> http://www.globallogic.com/email_disclaimer.txt
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
