http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2197
------- Comment #5 from elmer.elmer@xxxxxxx 2008-01-16 16:53 GMT -------
Thanks for your answer,
I have installed the SVN build.
Bug is still there...
How to reproduce:
Open ethtrace_full.pcap
Choose Statistics/VoIp calls :
There should be 7 calls displayed
Select the 4th one (from 31134 to 0, overlap sending so destination number is
not complete)
Then select graph:
-> You should only see H.225 signaling, no H.245
I have made deeper tests on my side...
In fact, the H.245 part of the 4th call is 'attached' to the first call (also
from 31134 to 0)
If you graph the first call, you should see 2 complete H.245 sequences attached
to it.
I don't know exactly which criteria are used by the VoIP calls feature to
attach a H.245 sequence to a call... (H.245 ports are negociated during H.323
opening)
In this test case, Source IP:port and destination IP:port are identical in both
first and 4th call. It may confuse the H.323 analysis.
The H.245 channel has been nicely closed for the first call (H.245 normally
closed 'end session', and associated TCP channel also closed)
I hope this could help you...
--
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.
