Hi Vivek, One of the use cases can be in IMS - wherein the SCSCF on the basis of some service specific criteria redirects(302) the session attempt to a CS domain endpoint. You can have a look at the call flow in section 10.4.3 of following 3gpp spec :
http://www.3gpp.org/ftp/tsg_sa/wg3_security/TSGS3_19_London/Docs/PDF/S3-010340.pdf Regards, Priyank IMS System Verification - NSN On Tue, Nov 19, 2013 at 1:01 PM, Vivek Gupta <[email protected]>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:[email protected]”), 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. > > 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 > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
