Send Notification Node Does Not Retain Link Of Last 5 Exits
(Doc ID 2583301.1)
Last updated on SEPTEMBER 02, 2019
Applies to:Oracle Communications Network Charging and Control - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (NCC), 18.104.22.168.0 version,
It is observed that Send notification node does not retain link of last 5 exits.
The ACS Send Notification node was enhanced to appropriately branch depending on the result of the send attempt. However, in NCC 12.0.2, it appears additional logic has been added to handle an upgrade scenario and direct the new exits to be treated the same as the "Delivery Failure" exit and it redirects the final 5 exits every single time.
Once the control Plan is saved, the Notification Node should keep the configured exits and should not redirects its final 5 exits, every single time.
The issue can be reproduced at will with the following steps:
1) Create new control plan.
2) Add Interaction -> Send Notification node -> Open and save with defaults.
3) Add 2 End nodes.
4) Link exit 2 (Delivery Failure) to one end node.
5) Link remaining exits to the other end node.
7) Reopen control plan --> Observe that exits 7->11 all go to the same endpoint as exit 2.
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