summaryrefslogtreecommitdiffstats
path: root/ggsn_tests
diff options
context:
space:
mode:
authorPhilipp Maier <pmaier@sysmocom.de>2018-04-11 18:12:23 +0200
committerHarald Welte <laforge@gnumonks.org>2018-04-11 16:50:59 +0000
commitc6e06f76ae5f6f22d5a429d44e14dd1410641cdd (patch)
tree7944244a2541874d44b1a651a4b64928a6d3c0ea /ggsn_tests
parent9f23091dabb930524417d44c6a2b34b1a9abbaec (diff)
MSC_Tests: fix TC_mo_crcx_ran_reject
The testcase intentionally responds to the RAN sided CRCX with a garbeled message to cause the MGCP handlin inside the MSC to fail. The MSC is then expected not to perform further MGCP operations since it did not get a proper response to the first CRCX, so the specific endpoint name is not known, eventually preventing from doing an MDCX. However, the testcase responds to incoming DLCX commands, instead setting the verdict to fail. Also the altstep that dispatches the message after the errornous MGCP response unconditionally catches all BSSAP messages before entering the sub-altstep as_clear_cmd_compl_disc() that handles the clearing of the connection. Eventually the clear command is never received in this sub-altstep. - Make sure the verdict is set to fail when an MGCP message is received after the errornous response to the CRCX. - Remove the unconditional BSSAP.receive in order to be able to dispatch the clear command properly - Update the expected-results.log file Change-Id: I806491741d310e4410f6cb4ce0309235e9bf4300 Related: OS#2882
Diffstat (limited to 'ggsn_tests')
0 files changed, 0 insertions, 0 deletions