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.
Thanks & Regards,
Vaibhav
"Martin
Mathieson"
<martin.r.mathies To
on@xxxxxxxxxxxxxx "Community support list for
> Wireshark"
Sent by: <wireshark-users@xxxxxxxxxxxxx>
wireshark-users-b cc
ounces@wireshark.
org Subject
Re: [Wireshark-users] Fw: I am not
decode the Nbap
08/07/2007 05:57 andsscopmessages.
PM
Please respond to
Community support
list for
Wireshark
<wireshark-users@
wireshark.org>
> Not RRC not directely on UDP,
> But stack is like this :- UDP-> FP-> MAC-> RLC-> RRC (But only difference
> is this FP over UDP not on ATM).
>
Hi,
There is support for FP (not MAC or RLC yet), but only currently for
DCT2000 or K12 format files (there is support for UDP over FP for
DCT2000, I don't think there is for K12...). Those formats both
contain the extra information needed to know how to interpret the FP
frame.
The alternative to having this information would be to infer the
configuration of the FP, MAC and RLC layers and simulate them based
upon RRC configuration. This would be quite involved. And impossible
if you need this info in order to decode the RRC messages in the first
place :(
Martin
_______________________________________________
Wireshark-users mailing list
Wireshark-users@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-users
*********************** 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."
