My Oracle Support Banner

Collect Common Traces for an Interaction Involving Messaging Manager and Triggering an ACS Control Plan (Doc ID 1267666.1)

Last updated on JULY 30, 2018

Applies to:

Oracle Communications Network Charging and Control - Version 2.2.0 and later
Information in this document applies to any platform.

Goal

This procedure explains in details how to collect common traces for a test SMS that triggers a service built with the Messaging Manager (MM) interface and an Advanced Control Services (ACS) Control Plan (CP).
It can be used by Oracle Support Engineer to request Oracle customers and partners the information they need in a detailed and reliable manner.

It will collect

This set of traces will be collected from the SLC (Service Logic Controller) on which the MM service is running.

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
 Before starting
 Step by step procedure
 Sanity check
 Identify the different files specific to your environment
 Prepare the DEBUG and non-DEBUG MM process startup file
 Prepare the TRACING and non-TRACING configuration files for slee_acs and xmsIF
 SNOOP the SUA/M3UA SIGTRAN interfaces used by xmsIF
 Enable Selective DEBUG on slee_acs and tracing on xmsTrigger
 Enable process DEBUG on xmsTrigger
 Collect the requested information
 Disable process DEBUG on xmsTrigger process WITHOUT process DEBUG activated
 Stop the SNOOP traces
 Sanity check
 Bundle the requested information into a single file
References

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