My Oracle Support Banner

How to Configure ATI MNP Query In OC3C/NCC ? (Doc ID 2804979.1)

Last updated on SEPTEMBER 06, 2021

Applies to:

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

Goal

As per "Location Capabilities Pack Technical Guide" document released with Oracle Communications - Convergent Charging Controller (OC-3C) 6.0.1.0, it can be seen Location Capabilities Pack(LCP) module contains a plugin to be used for Any Time Interrogation(ATI) request to Mobile Number Portability (MNP) database, "to retrieve the MSISDN and routing number of the called party"

See below document snippet:

atimnpPlugin
------------
The atimnpPlugin section contains the configuration for MNP USSD call-back and the ATI MNP plugin
(liblcpatimnp (on page 34)).

...
Example
Here is an example atimnpPlugin configuration.
atiMnpPlugin = {
mnpDbAddress = "1,1,55555"
gsmScfAddress = "1234"
gsmScfMapNOA = 1
tcapIF = "hlrIF"
origSSN = 1234
destSSN = 1235
}

...

liblcpatimnp
-------------
Purpose
This is ATIMNP plug-in, which sends ATIs to a MNP DB (whose GT must be specified in eserv.config at
atimnpPlugin (on page 16)) to retrieve the MSISDN and routing number of the called party.

Location
This library is located on SLCs.

Configuration
liblcpatimnp is configured in eserv.config. For more information about how to configure this library, see
atimnpPlugin (on page 16).

What is the detailed procedure to configure ATI MNP query?

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
References


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