How to Link Correlation ID in the AssistRequestInstructions to the RoutingAddress in the EstablishTemporaryConnection for IVR Calls in Snoop Traces
(Doc ID 1310239.1)
Last updated on AUGUST 19, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 4.3.0 [Release 4.3]
Information in this document applies to any platform.
The goal of this article is to demonstrate how to find the messages exchanged, in a network trace (e.g. snoop trace), on the secondary dialog between SLC (Service Logic Controller) and SRF (Specialized Resource Function), and link it to the primary dialog between SLC and the signalling switch (or MSS (Mobile Switching Center Server)) handling the call. This is done by finding correlationID in the ARI (assistRoutingInstructions) message using the assistingSSPIPRoutingAddress in the ETC (establishTemporaryConnection) message.
In general, normal calls (not involving interaction with SRF) can be fully tracked using the TCAP ID in the IDP and the subsequent messages, because there is only one dialog. However, in case there is an interaction with SRF, a secondary dialog is created between SLC and SRF. This secondary dialog doesn't have the same TCAP ID as that of primary dialog.
In the case of an interaction with IVR (Interactive Voice Response), the SLC will instruct the MSS to establishTemporaryConnection to an external resource that is defined in the acs.conf as shown below.
An important parameter in this configuration is useETC. If this parameter is set to Y, ETC is used to establish a connection to the SRF. If this parameter is set to N, CTR (connectToResource) will be used.
While ETC instructs the MSS to connect to SRF using a secondary dialog, CTR does not involve a secondary dialog since the IVR would be available on the MSS itself. All the IVR interaction in case of CTR will be in the primary dialog, this means that the TCAP ID for the IVR interaction will be the same.
The rest of the article will focus on the use of ETC to connect to SRF, since it involves two different dialogs, and hence different TCAP IDs.
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