Communications Monitor Configuration
Oracle Communications Session Border Controller (OCSBC) configuration on the Oracle Communications Operation Monitor (OCOM) consists of the following steps.
Note:
Enabling the comm-monitor so that the OCSBC sends call information to OCOM results in a significant performance load. Contact Oracle Customer Support for more information.Configure the Oracle Communications Operations Monitor
Use the following procedure to configure the Oracle Communications Operations Monitor (OCOM).
Note:
Enabling the comm-monitor so that the Oracle Communications Session Border Controller (OCSBC) sends call information to OCOM results in a significant performance load. Contact Oracle Customer Support for more information.From superuser mode, access comm-monitor configuration mode. Establish a connection between the OCSBC, acting as a exporter of protocol message traffic and related data, and an OCOM Mediation Engine, acting as an information collector.
- Optional—If the network
interface specified in Step 8 is a media interface, you can optionally use TLS
to encrypt the exporter-collector connection. To enable TLS encryption, use the
tls-profile
parameter to identify a TLS profile to be assigned to the network interface.
The absence of an assigned TLS profile (the default state) results in
unencrypted transmission. See
TLS Profile Configuration for configuration details.
ACMEPACKET(comm-monitor)# tls-profile commMonitor ACMEPACKET(comm-monitor)#
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.
Anonymize Sensitive Data in SIP Messages
When you allow people to examine SIP INVITE 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.
Note:
Enabling the anonymize-invite option adds an additional CPU load to the Oracle Communications Session Border Controller (OCSBC). Contact Oracle Customer Support for more information.Enable Anonymization in a SIP INVITE Message
Note:
Enabling the anonymize-invite option adds an additional CPU load to the OCSBC. Contact Oracle Customer Support for more information.