Wireshark-bugs: [Wireshark-bugs] [Bug 10464] UCP dissector bug of operation 30 - data not decode

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 15 Sep 2014 18:35:23 +0000

Comment # 3 on bug 10464 from 
(In reply to Martin Kaiser from comment #1)
> does this look ok? but what's the meaning of the trailing B5 byte?
> (see also https://code.wireshark.org/review/#/c/4098/ )
> 
> Universal Computer Protocol
>     Transaction Reference Number: 0
>     Length: 75
>     Type: Operation (79)
>     Operation: SMS message transfer (30)
>     Data
>         AdC: 49173789456
>         OAdC: 6006
>         AC: 8066
>         NRq: NAdC used (49)
>         NAdC: 49172123456
>         NPID: Mobile station (100)
>         AMsg: message
> 
> [...]
> 0070  33 34 35 36 2f 30 31 30 30 2f 2f 2f 2f 36 44 36   3456/0100////6D6
> 0080  35 37 33 37 33 36 31 36 37 36 35 2f 42 35 03      57373616765/B5.

Sorry, by accident I added another comment (no. 2) instead of replying to this
one.

My reply: It does look good. The trailing B5 byte is the UCP checksum of the
message.

You are receiving this mail because:
  • You are watching all bug changes.