|Main Archive Page > Month Archives > wireshark-dev archives|
Sharing this table between a dissector and a tap would probably be Bad
Sending this relevant information from the dissector to the tap may be
Question is how the generalize this for all types of calls.
On 2012-02-03 13:44, Anders Broman wrote:
> 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?
> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org] On Behalf Of Cristian
> Sent: den 3 februari 2012 13:01
> To: Developer support list for Wireshark
> Subject: [Wireshark-dev] slow sip voip flow for large captures
> 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 <email@example.com>