> Anders Broman skrev 2011-10-07 18:10:
> > Mike Morrin skrev 2011-10-07 17:48:
> >>
> >> I think that it should be a bit more flexible:
> >> * Have conversations per protocol, with 1 or more identifier keys.
> >> * When a new identifier is observed, if it can be associated with an
> >> existing co
On Oct 7, 2011, at 5:51 AM, Anders Broman wrote:
> I've been contemplating the idea of making it possible to filter a "call" in
> the Telco world that could involve
> A multitude of protocols for example SIP, DIAMETER, H248, ISUP, BICC and a
> number of Mobile protocols. I suppose this is
> Wha
: Re: [Wireshark-dev] Global conversation
On Fri, Oct 07, 2011 at 02:51:35PM +0200, Anders Broman wrote:
Perhaps it could be done if we had a Global conversation to which you
cold add a List of per protocol conversations.
We could create a new set of conversation functions, such as
Mike Morrin skrev 2011-10-07 17:48:
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Stephen Fisher
Sent: 07 October 2011 16:32
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Global conversation
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Stephen Fisher
Sent: 07 October 2011 16:32
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Global conversation
On Fri, Oct 07, 2011 at 02:51:35PM
On Fri, Oct 07, 2011 at 02:51:35PM +0200, Anders Broman wrote:
> Perhaps it could be done if we had a Global conversation to which you
> cold add a List of per protocol conversations.
We could create a new set of conversation functions, such as:
global_conversation_new()
global_
>>Thus wrote Guy Harris (g...@alum.mit.edu):
>
>> We should probably also add a notion of "conversations" available to
>> dissectors at multiple layers (a notion more general than the current
>> address-and-port-endpoint-pair notion, that can include multiple
>> address layers, "circuits" for
