The Number Matching Node Does Not Behave as Described in the Resource Guide and Online Help
Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.4.1 to 5.0.3 [Release 4.4 to 5.0]
Information in this document applies to any platform.
The Control Plan Editor's (CPE) Number Matching (MTCH) node can branch a control flow by matching a search pattern, or patterns. The node's documentation (online help and user guides) contains Configuring the node steps and states the following warning about the Static Pattern List field:
The following Configure Number Matching screen shot shows this:
However, if the Static Pattern List field is empty, the node will branch out exit 2 (Number Not Found), instead of exit 3.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms