Hi,
It was just a thought for this specific case, as I think it might be exactly the same hash table...
7Anders
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jaap Keuter
Sent: den 3 februari 2012 14:46
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] slow sip voip flow for large captures
Hi,
Sharing this table between a dissector and a tap would probably be Bad Style, IMHO.
Sending this relevant information from the dissector to the tap may be possible.
Question is how the generalize this for all types of calls.
Thanks,
Jaap
On 2012-02-03 13:44, Anders Broman wrote:
> Hi,
> Please put the patches in bugzilla, if possible split them in two
> parts one that's ok for all types(Step 2,3,4?) of calls and one which
> Implements the stuff for SIP but not for the other call types. I think
> the SIP dissector keeps a table over the calls as well could that
> table be shared?
> Regards
> Anders
>
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Cristian
> Constantin
> Sent: den 3 februari 2012 13:01
> To: Developer support list for Wireshark
> Subject: [Wireshark-dev] slow sip voip flow for large captures
>
> hi!
>
> wireshark can draw call flows for sip voip calls (accessible through
> the menu Telephony/VoIP Calls).
>
> however, when the capture is large, containing tens of thousands of
> sip voip calls, wireshark becomes very slow at producing the list of
> calls and the call flows.
>
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe