How to Troubleshoot Missing Traffic in Palladion / Oracle Communications Session Monitor (Doc ID 1682380.1)

Last updated on AUGUST 26, 2020

Applies to:

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

Purpose

This guide shows how to troubleshoot missing traffic in Palladion / Oracle Communications Session Monitor. Customers can use this document when they expect to see specific traffic in the OCSM interface and the traffic is not there. Some examples:

- specific calls not showing in OCSM

- call is showing in OCSM but a message from it is not showing in OCSM correctly

This document explains how to troubleshoot this case and how to check all potential places where missing traffic could have been lost, dropped or filtered out.

Troubleshooting Steps

	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

Troubleshooting Steps

1. Identify details of the missing traffic

2. Are all probes connected?

3. Is the traffic received by the ME?

4. Is the traffic received by the OCSM/OCOM Probes? (applies only if the missing traffic should come from an OCSM/OCOM Probe, or ME+Probe)

Check Network Settings (or Capture Settings)

Check Media Protocols

Check Signaling Filters

5. Find the call using Apps (applies only to customer with Apps license)

6. Is the Probe sending any traffic?

If the missing traffic should come from an OCOM Standalone Probe

If the missing traffic should come from an SBC Probe

Tracing to find the missing traffic

7. Using an external tool (if possible)

8. Tracing directly on the machine/s that should receive the missing traffic

9. Check potential service restarts

10. Open Service Request

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