Oracle recommends that you review the following Caveats before using Oracle® Communications Security Shield (OCSS). A Caveat explains certain behaviors that you might not expect, but which work as designed. Caveats do not include workarounds. Check this document periodically to stay informed of updates and other new information.

Outbound Call Validation List - Call Tags

When configuring a phone number for the Outbound Calling Number list, you can select an Internet Engineering Task Force (IETF) Call Tag attribute for the phone number. Note that the Call-Tag does not affect the outbound INVITE at this time, but setting the call tag does help to refine your searches at this time.

Cloud Communication Service Configuration

The Cloud Communication Service (CCS) does not support simultaneous use of the same CCS instance by different services, for example, OCSS and Oracle Session Delivery Manager Cloud (OSDMC). You must configure each CCS instance to support only one service.

The Dashboard Might Display Multiple Data Points for the Same Call

The OCSS evaluates a call based on multiple algorithms, such as Fraud, Reason Codes, and Reputation Score. The OCSS gives each call a reputation score and classifies the call as one of Critical Risk, Severe Risk, Significant Risk, Suspicious, Unclassified, or Regular. Whenever the OCSS identifies a call as a threat, for example Telephony Denial of Service (TDoS), it is very likely that the call will be classified as one of the high risk categories based on the reputation score assigned to that call. Due to this behavior, you might see multiple threats reported on the Dashboard for the same call. For example, the call might be reported in both the TDoS and Critical Risk graphs. You might see the same behavior for threats categorized based on Reason Codes.