Below are instructions for using the R-IM-SSF.
Including the RIM-SSF in a service composition
Before you can use the R-IM-SSF in a service composition you must create a service reference in your SIS IN instance. Use the sis-console command createlocalserviceref to do this (see 1 Creating Local Service References):
[Rhino@localhost (#1)] createlocalserviceref sis-in R-IM-SSF "name=R-IM-SSF,vendor=OpenCloud,version=1.4" Created service reference R-IM-SSF for local SLEE service ServiceID[name=R-IM-SSF,vendor=OpenCloud,version=1.4]
Supporting more than one R-IM-SSF use in a service composition
The rimssf-service-configuration-profile-table, rimssf-invite-builder-profile-table and rimssf-sdp-builder-profile-table tables are keyed on the ServiceKey. So, one can define many records in these tables with the ServiceKey = <value that corresponds to a service> and use a SIS signaling interceptor to update the ServiceKey in the InitialDP before the R-IM-SSF is triggered.
Rate limiting the R-IM-SSF
The R-IM-SSF defines a custom rate limiter endpoint, rimssf-triggers. By default this limiter endpoint is not associated with a limiter. You can create a limiter in the SIS using the sis-console, and associate it with the R-IM-SSF limiter endpoint if you wish.
[Rhino@localhost (#0)] listlimiterendpoints RAEntity/rimssf-cdr/Input RAEntity/rimssf_management/Input RAEntity/rimssf_management/rimssf-triggers RAEntity/sis-cap/Input RAEntity/sis-cap/inbound RAEntity/sis-inap/Input RAEntity/sis-inap/inbound RAEntity/sis-sip/Input RAEntity/sis-sip/inbound
