RAN SMS First PDU Often Not Decoded with Error Message "Could not get full decode of the pdu"

Asset ID:	1-72-2174501.1
Update Date:	2016-08-25
Keywords:

Solution Type Problem Resolution Sure

Solution 2174501.1 : RAN SMS First PDU Often Not Decoded with Error Message "Could not get full decode of the pdu"

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.4 to 10.0.0 [Release 9.0 to 10.0]
Information in this document applies to any platform.

Symptoms

In RAN SMS xDRs, the first PDU is not often decoded in the decoding window. The message displayed in the full decoding is "Could not get full decode of the PDU".

Changes

Cause

The sms content has been anonymized by replacing the content with "*" character.

SMS (text messages) coding in based on 7 bits dictionary whereas the anonymization uses a 8 bits "*", which induces unreadable sequence of characters and prevent MSU to be be displayed in ProTrace full decoding area.

This can be seen in SMS MSU:

00000000 Special case 0 GSM 7 bit default alphabet

And anonymized sms content:

2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A

Solution

ProTrace does not manage correctly such sms. Issue is no more present since PIC 10.2, the tool "Trouble shooting" (replacing ProTrace) displays correctly MSU containing anonymized SMS payload.

References

<NOTE:1683907.1> - ProTrace PDU Decoding not Displayed with "ERRlngth" Error Message on PIC 9.0.3 and 9.0.4

Attachments

This solution has no attachment