Handling of SIP Register at S-CSCF - (Success Case): 1: Receive REGISTER 2: Download subscriber data (over Cx interface) from HSS 3: Respond with 200 OK (of REGISTER message) 4: Perform filter checking at S-CSCF 5: Send REGISTER to Application Server (containing TO, FROM, CALLID, CONTACT) 6: Receive 200 OK from Application Server
Falure case from AS: On receiving a failure response to one of the REGISTER requests, the S-CSCF shall apply the "default handling" related with the initial Filter Criteria's trigger used. Detailed description: Upon receiving the initial registration request from the user, the S-CSCF shall authenticate the user and upon receiving a subsequent registration request containing valid authentication credentials, request the HSS to send the relevant service profile(s) for the user's subscription. More than one service profile may be sent, depending on configuration options for identifying implicitly registered public user identities. The initial filter criteria (subset of the profile) is stored locally at the S-CSCF. The S-CSCF shall verify if the triggers match, from the highest to the lowest priority. After a successfully authenticated registration, the S-CSCF shall download from the HSS all the implicitly registered public user identities associated with the registered public user identity. The S-CSCF shall then verify, in their order of priority, if the triggers downloaded from the HSS match. If the registration request from the user matches a trigger, the S-CSCF performs a third party registration to the application servers which are interested to be informed about the user registration event of these public user identities. This may trigger services to be executed by an Application Server. The important information carried in the third party REGISTER request is the public user identity, the S-CSCF address and the expiration time. It shall be possible based on operator configuration to use one of the implicitly registered public user identities as the public user identity in the To header of the third party REGISTER request sent to the Application Server. Additional application server specific data, which is associated with the Filter Criteria and obtained from the HSS, is added to the REGISTER request body. This data should include the IMSI for an Application Server that supports CAMEL services or the private user identity for other Application Servers as received from the HSS. This third party registration will include an expiration time that is equal to the expiration time sent to the UE by the SCSCF in the 200 OK response to the incoming REGISTER request. On receiving a failure response to one of the REGISTER requests, the S-CSCF shall apply the "default handling" related with the initial Filter Criteria's trigger used. For more details please refer: http://www.3gpp.org/ftp/TSG_CN/TSG_CN/TSGN_25/Docs/PDF/NP-040384.pdf#search=%22third%20party%20registration%20cscf%20application%20server%22 Section 6.3 Hope this helps ... Best regards, Harpreet Juneja On 13/09/06, Rakesh Hooda <[EMAIL PROTECTED]> wrote: > > > Regards > Rakesh Hooda > "None of us is as smart as all of us" > " DISCLAIMER: This message is proprietary to Flextronics Software Systems > Limited (FSS) and is intended solely for the use of the individual to whom > it is addressed. It may contain privileged or confidential information and > should not be circulated or used for any purpose other than for what it is > intended. If you have received this message in error, please notify the > originator immediately. If you are not the intended recipient, you are > notified that you are strictly prohibited from using, copying, altering, or > disclosing the contents of this message. FSS accepts no responsibility for > loss or damage arising from the use of the information transmitted by this > email including damage from virus." > > _______________________________________________ > 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
