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

[robie.die.katze@xxxxxx]

hi,

thx.
that was the missing parameter...
i changed ssn in tcap to 146.
then the the first 2 frames where displayed correct.
the next 2 frames where shown as tcap.
after selecting 'Service Respons Time Analyse' &
'persistent stats for SRT' in tcap
the last 2 frames where also displayed correct.

kr guenter

Hi,

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

Did you add the SSN 146 in the SCCP SSN list of the TCAP preferences ?

Regards
Florent

-----Message d'origine-----
De : wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] De la part de robie.die.katze@xxxxxx
Envoyé : lundi 20 septembre 2010 15:38
À : wireshark-dev@xxxxxxxxxxxxx
Objet : Re: [Wireshark-dev] TCAP different upper layer

hi,

thx for the tipps.
i had a look to the camel2.pcap file and also camel.pcap but wireshark
(1.4) showed me only sccp packets with the data block.
tcap & camel where not displayed.
is there anything special to configure?
i switched on 'service response time analyse' for camel
& tried it also for sccp but without any change.

kr guenter


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

-- 
GMX DSL SOMMER-SPECIAL: Surf & Phone Flat 16.000 für nur 19,99 Euro/mtl.!*
http://portal.gmx.net/de/go/dsl