Actions
Feature #3872
openosmo_scu_prim.conn_id should be picked from a distinct number space for outgoing and incoming N-CONNECT
Start date:
03/28/2019
Due date:
% Done:
0%
Spec Reference:
Description
Currently, to compose an outgoing N-CONNECT osmo_scu_prim, osmo-bsc iterates currently open SCCP connections and picks an unused conn_id from the list of active conns.
In theory, that is a scoping violation, since an incoming N-CONNECT might choose the same conn_id at the same time.
osmo-bsc should use the new conn_id scoping and osmo_sccp_user_* API asked for in #3871 to invent new outgoing osmo_scu_prim.connect.conn_id.
Related issues
Updated by neels about 5 years ago
- Blocked by Bug #3871: osmo_scu_prim conn_id should be scoped per-user and direction, and should not correlate with the local-reference spoken on the SCCP wire added
Actions