SSMN Node Core Dumps when Trying to Interpret ACS Language ID
(Doc ID 2370280.1)
Last updated on MARCH 14, 2018
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
On Oracle Communication Convergent Charging Controller (OC3C) and Oracle Communication Network Charging Controller (OCNCC) the Send Short Message Notification (SSMN) feature node core dumps when trying to interpret Advanced Control Services (ACS) language ID.
Due to the Send Notification (NOTF) feature node not supporting explicit encoding options for Messaging Manager (MM), the SSMN node is used for sending notifications. However, due to the general integer encoding problem on Linux, the internal ID is not interpreted correctly and the SSMN node core dumps.
In this case, language is set to "English", which is resolved to ID 21 - which works fine with NOTF node - when the SSMN node comes to resolve it, it's looking for the wrong number; as it does not find any language the slee_acs cores:
In slee-acs.log we see that the language is not found:
Due to this issue customers are unable to generate Short Message Service (SMS) notifications with the correct network encoding using dynamic subscriber language information.
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