Performance Intelligence Center (PIC) - xDR Builder Correlation Issues Due to Matching ID (RID) not Properly Set

Asset ID:	1-72-2116162.1
Update Date:	2018-03-30
Keywords:

Solution Type Problem Resolution Sure

Solution 2116162.1 : Performance Intelligence Center (PIC) - xDR Builder Correlation Issues Due to Matching ID (RID) not Properly Set

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 4.1 and later
Information in this document applies to any platform.

Symptoms

Sessions have correlation issues meaning several xDRs have "Not Matched", "Timer" and "Collision" status.

Cause

The linksets feeding the impacted session are assigned to different RID groups. Consequently the transaction messages will not be correlated by the builder when they are handled by more than one linkset (For example, the BEGIN coming on a first linkset and the END handled by the second).

Under CCM -> Network Elements -> Linksets, when selecting impacted linksets, it is possible to see that the linksets have different RIDs.

Matching ID can be seen in xDR to check how it was set.

Solution

To solve the issue, assign all linksets feeding the same session to the same RID Group.

More details about RID can be found in CCM and Protocol help (SS7).

Two default automatic RID are created which makes system configuration easier:

AUTO RID: RID_EQUALS_TXDPC_OR_RXOPC (65535)
AUTO RID REVERSE: RID_EQUALS_TXOPC_OR_RXDPC (65534)

Depending on the way of the MSU and the PC, RID will be tagged with OPC or DPC.

Attachments

This solution has no attachment