Skip to content
Sign in

Changes

Started by timer
Started 2 mo 23 days ago
Queued 5 ms
Took 2 min 43 sec on build5-deb12build-ansible
RAN_Emulation: Fix error: CLIENT multiple conns requires explicit addressing

Fixes fynamic test error during HNBGW_Tests.TC_sccp_cr_limit:
Dynamic test case error: Port CLIENT has more than one active connections. Message can be sent on it only with explicit addressing.

Related: SYS#7600
Change-Id: Icb038e041bd5e82f95141e1814571d7c7f75878b
library/RAN_Emulation.ttcnpp
Pau Espin Pedrol at
RAN_Emulation: Proper operation indication in RANAP_Connect prim to upper layers

Change-Id: Id39c68a0408fdc90304d8089dd200274eb843a8d
library/RAN_Emulation.ttcnpp hnbgw/ConnHdlr.ttcn
Pau Espin Pedrol at
RAN_Emulation: rename f_handle_userData() -> f_handle_userData_BSSAP()

To match its counterpart f_handle_userData_RANAP().

Change-Id: I9e07cd99d2ca01942aae671175753517d5d40572
library/RAN_Emulation.ttcnpp
Pau Espin Pedrol at
cosmetic: bsc-nat: MSC_Simulation.ttcn: Fix trailing whitespace

Change-Id: Ie80ad827f7024c977ed7895cbc11417b4de20fe5
bsc-nat/MSC_Simulation.ttcn
Pau Espin Pedrol at
RAN_Emulation: Rename RAN_ConnHdlr.BSSAP* ports to RAN_CONN

That port handles a lot more than BSSAP. Naming it BSSAP makes it really
confusing for instance when using it to handle RANAP in the Iu stack.

Change-Id: I75dc5b8b6db912b2eb69311612dbbb0a454374c3
bsc/BSC_Tests_LCLS.ttcn sgsn/BSSGP_ConnHdlr.ttcn bsc-nat/BSC_MS_ConnectionHandler.ttcn hnbgw/ConnHdlr.ttcn msc/MSC_Tests.ttcn msc/MSC_Tests_ASCI.ttcn bsc/BSC_Tests.ttcn msc/BSC_ConnectionHandler.ttcn bsc/BSC_Tests_VAMOS.ttcn bsc-nat/MSC_ConnectionHandler.ttcn sgsn/SGSN_Tests_Iu.ttcn sgsn/SGSN_Tests.ttcn library/RAN_Emulation.ttcnpp bsc/BSC_Tests_ASCI.ttcn hnbgw/HNBGW_Tests.ttcn bsc/MSC_ConnectionHandler.ttcn bsc-nat/BSC_MS_Simulation.ttcn msc/MSC_Tests_Iu.ttcn
Pau Espin Pedrol at
s1gw: correct handling of UE CONTEXT RELEASE REQUEST

By sending a UE CONTEXT RELEASE REQUEST, the eNB is requesting the
MME to terminate the UE context.  This procedure itself does not
terminate the UE context nor the associated E-RABs.  Therefore, the
S1GW should not terminate E-RAB FSMs upon receiving this PDU.

This means that we should not be expecting PFCP sesstion(s)
to be deleted in S1GW_ConnHdlr.f_ConnHdlr_ue_ctx_release_req().

Change-Id: Ibbb6da1f2888995608b980e7479758000e94864e
Related: osmo-s1gw.git If467162e871b7989f0578be30c04d1c32c263c99
Related: SYS#7738, SYS#7599
s1gw/S1GW_ConnHdlr.ttcn
laforge at