1. Essentials Guide
  2. Third Party Registration
  3. Third Party Registration via ACLI Configuration

Third Party Registration via ACLI Configuration

This section specifies the differences between Oracle Communications Unified Session Manager third party registration support via iFC as oppsed to via ACLI configuration.

As is true of the method described above, third party registration is generated by the Oracle Communications Unified Session Manager on behalf of the user in the To: header of REGISTER request.

When third party registration is generated by ACLI configuration on the Oracle Communications Unified Session Manager, the registration messages are generated as follows:

  • The request URI of the new REGISTER message uses the value of the hostname parameter in the session agent configuration element.
  • The From: header of the new REGISTER message uses the value of the from-user parameter in the third party regs configuration element as the user portion of the URI. If the from-user parameter is left blank, the Oracle Communications Unified Session Manager uses the user in the original From: header.
  • The From: header of the new REGISTER message uses the value of the from-host parameter in the third party regs configuration element as the host portion of the URI. If the from-host parameter is left blank, the Oracle Communications Unified Session Manager uses the IP address of the egress SIP interface as the host portion of the from header.
  • The Contact: header of the new REGISTER message uses the home server route parameter in the sip registrar configuration element. If the home server route parameter is left blank, the Oracle Communications Unified Session Manager uses the IP address of the egress interface.

See the following diagram:

This image depicts the OCUSM or OCCSM selecting information for third party registration.