https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-01-22T01:35:17ZOpen Source Mobile CommunicationsOsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=72062018-01-22T01:35:17Zlaforge
<ul><li><strong>Precedes</strong> <i><a class="issue tracker-1 status-5 priority-3 priority-high3 closed behind-schedule" href="/issues/2857">Bug #2857</a>: No automatic testing of IuPS interface</i> added</li></ul> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=72082018-01-22T01:38:17Zlaforge
<ul><li><strong>Precedes</strong> <i><a class="issue tracker-1 status-3 priority-1 priority-lowest closed behind-schedule" href="/issues/2858">Bug #2858</a>: No automatic testing of Iuh interface</i> added</li></ul> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=73672018-01-30T16:38:59Zlaforge
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul><p>I've done some initial investigation + trials, and I could successfully compile the RANAP, RUA and HNBAP asn sources (taken from wireshark.git/dissectors/epan/asn/) using ttcn3_makefilegen. The result is some rather large C++ and even larger object files.</p>
<p>What's missing to complete the chain now is to link this code against libosmo-iu and the glue code for the BER<->APER transcoding</p> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=96622018-05-30T15:00:42Zlaforge
<ul><li><strong>Tags</strong> set to <i>TTCN3, 3G</i></li></ul> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=139742019-04-15T09:50:52Zlaforge
<ul><li><strong>Category</strong> set to <i>IuCS support</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>10</i> to <i>20</i></li></ul><p>I have RANAP encoding/decoding now working in TTCN-3, and I've also created a set of RANAP templates to use. Integration into the MSC test suite via RAN_Emulation.ttcn is currently ongoing.</p> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=139992019-04-15T20:17:36Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Stalled</i></li></ul><p>The core RANAP integration, the templates etc. appear to be working. The problem is that due to bugs in the proprietary asn1 compiler we're not able to reliably transcode between BER and APER at this point. setting to stalled again.</p> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=140702019-04-20T20:51:07Zlaforge
<ul><li><strong>File</strong> <a href="/attachments/3658">iucs-auth-ttcn.pcap</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3658/iucs-auth-ttcn.pcap">iucs-auth-ttcn.pcap</a> added</li><li><strong>Status</strong> changed from <i>Stalled</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>20</i> to <i>30</i></li></ul><p>an update including related fixes of the asn1 compiler was released. I'm at the point where withe very little hacks to MSC_Tests.ttcn I can get LU/auth dialogue between simulated RNC and OSmoMSC going, see attached pcap file.</p>
<p>It seems any fundamental ASN.1 related issues have been resolved, and libfftranscode is working as expected.</p>
<p>I'll clean up the code and work on more test integration shortly.</p> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=140712019-04-20T20:52:08Zlaforge
<ul></ul><p>some initial tests already uncovered some bugs, see <a class="external" href="https://gerrit.osmocom.org/#/c/osmo-iuh/+/13722/">https://gerrit.osmocom.org/#/c/osmo-iuh/+/13722/</a> and <a class="external" href="https://gerrit.osmocom.org/#/c/osmo-iuh/+/13721/">https://gerrit.osmocom.org/#/c/osmo-iuh/+/13721/</a></p> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=140732019-04-21T10:34:30Zlaforge
<ul></ul><p>There are now packages of a working APER <-> BER tranascoder available from <a class="external" href="http://ftp.osmocom.org/binaries/libfftranscode/">http://ftp.osmocom.org/binaries/libfftranscode/</a> - the packages are for debian9 x86_64, which is what we use in or docker containers.</p> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=140832019-04-22T20:24:31Zlaforge
<ul><li><strong>% Done</strong> changed from <i>30</i> to <i>60</i></li></ul><p>libfftranscode is integrated in our docker builds. On my system locally I've already been running a number of IuCS TTCN3 tests. Will push them to gerrit once they have received more testing.</p> OsmoMSC - Bug #2856: No automatic testing of IuCS interfacehttps://osmocom.org/issues/2856?journal_id=142182019-05-05T16:06:07Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>60</i> to <i>100</i></li></ul><p>MSC Iu tests are now active in jenkins. Most of them fail due to <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: OsmoMSC doesn't close SCCP connection after successful LU over IuCS (Resolved)" href="https://osmocom.org/issues/3948">#3948</a>, but this issue is about "not automatic testing" which is resolved, even if the testing results in 'fail'.</p>