Wireshark-dev: Re: [Wireshark-dev] TCAP different upper layer

From: "DROUIN, FLORENT (FLORENT)" <florent.drouin@xxxxxxxxxxxxxxxxxx>
Date: Fri, 17 Sep 2010 15:29:05 +0200
Hi,

I think it is already implemented.
You can check with the sample camel2.pcap on the Wiki.
But you need to activate the Service Response Time analyze to keep the AP context, and ,as noticed, the TC Begin must be included in the traces.

Regards
Florent

-----Message d'origine-----
De : wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] De la part de Anders Broman
Envoyé : vendredi 17 septembre 2010 15:06
À : Developer support list for Wireshark
Objet : Re: [Wireshark-dev] TCAP different upper layer

Hi,
Currently not, but it should be possible to create a sub dissector table and have
Sub dissectors regestering by application-context-name. Of hand I don't remember if
The application-context is only there at dialog establishment if so it becomes a bit more complicated as
The dialog has to be tracked to find the right subdissector. Dissection would also fail
If dialog establisment isn't in the trace.
Regards
Anders 

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of robie.die.katze@xxxxxx
Sent: den 17 september 2010 14:58
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] TCAP different upper layer

hello experts,

exist a possibility for the tcap dissector to select upper protocols for example with help of the application-context-name and not only with help of subsystem number.

thx guenter

--
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!  
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
___________________________________________________________________________
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
___________________________________________________________________________
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