| 
 Hi,  I got a problem about ANSI_MAP ASN.1 compile in
wireshark 1.2.1. In wireshark ansi_map.asn file can’t
complie because it has some problems. At the first, SignalQuality is as below but these are
ranging values in 2.240(p.550-310) of 3GPP2 spec X.S0004-550-E_v2.0_070723. ///////////////////////////////////////////////////////////// Wireshark ansi_map.asn file ///////////////////////////////////////////////////////////// -- 6.5.2.121  -- 1 0 0 0 1 0 1 1 (0x8b)(11) SignalQuality ::= INTEGER{            not-a-usable-signal
(0),            treat-as-Not-a-usable-signal
(1),            treat-as-Not-a-usable-signal
(2),            treat-as-Not-a-usable-signal
(3),            treat-as-Not-a-usable-signal
(4),            treat-as-Not-a-usable-signal
(5),            treat-as-Not-a-usable-signal
(6),            treat-as-Not-a-usable-signal
(7),            treat-as-Not-a-usable-signal
(8),            usable-signal-range
(9),            usable-signal-range
(245),            treat-the-same-as-interference
(246),            treat-the-same-as-interference
(247),            treat-the-same-as-interference
(248),            treat-the-same-as-interference
(249),            treat-the-same-as-interference
(250),            treat-the-same-as-interference
(251),            treat-the-same-as-interference
(252),            treat-the-same-as-interference
(253),            treat-the-same-as-interference
(254),            interference
(255) } (0..255) ///////////////////////////////////////////////////////////// It should be change to like this..Just I guess. ///////////////////////////////////////////////////////////// -- 6.5.2.121  -- 1 0 0 0 1 0 1 1 (0x8b)(11) SignalQuality ::= INTEGER{            not-a-usable-signal
(0),            treat-as-Not-a-usable-signal
(1..8),            usable-signal-range
(9..245),            treat-the-same-as-interference
(246..254),            interference
(255) } (0..255) ---------------------------------------------------------------- And the other problem is TriggerAddressList. It is using a different name but has a same value
to 278 and thus it occurred to compile error. -- 6.5.2.de -- 1 0 1 1 1 1 1 1 (0xbf) -- 1 0 0 0 0 0 1 0 (0x82) -- 0 0 0 1 0 1 0 0 (0x14)(276) TriggerAddressList ::= SET{            triggerList                               [278]
IMPLICIT TriggerList, --         M
6.5.2.dg            triggerListOpt                [278]
IMPLICIT TriggerList OPTIONAL --         O
6.5.2.dg a ---------------------------------------------------------------- Please let me know about how can I complie it. Thanks H.R Choi. From:
Anders Broman [mailto:anders.broman@xxxxxxxxxxxx]  Hi, I don't think it's
possible currently. And I doubt that it's standardised how to do it. Do you have a sample
trace to share so we can see how it's done? Regards Anders From:
wireshark-users-bounces@xxxxxxxxxxxxx
[mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Horyong Choi Hi all, Please let me know that the way of
decode of ANSI MAP in case of SCCP and TCAP is ITU-T spec. Answer me please. Thanks. H.R. Choi  | 
- Prev by Date: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1], RTMP [TCP Retransmission]
 - Next by Date: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
 - Previous by thread: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1], RTMP [TCP Retransmission]
 - Next by thread: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
 - Index(es):