Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 5965] Wrong decode SCCP Unitdata message

Date: Fri, 27 May 2011 09:43:31 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5965

Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |jeff.morriss.ws@xxxxxxxxx
         Resolution|                            |INVALID

--- Comment #1 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2011-05-27 09:43:30 PDT ---
(In reply to comment #0)
> Please look at "Pointer to first Mandatory Variable parameter". The address
> 0x63, the value 0x03.
> 
> Q.713 page5 says:
> Coding of the pointers
> The pointer value (in binary) gives the number of octets between the most
> significant octet of the pointer itself (included) and the first octet (not
> included) of the parameter associated with that pointer2...
> 
> It's mean than the first Mandatory Variable parameter starts from the address
> 0x66 the value 0x0d. But the wireshark decodes the first Mandatory Variable
> parameter from address 0x67 the value 0x11. Address 0x66 is ignored.

That 0x0d is the length of the first Mandatory Variable parameter.  By default
the length is not shown in the tree.  If you want to see it, set the SCCP
preference "Show length".

Figure 2 in Q.713 doesn't count the length as part of the parameter which is
why selecting the parameter does not also select (highlight) the length octet.

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