I've got even some "mixed" traces that even cause WS to crash.
The problem here is that to fix this it requires to refactor how the
various MTPs are dealt by Wireshark.
That would as well require changes to the PCAP file format (a new DLT)
to accomodate for "multinational" MTP on the same capture.
While I cannot promise I will get into this soon, I would really
appreciate to have as many different captures as possible for when I
start on this.
\Lego
On Tue, Sep 16, 2008 at 3:39 PM, pu lei <pu.lei@xxxxxxx> wrote:
> Hello folks
>
>
>
> We can choose ITU or Chinese ITU as the ss7 standard used in mtp3
> packets. I Know one of the difference in these two types of standard is the
> bits of point code. The former is 14bits while the latter is 24bits.
>
>
>
> Now,I got a *.rf5 file which was captured by TEK K12 at different
> UMTS-PS-DOMAIN interfaces. In this file, some of the packets is 14bits
> (iu-ps-cp) point code and others is 24bits (gr).
>
>
>
> Wireshark can not dissect the two types of mtp3 point code right at the
> same time.
>
>
>
> Is it possible? Or how should I config Wireshark to do this?
>
>
>
> Thanks in advance.
>
>
>
> Brs
>
> Leo pu
>
> _______________________________________________
> Wireshark-users mailing list
> Wireshark-users@xxxxxxxxxxxxx
> https://wireshark.org/mailman/listinfo/wireshark-users
>
>
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan