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

Third Party Registrations via iFCs

The Oracle Communications Unified Session Manager performs third party registrations based on the iFC downloaded for the user. If the filter criteria successfully evaluates to a third party server, a third party registration entry is dynamically added in the Oracle Communications Unified Session Manager. The dynamic entry is automatically deleted if there are no more registrations being handled for that third party registration host.

When third party registration is performed by iFCs, the Oracle Communications Unified Session Manager generates the registration messages as follows:

  • The Contact: header is populated with the URI from the home server route configuration of the sip-registrar associated with the registration. If the home server route is left blank, the Oracle Communications Unified Session Manager uses the IP address of the egress interface.
  • The From: header of the new REGISTER message is the same as the FROM in the original message.
  • The To: header of the new REGISTER message is the the same as the TO in original message (AOR).