pespin has uploaded this change for review. ( 
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/42128?usp=email )


Change subject: hnbgw: TC_rab_assign_mgcp_to: Allow hnbgw to tear down CN conn 
at SCCP level
......................................................................

hnbgw: TC_rab_assign_mgcp_to: Allow hnbgw to tear down CN conn at SCCP level

Newer versions of osmo-hnbgw will be tearing down the CN conn at SCCP
level by transmitting an RLSD in this scenario, instead of sending a Iu
RANAP Release Request crafted by the osmo-hnbgw itself.
The HNBGW is expected to forward RANAP messages between UE/HNB and CN,
not to generate them.

Related: SYS#7294
Change-Id: Idb062a072c7403442ce981c6c9caeb7effb86554
---
M hnbgw/HNBGW_Tests.ttcn
1 file changed, 6 insertions(+), 3 deletions(-)



  git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks 
refs/changes/28/42128/1

diff --git a/hnbgw/HNBGW_Tests.ttcn b/hnbgw/HNBGW_Tests.ttcn
index f679205..d27a26f 100644
--- a/hnbgw/HNBGW_Tests.ttcn
+++ b/hnbgw/HNBGW_Tests.ttcn
@@ -1230,13 +1230,16 @@
                log("Ignoreing CRCX1", mgcp_cmd);
                repeat;
                }
-       [] RAN_CONN.receive(tr_RANAP_IuReleaseRequest(?)) { }
+       [] RAN_CONN.receive(tr_RANAP_IuReleaseRequest(?)) {
+               f_cn_iu_release_procedure();
+       }
+       [] RAN_CONN.receive(tr_MSC_CONN_PRIM_DISC_IND) {
+               RUA.receive(RUA_Disc_Ind:?);
+       }
        [] T.timeout {
                setverdict(fail, "Timeout waiting for IuRelease");
                }
        }
-
-       f_cn_iu_release_procedure();
 }

 testcase TC_rab_assign_mgcp_to() runs on test_CT {

--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/42128?usp=email
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings?usp=email

Gerrit-MessageType: newchange
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: Idb062a072c7403442ce981c6c9caeb7effb86554
Gerrit-Change-Number: 42128
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <[email protected]>

Reply via email to