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 1920] Bug in Sigcomp decoding, STATE-ACCESS instruction

Date: Fri, 19 Oct 2007 10:50:44 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1920





------- Comment #2 from rgarcia2@xxxxxxxxxxxx  2007-10-19 10:50 GMT -------
(In reply to comment #1)
> Could you provide a trace illustrating this so a bug fix can be verified.
> 

Hi,

Thanks for looking at the issue.

Unfortunately, the capture files that I have contain private subscribers data
as well as our propietary implementation of the bytecode. I've reached the
conclusion that the state_length "0" didn't work, because with the instruction:

STATE-ACCESS (rfc3485_id, 6, 0, 0, rfc3485_state, 0)

to access the SIP static dictionary, header words were not correctly decoded
("0" padding appeared at the decoded message instead), although understood by
the TE's implementation of the UDVM. However, when I changed the instruction
(and this was the only change) to

STATE-ACCESS (rfc3485_id, 6, 0, 4836, rfc3485_state, 0) 

(4836 is the length of the state), Wireshark decodes the message without
problems.

If you have a fix and want to send it to me, I can do the verification with the
capture files and tell you if I find any problem with it.

Thanks again for looking at the issue.


-- 
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.