Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092024-01-24T09:43:35ZOpen Source Mobile Communications
Redmine pySim - Bug #6340 (New): exception when using osmo-smdpp with python 3.9https://osmocom.org/issues/63402024-01-24T09:43:35Zdexter
<p>There is an exception when starting osmo-smdpp with python 3.9. This exception does not occur with python 3.10.</p>
<pre>
owner@osmotest:~/git_master/pysim$ python3.9 ./osmo-smdpp.py
Traceback (most recent call last):
File "/home/owner/git_master/pysim/./osmo-smdpp.py", line 100, in <module>
class SmDppHttpServer:
File "/home/owner/git_master/pysim/./osmo-smdpp.py", line 196, in SmDppHttpServer
def initiateAutentication(self, request: IRequest, content: dict) -> dict:
TypeError: 'staticmethod' object is not callable
</pre>
<p>Commit hash: af87cd544f784e51a41cea303cb57001d9954d9c</p> OsmoMGW - Feature #6171 (In Progress): mgcp-client API: there should be a separate mgcp_codec_par...https://osmocom.org/issues/61712023-09-08T15:21:26Zdexter
<p>This was previously discussed in ticket #5723, which got deleted due to an error.</p>
<p>There is a problem we face with the mgcp_client API. mgcp_client_fsm in particular.</p>
<p>The problem is that we are not able to assign different payload type numbers for the same codec. So it is not possible to have the following configuration:</p>
<p>codec: AMR, payload-type: 112<br />codec: AMR, payload-type: 113</p>
<p>However, this would be necessary in case we want to define AMR once in octet-aligned and once in bandwith-efficient configuration, which brings us to the second problem. Since there is only one mgcp_codec_param struct member "param", which only lets us to define exactly one set of codec parameters we cannot even define two different configurations.</p>
<p>Also in some cases it would be also convenient to circumvent the SDP parsing/generation of osmo-mgcp-client and use a user defined SDP string directly.</p> OsmoBSC - Bug #6159 (New): use paging queue for PAGING messages that come from the BSC co-located...https://osmocom.org/issues/61592023-08-30T12:38:17Zdexter
<p>When a BSC co-located PCU sends a PAGING message to the BSC via PCUIF, then this message is forwarded immediately via RSL as RSL PAGING COMMAND. This illegally circumvents the paging queue of OsmoBSC. The PAGING messages from the PCU should take the route through the paging queue like any other paging does.</p> OsmoPCU - Feature #6150 (New): PCUIF: Use unique identifiers instead of the TLLI as msg_id.https://osmocom.org/issues/61502023-08-25T14:05:40Zdexter
<p>When the PCUIF sends a MAC block for PCH (or AGCH) it may request a conformation when the MAC block is sent. For the conformation an uint32_t message id (msg_id) is used. At the moment we use the TLLI as message identifier. However, on the one hand side the TLLI may not be unique, and on the other hand the TBF may not have a TLLI assigned yet. This is in particular the case when the MS is just attaching to the network and has not completed the GMM attach phase yet.</p>
<p>A solution would be to somehow generate a truly unique identifier inside the PCU and use it when sending MAC blocks through the PCUIF. When the receiving end responds with the confirmation we will have to match the identifier back to the TBF to which it belongs.</p> OsmoSGSN - Feature #6139 (New): test mobility between GERAN (OsmoPCU) and EUTRAN (Open5GS) end to...https://osmocom.org/issues/61392023-08-22T09:55:50Zdexter
<p>The mobility features that we recently added to Open5GS and OsmoPCU were developed and tested against TTCN3 testsuites, but we didn't confirm the functionality on real hardware yet.</p>
<p>To do this we need to create a setup with an OsmoBTS/OsmoPCU based GERAN cell and an appropriate EUTRAN ENB that is controlled by Open5GS. In order to be able to trigger the cell change it may be required to equip the transmittig antennas of both radios with variable attenuators.</p> OsmoBSC - Bug #6059 (New): negotiate GSM-HR RTP packet format explicitlyhttps://osmocom.org/issues/60592023-06-13T10:38:00Zdexter
<p>In <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: osmo-bts-sysmo and osmo-bts-trx use different GSM-HR RTP packet format (Resolved)" href="https://osmocom.org/issues/5688">#5688</a> we have solved the problem that, depending on the BTS model, the BTS may use a different HR-GSM format (RFC5993 vs. TS 101.318. Now the user can chose via a VTY option which format the BTS should emit. This improves the situation a lot.</p>
<p>However if conversion is still needed for some reason, OsmoMGW will still blindly convert TS 101.318 to RFC5993 and vice versa. This means that there is a problem in case there is one BTS That speaks TS 101.318 and another one that speaks RFC5993 on the same MGW. OsmoMGW can already be explicitly instructed via SDP (similar to AMR BWE/OE) which format to use. We should add a VTY option to osmo-bsc so that we can specify the format we want to use on the link pointing to the core network side. Doing so, the MGW would accept any format on the leg pointing to the BTS and emit the specified format on the leg pointing towards the core network.</p>
<p>Unfortunately osmo-mgcp-client does not yet have the API to specify the format. #5723 already deals with the problem but this also means that this ticket is blocked by #5723</p> OsmoPCU - Bug #6015 (New): osmo-pcu (with ericsson RBS) is unable to keep TRAU frames in sync https://osmocom.org/issues/60152023-04-25T08:59:55Zdexter
<p>The problem is observed with an RBS installation that uses a DUG20 but a different (presumably older, RRUS 01?) transceiver. The symptom is that the PCU is unable to get a reliable sync on the TRAU frames coming from the CCU (transceiver unit). The CCU eventually closes the channel.</p>
<p>we see the following messages:</p>
<pre>
Mon Apr 24 09:34:08 2023 <0010> trau/trau_sync.c:519 trau_sync(trau-sync){FRAME_ALIGNED}: state_chg to FRAME_ALIGNMENT_LOST
</pre>
The reasons for this could be:
<ul>
<li>Unreliable E1 connection (the setup uses icE1usb+osmo-e1d)</li>
<li>The transceiver module has a slightly different TRAU frame format (unlikely)</li>
<li>Bug in the TRAU synchronizer of libosmo-abis</li>
</ul> pySim - Feature #5976 (New): pySim-prog: do not program linked files multiple timeshttps://osmocom.org/issues/59762023-03-27T16:05:01Zdexter
<p>In the card file system there are files that exist in DF.GSM and in ADF.USIM. In case the files share the same content there may be one physical file and one that is a link to that physical file. At the momen pySim-prog does not care about this. It just programs all files or it programs the file intentionally only in one of the two locations, the latter one is a problem in case the specification of one of the files evolves so that the link has to be removed for newer card revisions and two individual files have to be created. Then one of the two is no longer programmed.</p>
<p>This can be handled smarter. The FCP should tell if the file is a linked file or not. So we should check if the file in question is a linked file and if so, we would skip programming it. In case the file is a physical file we would program it. This would mean we would have to visit all files in all locations but we would be on the safe side in case we have to break up links in future card revisions.</p>
<p>(The topic came up while fixing <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: pySim-prog.py --mnclen=3 buggy / broken (Resolved)" href="https://osmocom.org/issues/5830">#5830</a>)</p> OsmoPCU - Feature #5930 (New): handle multiple BTSs with one PCUhttps://osmocom.org/issues/59302023-03-02T09:07:50Zdexter
<p>OsmoPCU has been used so far in BTS co-located scenario only. This scenario always consists of exactly one BTS instance and exactly one PCU instance. When the PCU is used on a BSC colocated scenario one PCU may serve multiple BTSs. OsmoPCU already manages a list with BTSs and the PCU socket protocol already supports multiple BTSs as well but it is unclear how mature this is. At least the code/API that is used to handle the direct PHY access is not able to distinguish between different BTSs.</p> OsmoBTS - Feature #5927 (Resolved): use "Direct TLLI" method to confirm IMMEDIATE ASSIGNMENT mess...https://osmocom.org/issues/59272023-02-28T10:42:39Zdexter
<p>To assign downlink TBFs, the PCU sends an IMMEDIATE ASSIGNMENT MAC block through the PCU SOCK interface to the BTS. The BTS confirms the sending of this IMMEDIATE ASSIGNMENT to the PCU by sending the MAC block back to the PCU. The MAC block essentially serves as a reference for the confirmation message. This method has some disadvantages so we decided to replace it.</p>
<p>The new method attaches a TLLI (and a paging group field) to the MAC block when it send to the BTS. The BTS then uses the TLLI instead of the MAC block as an identifier to confirm the sending of the IMMEDIATE ASSIGNMENT. The OsmoPCU already supports the method but OsmoBTS still have to be upgraded.</p>
<p>The related PCU/BTS TTCN3 tests also require an update.</p> OsmoMGW - Bug #3849 (New): race condition problem in rtp flow tests of the ttcn3 testsuitehttps://osmocom.org/issues/38492019-03-18T16:53:06Zdexter
<p>The TTCN3 tests that test actual RTP flow behavior through the MGW are prone to fail due to a race condition. The problem occurs when the RTP receiver in the test suite is switched off while at least one packet is still in the loop. When the packet eventually arrives the follwing error is generated:</p>
<pre>
RTP packets received while RX was disabled
MGCP_Test.ttcn:1424 MGCP_Test control part
MGCP_Test.ttcn:1364 TC_ts101318_rfc5993_rtp_conversion testcase
</pre>
<p>The problem is presumably more likely to occur when the test slave is under high load. Since all RTP tests are using the same API and work by the same principle all of those tests are prone to fail from time to time:</p>
<p>TC_one_crcx_loopback_rtp<br />TC_one_crcx_receive_only_rtp<br />TC_rtpem_selftest<br />TC_ts101318_rfc5993_rtp_conversion<br />TC_two_crcx_and_one_mdcx_rtp_ho<br />TC_two_crcx_and_rtp<br />TC_two_crcx_and_rtp_bidir<br />TC_two_crcx_and_unsolicited_rtp<br />TC_two_crcx_diff_pt_and_rtp<br />TC_two_crcx_diff_pt_and_rtp_bidir<br />TC_two_crcx_mdcx_and_rtp</p> OsmoBTS - Bug #3782 (New): OML bringup fails for osmo-bts-oc2g on high latency linkshttps://osmocom.org/issues/37822019-02-06T08:11:44Zdexter
<p>When osmo-bts-oc2g is used in lab setups with low latency links the OML bringup works without any problems. However, when there is a high latency link between BTS and BSC, then the OML bringup fails. The symptoms are not obvious, on the first look the bringup seems to work fine, but the BTS does not start transmitting and closer inspection of the OML related LOG output reveals that there are problems.</p> OsmoMSC - Bug #3704 (Resolved): When Paging request for SMS is unanswered, osmo-msc sends infinit...https://osmocom.org/issues/37042018-11-22T18:01:02Zdexter
<p>The problem occurs when the MSC is attempting to page for an MT SM but the BSC is not responding in any way. The paging requests repeat over and over, even when the SCCP connection is shut down one can still see by the logs that the BSC still trying to page.</p>
<p>The reason for this problem seems not to be located in the code that controls the paging, but rather in the code that runs the SM Queue. The problem is that when the paging fails the SM Queue is trying to deliver the SM again and again. However, there is indeed a mechanism implemented that shall prevent undeliverable SM cycling through the queue again and again. When there are errors during the delivery, the function db_sms_inc_deliver_attempts() is called and once the counters reach a certain maximum the SM is removed from the queue. For some reason this is only done when some error during the delivery happens, but not when the delivery could not be started because the paging did not succeed.</p> OsmoBSC - Bug #3527 (Resolved): When EFR is used Speech Version and Speech Codec seem to mismatch...https://osmocom.org/issues/35272018-09-06T07:28:28Zdexter
<p>The specification demands that Speech Codec (choosen) and Speech Version (choosen) are consistent. With osmo-bsc this seems not to be the case when EFR is used. It still shows "GSM speech full rate version 1" in the Speech Version field. This looks odd and needs to be checked back. There should be something like "GSM speech full rate version 2" or so but not 1.</p>
<p>Attached one finds a sample packet.</p> OsmoBTS - Bug #3497 (Resolved): udp/gsmtap multicast is broken osmo-bts-virtual and virtphyhttps://osmocom.org/issues/34972018-08-23T18:08:37Zdexter
<p>Unfortunately libosmocore change I4a8ffb8d598aca88801a4a0322944d7cdd8d4047 introduced than SO_REUSEADDR should be disabled when IPPROTO_UDP is used. Under normal conditions this makes sense and is also necessary to detect when two processes try to use the same port but for multicast situations like we have them with osmo-bts-virtual, virtphy and gsmtap in general this becomes a problem.</p> OsmoBTS - Bug #3465 (Resolved): TTCN3 tests for osmo-bts failhttps://osmocom.org/issues/34652018-08-14T13:20:27Zdexter
<p>At the moment, all osmo-bts tests fail.</p> OsmoMGW - Bug #3443 (New): Check audio-payload options in osmo-mgw VTYhttps://osmocom.org/issues/34432018-08-02T14:14:54Zdexter
<p>The VTY in osmo-mgw has some strange audio-payload settings, which can set payload number, name, ptime. Normally those are parameters that are set via LCO and SDP by the call agent. Why do we need to set those information in the VTY? We need to check back if those options are still used in a meaningful way and what they are for. Maybe this is a leftover from the refactoring which requires fixing/removal.</p>
<p>Here are some examples:</p>
<p>sdp audio-payload number<br />sdp audio-payload name NAME<br />sdp audio-payload send-ptime",</p> OsmoMGW - Bug #3442 (New): fix int mgcp_codec_decide() in mgcp_codec.chttps://osmocom.org/issues/34422018-08-02T14:08:40Zdexter
<p>The function mgcp_codec_decide() selects the codec that is later returned with the MGCP response in MGCP. The response is generated from rtp->codec, which is set by mgcp_codec_decide().</p>
<p>Unfortunately, the current implementation of mgcp_codec_decide() makes no sense at all. It only causes no trouble at the moment because endp->tcfg->no_audio_transcoding is set to 0, which means that transcoding is turned on at the moment even though we do not support trans coding.</p>
<p>mgcp_codec_decide() should be revised in the following way: <br />We remove rtp->codec, because Technically an MGW does not have one selected codec, it knows about several codecs and may make choices based on its transcoding capabilities and policies. In practice this would mean that mgcp_codec_decide() removes all the unsupported codecs from rtp->codecs[]. The functions that generate the SDP will then find only the selected codecs and return them. At the moment we can only return one codec from inside the SDP because we use rtp->codec as data source.</p>
<p>Since we do not support transcoding at the moment there will not be much in mgcp_codec_decide(), endp->tcfg->no_audio_transcoding is set to 0 we can display a warning that tells the user that transcoding is not supported yet.</p> libosmocore - Bug #3441 (Resolved): two processes can open the same UDP port without errorhttps://osmocom.org/issues/34412018-08-01T11:00:32Zdexter
<p>When two processes open a socket with the same UDP port there will be no error since we set SO_REUSEADDR also for UDP ports. This is dangerous and might lead into situations that are very difficult to debug. There is no point in setting SO_REUSEADDR for UDP ports since UDP is connection less and there can not be any lingering connections like with TCP.</p> OsmoBSC - Bug #3361 (Resolved): VTY option codec-support is not usedhttps://osmocom.org/issues/33612018-06-28T16:12:27Zdexter
<p>osmo-bts has per-bts codec support flags, which are stored in struct bts_codec_conf *codec</p>
<p>The vty option codec-support sets those flags:<br />codec->hr<br />codec->efr<br />codec->amr</p>
<p>But the flags seem not to be used anywhere. In osmo_bsc_bssap.c osmo-bts decides for a codec depending on what the MS and the MSC offer. We should include those flags here as well.</p> OsmoMGW - Feature #3334 (Resolved): use proper sdp in libosmo-mgcp-clienthttps://osmocom.org/issues/33342018-06-11T19:30:18Zdexter
<p>libosmo-mgcp-client currently uses hardcoded SDP with fixed values. It also uses a payload type 255, which is illegal.</p>
<p>- Add new struct members to allow setting of ptime, payload type and rtpmap if needed.<br />- Generate proper SDP and use it when communicating to the MGW<br />- Decode the SDP responses from osmo-mgw.<br />- Update both, the normal mgcp_client and mgcp_client_fsm</p> OsmoBSC - Bug #2939 (Resolved): TTCN3: Fix broken paging testshttps://osmocom.org/issues/29392018-02-13T11:11:23Zdexter
<p>Many of the paging tests still fail. The result is the same for pmaier/fsm and for current master. Also the jenkins shows a very similar picture.</p>
<pre>
#BSC_Tests.TC_paging_imsi_nochan # Pass
#BSC_Tests.TC_paging_tmsi_nochan # Fail
#BSC_Tests.TC_paging_tmsi_any # Fail
#BSC_Tests.TC_paging_tmsi_sdcch # Fail
#BSC_Tests.TC_paging_tmsi_tch_f # Fail
#BSC_Tests.TC_paging_tmsi_tch_hf # Fail
#BSC_Tests.TC_paging_imsi_nochan_cgi # Pass
#BSC_Tests.TC_paging_imsi_nochan_lac_ci # Pass
#BSC_Tests.TC_paging_imsi_nochan_ci # Pass
#BSC_Tests.TC_paging_imsi_nochan_lai # Fail
#BSC_Tests.TC_paging_imsi_nochan_lac # Fail
#BSC_Tests.TC_paging_imsi_nochan_all # Pass
#BSC_Tests.TC_paging_imsi_a_reset # Fail
#BSC_Tests.TC_paging_imsi_load # Fail
#BSC_Tests.TC_paging_counter # Fail
#BSC_Tests.TC_rsl_drop_counter # Pass
</pre> OsmoBSC - Feature #2918 (New): Implement a function to properly test connection clearing in MSC_C...https://osmocom.org/issues/29182018-02-09T17:11:45Zdexter
<p>BSC_ConnectionHandler.ttcn implements a function to test proper connection clearing: f_expect_clear()</p>
<p>We should have an inverse pendant in MSC_ConnectionHandler.ttcn for the BSC tests as well. Here we will probably have two scenarios, the first is when the BSC asks the MSC to clear the connection and the second will be when the MSC instructs the BSC to clear the connection (regular case)</p> OsmoBSC - Bug #2823 (Resolved): Use bsc_subscr_conn_fsm in BSChttps://osmocom.org/issues/28232018-01-08T22:28:12Zdexter
<p>On laforge/fsm a draft FSM implementation can be found to make the handling of the subscriber connection safer and stateful.</p> OsmoMSC - Bug #2745 (Resolved): UMTS ciphering on GSM does not work when both 2G and 3G keys are ...https://osmocom.org/issues/27452017-12-13T16:20:57Zdexter
<p>When populating the hlr database with 3G keys (auc_3g), then 2G authentication stops working, while 3G authentication on nano3G still works fine. When the 3G keys are removed, then 2G authentication works again. At the moment we suspect that osmo-msc trys to perform 3G authentication on 2G (specified) and fails because it does not work.</p>
<p>In the attached archive one finds a trace from the connection between MSC and BSC and the complete network configuration, hlr database logs and start scripts.</p> OsmoMGW - Feature #2580 (New): implement timeout/resend mechanism for mgcp_clienthttps://osmocom.org/issues/25802017-10-17T16:28:03Zdexter
<p>At the moment mgcp_client sends the the message out and waits for the response, when the response is received, then a the result is returned through a callback. If no response is received (e.g. packet loss), then simply nothing happens. It would be very helpful if the message gets resend after some time.</p>
<p>Each mgcp_message has a unique ID-Number and osmo-mgw is able to handle resend messages. So if the message was received osmo-mgw, but the response got lost on its way to the client, a resend would not hurt. We only need to upgrade the mgcp_client to resend messages after some timeout in case no response is received.</p> OsmoMGW - Feature #2517 (Resolved): use libosmocore counters for packet/byte counting (statistics)https://osmocom.org/issues/25172017-09-22T07:37:31Zdexter
<p>use any of the libosmocore counters, rather than having hand-coded counters. A rate counter would have the benefit that it would come with free CTRL interface access to the counters.</p>
<p>(see also the SGSN/PDP-Context per direction packet and byte counting)</p> OsmoSGSN - Bug #2501 (In Progress): suspected problem with unanswered neighbor solicitationhttps://osmocom.org/issues/25012017-09-07T12:20:44Zdexter
<p>getting and using an IPV6 pdp context has been tested successfully using a<br />samsung galaxy S2, but tests with a Getnord ONYX fail.</p>
<p>In the failure case, the PDP-Context is opened successfully, also the following<br />interactions look good. Except that the pdp context is closed by the phone a<br />shortly after it had been established. The dactivation cause is a regular<br />deactivation.</p>
<p>When comparing the two traces it is distinctive, that the trace from the<br />getnord does contain a neighbor solicitation request. This request seems to be<br />ignored by the GGSN. It is likely that the getnord mobile interprets this as<br />a failure and then closes the pdp context.</p>
<p>The traces of the two cases are attached to this ticket.</p> OsmoBTS - Bug #2355 (New): optimize log output of phy specific codehttps://osmocom.org/issues/23552017-07-10T08:44:24Zdexter
<p>In osmo-bts, there is plenty of log output in the phy specific code. Some of this log output could be moved to the common code. This would unify the log output.</p> libosmo-sccp + libosmo-sigtran - Bug #2259 (New): problem with local referencehttps://osmocom.org/issues/22592017-05-16T13:05:55Zdexter
<p>When a connection attemt (local reference = 2) is made, libosmo-sccp complains with "<000d> sccp_scoc.c:1528 Cannot find connection for local reference 2". Current master is at 872c6b2a8e309ca6739ef295f1fc468c189e4ec9. The problem seems to be introduced with commit 5527df78adc08b76df07c4b682263b5bdd6181d4 (libosmo-sccp.git). When the commit is reverted, the correct functionality of libosmo-sccp seems to be restored.</p>
<p>The problem can be demonstrated by using the client/server example that is shipped with libosmo-sccp. The following VTY-Commands were used to trigger the problem:</p>
<pre>
enable
sccp-user
called-addr-ssn 202
connect-req 2 hello
</pre>
<p>Note: In the good case I can see the normal CR with payload attached and the CC that with the payload that is echoed by the the echo subsystem. The bad case results in an CREF message, which contains an refusal cause code 0x0F (unqalified)</p>