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
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/T
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
