Skip to content
Success

Changes

Summary

  1. Explicitly configure ASPs asp-clnt-* as role=asp & sctp-role=client (details)
Commit 7c0bb4e34196913ff46532801b81236b97b3d0bc by Pau Espin Pedrol
Explicitly configure ASPs asp-clnt-* as role=asp & sctp-role=client

Until recently, the asp-clnt-* ASPs, which have specific handling in osmo_sccp_simple_client_on_ss7_id(),
were being always forcedly set to sctp-role CLIENT by code in that
function.
This prevented user of that API from explicitly configuring the ASP as
"sctp-role server" through the VTY as the option would be overwritten silently.

Now, the sctp-role from config is followed if the ASP is
defined/configured through the VTY (not dynamically created at the time
osmo_sccp_simple_client_on_ss7_id() is called).

Since the default for a VTY-specified ASP is to be in "sctp-role
server", the config files need to be updated to properly configure the
ASP to be in "sctp-role client", which is the desired mode here.

Same applies for "role", where the default is SG but it is actually used
as "ASP" here.

Change-Id: Idf84502ffa199926a5f0ee616313b515743811ab
Depends: osmo-ttcn3-hacks.git Change-Id I4eb5b5f6b4b24df079b4c74e2a2e2ebb8769b0bd
The file was modifiedttcn3-sgsn-test/osmo-sgsn.cfg
The file was modifiedosmo-hnbgw-master/osmo-hnbgw.cfg
The file was modifiedttcn3-hnbgw-test/osmo-hnbgw.cfg
The file was modifiedttcn3-hnbgw-test/with-pfcp/osmo-hnbgw.cfg
The file was modifiedosmo-hnbgw-latest/osmo-hnbgw.cfg
The file was modifiedttcn3-smlc-test/osmo-smlc.cfg
The file was modifiedosmo-cn-latest/osmo-msc.cfg
The file was modifiedttcn3-bsc-test/osmo-bsc.cfg
The file was modifiedttcn3-bsc-test-vamos/osmo-bsc.cfg
The file was modifiedttcn3-bsc-test/sccplite/osmo-bsc.cfg
The file was modifiedttcn3-msc-test/osmo-msc.cfg
The file was modifiedosmo-cn-latest/osmo-msc.cfg.base