Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 1498] New: GSM_MAP dissector decodes MAPv2 MT-ForwardShortMessage incorrectly

[bugzilla-daemon@xxxxxxxxxxxxx]

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1498

           Summary: GSM_MAP dissector decodes MAPv2 MT-ForwardShortMessage
                    incorrectly
           Product: Wireshark
           Version: SVN
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: sarkar.abhik@xxxxxxxxx


Build Information:
Version 0.99.6-SVN-20972

Compiled with GTK+ 2.10.7, with GLib 2.12.7, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1,
with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio
PortAudio V19-devel, with AirPcap.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 3.1
(packet.dll version 3, 1, 0, 27), based on libpcap version 0.9[.x], without
AirPcap.

Built using Microsoft Visual C++ 8.0 build 50727
--
In GSM MAP v1 and v2, there was no distiction in the op-codes of MT and MO
Forward Short Message. They were both 46 decimal.

However in MAP v3 (aka Phase 2+), MT-FSM is 44 and MO-FSM is 46. 

The GSM_MAP dissector is (currently) based on 3GPP TS 29.002 7.5.0. This causes
it to decode everything as MAPv3. However, several networks still use MAPv2 for
SMS, and some even MAPv1. This causes incorrect interpretation of the MAPv2
MT-ForwardShortMessage as a MAPv3 MO-ForwardShortMessage. It might be happening
for some other operation too, but I only have SMS related captures.

MAP v2 is described in ETSI GSM MAP specification "GSM 09.02 version 4.19.1".


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.