Wireshark-bugs: [Wireshark-bugs] [Bug 11466] Camel: ServiceInteractionIndicatorTwo incorrectly r

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 24 Aug 2015 13:06:24 +0000

Comment # 1 on bug 11466 from 
In 3GPP TS 29.078 11.0.0 (2011-09) which is used to generate the Camel
dissector
the ASN1 code is:

EstablishTemporaryConnectionArg {PARAMETERS-BOUND : bound} ::= SEQUENCE {
  assistingSSPIPRoutingAddress[0] AssistingSSPIPRoutingAddress {bound},
  correlationID            [1] CorrelationID {bound}    OPTIONAL,
  scfID                [3] ScfID {bound}         OPTIONAL,
  extensions            [4] Extensions {bound}     OPTIONAL,
  carrier            [5] Carrier {bound}         OPTIONAL,
  serviceInteractionIndicatorsTwo [6] ServiceInteractionIndicatorsTwo OPTIONAL,
  callSegmentID                [7]    CallSegmentID {bound}     OPTIONAL,
  naOliInfo            [50] NAOliInfo         OPTIONAL,
  chargeNumber            [51] ChargeNumber {bound}    OPTIONAL,
    ...,
etc

If you go to edit->preferences->protocols->BER and set "Show internal BER
encapsulation tokens" you will see

...0 0111 = Tag: 7
Length: 3
callSegmentID: 8519937

So I think Wiresharks decoding is correct.

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