[Anders Broman <anders.broman@xxxxxxxxxxxx>]

Hi,

OK I think I have fixed the bug in trunk and will backport the fix to be released in 1.8.5.

Regards

Anders

---

From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of damker
Sent: den 19 december 2012 08:12
To: 'Community support list for Wireshark'
Subject: [Wireshark-users] reply: REPLY: reply: there is some message element uncomplete decoded

The message type should be “measurement report” , but be dissected as “notification/FACCH” in version 1.8.4.

I don’t known the basic cause , maybe it is supposed to be SACCH with short protocol discriminator .actually it is SDCCH with normal protocol discriminator. Short protocol discriminator is used in VBS/VGCS more often.

 

 

发件人: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] 代表 Anders Broman
发送时间: 2012年12月19日 14:26
收件人: Community support list for Wireshark
主题: Re: [Wireshark-users] REPLY: reply: there is some message element uncomplete decoded

 

damker skrev 2012-12-19 03:11:

My focus is about layer 3 signalling, there is another bug in 1.8.4, so I can’t change to such version.

Can you be a bit more explicit about what the bug is?(saves me digging trough the specs).

 

In version 1.6.11

 

In version 1.8.4

 

___________________________________________________________________________

Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>

Archives:    http://www.wireshark.org/lists/wireshark-users

Unsubscribe: https://wireshark.org/mailman/options/wireshark-users

             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe