How to Analyse "User Data Header" Errors thrown by xmsTrigger for SMPP Traffic (Doc ID 1308314.1)

Last updated on AUGUST 01, 2011

Applies to:

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

Goal

This article will cover different User Data Header errors which can be thrown by xmsTrigger in regards to the SMPP (Short Message Peer to Peer ) protocol and how to understand them.

Firstly, a quick review of the SMPP "packet" and how the they fit together.  The following elements of an SMPP message which we are interested in are as follows:

TCP
- SMPP
- ...
- GSM Features (This is where the User Data Header Indicator will be set if required)
- ...
- User Data Length
- User Data
- User Data Header Length
- User Data Header
- ...

Where, TCP (Transmission Control Protocol) is the transport protocol for the SMPP packets and encoded within the SMPP message are the following TLVs (Tag Length Value) which we are interested in:
  • UDHI = User Data Header Indicator
The UDHI is a flag contained in the "esm_class" (External Short Message) bitmask.  In Wireshark, this bit mask is referred to as "GSM Features" (Global System for Mobile Communications).

Solution

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