Third Party Registration

7 Third Party Registration

Third party registration support on the Oracle Communications Core Session Manager provides a mechanism for sending registration information to a third party server. An IM (Instant Messaging) server might be the recipient of a third party REGISTER message.

The Oracle Communications Core Session Manager accepts incoming REGISTER requests from UAs. After the UA has been registered with the Oracle Communications Core Session Manager, the Oracle Communications Core Session Manager sends a third party REGISTER message to a third party server.

The image below depicts the OCUSM or OCCSM supporting third party registrations.

The Oracle Communications Core Session Manager supports third party registration via two methods:

For scenarios in which UAs receive iFCs from the HSS and the Oracle Communications Core Session Manager’s default iFC configuration, the Oracle Communications Core Session Manager generates third party registration requests and responses for matching triggers in its iFC evaluation.
Some third party servers may want the UA’s entire original request to the Oracle Communications Core Session Manager and response from the Oracle Communications Core Session Manager to the UA provided to them. The Oracle Communications Core Session Manager supports these scenarios, in some cases requiring additional configuration.
For scenarios in which the UA needs a third party registration that is not explicitly prescribed within iFCs, you can configure a third party server on the Oracle Communications Core Session Manager and achieve third party registration support.
For these configurations, the Oracle Communications Core Session Manager attempts third party registration to those servers for all UAs that register via the applicable Oracle Communications Core Session Manager registrar.

For both methodologies, you must configure all third party servers as session agents.