NP_SERVICE_PACK MTA Only Accepts Configuration Values Between 255 And 4294967295
(Doc ID 2530620.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Network Charging and Control - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The Number Portability Service Pack (NP Service Pack), accessed through SMS, provides flexibility and control over call routing of subscribers to the network.
Some of its functionalities include:
- Functionality to allow the IN platform to satisfy MNP SRF requirements through a MAP based application (MTA) that can trigger a control plan when a supported message is received. The control plan can then perform MNP and through the appropriate node, instruct the MTA on how to respond (for example, relay, ack or error)
- Simple GTT functionality provided in the MTA for performing relay actions
The MAP Trigger Application (MTA) receives a MAP message from the TCAP Interface. The MAP and SCCP parameters are matched against the configured trigger rules and the first rule to match causes an IDP to be sent to the service key defined in the trigger. An appropriate alarm is raised if there is a problem processing the MAP message.
The mta.cfg configuration file defines the list of parameters used by MTA.
On NCC 12.0.2 it was observed that MTA only accepts configuration values between 255 and 4294967295 for local_ssn parameter. Any value outside this interval will cause MTA to crash.
In the NP Service Pack Guide there is no constraint set for this value.
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