SDP Session ID Causing Over Correlation of Two Separate Outbound Legs
(Doc ID 2515358.1)
Last updated on SEPTEMBER 29, 2020
Applies to:Oracle Communications Session Monitor - Version 4.0 and later
Information in this document applies to any platform.
Customers report seeing outbound calls to separate carriers with different To\From numbers being correlated in Oracle Communications Operation Monitor (OCOM). The message flow has multiple INVITE's from the same SBC to the same Session Router but to different carriers and with different To\From information.
Two separate outbound legs are being incorrectly correlated together causing over correlation.
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