Discussion:
TCAP/CAMEL protocols dissection problem
mosbah abdelkader
2014-09-01 09:14:10 UTC
Permalink
Hello All,


I am sorry if my question is asked on the wrong place.


I have run the tshark command with the -V argument (to get protocol
details) on a capture file containing CAMEL protocol traces over M2PA
SIGTRAN (lower layers are TCAP/SCCP/MTP3/M2PA/SCTP). But the dissection
only detects the layers M2PA/MTP3/SCCP. Here is the output:

[Protocols in frame: eth:ip:sctp:m2ua:mtp3:sccp:data]


The dissector does not detect TCAP and CAMEL.


I have had the same problem with a file containing INAP and ISUP.


Here are the links of the pcap file and the tshark command output hosted on
google drive:

- pcap:
https://drive.google.com/file/d/0B-lcP-o4fZ9UMjlZeXJQNTVJeU0/edit?usp=sharing
- output:
https://drive.google.com/file/d/0B-lcP-o4fZ9UV2hNNG51emswSlE/edit?usp=sharing


Please help me upon this issue: is there any hint how to get these
protocols decoded correctly? Is this an issue with wireshark dissector?


Best Regards.
Jeff Morriss
2014-09-02 03:09:41 UTC
Permalink
Post by mosbah abdelkader
Hello All,
I am sorry if my question is asked on the wrong place.
I have run the tshark command with the -V argument (to get protocol
details) on a capture file containing CAMEL protocol traces over M2PA
SIGTRAN (lower layers are TCAP/SCCP/MTP3/M2PA/SCTP). But the dissection
[Protocols in frame: eth:ip:sctp:m2ua:mtp3:sccp:data]
The dissector does not detect TCAP and CAMEL.
I have had the same problem with a file containing INAP and ISUP.
Here are the links of the pcap file and the tshark command output hosted
https://drive.google.com/file/d/0B-lcP-o4fZ9UMjlZeXJQNTVJeU0/edit?usp=sharing
https://drive.google.com/file/d/0B-lcP-o4fZ9UV2hNNG51emswSlE/edit?usp=sharing
Please help me upon this issue: is there any hint how to get these
protocols decoded correctly? Is this an issue with wireshark dissector?
What version are you using?

It decodes as Camel for me in the current development version.

First thing to check is that your Camel dissector is registered for SSN
146. Go to Edit->Preferences->Protocols->Camel and make sure the SSN
(or SSN list) includes 146.

___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users-IZ8446WsY0/***@public.gmane.org>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request-IZ8446WsY0/***@public.gmane.org?subject=unsubscribe
mosbah abdelkader
2014-09-03 10:43:40 UTC
Permalink
Hello Jeff,


Thank you for your response. I am using: wireshark-1.8.10-7.el6_5.x86_64
under CentOS 6.5. I havn't yet tried the latest build but your advice
worked for me, Thanks a lot!


BR.

Loading...