Alan You're absolutely right that, in a purely Clearwater deployment, enabling I-CSCF doesn't add much value. The reason we added the function was for some users who wanted to use Clearwater as part of a larger IMS core network (for example, as part of a cap-and-grow strategy), where supporting the I-CSCF function and flows is essential for distributing SIP registrations and incoming calls to the right S-CSCFs.
We will continue to support operating in a "Clearwater-only" mode without the I-CSCF function as this is more efficient and significantly reduces the load on the HSS. Regards, Mike -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kwon, Alan Sent: 28 May 2014 21:37 To: [email protected] Subject: [Clearwater] I-CSCF Hi, Since Sprout nodes are seen as a cluster and it's always referred by cluster FQDN instead of individually by IP address, I'm not seeing what exactly enabling this provides. I enabled it in my deployment to see all the Diameter Cx interfaces to my HSS, but functionally I don't see any difference. Even in the SAR's it's using the cluster FQDN. So, other than being more IMS spec compliant, is there any use case where enabling I-CSCF is necessary? Thanks, Alan _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
