Short Message Using GSM7Bit Alphabet Fails Giving Error "MmxiSMPP Unsupported Alphabet: GSM7Bit Fallback to: GSM8Bit" for SMPP Adapter (Doc ID 1566432.1)

Last updated on AUGUST 27, 2013

Applies to:

Oracle Communications Network Charging and Control - Version 2.2.0 to 5.0.0 [Release 2.2 to 5.0]
Information in this document applies to any platform.

Symptoms

Messaging Manager can not send SMS (Short Message Service) when using its SMPP (Short Message Peer-to-Peer) adapter configured with a GSM7Bit alphabet.

THe following debug output can be seen in the /IN/service_packages/XMS/tmp/xmsTrigger.log file showing the GSM7Bit is not supported so uses the GSM8Bit alphabet instead.

The Messaging Manager Technical Guide - Chapter 3, Configuring the SMPP Adapter - states that GSM7Bit alphabet is allowed though.

Syntax: alphabet = "<charset>"
Description: Character set of the desired alphabet.
Type: String
Allowed: ...
              GSM7Bit
              GSM8Bit
              GSM7BitComp
              GSMBinaryComp
              GSMUCS2Comp
              ...

NCC documentation can be found by following Doc ID 1341844.1 - How to Download Oracle Communications Network Charging and Control (OCNCC/NCC) Documentation.

Messaging Manager documentation describes how to set the alphabet, depending on required message class (Store or Flash).  Example requirements may be:

  1. DCS = 0  having message class 0 (Store SMS) should have 8bit coding.
  2. DCS = F0 having message class 1 (Flash SMS) should have 7bit coding.

For more details, refer to Data Coding Scheme (DCS) section and Message Classes section of Global System for Mobile (GSM).

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