SIS 3.2 :: SIS Administration Guide :: Enabling Call Traffic Audit Logging

The call audit logging feature provides a summary of SIS decisions during a call, such as the trigger and composition selected and services invoked. Below is an overview of SIS audit levels, information collected by the audit, instructions for using audit logging, and some examples.

Audit logging levels

The SIS currently supports the following audit levels:

Level	Information logged
ALL	every call received from the network
COMPONENT	selected components only
NONE	(no information)

Level

Information logged

ALL

every call received from the network

 COMPONENT

selected components only

 NONE

(no information)

Component settings

You can enable auditing for individual compositions, address subscriptions, service key descriptions, and trigger addresses.

Initial settings, changes, and default

You can specify initial audit settings, that apply when a composition is installed or when a subscription is created.
Changes to component audit settings can be made at any time, and take immediate effect.
The default component audit setting, if unspecified, is disabled.

Changes only apply to new calls

The SIS determines the audit level for the lifetime of a call during initial request processing. Any changes to audit settings apply only to new calls (those subsequently triggered in the SIS).

Collected information

An individual call audit log contains the network dialog identifier, parameters of the initial request, and any of the following optional information, depending on call processing:

Information	Log details
if initial processing aborted	for example, due to insufficient license capacity or the initial request missing a required parameter
Outcome of trigger processing
subscription profile located	search key and name of profile
trigger matched and successfully found a composition	trigger’s component identifier
composition selected	composition’s component identifier
trigger matched and its failure clause invoked	trigger’s component identifier
no triggers matched
Outcome of composition evaluation
entry and exit from the script input and output interceptors (if present)
the name of the service reference of a composition service that becomes eligible for invocation
entry and exit from composition service input and output interceptors (if present)
the name of the extension reference of an extension component that is invoked by an interceptor
if the composition service invocation failed	reason for failure (for example, service response timeout, local service not active)
if the extension component invocation failed	reason for failure (for example, service response timeout)
if IN FurnishChargingInformation data from a composition service is discarded after initial acceptance due to the interaction policy in force	the name of the service reference for the service that generated the discarded FCI data
composition completed normally
composition halted by a script or service instruction

Information

Log details

if initial processing aborted

for example, due to insufficient license capacity or the initial request missing a required parameter

Outcome of trigger processing

subscription profile located

search key and name of profile

trigger matched and successfully found a composition

trigger’s component identifier

composition selected

composition’s component identifier

trigger matched and its failure clause invoked

trigger’s component identifier

no triggers matched

Outcome of composition evaluation

entry and exit from the script input and output interceptors (if present)

the name of the service reference of a composition service that becomes eligible for invocation

entry and exit from composition service input and output interceptors (if present)

the name of the extension reference of an extension component that is invoked by an interceptor

if the composition service invocation failed

reason for failure (for example, service response timeout, local service not active)

if the extension component invocation failed

reason for failure (for example, service response timeout)

if IN FurnishChargingInformation data from a composition service is discarded after initial acceptance due to the interaction policy in force

the name of the service reference for the service that generated the discarded FCI data

composition completed normally

composition halted by a script or service instruction

Initial request processing only

The audit log only reports on initial request processing — the decisions made during trigger processing and composition evaluation. It does not include any information about processing of events later in the call.

Using audit logging

To use the SIS audit logging features:

Enable audit logging in the SIS. WARNING: This is required for the SIS to check any other audit logging settings.
Reload the SIS configuration, for the configuration change to take effect.
If the COMPONENT audit level is selected, configure audit settings for compositions or other entities in the SIS (such as subscriptions).

The SIS outputs one audit record log message:

for each call for which audit logging is enabled (either explicitly or implicitly)
using the SLEE Tracer named "audit", for the SIS instance at the Info trace level
to the Rhino console log (by default) using the log key trace.<SIS instance name>.audit.

You can capture audit records several ways, including: by registering a trace notification listener with the SLEE to capture the audit trace messages from the SIS, or by creating a Rhino logging configuration that channels the audit log messages to a separate log file.

Examples

Trigger failure

2009-10-14 16:52:29.397  Info    [trace.sis_cap.insis.audit]  [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=91,incarnationID=0]]:
    trigger event: InitialDP[dialog=...serviceKey=50,callingPartyNumber=...610001234...eventType=(o) collected info...calledPartyBCDNumber=...610031097...]
    TriggerID[name=O-Trigger Handling,vendor=OpenCloud,version=1.0] failed (Fail[UserError[reason=missing-customer-record],dialog-termination=user-abort])

Basic composition with multiple services

2009-10-14 16:56:03.916  Info    [trace.sis_cap.insis.audit]  [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=103,incarnationID=0]]:
    trigger event: InitialDP[dialog=...serviceKey=50,callingPartyNumber=...610051593...eventType=(o) collected info...calledPartyBCDNumber=...610072502...]
    address 34610051593 matched subscription 34610051593
    matched TriggerID[name=O-Trigger Handling,vendor=OpenCloud,version=1.0]
    selected CompositionID[name=Originating,vendor=OpenCloud,version=1.0]
    invoking service VPN
    invoking service Call Barring
    invoking service Call Duration Logging
    composition completed

Composition with interceptors

2009-10-14 17:05:23.110  Info    [trace.sis_inap.insis.audit]  [Dialog[appContext=INAP-CS1:SSP->SCP,appID=2868,dialogID=1,incarnationID=0]]:
    trigger event: InitialDP[dialog=...serviceKey=50,callingPartyNumber=...6109000003...calledPartyNumber=8000048...eventType=(o) collected info...]
    service key 50 matched subscription 50
    matched TriggerID[name=O-Trigger Handling,vendor=OpenCloud,version=1.0]
    selected CompositionID[name=07020106,vendor=OpenCloud,version=1.0]
    invoking service Home Zone
    evaluating service-input-interceptor
    invoking extension component ext-service1
    service-input-interceptor complete; invoking service
    evaluating service-output-interceptor
    service-output-interceptor complete
    invoking service VPN
    invoking service Call Duration Logging
    composition completed

Previous page Next page