My Oracle Support Banner

Prioritizing a Source and Avoiding Duplicate Packets if Traffic is Received twice from Different Sources (Doc ID 1935406.1)

Last updated on JANUARY 18, 2018

Applies to:

Oracle Communications Session Monitor - Version 3.x and later
Information in this document applies to any platform.

Goal

Prioritize a source of traffic over another one if there traffic monitored to OCOM/Palladion is overlapping partially  - for example if two OCSM probes, or an SBC and an OCSM probe are capturing/monitoring same traffic to OCOM/Palladion.

If the same traffic is received two or more times from different sources - from SBC via IPFIX (comm-monitor functionality of Oracle SBC) and a second time via the sniffing functionality of a OCOM/Palladion probe - this could result in duplicate packets. This could especially happen in scenarios where the SBC is supposed to monitor the traffic coming in from the public Internet and the traffic in the core network is monitored by the probe functionality.

Since the SBC monitors in every case the incoming side of a call, as well as the outgoing (so core and public are monitored), the core site might get monitored twice.

Solution

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
Goal
Solution
 1. What criteria is used to decide that packets are duplicate
 2. Avoid duplicate packets on probe
 2.1 Activate deduplication in the "Signaling Protocols" section in PSA ( https://<IPofProbe>/setup/ )
 2.2 Optimize the traffic filters (if the duplicates come from two different probes)
 3. Enable deduplication globally (on the ME)
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.