IMSSF Doesn't Populate NOA Token In B2B SAL INVITE Caused By Connect (Doc ID 1497120.1)

Last updated on OCTOBER 10, 2016

Applies to:

Oracle Communications Service Broker - Version 6.0.0.1.0 and later
Information in this document applies to any platform.

Symptoms

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).

Cause

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