Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: [Wireshark-users] Fw: Fw: I am not able to decode FP messages.

Date: 08-Aug-2007 19:25:40 ZE5B

Hi ,

Please tell me, How to set default values of FP (For your refrence please
see below mail).

Thanks & Regards,

             <martin.r.mathies                                          To 
             on@xxxxxxxxxxxxxx         Vaibhav Agarwal/NokiaDDF@NOKIADDF   
             >                                                          cc 
                                       "Community support list for         
             08/07/2007 06:31          Wireshark"                          
             PM                        <wireshark-users@xxxxxxxxxxxxx>     
                                       Re: [Wireshark-users] Fw: I am not  
                                       able to decode FP messages.         

> Hi,
> I only want to decode RRC or FP message , I do not want to decode RLC and
> MAC layer messages.
> But in over case FP over UDP not on ATM.
> Please tell how to configure FP over UDP then RRC.

You won't be able to decode the FP messages without supplying the
dissector with at least some of the extra information stored in this
structure (see packet-umts_fp.h) and attaching it to the packet, as
the DCT2000 and K12 dissectors do.

We could maybe add preferences to the FP dissector to set default
values for some of these in the absence of complete configuration...

enum fp_interface_type

typedef struct fp_info
    enum fp_interface_type iface_type;
    guint8  release;                     /* e.g. 99, 4, 5, 6 */
    guint16 release_year;                /* e.g. 2001 */
    guint8  release_month;               /* e.g. 12 for December */
    gboolean is_uplink;
    gint channel;                       /* see definitions above */
    guint8  dch_crc_present;            /* 0=No, 1=Yes, 2=Unknown */
    gint paging_indications;
    gint num_chans;
#define MAX_FP_CHANS  64
    gint chan_tf_size[MAX_FP_CHANS];
    gint chan_num_tbs[MAX_FP_CHANS];

#define MAX_EDCH_DDIS 16
    gint   no_ddi_entries;
    guint8 edch_ddi[MAX_EDCH_DDIS];
    guint  edch_macd_pdu_size[MAX_EDCH_DDIS];
} fp_info;

... but I don't think you'll have RRC directly over FP, you'll have
MAC and RLC.  If you don't care about displaying their details, you
still need to understand them to skip their headers properly and
reassemble their data.


***********************  Aricent-Unclassified   ***********************

***********************  Aricent-Unclassified   ***********************

"DISCLAIMER: This message is proprietary to Aricent  and is intended solely
for the use of
the individual to whom it is addressed. It may contain privileged or
confidential information and should not be
circulated or used for any purpose other than for what it is intended. If
you have received this message in error,
please notify the originator immediately. If you are not the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."