Hi,
With Ethereal 0.10.9 and MTP3 set as ANSI (
Edit->preferences->ptrotocols->MTP3) the second frame decodes
as:
Transaction Capabilities Application Part
Message
Type: TC-END (0x64)
Length: 0x54
Destination Transaction ID
Transaction Id: Destination Transaction ID
(73)
Length:
0x04
Value:
0x6a011600
Dialogue
Portion
Dialogue Portion
Tag
Length:
0x2a
External Tag:
0x28
Length:
0x28
Object Identifier
Tag
Length:
7
OID: 0.0.17.773.1.1.1 (itu-t(0)
recommendation(0) q(17) 773 as(1) dialogue-as(1)
version1(1))
Single-ASN.1-type
Tag
Length:
0x1d
Dialogue
Response
Dialogue Type: Dialogue Response
(0x61)
Length:
0x1b
Protocol Version Tag:
0x80
Length:
0x02
Binary Data:
0780
Application Context Name Tag:
0xa1
Length:
0x09
Length: 7
OID:
0.4.0.0.1.0.5.3
Result Tag
Length:
0x03
Integer
Tag
Length:
0x01
Accepted 0
Result Source Diagnostic
Tag
Length:
0x05
Dialogue Service User
Tag
Length:
0x03
Integer
Tag
Length:
0x01
Null
0
Components
Portion
Component Portion
Tag
Length:
0x20
Component
GSM Mobile
Application Part
Component
Return Result(Last) Type
Tag: a2
Length:
0x1e
Invoke
Id
Invoke
Id Tag:
0x02
Length:
0x01
Invoke Id: 180
Sequence
Tag: 0x30
Length:
0x19
Operation
Code
Operation Code Tag:
0x02
Length:
0x01
Operation Code: Send Routing Info
(22)
Sequence
Tag:
0xa3
Length:
0x14
Parameter
Tag:
0x89
Length:
0x08
Parameter
Data
Parameter
Tag:
0x04
Length:
0x08
Parameter Data
Best regards
Anders
Hi All,
Error in decoding of the GSM Map message-MAP END message, I
think it could have been decoded like the test file.
Best regards,
Deepesh
ALL-NEW Yahoo!
Messenger - all new features - even more
fun!