My Oracle Support Banner

How to Trace the Raw Signaling Traffic between Different Session Monitor Processes for Troubleshooting Purposes (Doc ID 2078806.1)

Last updated on AUGUST 21, 2023

Applies to:

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


There might be a situation when some issue is being troubleshooted that a raw traffic trace is required. That is, a trace not from the OCOM GUI (Traces page) but taken for the traffic before it is received by the OCOM processes. One example would be when there is an assumption that specific messages are received correctly by the server but get lost or processes incorrectly until they arrive to the web interface.

Also, in case of multiple Probe setup (and optionally with ME also acting as a Probe) it is advantageous to be able to get a trace at one single point (on the ME) and not separate traces on each of the Probes.


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
 The path of the messages
 Tracing on the ME (between apid and vsi processes)
 Tracing on the probe (between rat and rapid processes)

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