Wireshark-bugs: [Wireshark-bugs] [Bug 7762] Getting dissector bug when cookie-echo decoded as ru

Date: Thu, 27 Sep 2012 03:21:03 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7762

--- Comment #5 from rohini <rn0055832@xxxxxxxxxxxxxxxx> 2012-09-27 03:21:02 PDT ---
Can you please decode the data part as RUA?
> Hmm, this is the decode I get:
> 
> ~~~
> No.     Time            Source                Destination           Protocol
> Severity Info
>       3 12:12:17.616679 localhost             localhost             RUA        
>       COOKIE_ECHO (RUA) 
> 
> Frame 3: 426 bytes on wire (3408 bits), 426 bytes captured (3408 bits)
> Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst: 00:00:00_00:00:00
> (00:00:00:00:00:00)
> Internet Protocol Version 4, Src: localhost (127.0.0.1), Dst: localhost
> (127.0.0.1)
> Stream Control Transmission Protocol, Src Port: 4444 (4444), Dst Port: 1234
> (1234)
> UTRAN Iuh interface RUA signalling
>     RUA-PDU: initiatingMessage (0)
>         initiatingMessage
>             procedureCode: id-Connect (1)
>             criticality: reject (0)
>             value
>                 Connect
>                     protocolIEs: 5 items
>                         Item 0: id-CN-DomainIndicator
>                             ProtocolIE-Field
>                                 id: id-CN-DomainIndicator (7)
>                                 criticality: reject (0)
>                                 value
>                                     CN-DomainIndicator: cs-domain (0)
>                         Item 1: id-Context-ID
>                             ProtocolIE-Field
>                                 id: id-Context-ID (3)
>                                 criticality: reject (0)
>                                 value
>                                     Context-ID: 490003 [bit length 24, 0100
> 1001  0000 0000  0000 0011 decimal value 4784131]
>                         Item 2: id-IntraDomainNasNodeSelector
>                             ProtocolIE-Field
>                                 id: id-IntraDomainNasNodeSelector (5)
>                                 criticality: ignore (1)
>                                 value
>                                     IntraDomainNasNodeSelector
>                                         version: release99 (0)
>                                             release99
>                                                 cn-Type: gsm-Map-IDNNS (0)
>                                                     gsm-Map-IDNNS
>                                                         routingbasis:
> localPTMSI (0)
>                                                             localPTMSI
>                                                                
> routingparameter: 0000 [bit length 10, 6 LSB pad bits, 0000 0000  00.. ....
> decimal value 0]
>                                                         .... ...0 dummy: False
>                         Item 3: id-Establishment-Cause
>                             ProtocolIE-Field
>                                 id: id-Establishment-Cause (6)
>                                 criticality: reject (0)
>                                 value
>                                     Establishment-Cause: normal-call (1)
>                         Item 4: id-RANAP-Message
>                             ProtocolIE-Field
>                                 id: id-RANAP-Message (4)
>                                 criticality: reject (0)
>                                 value
>                                     RANAP-Message:
> 0000003c4000020036401900000200350002001c40031002...
> Data (64 bytes)
> 
> 0000  00 00 00 3c 40 00 02 00 36 40 19 00 00 02 00 35   ...<@[email protected]
> 0010  00 02 00 1c 40 03 10 02 9a 00 35 00 02 01 bc 40   [email protected]....@
> 0020  03 10 02 9a 00 29 40 0e 00 00 01 00 28 40 07 00   .....)@.....(@..
> 0030  80 00 04 02 00 00 00 00 00 e9 40 04 60 7b 00 7b   ..........@.`{.{
> ~~~
> 
> Ah, OK, I guess the RANAP dissector is not being called in my case; do you do
> something special to get the RANAP message decoded as RANAP?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.