https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092017-07-10T22:17:59ZOpen Source Mobile Communicationslibosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=45122017-07-10T22:17:59Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-2 priority-default closed" href="/issues/2005">Feature #2005</a>: STP: Allow VTY configuration of M3UA ASP side</i> added</li></ul> libosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=45842017-07-17T19:31:17Zdexter
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul> libosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=46942017-07-24T19:40:57Zdexter
<ul><li><strong>% Done</strong> changed from <i>10</i> to <i>70</i></li></ul><p>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: <a class="external" href="https://gerrit.osmocom.org/#/c/3303/">https://gerrit.osmocom.org/#/c/3303/</a></p>
<p>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.</p> libosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=47212017-07-25T08:02:35Zdexter
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-3 priority-high3 closed" href="/issues/2289">Feature #2289</a>: implement AoverIP (OsmoMSC side)</i> added</li></ul> libosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=47512017-07-31T11:05:16Zdexter
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Stalled</i></li></ul><p>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.</p>
<p>The next step would be to select and lock down the commands which are not needed in a client application.</p> libosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=49372017-08-10T16:20:45Zdexter
<ul></ul><p>Todo:</p>
<ul>
<li>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.</li>
<li>doxygen comments for simple client</li>
</ul> libosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=49802017-08-14T20:13:03Zdexter
<ul><li><strong>% Done</strong> changed from <i>70</i> to <i>80</i></li></ul><ul>
<li>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</li>
<li>Doxygen comments for simple client are added</li>
<li>PC of the CS7 instance is checked. If it is invalid. The default setting will be used.</li>
</ul> libosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=51402017-08-21T21:03:11Zdexter
<ul><li><strong>% Done</strong> changed from <i>80</i> to <i>90</i></li></ul><p>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.</p> libosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=52202017-08-28T20:27:42Zdexter
<ul><li><strong>Status</strong> changed from <i>Stalled</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul><p>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.</p> libosmo-sccp + libosmo-sigtran - Bug #2351: unify sccp instance configurationhttps://projects.osmocom.org/issues/2351?journal_id=57212017-10-11T02:53:54Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>