Bug #2351

unify sccp instance configuration

Added by dexter almost 2 years ago. Updated over 1 year ago.

Target version:
Start date:
Due date:
% Done:


Spec Reference:


The configuration of the sccp instance can be unified. The parameters of osmo_sccp_simple_client() which is used to create the sccp instance could be configured using the built in VTY of libosmo-sccp. This would unify the configuration of SCCP and offload the application specific VTY. It also would help to simplify the configuration from the users perspective. The user will not have to learn a new way to configur SS7 applications all the time.

struct osmo_sccp_instance *
osmo_sccp_simple_client(void *ctx, const char *name, uint32_t pc,
            enum osmo_ss7_asp_protocol prot, int local_port,
            const char *local_ip, int remote_port, const char *remote_ip); 

Related issues

Related to OsmoSTP - Bug #2005: STP: Allow VTY configuration of M3UA ASP sideNew2017-04-10

Related to OsmoMSC - Feature #2289: implement AoverIP (OsmoMSC side)Closed2017-05-24


#1 Updated by laforge almost 2 years ago

  • Related to Bug #2005: STP: Allow VTY configuration of M3UA ASP side added

#2 Updated by dexter almost 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

#3 Updated by dexter over 1 year ago

  • % Done changed from 10 to 70

The simple client is now fully configurable via VTY, while the basic idea here is to use the VTY configuration whenever it is available. If no configuration is detected, the caller provided parameters are used. The patch can be found here:

However, there is still room for improvement. Since it does not make much sense to set routes on a client application we should try to hide this functionality from the user. At the moment setting a default route is only necessary when an AS/ASP configuration is set by the user via VTY. If it is left out, there is no problem. AS/ASP will be created automatically. If the user saves the VTY config, the result will be a valid config with AS, ASP and default route. This can be confusing, so making a good selection of VTY commands and disabling the commands that only make sense in an STP application would be the next step here.

#4 Updated by dexter over 1 year ago

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

#5 Updated by dexter over 1 year ago

  • Status changed from In Progress to Stalled

Its probably best to close this and do the next steps with a separate tasks. But should keep it open that we do not forget about it.

The next step would be to select and lock down the commands which are not needed in a client application.

#6 Updated by dexter over 1 year ago


  • libosmo-sccp now has capabilities to check if the PC of a CS7 instance is set or not, check and use default pc if necessary.
  • doxygen comments for simple client

#7 Updated by dexter over 1 year ago

  • % Done changed from 70 to 80
  • We now create the default route for ASP applications automatically, also the VTY command for creating routes is locked down in ASP mode, so there should be no longer confusion about this
  • Doxygen comments for simple client are added
  • PC of the CS7 instance is checked. If it is invalid. The default setting will be used.

#8 Updated by dexter over 1 year ago

  • % Done changed from 80 to 90

I think this is also pretty much done now. We need to see how the VTY performs in real life. Lets keep this at 90% for now in case there is something to add that we did not thought about yet.

#9 Updated by dexter over 1 year ago

  • Status changed from Stalled to Resolved
  • % Done changed from 90 to 100

There were no acute problems with this in the past week. Lets consider this as resolved and add new tasks in case of problems/feature-requests.

#10 Updated by laforge over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)