How to Analyse "User Data Header" Errors thrown by xmsTrigger for SMPP Traffic
(Doc ID 1308314.1)
Last updated on JANUARY 05, 2023
Applies to:Oracle Communications Network Charging and Control - Version 2.2.0 and later
Information in this document applies to any platform.
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:
Note: Wireshark does not decode/display the IE Data (ID, #Segments and Current Segment) in a UDH of Concatenated Short Messages fully in the Packet Details pane. Refer to the Packet Bytes Pane to find out the UDH information as per the following example of a UDH for the first of five segments in a concatenated SMS:
- UDHL = User Data Header Length
As described for the UDH, the UDHL is the first octet in the UDH and represent the total length of the UDH. This will usually be 5 as the octet which contains the length of the UDH is not included in the UDHL count.
The relationship between the aforementioned elements of an SMPP message can also be visualised as:
Where if the UDHI is set, then the UDL will be the length of the UDH + UD and within the UDH, is the UDHL which is the length of the UDH.
Note: The "octets" are not to scale.
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