aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2016-11-12 13:31:10 +0100
committerPascal Quantin <pascal.quantin@gmail.com>2016-11-12 12:41:50 +0000
commitb085a2379aa61dbf90381acfff286f36f95e9794 (patch)
tree0ad68cbbe9342e99e407d01de3fe8b6f7256e0af
parent54c3df86f31e05fa8444daddce332d4ad7802173 (diff)
gsm_abis_om2000: Expand bit-width of CON CCP and CI fields
It seems more recent RBS2000 models have extended the range of the CON Connection Point (CCP) by one bit, as I'm seeing CCP 1896 in protocol traces. Similarly, the Contiguity Index can at least reach 96. Using the full 8bit value to make sure IS and CON dissectors use the same ranges for connection points and contiguity index. Change-Id: Iece34106fc97a11dc8a01cf2578b5e4245a4c9e8 Reviewed-on: https://code.wireshark.org/review/18753 Reviewed-by: Pascal Quantin <pascal.quantin@gmail.com>
-rw-r--r--epan/dissectors/packet-gsm_abis_om2000.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/epan/dissectors/packet-gsm_abis_om2000.c b/epan/dissectors/packet-gsm_abis_om2000.c
index 5c479826e9..000a8f6ed7 100644
--- a/epan/dissectors/packet-gsm_abis_om2000.c
+++ b/epan/dissectors/packet-gsm_abis_om2000.c
@@ -1564,12 +1564,12 @@ proto_register_abis_om2000(void)
},
{ &hf_om2k_conl_ccp,
{ "CON Connection Point", "gsm_abis_om2000.con_list.cpp",
- FT_UINT16, BASE_DEC, NULL, 0x3ff,
+ FT_UINT16, BASE_DEC, NULL, 0x7ff,
NULL, HFILL }
},
{ &hf_om2k_conl_ci,
{ "Contiguity Index", "gsm_abis_om2000.con_list.ci",
- FT_UINT8, BASE_DEC, NULL, 0x7,
+ FT_UINT8, BASE_DEC, NULL, 0,
NULL, HFILL }
},
{ &hf_om2k_conl_tag,