Project

General

Profile

Feature #2396

Comfortable CS7/SS7 VTY configuration for osmo-bsc and osmo-msc

Added by dexter over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
OpenBSC
Target version:
-
Start date:
07/24/2017
Due date:
% Done:

100%

Resolution:
fixed
Spec Reference:

Description

osmo-msc and osmo-bsc currently lack important SS7 related VTY configuration features. Add proper VTY configuration commands to both applications


Related issues

Related to OsmoMSC - Feature #2289: implement AoverIP (OsmoMSC side)Closed05/24/2017

History

#1 Updated by dexter over 2 years ago

  • Status changed from New to In Progress

The current status is:

  • osmo-msc: Fully configurable, configuration may even be left out completely. In this case osmo-msc will automatically assume a default configuration.
  • osmo-bsc: Configuration may not be left out. The user must set up a local address. The VTY still has some issues to be fixed. The goal here is to reach a state, where it works without configuring anything, just like it already is with osmo-msc

In order to move on with this properly, we must agree on a a default configuration for each component and on a default environment. The default environment should be the "Everything on one box" situation. Which means the ip-addresses will be all loopback addresses. We also must agree on pointcodes for each application. I would suggest to put this into a header file, but then there is the problem where to put it. libosmo-sccp sounds like a good place. Maybe having it just as a wiki-page is also enough.

#2 Updated by dexter over 2 years ago

  • Tracker changed from Bug to Feature

#3 Updated by dexter over 2 years ago

  • Related to Feature #2289: implement AoverIP (OsmoMSC side) added

#4 Updated by dexter over 2 years ago

osmo-bsc to-do:
  • Do not mix up different addresses from different CS7 instahces (means, local and remote address must come from the same CS7 instance)
  • Use only the msc address to determine the CS7 instance. Using the local address does not make too much sense especially when it is generated automatically from the selected CS7 instance.

#5 Updated by dexter over 2 years ago

We now prevent mixing addresses from different CS7 instances.

#6 Updated by dexter over 2 years ago

neels patches for this are on pmaier/aoip3

#7 Updated by dexter over 2 years ago

  • We now have CS7 default values in osmo-bsc that are complementary to the ones used in osmo-msc. The user may leave out the CS7 configuration completely when all processes are used on the same machine.
  • Fixed pmaier/aoip so that it compiles again with the current master libosmo-sccp.

#8 Updated by dexter over 2 years ago

Todo:
  • It does not make much sense to offer auto configuration for more than one MSC since it is a very rare and unlikely situation => Only allow one instance to be auto configured

Agreed with neels for the following default pointcodes:

MSC: 1.0.0
BSC: 3.0.0
SGSN: 2.0.0
HNBGW: 4.0.0

#9 Updated by laforge over 2 years ago

On Thu, Aug 10, 2017 at 04:24:11PM +0000, dexter [REDMINE] wrote:

Agreed with neels for the following default pointcodes:

MSC: 1.0.0
BSC: 3.0.0
SGSN: 2.0.0
HNBGW: 4.0.0

I don't think it matters much, but normally you would rather change the lower bits than the higher bits.
similar to ip adresses. This allows entire prefixes to be routed/aggregated in the network.

so something like

MSC: 1.23.1
BSC: 1.23.3
SGSN: 1.23.2
HNBGW 1.23.4

would be more "realistic"

#10 Updated by dexter over 2 years ago

  • % Done changed from 50 to 80

...would be more "realistic"

Yes, I think so too. We should use that set of pointcodes.

We still have a bug with osmo-bsc, according to neels the configuration files can not be read back because it prints a "(null)" into the config file during write. Should be simple to fix. Apart from that I think we made good progress with the VTY and the automatic configuration simplifies everything a lot.

#11 Updated by dexter over 2 years ago

  • % Done changed from 80 to 90

The problems with the "(null)" strings are fixed. I think the VTY in terms of CS7/SS7 is pretty much done now. We will see how it performs in real life situations. Maybe there are some things we did not have on the radar yet, we will see. Lets keep this at 90% for now.

Sinde there is a bug in libosmo-sccp that seems to prevent the usage of pointcodes longer than 8 bit (see http://osmocom.org/issues/2441) We use the following default pointcodes now:

MSC A-Interface: 0.23.1
MSC Iu-Interface: 0.23.2
MSC A-Interface+Iu-Interface: 0.23.1
BSC: 0.23.3

#12 Updated by dexter over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

There were no acute problems (other than a minor merge conflict in osmo-msc) with this in the past week. Lets consider this as resolved and add new tasks in case of problems/feature-requests

#13 Updated by laforge about 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)