diff options
author | Philipp Maier <pmaier@sysmocom.de> | 2017-07-21 18:38:36 +0200 |
---|---|---|
committer | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2017-07-22 16:25:24 +0200 |
commit | d8a6e0640246cf34f44979ebef91f25cb1c3c650 (patch) | |
tree | a089f08894a7f1fb9477e5ff8e1e7f6c060e6255 /openbsc/tests/msc_vlr/msc_vlr_test_gsm_ciph.err | |
parent | f558587cc65c09a42e30c8e357d591e29b0cc6b9 (diff) |
vty: Fixup sccp/ss7 configuration
The sccp/ss7 configuration is now fixed. The cs7 instance id is
implicitly detected from the bsc_addr or the msc_addr. Depending
on what is listed last. (I am not sure if that is wise, maybe
we should only use the local/bsc address to do the lookup).
Remove cs7-instance vty command
Modify VTY commands, so that the fixed API is used
Set msc->a.cs7_instance from the VTY to when msc/bsc addr is parsed
Fix the initalization to use osmo_sccp_simple_client_on_ss7_id() and
pass the cs7-instance id we determined from the vty.
The whole thing is not waterproof yet. We are still not at the
point where we allow to leave the local address out. This would
be fine, but when it is left out, the only way to determine the
cs7 instance is to use the msc_addr then.
We also might want to make sure to reach a state where all cs7
related config may be left out (like with the MSC)
Diffstat (limited to 'openbsc/tests/msc_vlr/msc_vlr_test_gsm_ciph.err')
0 files changed, 0 insertions, 0 deletions