SBC probe connects to OCOM 3.3 server but fails to connect to OCOM 4.0+
(Doc ID 2557091.1)
Last updated on SEPTEMBER 22, 2020
Applies to:Oracle Communications Session Monitor - Version 4.0 and later
Information in this document applies to any platform.
An existing SBC probe configured as per:
How to Configure the SBC as a Probe for Oracle Communications Session Monitor (Palladion), using the comm-monitor Feature (Doc ID 1679579.1)
connects fine to OCOM 3.3 ME but is unable to connect to a OCOM 4.0 server so no data is sent. The SBC probe is configured to use an un-secure connection. The /var/log/messages file on the OCOM 4.0+ ME though shows SSL errors:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document