Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092023-11-06T13:48:35ZOpen Source Mobile Communications
Redmine OCTOI - Osmocom Community TDM over IP - Feature #6246 (New): co-locate cisco 2811 for FrameRelay...https://osmocom.org/issues/62462023-11-06T13:48:35Zlaforge
<p>let's put a Cisco 2811 into the co-location, ideally with support for both X.25 as well as FrameRelay.</p>
<p>The idea would be to use it as basis for interop testing any Linux/FOSS work on X.25/framerelay routing/switching that would happen on the OCTOI hub.</p> OsmoMSC - Bug #6207 (Feedback): "MO SMS without prior CM Service Request" for every SMS in 4Ghttps://osmocom.org/issues/62072023-10-05T14:21:26Zosmith
<p>With 4G over the RBS6402, OsmoMSC logs the following error for every SMS:</p>
<blockquote>
<p>MO SMS without prior CM Service Request</p>
</blockquote>
<p>The SMS arrives successfully though.</p>
<p>CC: <a class="user active" href="https://osmocom.org/users/91">neels</a></p>
<p>EDIT: 4G, not 3G</p> OsmoSGSN - Bug #6197 (Feedback): "Cannot handle SM for unknown MM CTX"https://osmocom.org/issues/61972023-09-28T14:32:29Zfixeria
<p>I am observing relatively long PDP Context activation with Sony Ericsson K800i and recent osmo-sgsn:</p>
<p>osmo-sgsn 1.11.0<br />osmo-pcu 1.3.1.1-c1b0</p>
<p>I don't remember if this was the case before, most likely not.</p>
<p>As can be seen from the attached PCAP, the MS orders a PDP Context activation right after completing the Attach (frame 259):</p>
<pre>
130 16.160906108 127.0.0.1 → 127.0.0.1 GPRS-LLC 107 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 0(DTAP) (GMM) Attach Request
156 16.161190149 127.0.0.1 → 127.0.0.1 GPRS-LLC 86 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 0(DTAP) (GMM) Identity Request
157 16.797408334 127.0.0.1 → 127.0.0.1 GPRS-LLC 86 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 1(DTAP) (GMM) Identity Response
173 16.797533278 127.0.0.1 → 127.0.0.1 GPRS-LLC 86 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 1(DTAP) (GMM) Identity Request
181 17.200282825 127.0.0.1 → 127.0.0.1 GPRS-LLC 86 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 2(DTAP) (GMM) Identity Response
226 17.225222456 127.0.0.1 → 127.0.0.1 GPRS-LLC 113 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 2(DTAP) (GMM) Attach Accept
239 17.697504097 127.0.0.1 → 127.0.0.1 GPRS-LLC 77 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 3(DTAP) (GMM) Attach Complete
259 17.739056217 127.0.0.1 → 127.0.0.1 GPRS-LLC 136 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 4(DTAP) (SM) Activate PDP Context Request <-- (!)
274 17.739270297 127.0.0.1 → 127.0.0.1 GPRS-LLC 76 SAPI: LLGMM, U, XID
275 17.739280476 127.0.0.1 → 127.0.0.1 GPRS-LLC 75 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 0(DTAP) (GMM) Detach Request <-- (!)
</pre>
<p>The SGSN is responding with GMM Detach Request (frame 275), here is the related logging:</p>
<pre>
259 17.739056217 127.0.0.1 → 127.0.0.1 GPRS-LLC 136 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 4(DTAP) (SM) Activate PDP Context Request
260 17.739109847 127.0.0.1 → 127.0.5.1 GSMTAP 180 NSE(00101)-NSVC(00101) Rx NS-UNITDATA
261 17.739128332 127.0.0.1 → 127.0.5.1 GSMTAP 263 GPRS-NS2-VC(UDP-NSE00101-NSVC00101-0_0_0_0:23000-127_0_0_1:23023)[0x55e69ba253d0]{UNBLOCKED}: Received Event RX-UNITDATA
262 17.739139873 127.0.0.1 → 127.0.5.1 GSMTAP 180 NSE(00101)-NSVC(00101) Rx NS-UNITDATA
263 17.739148439 127.0.0.1 → 127.0.5.1 GSMTAP 183 BSSGP TLLI=0x85c79efb Rx UPLINK-UNITDATA
264 17.739181411 127.0.0.1 → 127.0.5.1 GSMTAP 236 LLME(ffffffff/85c79efb){UNASSIGNED} LLC RX: unknown TLLI 0x85c79efb, creating LLME on the fly
265 17.739188394 127.0.0.1 → 127.0.5.1 GSMTAP 193 LLC SAPI=1 C U GEA0 IOV-UI=0x000000 FCS=0x3ef88c
266 17.739193033 127.0.0.1 → 127.0.5.1 GSMTAP 149 CMD=UI
267 17.739196720 127.0.0.1 → 127.0.5.1 GSMTAP 147 DATA
268 17.739200627 127.0.0.1 → 127.0.5.1 GSMTAP 143
269 17.739212048 127.0.0.1 → 127.0.5.1 GSMTAP 214 LLME(ffffffff/85c79efb){UNASSIGNED} Cannot handle SM for unknown MM CTX
270 17.739224792 127.0.0.1 → 127.0.5.1 GSMTAP 198 LLME(ffffffff/85c79efb){UNASSIGNED} LLGM Reset (SAPI=1)
271 17.739243207 127.0.0.1 → 127.0.5.1 GSMTAP 180 NSE(00101)-NSVC(00101) Tx NS-UNITDATA
272 17.739252294 127.0.0.1 → 127.0.5.1 GSMTAP 215 <- GMM DETACH REQ (type: re-attach required, cause: Implicitly detached)
273 17.739257293 127.0.0.1 → 127.0.5.1 GSMTAP 180 NSE(00101)-NSVC(00101) Tx NS-UNITDATA
274 17.739270297 127.0.0.1 → 127.0.0.1 GPRS-LLC 76 SAPI: LLGMM, U, XID
275 17.739280476 127.0.0.1 → 127.0.0.1 GPRS-LLC 75 SAPI: LLGMM, UI, protected, non-ciphered information, N(U) = 0(DTAP) (GMM) Detach Request
</pre>
<p>The MS repeats the request again (frame 517) 30 seconds after the first attempt, and finally gets a PDP Context activated.<br />The key difference between frames 259 (first attempt) and 517 (second attempt) is TLLI indicated in the BSSGP header.</p> pySim - Feature #6092 (New): "export" suport for ARA-Mhttps://osmocom.org/issues/60922023-07-10T18:47:34Zlaforge
<p>right now the "export" command is focussed around exporting files present in the file system hierarchy of the MF, as well as the various ADFs.</p>
<p>However, there are applications like ARA-M, which have data stored outside of the filesystem. So we should probably introduce an <code>export(self)</code> method within the <code>CardApplication</code> class. If that method is present, use this to export, and fall back to the filesystem for all others.</p>
<p>This way the ARA-M <code>CardApplication</code> could implement a custom method for doing the equivalent of the <code>aram_get_all</code> vty command. However, that wouldn't by itself be something that can be executed when the "export" text is re-run as a script by pySim-shell. For that to work we'd have to export different aram_* vty commands depending on the data we are reading from aram_get_all.</p> OsmoPCU - Feature #5833 (New): A "meas-feed" for osmo-pcuhttps://osmocom.org/issues/58332022-12-18T18:32:10Zkeith
<p>It might be interesting to observe real-time display of some parameters available from the PCU;<br />such as:</p>
<ul>
<li>RSSI </li>
<li>Link Quality</li>
<li>Coding Scheme</li>
<li>DL Throughput.</li>
</ul>
<p>This could be integrated into the "meas web" app<sup><a href="#fn1">1</a></sup>.</p>
<p>[1] <a class="external" href="https://gitlab.tic-ac.org/keith/meas_web">https://gitlab.tic-ac.org/keith/meas_web</a></p> OCTOI - Osmocom Community TDM over IP - Feature #5526 (New): ability to generate GSMTAP traces fr...https://osmocom.org/issues/55262022-04-12T12:08:36Zlaforge
<p>In a typical setup, where icE1usb + osmo-e1d are used to connect some PBX or other PRI capable equipment, it would be nice if osmo-e1d could be used to generate signaling protocol traces.</p>
This would work as follows:
<ul>
<li>some VTY command to create a GSMTAP source</li>
<li>some VTY command to create software HLDC decoder instances (always in pairs for Rx+Tx) on specific timeslots of specific lines</li>
</ul>
<p>GSMTAP source and software HDLC are available in libosmocore, they just need to be hooked up accordingly</p> gr-osmosdr - Bug #5448 (New): a bug related to gqrx using gr-osmosdr for sdrplay rsp1 through soa...https://osmocom.org/issues/54482022-02-09T02:56:35Zagerasageras@tutanota.com
<p>There is a bug in gqrx with sdrplay rsp1 that it probably has to do with gr-osmosdr.<br />i have posted the issue on gqrx github <a class="external" href="https://github.com/gqrx-sdr/gqrx/issues/970">https://github.com/gqrx-sdr/gqrx/issues/970</a><br />and came in to the conclusion the it is probably on gr-osmosdr.</p>
<p>I use arch linux and the same problem consists for a year or more.<br />I am using gqrx v2.15.2-20-gdadc20b and gr-osmosdr 0.2.3-8.</p>
<p>In gqrx the input rate is only 0.2 MHz available in the 5, 6, 8 MHz, or whatever rate i choose.<br />It renders all the 8 MHz as an example but all of it is noise only for a 0.2 MHz hump in the middle.<br />Everything out of the hump is muted, you can only receive signal in the middle of the hump.</p>
<p>Every other software that i use through soapy has no problem but it is not through gr-osmosdr.</p> SIMtrace 2 - Bug #5423 (New): "trace" firmware continuous test setuphttps://osmocom.org/issues/54232022-01-27T12:24:54Zlaforge
<p>Similar to <code>cardem</code> in <a class="issue tracker-2 status-2 priority-2 priority-default" title="Feature: "cardem" continuous testing setup (In Progress)" href="https://osmocom.org/issues/5422">#5422</a>, we should also create a continuous test setup for passing SIM protocol tracing. The IUT is the simtrace2 firmware.</p>
<p>We can use diffeent modems / CCID readers accessing a SIM card via a SIMtrace2 device while tracing the communication.</p> E1/T1 Hardware Interface (including icE1usb) - Bug #5382 (New): icE1usb: detect all-1 pattern an...https://osmocom.org/issues/53822022-01-02T12:17:29Zlaforge
<p>This applies to both DAHDI and e1d.</p> osmo-lab-rack - Feature #5372 (New): AC power supplyhttps://osmocom.org/issues/53722021-12-23T18:33:30Zlaforge
<p>It would be nice to have a component carrier mouted AC/DC converter for 5V or even dual-rail 5V+12V.</p>
<p>There are products on the market, but only for pricing of 200 EUR or the like, which is slightly overpriced for most use cases.</p> OsmoCBC - Feature #4944 (New): 3G SABP support in OsmoCBChttps://osmocom.org/issues/49442021-01-13T09:09:23Zlaforge
<p>Currently, OsmoCBC only supports 2G/GSM using the CBSP protocol.</p>
<p>This ticket is about supporting 3G/UMTS support via the SABP protocol towards the RNC/HNB-GW</p> osmo-clock-gen - Bug #4814 (New): alignment of DC barrel with face platehttps://osmocom.org/issues/48142020-10-16T17:30:40Zlaforge
<p>Check if <a class="issue tracker-2 status-1 priority-1 priority-lowest" title="Feature: alignment of DC barrel with face plate (New)" href="https://osmocom.org/issues/4809">#4809</a> also applies here.</p> osmo-ccid-firmware - Feature #4806 (New): Add support of T=1?https://osmocom.org/issues/48062020-10-14T09:26:43Zrousseau
<p>The sysmoOCTSIM reader does support only the T=0 protocol as indicated in the USB CCID descriptor:<br /> dwProtocols: 0x0000 0x0001<br /> T=0</p>
<p>Maybe it can be easy to add support of T=1 protocol?<br />The reader works in TPDU mode so a lot of the T=1 work is done by the CCID driver on the host.</p>
<p>I do not have a real use case for T=1 myself. So this issue importance is minor.</p>
<p>I think that is the first time I have a reader (in which you can insert the card I want) that supports only T=0 cards.</p>
<p>You can see a list of readers that support only T=0 at <a class="external" href="https://ccid.apdu.fr/select_readers/?dwProtocols=1">https://ccid.apdu.fr/select_readers/?dwProtocols=1</a><br />But all/most of them are tokens so the T=0 card is embedded and can't be replaced by a T=1 card.</p> OsmoBSC - Bug #4614 (Stalled): "bogus channel load sample" when using BS-11, Nokia or Ericsson BTShttps://osmocom.org/issues/46142020-06-15T13:47:09Zlaforge
<pre>
Mon Jun 15 15:36:12 2020 DRLL chan_alloc.c:208 (bts=0) bogus channel load sample (used=0 / total=0)
Mon Jun 15 15:36:13 2020 DRLL chan_alloc.c:208 (bts=0) bogus channel load sample (used=0 / total=0)
</pre>
<p>Also, interestingly:<br /><pre>
OsmoBSC> show trx
TRX 0 of BTS 0 is on ARFCN 121
Description: (null)
RF Nominal Power: 24 dBm, reduced by 0 dB, resulting BS power: 24 dBm
NM State: Oper 'NULL', Admin 'Unlocked', Avail 'Power off'
RSL State: connected
Baseband Transceiver NM State: Oper 'NULL', Admin 'unknown 0x0', Avail 'Power off'
E1 Signalling Link:
E1 Line 2, Type dahdi: Timeslot 1, Mode RSL
E1 TEI 1, SAPI 0
</pre></p>
<p>I think the problem is that the Siemens BS-11 MO structure is quite unlike what TS 12.21 describes, so the baseband transceiver object is simply never initialized.</p>
<p>The " OC=<abbr title="a5">SIEMENSHW</abbr> INST=(03,00,00)" might be can idea?</p> libosmo-sccp + libosmo-sigtran - Feature #4608 (New): "action" commands to interactively shutdown...https://osmocom.org/issues/46082020-06-10T13:12:24Zlaforge
<p>would be great to do that, especially for testing/debugging.</p> Cellular Network Infrastructure - Feature #4587 (New): Add port numbers to /etc/services during i...https://osmocom.org/issues/45872020-06-06T09:40:54Zlaforge
<p>I think it would be great if we'd add the <code>/etc/services</code> snippet from <a class="wiki-page" href="https://osmocom.org/projects/cellular-infrastructure/wiki/Port_Numbers#etcservices">Port_Numbers</a> to /etc/services during the installation. This enables people to do <code>telnet localhost osm-msc</code> or the like, without having to memorize port numbers all the time.</p>
<p>It's a bit ugly as there is no /etc/services.d or the like, so we have to add/patch the services to the file.</p>
In order to do that reasonable, the related postinst script should (for each service)
<ul>
<li>check if the entry already exists, and do nothing if it does</li>
<li>append the entry to the end of the file, if no entry exists yet</li>
</ul>
<p>We could do this in bulk from libosmocore, or we could add/remove each individual line for each program we install from the respective osmo-* package.</p>
<p>The alternative would be to ship something like an 'osmo-telnet' client program that would have compile-time knowledge about the port numbers. As we already maintain a fork of libtelnet.git on osmocom.org, that may be an option...</p> OsmoHNBGW - Feature #4128 (New): Add support of Huawei hNodeB protocolhttps://osmocom.org/issues/41282019-07-24T15:39:58Zcopslock
<p>Hello developers,the osmo-HNBGW works great with the 3GPP standard femtocells which implemented the HNBAP&RUA protocol,thank you very much,but as Welte said it's somehow dfficult to find some not "lock-down" hNodeB devices,such devices like the ip.access nano3g s8 is really hard to get one even not care about the price nowadays,but the Huawei's old brother ePico3801B variant is somehow easy to get one from some online platform with pretty reasonable price.</p>
<p>I know you guys may not want to waste time on some proprietary blobs that even hard to get one in Europe,but after some reverse-engineering work and according to datasheet from Huawei,it showed that the RUA was replaced with SPUA,and the HNBAP was replaced with APM protocol.And it seems likes Huawei used the commercial NodeB source code and add some sccp-proxy to convert the standard SCCP signaling into SPUA protocol which possible actually implemented the RUA protocol(rua.c source file compiled),and the structure of SPUA signaling is somehow similar with the RUA signaling types,but the APM protocol is completely different compare to the simple HNBAP protocol.<br />All in all,it will be pretty nice to support these protocols,if anyone need some hardware to analyse,i can send one for free,:)</p>
<p>The <strong>SPUA</strong> proxy calls<br /><code>[Sccppry_SpuaPDUType]: Invalid Msg type ucMsgClass = %u<br />[Sccppry_InitTemplate]: gpSpuaConnReq is Null Ptr\r\n <br />[Sccppry_InitTemplate]: gpSpuaConnConf is Null Ptr \r\n <br />[Sccppry_InitTemplate]: gpSpuaDisConnReq is Null Ptr \r\n <br />[Sccppry_InitTemplate]: gpSpuaData is Null Ptr \r\n <br />[Sccppry_InitTemplate]: gpSpuaSsnState is Null Ptr \r\n <br />[Sccppry_InitTemplate]: gpSpuaResCheckReq is Null Ptr \r\n <br />[Sccppry_InitTemplate]: gpSpuaResRelReq is Null Ptr \r\n <br />[Sccppry_InitTemplate]: gpSpuaUnitData is Null Ptr \r\n <br />[Sccppry_HandleSpuaMsg]ulAssocId %u, usStream:%u, ulSlNum:%u, recieve %u bytes data.\n<br />[Sccppry_HandleSpuaMsg]: ucMSGType = %u\r\n<br />[Sccppry_HandleSpuaMsg]: Bad MsgType = %u\r\n<br />[Sccppry_HandleSpuaMsg]: Err Code = %u \r\n<br />[Sccppry_SpuaLnkUpInd]: SctpApiSend Fail ulRet = %u \r\n<br />[Sccppry_SpuaLnkUpAck]: SPUA Msg Len = %u. \r\n<br />[Sccppry_SpuaLnkUpAck]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u. \r\n<br />[Sccppry_SpuaLnkUpAck]: ucDlgReason = %u. \r\n<br />[Sccppry_SpuaLnkUpAck]: ulApId = %u. \r\n<br />[Sccppry_SpuaLnkUpAck]: ucLnkAdmission = %u. \r\n<br />[Sccppry_SpuaLnkUpAck]: SPUA_IE_TIME :%u-%u-%u<br />[Sccppry_SpuaLnkUpAck]: OmSetCurrentTime Fail, ulRslt = %u \r\n<br />[Sccppry_SpuaLnkUpAck]: SctpApiShutdown Fail, ulRet = %u \r\n<br />[Sccppry_SpuaLnkUpAck]: Update Eiu State Fail, ulRet = %u , Connect to next AG.\r\n<br />[Sccppry_SpuaLnkUpAck]: AG Auth: %u(1:Yes, 0:No), AP Auth: %u(1:Yes, 0:No). \r\n<br />[Sccppry_SpuaLnkUpAck]: Update Eiu State Fail, ulRet = %u, Needn't Auth. \r\n<br />[Sccppry_SpuaSIGStateInd]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaSIGStateInd]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaSIGStateInd]: ucSigpointStatus = %u\r\n<br />[Sccppry_SpuaSIGStateInd]: ulSigPoint = %u\r\n<br />[Sccppry_SpuaSSNStateConf]: Sctp Send data Fail, ulRet =\r\n<br />[Sccppry_SpuaSSNStateInd]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaSSNStateInd]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaResCheckReq]: ucAffectedSubsystem = %u\r\n<br />[Sccppry_SpuaResCheckReq]: ucEnStatus = %u\r\n<br />[Sccppry_SpuaSSNStateTest]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaSSNStateTest]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaResCheckReq]: ucAffectedSSN = %u\r\n<br />[Sccppry_SpuaResCheckReq]: ulAffectedSigPoint = %u\r\n<br />[Sccppry_SpuaResCheckReq]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaResCheckReq]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaResCheckReq]: ulMappingConnectId = %u\r\n<br />[Sccppry_SpuaResCheckReq]: ulUserConnectId = %u\r\n<br />[Sccppry_SpuaResRelReq]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaResRelReq]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaUnitDataTrans]: ulUserConnectId = %u\r\n<br />[Sccppry_SpuaUnitDataTrans]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaUnitDataTrans]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaUnitDataTrans]: ucReturnReason = %u\r\n<br />[Sccppry_SpuaUnitDataTrans]: ucSequenceCtrl = %u\r\n<br />[Sccppry_SpuaUnitDataTrans]: ucImportance = %u\r\n<br />[Sccppry_SpuaUnitDataTrans]: usDataLen = %u\r\n<br />[Sccppry_SpuaNoticeInd]: In Sccppry_SpuaNoticeInd\r\n<br />[Sccppry_SpuaConnectReq]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaConnectReq]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaConnectReq]: ulMappingConnectId = %u\r\n<br />[Sccppry_SpuaConnectReq]: ucProtocalType = %u\r\n<br />[Sccppry_SpuaConnectReq]: ulWindowSize = %u\r\n<br />[Sccppry_SpuaConnectReq]: ucExp = %u\r\n<br />[Sccppry_SpuaConnectReq]: ucImportance = %u\r\n<br />[Sccppry_SpuaConnectReq]: usDataLen = %u\r\n<br />\\[Sccppry_SpuaConnectConf]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaConnectConf]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaConnectConf]: ulMappingConnectId = %u\r\n<br />[Sccppry_SpuaConnectConf]: ulUserConnectId = %u\r\n<br />[Sccppry_SpuaConnectConf]: ucProtocalType = %u\r\n<br />[Sccppry_SpuaConnectConf]: ulWindowSize = %u\r\n<br />[Sccppry_SpuaConnectConf]: ucExp = %u\r\n<br />[Sccppry_SpuaConnectConf]: ucImportance = %u\r\n<br />[Sccppry_SpuaConnectConf]: usDataLen = %u\r\n<br />[Sccppry_SpuaDisConnectReq]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaDisConnectReq]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaDisConnectReq]: ulUserConnectId = %u\r\n<br />[Sccppry_SpuaDisConnectReq]: ucOriginator = %u\r\n<br />[Sccppry_SpuaDisConnectReq]: ucReason = %u\r\n<br />[Sccppry_SpuaDisConnectReq]: ucImportance = %u\r\n<br />[Sccppry_SpuaDisConnectReq]: usDataLen = %u\r\n<br />[Sccppry_SpuaDataTransfer]: SPUA Msg Len = %u\r\n<br />[Sccppry_SpuaDataTransfer]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaDataTransfer]: ulUserConnectId = %u\r\n<br />[Sccppry_SpuaDataTransfer]: ucImportance = %u\r\n<br />[Sccppry_SpuaDataTransfer]: usDataLen = %u\r\n<br />[Sccppry_SpuaUdpMulCapInd]: SctpApiSend Fail ulRet = %u \r\n<br />[Sccppry_SpuaUdpMulCapInd]: Start ghtMulFunIndTimer Fail \r\n<br />[Sccppry_SpuaUdpMulCapAck]: Stop ghtMulFunIndTimer Fail \r\n<br />[Sccppry_SpuaUdpMulCapAck]: ucMsgType = %u, usProMsgLen = %u, usMsgLen = %u\r\n<br />[Sccppry_SpuaUdpMulCapAck]: ucIsEnable = %u\r\n<br />[Sccppry_SpuaUdpMulCapAck]: usReceiveUdpPort = %u\r\n<br />[Sccppry_SpuaUdpMulCapAck]: Len(%u),ucIsEnable(%u),usReceiveUdpPort(%u),msgtype(%u)\r\n<br /></code></p>
<p>Possible the <strong>APM</strong> calls<br /><code>D:\\\\CI_Views\\\\p_ePico3801V200R011C01_Main\\\\UMTS_AP_Code\\\\UAP3801\\\\CPU/app/src/rr/asn1/apm/Asn1ApmDecode.c<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeUmtsNeighbCellList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_UMTS_NEIGHBCELL_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeGsmNeighbCellList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_GSM_NEIGHBCELL_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br />Decode Error In OctString:ulApmIpaddr.<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeAgBoardList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_AGBD_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeAgList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_AG_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeHuaweiipclkList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_HUAWEIIPCLK_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeIeee1588ClkMasterTable_Unsupported<br />Decode Error In usCnt(APM_MAX_LEN_IEEE1588CLKMASTBL_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeSgwServerList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_SGWSVR_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeSgwPathList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_OF_SGW_PATH_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeSgwNwList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_OF_SGW_NETWORK_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br />ApmInfo.<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeUePermissionList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_UEPERMISSION_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeGaPolygon_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_OF_POINT).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeGiUeList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_GI_UE_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodePacketBasedRuleList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_PACKET_BASED_RULE_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeApnBasedRuleList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_APN_BASED_RULE_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeDomainBasedRuleList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_DOMAIN_BASED_RULE_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeUeOffloadRuleList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_UE_OFFLOAD_RULE_LST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br /> Error detected in DecodeUnsupport function :ASN1_APM_DecodeLicenseArithmeticList_Unsupported<br />Decode Error In usCnt(APM_MAX_NO_OF_LICENSE_ARITHMETIC_LIST_PTL).\r\nBad Value: %u = usCnt.,and Modify it to the ProductValue<br />EapMd5Info In PDU of IeId:id_EAP_MD5Info\r\n<br />D:\\\\CI_Views\\\\p_ePico3801V200R011C01_Main\\\\UMTS_AP_Code\\\\UAP3801\\\\CPU/app/src/rr/asn1/apm/Asn1ApmEncode.c<br />Encode Error In ASN1_APM_EncodeUmtsNeighbCellList<br />Encode Error In ASN1_APM_EncodeGsmNeighbCellList<br />Detect the Encode Error in Encoding APM_AP_BOOT_REQ_STRU ;\n<br /> Error in ASN1_APM_EncodeApId\n<br /> Error in ASN1_APM_EncodeLocInfo\n<br />Warning the Extension container --- APM_AP_BOOT_REQ_STRU have no PDU .Check input.;\n<br />Detect the Encode Error in Encoding APM_PROTCL_EXT_AP_BOOT_REQ_STRU ;\n<br />Warning the Extension container --- APM_PROTCL_EXT_AP_BOOT_REQ_STRU have no PDU .Check input.;\n<br />APM_AP_BOOT_REQ_STRU.;\n<br />APM_PROTCL_EXT_AP_BOOT_REQ_STRU.;\n<br />Encode Error In OctString:ulApmIpaddr.<br />Encode Error In ASN1_APM_EncodeAgBoardList<br />Encode Error In ASN1_APM_EncodeAgList<br />Encode Error In ASN1_APM_EncodeHuaweiipclkList<br />Encode Error In ASN1_APM_EncodeIeee1588ClkMasterTable<br />Detect the Encode Error in Encoding APM_IE_EXT_SGW_SERVER_STRU ;\n<br />Warning the Extension container --- APM_IE_EXT_SGW_SERVER_STRU have no PDU .Check input.;\n<br />APM_IE_EXT_SGW_SERVER_STRU.;\n<br />Encode Error In ASN1_APM_EncodeSgwServerList<br />Encode Error In ASN1_APM_EncodeSgwPathList<br />Encode Error In ASN1_APM_EncodeSgwNwList<br />Detect the Encode Error in Encoding APM_IE_EXT_SGW_INFO_STRU ;\n<br /> Error in ASN1_APM_EncodeSgwNwList\n<br />Warning the Extension container --- APM_IE_EXT_SGW_INFO_STRU have no PDU .Check input.;\n<br />APM_IE_EXT_SGW_INFO_STRU.;\n<br />ApmInfo.<br />Detect the Encode Error in Encoding APM_AP_BOOT_RSP_STRU ;\n<br /> Error in ASN1_APM_EncodeApContext\n<br />Warning the Extension container --- APM_AP_BOOT_RSP_STRU have no PDU .Check input.;\n<br />APM_AP_BOOT_RSP_STRU.;\n<br />Detect the Encode Error in Encoding APM_IE_EXT_AP_RADIO_INFO_STRU ;\n<br />Warning the Extension container --- APM_IE_EXT_AP_RADIO_INFO_STRU have no PDU .Check input.;\n<br />APM_IE_EXT_AP_RADIO_INFO_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_PARA_UPT_IND_STRU ;\n<br /> Error in ASN1_APM_EncodeApRadioInfo\n<br />Warning the Extension container --- APM_AP_PARA_UPT_IND_STRU have no PDU .Check input.;\n<br />APM_AP_PARA_UPT_IND_STRU.;\n<br />Encode Error In ASN1_APM_EncodeUePermissionList<br />Detect the Encode Error in Encoding APM_IE_EXT_AP_PERMISSION_LIST_STRU ;\n<br />Warning the Extension container --- APM_IE_EXT_AP_PERMISSION_LIST_STRU have no PDU .Check input.;\n<br />APM_IE_EXT_AP_PERMISSION_LIST_STRU.;\n<br />Detect the Encode Error in Encoding APM_IE_EXT_LOC_IND_STRU ;\n<br /> Error in ASN1_APM_EncodeAudioToneInsertion\n<br />Warning the Extension container --- APM_IE_EXT_LOC_IND_STRU have no PDU .Check input.;\n<br />APM_IE_EXT_LOC_IND_STRU.;\n<br />Encode Error In ASN1_APM_EncodeGaPolygon<br />Encode Error In ASN1_APM_EncodeGiUeList<br />Encode Error In ASN1_APM_EncodePacketBasedRuleList<br />Encode Error In ASN1_APM_EncodeApnBasedRuleList<br />Encode Error In ASN1_APM_EncodeDomainBasedRuleList<br />Encode Error In ASN1_APM_EncodeUeOffloadRuleList<br />Detect the Encode Error in Encoding APM_IE_EXT_AP_INFO_SYNC_STRU ;\n<br /> Error in ASN1_APM_EncodeLicenseInfo\n<br /> Error in ASN1_APM_EncodeLicenseArithmetic\n<br /> Error in ASN1_APM_EncodeApGiInfo\n<br />Warning the Extension container --- APM_IE_EXT_AP_INFO_SYNC_STRU have no PDU .Check input.;\n<br />APM_IE_EXT_AP_INFO_SYNC_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_PARA_SYNC_REQ_STRU ;\n<br /> Error in ASN1_APM_EncodeApInfoSync\n<br />Warning the Extension container --- APM_AP_PARA_SYNC_REQ_STRU have no PDU .Check input.;\n<br />APM_AP_PARA_SYNC_REQ_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_PARA_SYNC_RSP_STRU ;\n<br />Warning the Extension container --- APM_AP_PARA_SYNC_RSP_STRU have no PDU .Check input.;\n<br />APM_AP_PARA_SYNC_RSP_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_ACCESS_REQ_STRU ;\n<br />Warning the Extension container --- APM_AP_ACCESS_REQ_STRU have no PDU .Check input.;\n<br />Encode Error In ASN1_APM_EncodeLicenseArithmeticList<br />Detect the Encode Error in Encoding APM_PROTCL_EXT_AP_ACCESS_REQ_STRU ;\n<br /> Error in ASN1_APM_EncodeLicenseArithmeticList\n<br />Warning the Extension container --- APM_PROTCL_EXT_AP_ACCESS_REQ_STRU have no PDU .Check input.;\n<br />APM_AP_ACCESS_REQ_STRU.;\n<br />APM_PROTCL_EXT_AP_ACCESS_REQ_STRU.;\n<br />Detect the Encode Error in Encoding APM_IE_EXT_PERMISSION_LIST_STRU ;\n<br />Warning the Extension container --- APM_IE_EXT_PERMISSION_LIST_STRU have no PDU .Check input.;\n<br />APM_IE_EXT_PERMISSION_LIST_STRU.;\n<br />Detect the Encode Error in Encoding APM_IE_EXT_AP_ACCESS_INFO_STRU ;\n<br /> Error in ASN1_APM_EncodeEapMd5Info\n<br />Warning the Extension container --- APM_IE_EXT_AP_ACCESS_INFO_STRU have no PDU .Check input.;\n<br />APM_IE_EXT_AP_ACCESS_INFO_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_ACCESS_RSP_STRU ;\n<br /> Error in ASN1_APM_EncodeTime\n<br /> Error in ASN1_APM_EncodeApAccessInfo\n<br />Warning the Extension container --- APM_AP_ACCESS_RSP_STRU have no PDU .Check input.;\n<br />APM_AP_ACCESS_RSP_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_PARA_MODIFY_IND_STRU ;\n<br />Warning the Extension container --- APM_AP_PARA_MODIFY_IND_STRU have no PDU .Check input.;\n<br />APM_AP_PARA_MODIFY_IND_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_PARA_MODIFY_CONF_STRU ;\n<br />Warning the Extension container --- APM_AP_PARA_MODIFY_CONF_STRU have no PDU .Check input.;\n<br />APM_AP_PARA_MODIFY_CONF_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_REBOOT_IND_STRU ;\n<br />Warning the Extension container --- APM_AP_REBOOT_IND_STRU have no PDU .Check input.;\n<br />APM_AP_REBOOT_IND_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_INQUIRE_IMSI_REQ_STRU ;\n<br />Warning the Extension container --- APM_AP_INQUIRE_IMSI_REQ_STRU have no PDU .Check input.;\n<br />APM_AP_INQUIRE_IMSI_REQ_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_INQUIRE_IMSI_RSP_STRU ;\n<br />Warning the Extension container --- APM_AP_INQUIRE_IMSI_RSP_STRU have no PDU .Check input.;\n<br />APM_AP_INQUIRE_IMSI_RSP_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_QOS_DETECT_BEGIN_REQ_STRU ;\n<br />Warning the Extension container --- APM_AP_QOS_DETECT_BEGIN_REQ_STRU have no PDU .Check input.;\n<br />APM_AP_QOS_DETECT_BEGIN_REQ_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_QOS_DETECT_BEGIN_RSP_STRU ;\n<br />Warning the Extension container --- APM_AP_QOS_DETECT_BEGIN_RSP_STRU have no PDU .Check input.;\n<br />APM_AP_QOS_DETECT_BEGIN_RSP_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_QOS_DETECT_END_REQ_STRU ;\n<br />Warning the Extension container --- APM_AP_QOS_DETECT_END_REQ_STRU have no PDU .Check input.;\n<br />APM_AP_QOS_DETECT_END_REQ_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_QOS_DETECT_END_RSP_STRU ;\n<br />Warning the Extension container --- APM_AP_QOS_DETECT_END_RSP_STRU have no PDU .Check input.;\n<br />APM_AP_QOS_DETECT_END_RSP_STRU.;\n<br />Detect the Encode Error in Encoding APM_AP_CFG_TRANSF_STRU ;\n<br /> Error in ASN1_APM_EncodeSonCfgTransf\n<br />Warning the Extension container --- APM_AP_CFG_TRANSF_STRU have no PDU .Check input.;\n<br />APM_AP_CFG_TRANSF_STRU.;\n<br /></code></p> OsmoBSC - Bug #3737 (New): abort because unused lchan has non-null conn pointer, after AMR config...https://osmocom.org/issues/37372018-12-18T02:23:42Zneelsnhofmeyr@sysmocom.de
<p>I was just establishing a call and osmo-bsc crashes on me. Log follows.</p> Cellular Network Infrastructure - Feature #3477 (New): add a wiki page explaining interconnection...https://osmocom.org/issues/34772018-08-20T09:21:37Zneelsnhofmeyr@sysmocom.de
<p>The <a class="wiki-page" href="https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box">Osmocom Network In The Box</a> wiki page explains running components on the same machine.<br />As soon as this is split up between several boxes, numerous config items become necessary to set bind-addresses and remote addresses.<br />Each user manual should explain this, but it would also be nice to have a common wiki page guiding through this process.</p> OsmoHLR - Feature #3019 (New): add config for number of auth tuples returnedhttps://osmocom.org/issues/30192018-03-01T12:32:06Zneelsnhofmeyr@sysmocom.de
<p>by default osmo-hlr returns 5 auth tuples to any client requesting tuples (MSC, SGSN).<br />Allow configuring the number of tuples returned.</p>
<p>Rationale: the nr of tuples cached by the MSC / SGSN are a tuning detail allowing a tradeoff between HLR DB traffic and quick turnaround of the cached data in the MSC / SGSN.</p> OsmocomBB - Feature #2913 (New): Add a tool that decodes Cell Broadasts (SMSCB)https://osmocom.org/issues/29132018-02-07T20:34:14Zroox
<p>Add tool to osmocom-bb that can decode SMS-CB and log data.</p>
<p>A good starting point is the work done by Alex Badea in 2010 and 2013:</p>
<ol>
<li>changes to libosmocore (even with unit tests)<br /><a class="external" href="http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003871.html">http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003871.html</a></li>
<li>changes to cell_log<br /><a class="external" href="http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003887.html">http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003887.html</a></li>
<li>changes to L1 (already merged in sylvain/testing)<br /><a class="external" href="http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003835.html">http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003835.html</a><br /><a class="external" href="http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003836.html">http://lists.osmocom.org/pipermail/baseband-devel/2013-January/003836.html</a></li>
</ol>
<p>There were reasons a that time to not to include these patches into master.</p>
<p>Time went by and now there's even initial support for SMSCB in OsmoBTS/OsmoBSC.<br /><a class="external" href="https://osmocom.org/projects/cellular-infrastructure/wiki/Cell_Broadcast">https://osmocom.org/projects/cellular-infrastructure/wiki/Cell_Broadcast</a></p>
<p>An interesting use-case for (at least for germans) could be the mapping of older BTS from VIAG-Interkom/O2 that still broadcast their locations in Gauss Krueger coordinates.<br />I've written a perl script that uses the logs from Alex Badeas patched cell_log to generate a KML file with the BTS's coordinates.</p> OsmoMSC - Bug #2698 (New): Add more tests to jenkins job testing osmo-msc against NG40testerhttps://osmocom.org/issues/26982017-12-01T12:36:00Zpespin
<p>So far, in sysmocom's jenkins instance job (ng40-test-core-network), we only run 1 test which checks that LU works for 300 MS connecting to osmo-msc.</p>
<p>We need to find a list of screnarios we want to test and implement them using NG40.</p> OsmoBTS - Bug #2675 (New): /usr/bin/lc15bts-mgr can't find GPS 3D fix to for calibrationhttps://osmocom.org/issues/26752017-11-22T16:42:02Zrshack
<p>Hi,</p>
<p>We have a Litecell 1.5 unit. It is updated to the latest packages on the nightly build and configured to an osmo-bsc set up on an another machine.</p>
<p>On mobile phones, the network does not show the short or long name set, instead it shows just numbers "09070" and calls can not be made.</p>
<p>This has happened to us before when there was problem with the clock calibration on the BTS.</p>
<p>A GPS device is attached to the BTS, and when running cgps, there is a 3D Fix and a correct GPS location coordinates show up.</p>
<p>The lc15 bts should be able to calibrate automatically using the lc15bts-mgr package, however, it seems like it is failing to do so.</p>
<p>When we tried stopping the lc15bts-mgr service and start it manually to log the output by running:</p>
<pre>
/usr/bin/lc15bts-mgr -s -c /etc/osmocom/lc15bts-mgr.cfg
</pre>
<p>We notice the following errors:</p>
<pre>
Failed to open /mnt/storage/var/run/lc15bts-mgr/volt-supply-max due to 'No such file or directory' error
<0000> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_misc.c:315 Total hours of Operation: 393
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:271 Going to calibrate the system.
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:121 Last GPS 3D fix can not read (-2). Last GPS 3D fix sets to zero
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:126 GPS has no fix
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:126 Going to check for watchdog notification.
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:67 Missing watchdog events: e:0x000000000000002e,m:0x000000000000007f
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:126 Going to check for watchdog notification.
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:67 Missing watchdog events: e:0x000000000000002f,m:0x000000000000007f
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:271 Going to calibrate the system.
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:121 Last GPS 3D fix can not read (-2). Last GPS 3D fix sets to zero
<0003> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_mgr_calib.c:126 GPS has no fix
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:126 Going to check for watchdog notification.
<0004> ../../../git/src/osmo-bts-litecell15/misc/lc15bts_swd.c:67 Missing watchdog events: e:0x000000000000002f,m:0x000000000000007f
</pre>
<p>It seems the lc15bts_mgr service can not read the values from the GPS device for some reason, can someone please advise what might be causing this issue?</p>
<p>Best Regards,<br />Rayan</p> Cellular Network Infrastructure - Feature #2451 (New): Add static builds to jenkins jobshttps://osmocom.org/issues/24512017-08-18T10:51:23Zmsuraev
<p>Right now most (all?) Osmocom projects support static builds which is sometimes useful for testing and deployment in particular environments.</p>
<p>However, in the absence of per-commit tests it can be easily broken as an unintended side-effect of some patches.</p>
<p>We should add "--enable-static" test builds to the corresponding jenkins jobs to avoid breaking it.</p> OsmoMSC - Feature #2391 (New): add osmocom specific TLVs to A-interface for BTS/TS and subscriber...https://osmocom.org/issues/23912017-07-24T15:24:20Zneelsnhofmeyr@sysmocom.de
<p>Enhance the A-interface by osmocom-specific information, so that the MSC knows which BTS and timeslot a given call is running on and the BSC knows which subscriber a call is for. See in osmo-msc the code marked #if BEFORE_MSCSPLIT and re-enable related bits. See also <a class="external" href="https://lists.osmocom.org/pipermail/openbsc/2017-July/010957.html">https://lists.osmocom.org/pipermail/openbsc/2017-July/010957.html</a></p> OsmoGSMTester - Feature #2271 (New): add test names to pick to the -s cmdline optionhttps://osmocom.org/issues/22712017-05-18T12:32:55Zneelsnhofmeyr@sysmocom.de
<p>When picking individual tests to run, we have the same test names across all suites.<br />Semantically each suite should have its own set of test names.</p>
<p>With argparse, we can't figure out which -t option came in-between which -s options, and also to confuse the users less, we should change the cmdline arg -s to include the test names in the suite:scenarios scheme like:</p>
<pre>
-s suite[:[scenario[+scenario]][:test_name+test_name]]
</pre>
<p>e.g.</p>
<pre>
-s sms:sysmo
-s sms:sysmo+aoip:mo_mt_sms
-s debug::fail
</pre>
<p>(and maybe replace '+' with ',' or allow both -- the one adds requirements, the other lists items, but for the user it's just a separating character and easy to forget which is which)</p>
<p>This way it is also possible to add specific test names to the default-suites.conf</p> OsmoBSC - Feature #1946 (New): Add checks to the BSC VTY to prevent configurations known to not workhttps://osmocom.org/issues/19462017-02-08T23:41:53Zneelsnhofmeyr@sysmocom.de
<p>e.g. running TCH/F_TCH/H_PDCH timeslots on a nanobts doesn't work,<br />similarly, the BS11 should reject any codec except HRv1, FR and EFR (i.e. no AMR),<br />and so on.</p> OsmoBTS - Bug #1744 (New): 1-way voice between sysmobts and nanobts if DTX is enabledhttps://osmocom.org/issues/17442016-06-03T16:23:39Zmsuraev
<p>Not sure if it's osmobts or openbsc to blame but in following setup there's 1-way audio:</p>
<p>ms1 <-> sysmobts <-> openbsc <-> nanobts <-> ms2</p>
<p>The audio ms2 -> ms1 can be heard (if -P option is used for openbsc than some stattering in voice is audible, not sure if it's a separate issue) but the audio ms1 -> ms2 is nonexistent. In some test 1-2 words could be heard before audio is gone. Switching phones change nothing.</p>
<p>OpenBSC is configured for full-rate channels with AMR codec in the attached .pcap although the same effect could be observed with other codecs too.</p> OsmoPCU - Feature #1555 (New): Add support for unacknowledged RLC Modehttps://osmocom.org/issues/15552016-02-23T15:12:44Zlaforge
<p>OsmoPCU currently only supports acknowledged RLC mode. Unacknowledged mode should be possible to add without too much effort. The question is: Is it needed/used ?</p>
<p>The selection of acknowledged/unacknowledged RLC mode should be based on the QoS requirements of the PDP context.</p> OsmocomDECT - Bug #5388 (New): {MM-INFO-SUGGEST} message not sent with ext bit set to 0https://osmocom.org/issues/53882010-10-05T00:00:00Z
<p>GAP (ETSI EN 300 444) section 8.29 (Location update) requires two consecutive {MM-INFO-SUGGEST} messages to be sent, one with the ext bit set to one, one with the ext bit set to zero, presumably for compatibility with old equipment. libdect always sets the ext bit to one on the final octet.</p>