1. Essentials Guide
  2. Third Party Registration
  3. Third Party Registrations via iFCs
  4. Embedded REGISTER

Embedded REGISTER

As an option within standard iFC third party registration support, the Oracle Communications Unified Session Manager supports 3GPP’s methodology of embedding the original UE registration (and/or its response from the S-CSCF/Registrar) as a MIME body in the third party REGISTER sent from the S-CSCF to the third party server. This methodology, presented in 3GPP TS 23.218 and 29.228, uses an optional iFC extension ("IncludeRegisterRequest" and "IncludeRegisterResponse") that tells the third party server to expect the entire original REGISTER request and/or REGISTER 200OK in the mime of the third party REGISTER.

Implementation details for this methodology include the following:

  • There may be further configuration required on the Oracle Communications Unified Session Manager.
  • The Oracle Communications Unified Session Manager does not embed original registration requests or responses to any third party server outside its trust domain.
  • The HSS or configured iFCs must be preconfigured for embedded third party registrations.

An HSS confiuration may not support the optional "IncludeRegisterRequest" and "IncludeRegisterResponse". For these cases, there is a Oracle Communications Unified Session Manager configuration option that allows you to control this inclusion, as follows:

  • If the iFCs specify inclusion in an environment where you do not want it, you can set a registrar option to never include the original REGISTER
  • If the iFCs do not specify inclusion in an environment where you want it, you can set a registrar option to always include the original REGISTER.

You can set these options for either the third party register, the 200 OK, or both.