Q.3 Application usage of SIP
24.2293GPPIP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Release 18Stage 3TS
Q.3.1 Procedures at the UE
Q.3.1.0 Void
Q.3.1.0a IMS_Registration_handling policy
Not applicable.
Q.3.1.1 P-Access-Network-Info header field
The cdma2000® 1x FAP shall include the P-Access-Network-Info header field where indicated in subclause 5.1.
Q.3.1.1A Cellular-Network-Info header field
Not applicable.
Q.3.1.2 Availability for calls
Not applicable.
Q.3.1.2A Availability for SMS
Void.
Q.3.1.3 Authorization header field
Void.
Q.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE
Not applicable.
Q.3.1.5 3GPP PS data off
Not applicable.
Q.3.1.6 Transport mechanisms
No additional requirements are defined.
Q.3.1.7 RLOS
Not applicable.
Q.3.2 Procedures at the P-CSCF
Q.3.2.0 Registration and authentication
Void.
Q.3.2.1 Determining network to which the originating user is attached
If access-type field in the P-Access-Network-Info header field indicated 3GPP2-1X-Femto access the P-CSCF shall assume that an initial request for a dialog or standalone transaction or an unknown method destined for a PSAP is initiated in the same country.
Q.3.2.2 Location information handling
Not applicable
Q.3.2.3 Void
Q.3.2.4 Void
Q.3.2.5 Void
Q.3.2.6 Resource sharing
Not applicable.
Q.3.2.7 Priority sharing
Not applicable.
Q.3.2.8 RLOS
Not applicable.
Q.3.3 Procedures at the S-CSCF
Q.3.3.1 Notification of AS about registration status
Not applicable
Q.3.3.2 RLOS
Not applicable.