GSM SMS PDU TPVPF wrong interpretation.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4524

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@31985 f5534014-38df-0310-8fa8-9805f1628bb7

diff --git a/epan/dissectors/packet-gsm_sms.c b/epan/dissectors/packet-gsm_sms.c
index e1511234f688428413c275051ca5d977d1205728..07d29c408fcb2c9fb5a089a35a57682c2a5ec238 100644 (file)
--- a/epan/dissectors/packet-gsm_sms.c
+++ b/epan/dissectors/packet-gsm_sms.c
@@ -280,11 +280,12 @@ static const value_string msg_type_strings_ms_to_sc[] = {
     { 0, NULL },
 };
 
+/* 9.2.3.3 TP-Validity-Period-Format (TP-VPF) */
 static const value_string vp_type_strings[] = {
-    { 0,       "TP VP field not present"},
-    { 1,       "TP VP field present - relative format"},
-    { 2,       "TP-VP field present - enhanced format"},
-    { 3,       "TP VP field present - absolute format"},
+    { 0,       "TP-VP field not present"},
+    { 2,       "TP-VP field present - relative format"},
+    { 1,       "TP-VP field present - enhanced format"},
+    { 3,       "TP-VP field present - absolute format"},
     { 0, NULL },
 };