My Oracle Support Banner

SSMN Marked As Requiring Telephony, Leading To Invalid GUI Error (Doc ID 2755448.1)

Last updated on MARCH 09, 2021

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications Network Charging and Control (NCC) and Oracle Communications Convergent Charging Controller (OC3C) version 6.0.1 and later. Use the Send Short Message Notification (SSMN) feature node to construct and send an INTERNAL short message from Messaging Manager that you specify either in the feature node, or by using a notification template defined in Advanced Control Services (ACS).

 

There is an issue with the SSMN node where is has a USES_TELEPHONY value of 2 for some reason. This means if you run a Disconnect Call node straight to it, the CPE pops up an error saying "Cannot join a non-telephony exit to a telephony node".


This should not be the case as SSMN should not be telephony.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.