https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6741
--- Comment #3 from gsmguy <mail2nitinkalra@xxxxxxxxx> 2012-01-16 10:33:53 PST ---
Hi Anders,
Thanks bunch for the reply. I was hoping to 919120141420f6 as 19024141026 as
MSISDN.
Actually processUnstructuredSS-Request is the message from Ericsson MSC to a
billing application, while unstructuredSS-Request is a message from billing
application to Ericsson MSC.
I think its because of the ASN.1 definition, but if I have to view the packet
correctly then what version of ASN shall I use in wireshark to view the packet
correctely.
Thanks in advance.
BR/
Nitin
(In reply to comment #2)
> Hi,
> In the first trace the problem is with MAP-DialoguePDU Wireshark uses this
> asn1 specification:
>
> MAP-OpenInfo ::= SEQUENCE {
> destinationReference [0] AddressString OPTIONAL,
> originationReference [1] AddressString OPTIONAL,
> ...,
> extensionContainer ExtensionContainer OPTIONAL
> -- extensionContainer must not be used in version 2
> }
>
> If you change the BER preferences to "Show internal BER encapsulation tokens"
> you can see tahat in your trace there is Tag 1
> ...0 0001 = Tag: 1
> Length: 7
> originationReference: 919120140450f3
>
> And Tag 2
> ...0 0010 = Tag: 2
> Length: 7
> BER Error: This field lies beyond the end of the known sequence definition.
> 919120141420f6
>
> As Tag 2 is not present in the ASN1 description abowe.
> Could it be that the tags should have been 0 and 1 instead?
> Tag 2 looks like a number too.
>
> Regards
> Anders
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.