https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-07-10T22:17:59ZOpen Source Mobile CommunicationsOsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=45112017-07-10T22:17:59Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed" href="/issues/2351">Bug #2351</a>: unify sccp instance configuration</i> added</li></ul> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=45132017-07-10T22:18:23Zlaforge
<ul><li><strong>Assignee</strong> set to <i>laforge</i></li></ul> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=56842017-10-11T01:17:22Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>laforge</i> to <i>dexter</i></li></ul><p>I think this has long been resolved? We are using M3UA in ASP mode from osmo-bsc and osmo-msc. Please confirm.</p> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=57972017-10-13T13:23:48Zdexter
<ul></ul><p>I am not sure. We never tried it or even thought about it. When I get it correct, this would be a configuration where e.g. two OsmoSTP are connecting to each other. This means that one of them must take the client role. The topology could be something like this:</p>
<pre>
osmo-bsc (ASP) <------> (STP) OsmoSTP (ASP) <------> (STP) OsmoSTP (STP) <------> (ASP) osmo-msc
</pre>
<p>I think this is something we have to test in order to be sure that it really works.</p> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=59642017-10-29T18:33:17Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=158402019-09-04T09:26:43Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>dexter</i> to <i>laforge</i></li></ul> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=161772019-10-08T14:59:06Zlaforge
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Feature</i></li><li><strong>Assignee</strong> changed from <i>laforge</i> to <i>pespin</i></li><li><strong>Priority</strong> changed from <i>Low</i> to <i>Normal</i></li></ul><p>The M3UA protocol defines various roles of M3UA endpoints: SGW, ASP and IPSP.</p>
<p>osmo-stp currently implements only the SGW (Signaling Gateway) role, allowing external M3UA entities in ASP role to connect to it. It does not permit the SGW to operate in ASP role to connect to external SGWs</p>
The implementation of this feature will include
<ol>
<li>Extension of the VTY interface to operate the osmo-stp send of the M3UA link in ASP mode</li>
<li>Extension of the osmo-stp internal implementation to behave accordingly</li>
<li>Implementation of automatic test cases in TTCN-3</li>
</ol> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=163272019-10-29T21:13:35Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> changed from <i>pespin</i> to <i>laforge</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>30</i></li></ul><p>I've made an initial implementation as part of <code>laforge/wip</code>, but it requires thorough testing before pushing for inclusion. There are two new VTY commands for specifying the SCTP role (client / server) and the xUA role (sg / asp).</p> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=163282019-10-29T21:20:13Zlaforge
<ul><li><strong>File</strong> <a href="/attachments/3946">20191029-m3ua_asp_side.pcap</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3946/20191029-m3ua_asp_side.pcap">20191029-m3ua_asp_side.pcap</a> added</li></ul><p>Initial testing shows that the ASP transitions through ASPUP and ASPAC as expected. However, both the ASP and the SG are sending NOTIFY to each other, which is probably not how it's supposed to be. We need to suppress NOTIFY generation if we're not in SG role.</p> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=163292019-10-29T21:30:00Zlaforge
<ul><li><strong>File</strong> <a href="/attachments/3947">20191029-m3ua_asp_side2.pcap</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3947/20191029-m3ua_asp_side2.pcap">20191029-m3ua_asp_side2.pcap</a> added</li><li><strong>% Done</strong> changed from <i>30</i> to <i>60</i></li></ul><p>NOTIFY problem has been fixed. They are now suppressed when operating in ASP role.</p>
<p>Attaching a new pcap file.</p>
<p>The ASP side config looked like this:</p>
<pre>
cs7 instance 0
point-code format 24
asp asp-sender 2905 9999 m3ua
local-ip 127.0.0.1
remote-ip 127.0.0.1
role asp
sctp-role client
as as-sender m3ua
asp asp-sender
routing-key 1023 23
route-table system
update route 23 16777215 linkset as-sender
</pre>
<p>while the SG side looked like that:</p>
<pre>
cs7 instance 0
point-code format 24
asp asp-sender 9999 2905 m3ua
local-ip 127.0.0.1
remote-ip 127.0.0.1
as as-sender m3ua
asp asp-sender
routing-key 1023 23
route-table system
update route 23 16777215 linkset as-sender
listen m3ua 2905
accept-asp-connections dynamic-permitted
</pre>
<p>the routing doesn't yet make sense in the above configs, I'm just pasting them to illustrate how to use the 'role' and 'sctp-role' commands to switch a given section into operating as client/ASP towards another SG.</p> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=163452019-11-05T16:27:09Zlaforge
<ul><li><strong>% Done</strong> changed from <i>60</i> to <i>90</i></li></ul><p>This is implemented in <a class="external" href="https://gerrit.osmocom.org/#/c/libosmo-sccp/+/15974/">https://gerrit.osmocom.org/#/c/libosmo-sccp/+/15974/</a> and <a class="external" href="https://gerrit.osmocom.org/#/c/libosmo-sccp/+/15975/">https://gerrit.osmocom.org/#/c/libosmo-sccp/+/15975/</a> - automatic tests (all passing) are in the <code>laforge/wip</code> branch of osmo-ttcn3-hacks.git.</p>
<p>Once it passes code review, it will be in master.</p> OsmoSTP - Feature #2005: STP: Allow VTY configuration of M3UA ASP sidehttps://osmocom.org/issues/2005?journal_id=164502019-11-13T16:53:06Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul><p>all code / patches in master; tests are executed automatically and pass, see those including <em>clnt</em> in the name at <a class="external" href="https://jenkins.osmocom.org/jenkins/job/ttcn3-stp-test/test_results_analyzer/">https://jenkins.osmocom.org/jenkins/job/ttcn3-stp-test/test_results_analyzer/</a></p>