http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=892
------- Comment #3 from mike.oliveras@xxxxxxxxx 2006-06-24 20:58 GMT -------
I noticed from the dev mailing list that a patch was submited by Martin
Mathieson to fix part of this issue.
http://www.wireshark.org/lists/wireshark-dev/200606/msg00056.html
"This patch fixes the part where the DeleteConnection messages and responses
were not being included in the graphs. There is a test that allows messages
such as these for 1 second after the call has been hung up, but the time
calculation was wrong."
I tested this using version 1.1.0-svn-18572, and found that it is partially
fixed.... the DLCX and 250 response are shown for one of the call legs but not
the other. Referencing the attached trace, the time between endpoint
192.168.1.6 sends a NTFY:hu (frame 22421) and a DLCX is returned (frame 24206)
is 1.44 secs.. Maybe the 1 second delay should be increased a bit? Is three
seconds too long?
Best Regards,
Mike Oliveras
--
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.