IMSSF Doesn't Populate NOA Token In B2B SAL INVITE Caused By Connect
(Doc ID 1497120.1)
Last updated on MARCH 05, 2019
Applies to:Oracle Communications Service Broker - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
In IN mediation scenario (IMSSF Over IMSCF) once SCP sends Connect, IMSSF creates B2B SAL INVITE back to IMSCF without NOA (or + for International) token in Request URI, To, From, PAI, etc. headers. That's causing IMSCF to set Parameters to original from the network or to default (UNKNOWN).
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