My Oracle Support Banner

SMS DCS Changes When Converting Between Protocols (Doc ID 2416390.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.

Symptoms

In all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), Messaging Manager (MM) may change the encoding of certain Short Message Service (SMS) fields if it is also perform a protocol change between an incoming and outgoing SMS.

For example, if a Short Message Peer-to-Peer (SMPP) arrives at MM which performs a conversion to Mobile Application Part (MAP), the Data Coding Scheme(DCS) encoding may change from 0xF6 to 0x15.  For example:

Incoming SMPP DCS

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.