*_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
diff --git a/library/BSSGP_Emulation.ttcn b/library/BSSGP_Emulation.ttcn
index 321c344..38666b8 100644
--- a/library/BSSGP_Emulation.ttcn
+++ b/library/BSSGP_Emulation.ttcn
@@ -441,15 +441,15 @@
[] 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;
}
}