Routing of CDR is not Happening Based on Pipeline Name from Recycle EP
Last updated on MAY 09, 2017
Applies to:Oracle Communications Offline Mediation Controller - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, IP Core: Routing of CDR is not happening Based on Pipeline Name from Recycle EP
We have CDR suspended in OCOMC both from DC and EP Node. During Recycling of the suspended record, we expect all the CDR value to be routed based on pipeline name from the node where it was suspended. But during our build we observed, the routing is not happening based on pipeline name and recycled CDR is going to both EP and DC .
Our understanding is that Recycle CDR will go back to the node where it was suspended and we don't need to do any customization? Can you please let us know whether OCOMC handles the above scenario?
The Custom architecture has following Nodes:
1) CC :Mobile(to map mediation entries to Mobile format)
2) EP :Usage Class(To enhance Usage Class)
3) EP : country Description( To enhance Country description)
4) DC :OCOMC ( for multiple payload)
5) CC NAR(for fetching suspended archive file)
6) Suspense DC
7) Recycle CC
8) Recycle EP
a) From EP: Country Description , CDR are suspended since a mandatory value was missing. Suspension is done by passing pipeline name,category and error code.
b) EP : Country Description is connected to Suspense DC. Suspense DC creates out file with suspense_usage/telco object and loads into BRM.
c) In suspense Manager, CDR is rectified using editable fields and recycled.
d) Recycle EP is connected to EP : Country Description and DC :OCOMC.
e) Recycle EP is sending CDR to both EP : Country Description and DC :OCOMC.
The node id of EP : Country Description is passed as pipeline name during suspension and we expect recycled CDR to go only to EP : Country Description.
But the recycled CDR is going to Both EP : Country Description and DC :OCOMC which is an issue. Since pipeline name is there, we expect CDR going only to EP : country Description. Is this behavior expected in OCOMC?
The routing cannot be kept as directed as node id is not a constant value and keep changing for every environment.
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