OCSC Sent Wrong ACR To NCC In Some Scenario
(Doc ID 2346696.1)
Last updated on NOVEMBER 21, 2019
Applies to:
Oracle Communications Service Broker - Version 6.0.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
OCSC received consisting of ACR(False) and ERB(oDisconnect). And OCSC sent consisting of ERB(oDisconnect) and consisting of ACR(True) to NCC, which caused NCC to abort TCAP session but not to end the diameter charging.
In this scenario, OCSC is expected to send consisting of ERB(oDisconnect) and consisting of ACR(False) to NCC.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |