https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092019-03-21T02:17:55ZOpen Source Mobile CommunicationsOsmoSTP - Bug #3838: connecting two BSCs to OsmoSTP will both end up with the same routing keyhttps://projects.osmocom.org/issues/3838?journal_id=136072019-03-21T02:17:55Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> changed from <i>neels</i> to <i>laforge</i></li></ul><p>I actually had explicit routing keys in the .cfg files.</p>
<p>This comes from the need to configure distinct point-codes for the two BSC.<br />We actually still lack a similar section in the osmo-bsc manual, but looking at the osmo-msc manual section 5.4.1:</p>
<pre>
A full configuration needs an asp on an as — an Application Server Process running on an Application Server — as well as a
local point code and routing configuration. The SCCP VTY automatically creates those parts that are missing, by assuming sane
defaults. A complete configuration would look like this:
cs7 instance 0
point-code 0.23.1
asp my-OsmoMSC-A-Iu 2905 0 m3ua
remote-ip 127.0.0.1
as my-as-for-OsmoMSC-A-Iu m3ua
asp my-OsmoMSC-A-Iu
routing-key 0 0.23.1
</pre>
<p>i.e. for some weird reason the local point-code apparently needs to be repeated in the AS config.<br />Even though I probably wrote the manual for this, I can't claim to understand any of this config in detail.<br />This cfg shown in the manual probably came from the 'show running-config' output.</p>
<p>I just checked, I cannot just drop the 'routing-key' line, the result is that both BSCs constantly go through their RESET cycle, and neither of them ever receive a RESET ACK.</p>
<p>What works though is that I completely drop the entire 'as' section in both osmo-bsc cfgs,<br />then the point-code configured on top gets applied to the 'as' auto config, and things work out fine.</p>
<p>What I still wonder, what if a user for whatever reason wants to manually configure an 'as',<br />it then seems impossible to still use automatic RKM?</p>
<p>To summarize:</p>
<ul>
<li>a config fix is to drop the 'as' section from 'cs7',</li>
<li>the osmo-msc manual needs fixing,</li>
<li>the osmo-bsc manual needs a cs7 configuration section in the first place.</li>
</ul> OsmoSTP - Bug #3838: connecting two BSCs to OsmoSTP will both end up with the same routing keyhttps://projects.osmocom.org/issues/3838?journal_id=187132020-06-13T18:13:40Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>laforge</i> to <i>neels</i></li></ul><p>not quite sure what kind of feedback you were expecting here. I think all your observations are correct, nothing to add from my side.</p> OsmoSTP - Bug #3838: connecting two BSCs to OsmoSTP will both end up with the same routing keyhttps://projects.osmocom.org/issues/3838?journal_id=193832020-08-17T14:55:09Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Rejected</i></li></ul><p>we refactored osmo-bsc's SCCP link establishment in the meantime.<br />Let's close this and re-raise an issue if this comes up again</p>