diff options
| author | Harald Welte <laforge@gnumonks.org> | 2018-05-31 22:17:46 +0200 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2018-06-01 12:00:56 +0200 |
| commit | e32ad992af328bf9a021ac44c5980a6dccb78d19 (patch) | |
| tree | 9d4a03740eab66ff09b309c7c112121895f85858 /library/BSSGP_Emulation.ttcn | |
| parent | d68d2f0c0d05633bdeb2660f31a2c87bb33d752b (diff) | |
*_Emulation.ttcn: Specify destination when replying on procedure ports
procedure ports (like message ports) require us to specify the
destination of a message ("reply") in case it is connected 1:N and not
just 1:1. This didn't show up as a problem so far, as we typically only
had one component talking to those procedure ports at any given point
in time.
Change-Id: I696ec67080815348bb95e43ecbbf262e533e39a3
Diffstat (limited to 'library/BSSGP_Emulation.ttcn')
| -rw-r--r-- | library/BSSGP_Emulation.ttcn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/library/BSSGP_Emulation.ttcn b/library/BSSGP_Emulation.ttcn index 321c344b..38666b80 100644 --- a/library/BSSGP_Emulation.ttcn +++ b/library/BSSGP_Emulation.ttcn @@ -441,15 +441,15 @@ altstep as_allstate() runs on BSSGP_CT { [] BSSGP_PROC.getcall(BSSGP_register_client:{?,?,?}) -> param(imsi, tlli, cell_id) sender vc_conn { f_tbl_client_add(imsi, tlli, cell_id, vc_conn); - BSSGP_PROC.reply(BSSGP_register_client:{imsi, tlli, cell_id}); + BSSGP_PROC.reply(BSSGP_register_client:{imsi, tlli, cell_id}) to vc_conn; } [] BSSGP_PROC.getcall(BSSGP_unregister_client:{?}) -> param(imsi) sender vc_conn { f_tbl_client_del(imsi, vc_conn); - BSSGP_PROC.reply(BSSGP_unregister_client:{imsi}); + BSSGP_PROC.reply(BSSGP_unregister_client:{imsi}) to vc_conn; } [] BSSGP_PROC.getcall(BSSGP_llgmm_assign:{?,?}) -> param(tlli_old, tlli) sender vc_conn { f_tbl_client_llgmm_assign(tlli_old, tlli, vc_conn); - BSSGP_PROC.reply(BSSGP_llgmm_assign:{tlli_old, tlli}); + BSSGP_PROC.reply(BSSGP_llgmm_assign:{tlli_old, tlli}) to vc_conn; } } |