Oracle Communications Operations Monitor (OCOM) Configuration
Oracle Communications Session Border Controller configuration on the consists of the following steps.
TSCF Rekey Profile Configuration
Rekeying is a cryptographic technique that enhances security by enforcing the negotiation of existing keys on an ongoing secure connection. Rekeying can be either time-based, in which case new keys are negotiated at the expiration of a timer, or traffic-based, in which case new keys are negotiated when a threshold byte count is exceeded.
Use the following procedure to configure an optional tscf-rekey-profile. Later, you will assign the profile to a specific TSCF interface. If you do not intend to enforce re-keying, this procedure can be safely ignored.
TLS Profile Configuration
Use the following procedure to configure a tls-profile that identifies the cryptographic resources, specifically certificates and protocols, required for the establishment of a secure/encrypted connection between the Oracle Communications Session Border Controller and the Oracle Communications Operations Monitor (OCOM) Mediation Engine.
Making Personal Data in Messaging Sent to OCOM Anonymous
When you allow people to examine SIP INVITE or SIP MESSAGE messages in the Oracle Communications Operations Monitor (OCOM), you might want to hide certain sensitive information from their view for security and confidentiality reasons. For example, you might want to hide the SUBJECT header in the message and in the CPIM body, as well as the MIME content of the CPIM body. Oracle's solution is to provide an option to anonymize such information for display in OCOM.
When you enable the anonymize-invite option, the system makes a copy of the inbound SIP INVITE and allows the original to continue on its way. In the copy, the system parses the body of the INVITE and replaces the SUBJECT header and MIME content with a hyphen (-). No other message content is affected, and the full functionality of the OCOM remains available. When the troubleshooter views the SIP INVITE message, OCOM displays the anonymized copy of the SIP INVITE.
You can also enable the anonymize-message option, which performs the same functions to the SIP MESSAGE, defined in RFC 3428, to support the transfer of Instant Messages. When enabled, this option hides the SUBJECT header as well as the CPIM subject and MIME content, replacing them with a hyphen (-) before sending them to OCOM.
The default setting for both options is disabled. Use the options parameter in the comm-monitor configuration to enable them.
Enabling Anonymization of Information Sent to OCOM
Note:
The anonymize-invite option for CommMonitor is not RTC.You can enable the same functionality for the SIP MESSAGE method using the anonymize-message option. You can enable both options on the same comm-monitor, if desired using the options' plus-sign (+) syntax.
The default setting for these anonymize options is disabled. Use the options parameter in the comm-monitor configuration to enable them.