Wireshark-users: [Wireshark-users] GSM MAP SendRoutingInfo not decoded correctly?
From: "Joyce" <joyce.xie@xxxxxxxxxxxxxxxxxx>
Date: Thu, 28 Jun 2007 11:53:26 +0800
|
Hi all,
For those experienced in GSM MAP, you may know when
GMSC send out a "sendRoutingInfo" to HLR to query a msisdn, it will expect
to receive imsi of the msisdn. However I found my trace file does not decode the
"sendRoutingInfoRes" correctly, it seems to be cut as seen in below extracted
record, the first Frame has empty "GSM Mobile
Application" part.
and acturally I can see in the "Transaction
Capabilities Application Part" of first Frame, "Data: 24004102320279F7" indicate the imsi, however it does not show correctly in MAP part.
If you tried to use wireshark to decode the trace
file I attached, you will see "GSM MA Unknow GSM-MAP PDU". And the second Frame
also indicate "BER: Dissector for
OID:1.2.826.0.1249.58.1.0 not implemented. Contact Wireshark developers if you
want this supported".
Any hint is appreciated!
Joyce
Frame 1
Transaction Capabilities Application Part continue Source Transaction ID Transaction Id: 5C0001A3 Destination Transaction ID Transaction Id: 88270003 oid: 0.0.17.773.1.1.1 (itu-t(0) recommendation(0) q(17) 773 as(1) dialogue-as(1) version1(1)) dialogueResponse Padding: 7 protocol-versionre: 80 (version1) 1... .... = version1: True application-context-name: 0.4.0.0.1.0.5.3 (itu-t(0) identified-organization(4) etsi(0) mo bileDomain(0) gsm-Network(1) map-ac(0) locInfoRetrieval(5) version3(3)) result: accepted (0) result-source-diagnostic: dialogue-service-user (1) dialogue-service-user: null (0) components: 2 items Item: returnResultNotLast (7) returnResultNotLast invokeID: 1 resultretres opCode: localValue (0) localValue: 22 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x54 Parameter (0x09) Tag: 0x09 Length: 0x08 Data: 24004102320279F7 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x46 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x42 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x1e CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x00 Length: 0x17 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x00 Length: 0x13 Parameter (0x0a) Tag: 0x0a Length: 0x01 Data: 0C Parameter (0x02) Tag: 0x02 Length: 0x02 Data: 1F44 Parameter (0x00) Tag: 0x00 Length: 0x07 Data: 91695650900630 Parameter (0x01) Tag: 0x01 Length: 0x01 Data: 01 CONSTRUCTOR EOC Parameter (0x00) Tag: 0x00 Length: 0x01 Data: 02 CONSTRUCTOR EOC CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x1e CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x00 Length: 0x17 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x00 Length: 0x13 Parameter (0x0a) Tag: 0x0a Length: 0x01 Data: 02 Parameter (0x02) Tag: 0x02 Length: 0x02 Data: 1F44 Parameter (0x00) Tag: 0x00 Length: 0x07 Data: 91695650900630 Parameter (0x01) Tag: 0x01 Length: 0x01 Data: 01 CONSTRUCTOR EOC Parameter (0x00) Tag: 0x00 Length: 0x01 Data: 02 CONSTRUCTOR EOC CONSTRUCTOR EOC CONSTRUCTOR EOC CONSTRUCTOR EOC GSM Mobile Application Frame 2
Transaction Capabilities Application
Part
end Destination Transaction ID Transaction Id: 88270003 components: 1 item Item: returnResultLast (2) returnResultLast invokeID: 1 resultretres opCode: localValue (0) localValue: 22 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x3d CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x1e CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x17 Parameter (0x02) Tag: 0x02 Length: 0x02 Data: 0422 Parameter (0x01) Tag: 0x01 Length: 0x06 Data: 915669814544 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x09 Parameter (0x00) Tag: 0x00 Length: 0x07 Data: 25F5100064166D CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x03 Parameter (0x0a) Tag: 0x0a Length: 0x01 Data: 01 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x19 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x17 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x00 Length: 0x15 Parameter (0x06) Tag: 0x06 Length: 0x09 Data: 2A863A0089613A0100 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x02 Length: 0x08 CONSTRUCTOR CONSTRUCTOR Tag Tag: 0x00 Length: 0x06 Parameter (0x01) Tag: 0x01 Length: 0x01 Data: 02 Parameter (0x05) Tag: 0x05 Length: 0x01 Data: 07 CONSTRUCTOR EOC GSM Mobile Application Component: returnResultLast (2) returnResultLast invokeID: 1 resultretres opCode: localValue (0) localValue: sendRoutingInfo (22) extendedRoutingInfo: routingInfo (0) subscriberInfo locationInformation ageOfLocationInformation: 1058 vlr-number: 915669814544 1... .... = Extension: No Extension .001 .... = Nature of number: International Number (0x01) .... 0001 = Number plan: ISDN/Telephony Numbering (Rec ITU-T E.164) (0x01 ) ISDN Address digits: 6596185444 Country Code: 65 Singapore length 2 cellGlobalIdOrServiceAreaIdOrLAI: cellGlobalIdOrServiceAreaIdFixedLength (0) cellGlobalIdOrServiceAreaIdFixedLength: 25F5100064166D subscriberState: netDetNotReachable (2) netDetNotReachable: imsiDetached (1) extensionContainer privateExtensionList: 1 item Item extId: 1.2.826.0.1249.58.1.0 (iso(1) member-body(2) bsi(826) disc(0) eric sson(1249) gsmNetworkApplicationsDefinition(58) gsm-Map(1) gsm-Map-Ext(0)) Extension Data BER: Dissector for OID:1.2.826.0.1249.58.1.0 not implemented. Contact Wireshark developers if you want this supported [CONTEXT 5] SEQUENCE [CONTEXT 1] 02 [CONTEXT 5] 07 |
Attachment:
Monitor.pcap.1.00046
Description: Binary data
- Follow-Ups:
- Re: [Wireshark-users] GSM MAP SendRoutingInfo not decoded correctly?
- From: Anders Broman
- Re: [Wireshark-users] GSM MAP SendRoutingInfo not decoded correctly?
- Prev by Date: [Wireshark-users] how to drop 400 unwanted packets to analyze with wireshark ?
- Next by Date: Re: [Wireshark-users] how to drop 400 unwanted packets to analyze with wireshark ?
- Previous by thread: Re: [Wireshark-users] how to drop 400 unwanted packets to analyze with wireshark ?
- Next by thread: Re: [Wireshark-users] GSM MAP SendRoutingInfo not decoded correctly?
- Index(es):