This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Help needed in NAS msg container

0

I am using wireshark Version 1.8.7. In case of SGsAP Uplink Unitdata or SGsAP Downlink Unitdata packet in NAS msg container IE for TP-MTI in TPDU SMS-SUBMIT-REPORT the spec says the field TP-Failure-Cause is mandatory.But the wireshark does not show so.It never show TP-Failure-Causs field.Is it right?

asked 28 May '13, 00:56

swap's gravatar image

swap
11556
accept rate: 0%


2 Answers:

0

TP-Failure-Cause field is only present in case of RP-ERROR. In case of RP-ACK it is not present. Are you in the RP-ERROR case? Can you share a pcap file?

answered 28 May '13, 03:03

Pascal%20Quantin's gravatar image

Pascal Quantin
5.5k1060
accept rate: 30%

0

What is the specific scenario being referenced? As per 3GPP TS 23.040 section 9.2.2.2, Pascal is correct on spec (TP-Failure-Cause is only mandatory in SMS-SUBMIT-REPORT for RP-ERROR). First I suggest you double-check the message container to see if it falls under the IE breakdown of 9.2.2.2a(i) or 9.2.2.2a(ii) tables in 3GPP TS 23.040.

Barring that, you mention this is specific to an SGs interface trace. Have you followed this message through at a MAP level, or compared it to an unciphered NAS message container from an S1-MME or Iu trace to say that a TP-Failure-Cause was being decoded by Wireshark elsewhere for this NAS message? The .pcaps would be very helpful here if you are able to share them though considering this is carrier SMS I'm guessing you cannot.

answered 28 May '13, 20:51

Quadratic's gravatar image

Quadratic
1.9k6928
accept rate: 13%