https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7066
--- Comment #13 from Cristian Constantin <const.crist@xxxxxxxxxxxxxx> 2012-04-13 02:54:17 PDT ---
(In reply to comment #11)
> Yes, it should take into account the most recent setup frame.
> I was looking at
> http://anonsvn.wireshark.org/viewvc/trunk/epan/conversation.c?0=39484&1=40837&pathrev=40837
> and don't see anything particularly shocking there, but then i never worked
> much with conversations.
> As i understand it, there can be multiple conversations for the same key,
> sorted by setup-frame. Did you maintain that scheme?
>
> What about if you debug the calls to conversation_new for the various SDP
> setup-frames? Maybe you could see something wrong there.
cristian: there was something really wrong in conversation_lookup_hashtable().
I have posted a patch. I have tested the t38 capture and it works now.
can you pls. test it as well? do you have some other captures with multiple
(overlapping) sessions?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.