Comment # 2
on bug 11466
from Sasa Hercog
(In reply to Anders Broman from comment #1)
> 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.
3GPP TS 29.078 11.0.0 is for Camel phase 3.
For Camel phase 2 you must check GSM 09.78 version
7.1.0(http://www.3gpp.org/DynaReport/0978.htm) and in that document tag 7 is
for serviceInteractionIndicatorsTwo, see below
EstablishTemporaryConnectionArg ::= SEQUENCE {
assistingSSPIPRoutingAddress [0] AssistingSSPIPRoutingAddress,
correlationID [1] CorrelationID
OPTIONAL,
scfID [3] ScfID
OPTIONAL,
extensions [4] SEQUENCE SIZE(1..numOfExtensions)
OF
ExtensionField
OPTIONAL,
serviceInteractionIndicatorsTwo [7] ServiceInteractionIndicatorsTwo
OPTIONAL,
...,
na-info [50] NA-Info
OPTIONAL
}
Br,
Sale
You are receiving this mail because:
- You are watching all bug changes.