Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092024-02-28T00:28:49ZOpen Source Mobile Communications
Redmine OsmoBSC - Bug #6378 (New): Ericsson DUG 20 rejects SI2quaterhttps://osmocom.org/issues/63782024-02-28T00:28:49Zkeith
<p>Sending SI2quater to the DUG20 results in</p>
<pre>
ERROR REPORT (cause=Radio Resource not available [ 21 01 80 ])
</pre>
<p>For what it may be worth, the SI and the error are in the attached pcap.</p>
<p>Maybe the BTS software version I have simply does not support it?</p> OsmoMSC - Bug #6358 (Closed): SMS from 4G fails - RP-DATA (MO) without DST or TPDU ?!?https://osmocom.org/issues/63582024-02-13T00:34:55Zkeith
<p>WE currently cannot send SMS from a UE on 4G RAN</p>
<p>RP-DATA (MO) without DST or TPDU ?!?</p>
<pre>
20240213001943906 DLSMS DEBUG trans(SMS IMSI-334070000000968:MSISDN-68070122968:TMSI-0x1DCB852B:EUTRAN-SGs:CM_SERVICE_REQ callref-0x4000000c tid-8) RX_RP-DATA: src_len=0, dst_len=0 ud_len=15 (gsm_04_11.c:768)
20240213001943906 DLSMS ERROR trans(SMS IMSI-334070000000968:MSISDN-68070122968:TMSI-0x1DCB852B:EUTRAN-SGs:CM_SERVICE_REQ callref-0x4000000c tid-8) RP-DATA (MO) without DST or TPDU ?!? (gsm_04_11.c:775)
20240213001943906 DLSMS NOTICE trans(SMS IMSI-334070000000968:MSISDN-68070122968:TMSI-0x1DCB852B:EUTRAN-SGs:CM_SERVICE_REQ callref-0x4000000c tid-8) TX: SMS RP ERROR, cause 96 (Invalid Mandatory Information) (gsm_04_11.c:714)
</pre>
<p>Maybe this is due to a change in latest open5gs?</p> OsmoBSC - Bug #6324 (New): Making a data call results in B0RKEN lchanshttps://osmocom.org/issues/63242024-01-05T20:31:49Zkeith
<p>I made a data call from a GSM modem and ended up with a CHAN NACK from osmo-bts (as is to be expected, I suppose)</p>
<p>Should we enhance osmo-bsc's NACK handling to do something a little more helpful than just B0RK the channel?</p> OsmoBTS - Bug #6180 (Resolved): ASSERT in l1sap_tch_indhttps://osmocom.org/issues/61802023-09-14T21:35:48Zkeith
<p>On a sysmoBTS with the latest release, I observed regularly hitting this ASSERT at <a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/33832/5/src/common/l1sap.c#1982">https://gerrit.osmocom.org/c/osmo-bts/+/33832/5/src/common/l1sap.c#1982</a></p>
<pre><code class="c syntaxhl"> <span class="k">case</span> <span class="n">RSL_CMOD_SPD_SIGN</span><span class="p">:</span>
<span class="k">default</span><span class="o">:</span> <span class="cm">/* shall not happen */</span>
<span class="n">OSMO_ASSERT</span><span class="p">(</span><span class="mi">0</span><span class="p">);</span>
<span class="err">}</span>
</code></pre>
<p>I've patched to avoid this ASSERT based on <a class="user active" href="https://osmocom.org/users/67">fixeria</a> 's advice on IRC to get this BTS back up and running, so I can't reproduce right now. <br />(I've only installed the release on one system)</p>
<p>Here's a backtrace I did grab from the terminal scrollback, probably not very useful:</p>
<pre>
((*))
|
/ \ OsmoBTS
Assert failed 0 ../../../git/src/common/l1sap.c:1983
backtrace() returned 0 addresses
Program received signal SIGABRT, Aborted.
0x432dcf74 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x432dcf74 in raise () from /lib/libc.so.6
#1 0x432de358 in abort () from /lib/libc.so.6
#2 0xb6e778d4 in osmo_panic_default (args=..., fmt=0x0)
at /usr/src/debug/libosmocore/1.9.0+gitrAUTOINC+aca2c724ae-r2.18.0/git/src/core/panic.c:45
#3 osmo_panic (fmt=0x5f448 "Assert failed %s %s:%d\n")
at /usr/src/debug/libosmocore/1.9.0+gitrAUTOINC+aca2c724ae-r2.18.0/git/src/core/panic.c:80
#4 0x0005098c in l1sap_tch_ind (tch_ind=<optimized out>, l1sap=<optimized out>, trx=0xb6b5a038)
at /usr/src/debug/osmo-bts/1.7.0+gitAUTOINC+e97834f2db-r0.18/git/src/common/l1sap.c:1983
#5 l1sap_up (trx=trx@entry=0xb6b5a038, l1sap=<optimized out>)
at /usr/src/debug/osmo-bts/1.7.0+gitAUTOINC+e97834f2db-r0.18/git/src/common/l1sap.c:2184
#6 0x00051b34 in add_l1sap_header (trx=trx@entry=0xb6b5a038, rmsg=<optimized out>, lchan=<optimized out>,
chan_nr=<optimized out>, fn=5084, ber10k=1184, lqual_cb=102, rssi=-104 '\230', ta_offs=192, is_sub=0 '\000')
at /usr/src/debug/osmo-bts/1.7.0+gitAUTOINC+e97834f2db-r0.18/git/src/common/l1sap.c:179
#7 0x00020b8c in l1if_tch_rx (trx=trx@entry=0xb6b5a038, chan_nr=chan_nr@entry=26 '\032',
l1p_msg=l1p_msg@entry=0x187060)
at /usr/src/debug/osmo-bts/1.7.0+gitAUTOINC+e97834f2db-r0.18/git/src/osmo-bts-sysmo/tch.c:611
#8 0x000188e0 in handle_ph_data_ind (l1p_msg=0x187060, data_ind=0x187128, fl1=<optimized out>)
at /usr/src/debug/osmo-bts/1.7.0+gitAUTOINC+e97834f2db-r0.18/git/src/osmo-bts-sysmo/l1_if.c:976
#9 l1if_handle_ind (fl1=<optimized out>, msg=0x187060)
at /usr/src/debug/osmo-bts/1.7.0+gitAUTOINC+e97834f2db-r0.18/git/src/osmo-bts-sysmo/l1_if.c:1139
---Type <return> to continue, or q <return> to quit---q
</pre> OsmoPCU - Bug #6179 (Feedback): ASSERT in st_wait_releasehttps://osmocom.org/issues/61792023-09-14T19:25:37Zkeith
<p>osmo-pcu from the recent release:</p>
<p>Here's a backtrace (from sysmobts with osmo-pcu-dbg and libosmocore-dbg symbols installed)<br /><pre>
Assert failed 0 ../../git/src/tbf_dl_fsm.c:309
backtrace() returned 0 addresses
Program received signal SIGABRT, Aborted.
0x432dcf74 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x432dcf74 in raise () from /lib/libc.so.6
#1 0x432de358 in abort () from /lib/libc.so.6
#2 0xb6eb38d4 in osmo_panic_default (args=..., fmt=0x0)
at /usr/src/debug/libosmocore/1.9.0+gitrAUTOINC+aca2c724ae-r2.18.0/git/src/core/panic.c:45
#3 osmo_panic (fmt=0x66fd4 "Assert failed %s %s:%d\n")
at /usr/src/debug/libosmocore/1.9.0+gitrAUTOINC+aca2c724ae-r2.18.0/git/src/core/panic.c:80
#4 0x00040f5c in st_wait_release (fi=<optimized out>, event=<optimized out>, data=<optimized out>)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/tbf_dl_fsm.c:309
#5 0xb6ea7824 in _osmo_fsm_inst_dispatch (fi=0x15e420, event=0, event@entry=3, data=data@entry=0x0, file=0x70098 "../../git/src/tbf.cpp",
line=line@entry=540) at /usr/src/debug/libosmocore/1.9.0+gitrAUTOINC+aca2c724ae-r2.18.0/git/src/core/fsm.c:875
#6 0x000356cc in gprs_rlcmac_tbf::poll_timeout (this=0x162920, pdch=0x154e64, poll_fn=223816, reason=<optimized out>)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/tbf.cpp:540
#7 0x0003585c in tbf_poll_timeout (tbf=<optimized out>, pdch=<optimized out>, poll_fn=<optimized out>, reason=<optimized out>)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/tbf.cpp:828
#8 0x0004cdf8 in pdch_ulc_expire_fn (ulc=0x1549d0, fn=223816, fn@entry=1395928)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/pdch_ul_controller.c:331
#9 0x00026a70 in pcu_rx_data_ind_pdtch (bts=bts@entry=0x154cd8, pdch=0x154e64, data=0x0, len=<optimized out>, fn=223816, meas=0xbefffb80,
meas@entry=0xbefffb78) at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/pcu_l1_if.cpp:396
#10 0x00015d70 in handle_ph_data_ind (fl1h=0x15de28, fl1h=0x15de28, l1p_msg=0x202ef8, data_ind=0x202fc0)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/osmo-bts-sysmo/sysmo_l1_if.c:220
</pre></p>
<p>It's always happening at line 540 in tbf.cpp:<br /><pre><code class="c syntaxhl"><span class="n">osmo_fsm_inst_dispatch</span><span class="p">(</span><span class="n">this</span><span class="o">-></span><span class="n">state_fi</span><span class="p">,</span> <span class="n">TBF_EV_MAX_N3105</span><span class="p">,</span> <span class="nb">NULL</span><span class="p">);</span>
</code></pre></p>
<p>Logs are messy, there's a lot going on.<br />Maybe attached log (at INFO) helps.</p> OsmoPCU - Bug #6002 (Resolved): retention or rapid re-creation of ms entries.https://osmocom.org/issues/60022023-04-14T19:02:56Zkeith
<p>I mailed (privately) <a class="user active" href="https://osmocom.org/users/30187">pespin</a> about this a couple of weeks ago.. because I saw a case where there were over 100,000 ms entries. It was in spanish so I won't repost here.</p>
<p><img src="https://osmocom.org/attachments/download/6801/clipboard-202304142058-4itci.png" alt="" /></p>
<p>Can't really add more now anyway, other than just point that the issue exists. Those stats are not latest release, but the 100,000 was with latest.</p>
<p>This is just the latest to be added:</p>
<pre>
MS TLLI=92f209e0, IMSI=
Timing advance (TA): 7
Coding scheme uplink: MCS-1
Coding scheme downlink: MCS-7
Mode: EGPRS
MS class: 12
EGPRS MS class: 12
PACCH: 5
LLC queue length: 4
LLC queue octets: 36
RSSI: -110 dBm
Bit error rate: 0 %
Link quality: 7 dB
Burst timing offset: 3/4 bit
MS C value: 7 dB
Downlink TBF: TFI=1, state=ASSIGN
Current DL Throughput: 0 Kbps
MS Statistics:
Amount of DL CTRL messages scheduled: 113 (0/s 0/m 0/h 113/d)
</pre> OsmoBSC - Bug #5986 (New): PAGING impossible until CCCH LOAD IND is received from the BTShttps://osmocom.org/issues/59862023-03-29T20:10:54Zkeith
<p>I noticed this with the RBS unit, that does not seem to be sending CCCH LOAD ind.</p>
<p>At <a class="external" href="https://gitea.osmocom.org/cellular-infrastructure/osmo-bsc/src/branch/master/src/osmo-bsc/paging.c#L249">https://gitea.osmocom.org/cellular-infrastructure/osmo-bsc/src/branch/master/src/osmo-bsc/paging.c#L249</a> we fully delay all paging requests and log "Paging delayed: waiting for available slots at BTS" until such a LOAD ind has been received.</p>
<p>Maybe this check should be removed/relaxed if the vty param "paging load -1" is set?</p>
<p>Maybe the check for (bts_pag_st->free_chans_need != -1) and the above can be reordered?</p> OsmoBSC - Feature #5983 (Resolved): Exit if osmo-e1d goes down or is restartedhttps://osmocom.org/issues/59832023-03-29T17:27:36Zkeith
<p>If something happens to osmo-e1d while osmo-bsc is running and connected, osmo-bsc will spam with log with </p>
<pre><code>DLMI ERROR input/e1d.c:74 E1TS(0:1) handle_ts_sign_read read failed 0 (Broken pipe)</code></pre>
<p>This causes high cpu usage of osmo-bsc, a terminal it may be running in and possibly also systemd-journald, and quite some disk access.</p>
<p>On one hardware type/configuration this appears to cause the network to become unresponsive and I couldn't even stop osmo-bsc via ssh. That's not something to fix here, but at least osmo-bsc should probably exit in this case, as it <strong>will not recover when osmo-e1d comes back on line</strong> .</p> OsmoBSC - Bug #5982 (Feedback): conn->fi is NULL in gscon_bssmap_clear()https://osmocom.org/issues/59822023-03-29T16:50:48Zkeith
<p>not master, but I don't think anything relevant has changed, there is one SEGV fix (7a0bef1ae4784203bf5f93b2dc2c4138dcad9397) but my quick static analysis suggests it's not related.</p>
<p>Program terminated with signal SIGSEGV, Segmentation fault.</p>
<pre>
(gdb) bt
#0 0x0000558c248184b4 in gscon_bssmap_clear (conn=conn@entry=0x558c262a0410, cause=cause@entry=GSM0808_CAUSE_EQUIPMENT_FAILURE) at bsc_subscr_conn_fsm.c:151
#1 0x0000558c24819932 in gscon_forget_lchan (conn=conn@entry=0x558c262a0410, lchan=lchan@entry=0x7faef1906718) at bsc_subscr_conn_fsm.c:943
#2 0x0000558c2487f3cf in lchan_fsm_wait_rf_release_ack_onenter (fi=<optimized out>, prev_state=<optimized out>) at lchan_fsm.c:1429
#3 0x00007faef078b41b in ?? () from /usr/lib/x86_64-linux-gnu/libosmocore.so.19
#4 0x00007faef078bb1d in _osmo_fsm_inst_state_chg () from /usr/lib/x86_64-linux-gnu/libosmocore.so.19
#5 0x0000558c24871c56 in lchan_fsm_timer_cb (fi=0x558c26255430) at lchan_fsm.c:1810
#6 0x00007faef078d0f1 in ?? () from /usr/lib/x86_64-linux-gnu/libosmocore.so.19
#7 0x00007faef07861f6 in osmo_timers_update () from /usr/lib/x86_64-linux-gnu/libosmocore.so.19
#8 0x00007faef0786d25 in ?? () from /usr/lib/x86_64-linux-gnu/libosmocore.so.19
#9 0x00007faef0786db6 in osmo_select_main_ctx () from /usr/lib/x86_64-linux-gnu/libosmocore.so.19
#10 0x0000558c247dc486 in main (argc=<optimized out>, argv=<optimized out>) at osmo_bsc_main.c:1031
(gdb) p conn->fi
$4 = (struct osmo_fsm_inst *) 0x0
</pre>
<p>I don't have log at level DEBUG but this looks to be the trigger condition:</p>
<pre><code>DRSL ERROR handover_fsm.c:1557 handover(intraBSC_msc0-conn1_subscr-IMSI-[redacted]-TMSI-0x213e241e)[0x558c262a2e70]{WAIT_LCHAN_ACTIVE}: (4-0-4-TCH_F-0-SPEECH_V1) --HO-> (0-0-4-TCH/F_TCH/H_SDCCH8_PDCH:PDCH-0) (subscr subscr-IMSI-[redacted]-TMSI-0x213e241e) HO-intraBSC: Handover failed in state WAIT_SCCP_RLSD, Connection released: Connection releasing in the middle of handover</code></pre>
<p>I have four SEGV in the log over the last few days and all are preceded by this RSL ERROR, however in at least one of the core dumps, conn->fi is not NULL but the crash is the same, weird?</p>
<p>coredumps are available. ping me on IRC for access.</p> OsmoBTS - Bug #5944 (In Progress): DTXu + AMR on TCH/H appears to be not usable on osmo-bts-sysmohttps://osmocom.org/issues/59442023-03-11T05:12:25Zkeith
<p>The problem is that conversation is uncomfortable bordering on impossible due to random lost words and cut off of initial speech after silence periods.</p>
<p>I've been experimenting sending the AMR RTP stream into decoders or SIP endpoints, (all using libopencore-amr) and also, without using any external MNCC, thereby only having the the audio stream pass through osmo-mgw before going to a B-leg MS. I observe the problem in all cases.</p>
<p>I've put quite some hours into this so far, without being able to achieve any improvements. Rather than leave it all fade from memory, I'll just make a quick note of the main points of what was observed:</p>
<p>It all seems fine as long as you have sequences of speech followed by SID_FIRST_P1, SID_FIRST_P2, then eventually an ONSET, followed by speech frames... rinse and repeat. This is fine.</p>
<p>When it goes wrong is if you have a situation where (because of the timing of the VAD) you get either a SID_FIRST_INH or a SID_UPDATE_INH, in these cases, what I've observed is that after the SID_UPDATE_INH, the L1 does not seem to be sending us any Speech frames, (just TCH/H with no payload) even though I am speaking. Eventually, there will be an ONSET followed by speech frames.</p>
<p>I may be wrong, but I don't think there's anything that osmo-bts is doing or can do about this, so I'm pretty convinced at this point that is is an L1 problem, and therefore will not (cannot?) be fixed. I'm aware that there is code in libosmocore to deal with all this weird interleaving and such that goes on in AMR DTX, but we don't use any of it in osmo-bts-sysmo.</p>
<p>The pcap comes from an osmo-bts with some modifications to logging and RTP marking, (ignore the BAD AMR frames following ONSET - that's a hack but not relevant) the main point would be to observe what is happening around and after packet no 1482 - Note all that PH-DATA.ind TCH/H with no payload. I am speaking then.</p> OsmoBTS - Bug #5925 (Resolved): dtx downlink causing ABORT in osmo-bts-sysmohttps://osmocom.org/issues/59252023-02-27T21:58:17Zkeith
<p>With param <strong>dtx downlink</strong> and making a call, causes</p>
<pre>
==24631== Process terminating with default action of signal 6 (SIGABRT)
==24631== at 0x6612E87: raise (raise.c:51)
==24631== by 0x66147F0: abort (abort.c:79)
==24631== by 0x5D648AF: osmo_panic (in /usr/lib/x86_64-linux-gnu/libosmocore.so.20.0.0)
==24631== by 0x114E8E: msgb_pull (msgb.h:407)
==24631== by 0x116751: ph_tch_req (l1_if.c:508)
==24631== by 0x116A08: ph_tch_req (l1_if.c:564)
==24631== by 0x116CE9: bts_model_l1sap_down (l1_if.c:632)
==24631== by 0x164A1F: l1sap_down (l1sap.c:1849)
==24631== by 0x16285D: l1sap_tch_rts_ind (l1sap.c:1324)
==24631== by 0x164821: l1sap_up (l1sap.c:1809)
==24631== by 0x117637: handle_ph_readytosend_ind (l1_if.c:886)
==24631== by 0x118438: l1if_handle_ind (l1_if.c:1119)
</pre>
<p>ph_tch_req() calls itself passing l1sap->oph.msg as msg<br />then<br />msgb_pull(msg, sizeof(*l1sap));<br />is called.</p> OsmoBTS - Bug #5895 (New): LC15: Audio Quality Problem sometime after cf7a7fcebf625a14fd764355c3b...https://osmocom.org/issues/58952023-02-07T03:11:09Zkeith
<p>Writing this up now while it's a bit fresh...</p>
<p>I have spent the last 12 hours or so working with people on site to try to track down these problems:</p>
<p>Fierce complaints about audio quality (no audio, unintelligible, intermittent, chopped)</p>
<p>Observation of a lot of very variable Q in meas reps, especially on downlink (associated with bad audio) and more pronounced when the call B-leg was using another codec such as G.729 on the other side of the PBX, - in fact not transcoding at site and sending AMR to our data centre and trancoding there to PCMA/U for the upstream VoIP was giving better results most of the time.</p>
<p>However, today I discovered the extent of how bad this was on local MS to MS calls.</p>
<p>After exhausting everything I could think of, we went back to the timeline and there were some opinions that this started around a date last year which seemed to be around the time I changed this site away from osmo-nitb. Given I wasn't seeing any signalling problems, I had been looking for problems with maybe the MGW or something with RTP that would have changed. but I could find nothing.</p>
<p>Of course none of that was at fault, what happened was that along with the move to osmo-bsc, I built v1.4.0 of osmo-bts - I think not 1.5.0 because at the time 1.4.0 built against the libs I had on the BTS, anyway, going back to the binary I had built before from cf7a7fce "solves" the problem.</p>
<p>Given the current somewhat tense situation I don't envisage "test"-ing anything at this site for the time being so I can't exactly try to dissect between cf7a7fce and 1.4.0 not that it would be very easy to run each commit against a bunch of manual tests that annoy the local people, asking them to make calls to each other.</p>
<p>So what to do? Well note it at least. I don't have another lc15 to test on. <br />Maybe shout-out to the main devs who committed code that touched lc15 or common, (which seems to have to do with power control, interference measurements) to see if they have any ideas. My feeling is that something that was done is not happy on the LC15 PHY.</p>
<p>There's the chance that this was fixed since 1.4.0 or in another lib.</p>
<p><em>Trivia: cf7a7fce is the last commit that can do RSL/OML bring-up against osmo-nitb.. that's why that one.</em></p> OsmoHLR - Feature #5865 (New): Automate selection of LU Reject Causehttps://osmocom.org/issues/58652023-01-20T13:59:07Zkeith
<p>There is some suggestion in <a class="external" href="https://gerrit.osmocom.org/c/osmo-hlr/+/16808">https://gerrit.osmocom.org/c/osmo-hlr/+/16808</a> that osmo-hlr could use some criteria to decide what cause/reason to send to the GSUP client when rejecting a Location/Routing Update</p>
<p>Possibly, sending "IMSI Unknown in HLR" is wrong when the SIM is foreign to our network.</p>
<p>We could have a regex config option to let osmo-hlr know what is "our" SIM or not. Or maybe a GSUP client like osmo-msc can comunicate MNC-MCC info from the MSC network config over GSUP? I'm not familiar with GSUP.</p> Cellular Network Infrastructure - Bug #5856 (Resolved): Very annoying "this BTS model does not su...https://osmocom.org/issues/58562023-01-14T23:27:07Zkeith
<p>Since some months ago, when connecting osmo-bts-sysmo to a remote osmo-bsc that is not directly on the LAN, (and very occasionally on the LAN), but rather on some higher latency link, I am often seeing</p>
<p><strong>common/oml.c:991 OC=<abbr title="03">CHANNEL</abbr> INST=(00,00,00): SET CHAN ATTR: this BTS model does not support TSC 7 != BSIC-BCC 0</strong></p>
<p>Seemingly because in the OML bringup we are sending <strong>Set CHAN attrs</strong> before we have sent <strong>Set BTS attrs</strong></p>
<p>I don't know what controls this sequence, but maybe it would be good if that were a little more robust.</p> OsmoHLR - Bug #5854 (Resolved): Memory leak: many 1000s of proxy_subscr_listentryhttps://osmocom.org/issues/58542023-01-13T05:34:32Zkeith
<p>After running osmo-hlr with a dGSM setup for a few hours, memory consumption points to an obvious leak, and there are thousands of</p>
<pre>
struct proxy_subscr_listentry contains 944 bytes in 1 blocks (ref 0) 0x55f7cf8ba070
struct proxy_subscr_listentry contains 944 bytes in 1 blocks (ref 0) 0x55f7cf8e4960
struct proxy_subscr_listentry contains 944 bytes in 1 blocks (ref 0) 0x55f7cf8e5120
</pre>
<p>I <em>AM</em> running a few patches on master, but nothing that allocates a <strong>proxy_subscr_listentry</strong></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> OsmoBSC - Feature #5740 (New): Disallow unworkable AMR modes.https://osmocom.org/issues/57402022-11-03T19:21:01Zkeith
<p>This is fairly trivial, but as a note to self, two things.</p>
<p>1) establish exactly what's wrong and make it not possible to configure osmo-bsc like this?<br />2) Can "RADIO INTERFACE MESSAGE FAILURE" be any more sepcific? (LOG / Tx to MSC)</p>
<p>config:<br /><pre>
amr tch-h modes 2 3 4 5
amr tch-h threshold ms 32 24 32
amr tch-h hysteresis ms 8 4 4
amr tch-h threshold bts 32 24 32
amr tch-h hysteresis bts 8 4 4
amr tch-h start-mode 3
</pre></p>
<pre>
Radio Signalling Link (RSL)
GSM A-I/F DTAP - Assignment Command
Protocol Discriminator: Radio Resources Management messages (6)
DTAP Radio Resources Management Message Type: Assignment Command (0x2e)
Channel Description 2 - Description of the First Channel, after time
Power Command
Channel Mode - Mode of the First Channel(Channel Set 1)
Element ID: 0x63
Channel Mode: speech full rate or half rate version 3(FR AMR or HR AMR) (65)
MultiRate configuration
Element ID: 0x03
Length: 6
001. .... = Multirate speech version: Adaptive Multirate speech version 1 (1)
...0 .... = NSCB: Noise Suppression Control Bit: Noise Suppression can be used (default) (0)
.... 1... = ICMI: Initial Codec Mode Indicator: The initial codec mode is defined by the Start Mode field (1)
.... ..10 = Start Mode: 2
0... .... = 12,2 kbit/s codec rate: is not part of the subset
.0.. .... = 10,2 kbit/s codec rate: is not part of the subset
..1. .... = 7,95 kbit/s codec rate: is part of the subset
...1 .... = 7,40 kbit/s codec rate: is part of the subset
.... 1... = 6,70 kbit/s codec rate: is part of the subset
.... .1.. = 5,90 kbit/s codec rate: is part of the subset
.... ..0. = 5,15 kbit/s codec rate: is not part of the subset
.... ...0 = 4,75 kbit/s codec rate: is not part of the subset
..10 0000 = AMR Threshold: 16.0 dB (32)
1000 .... = AMR Hysteresis: 4.0 dB (8)
.... 0110 00.. .... = AMR Threshold: 12.0 dB (24)
..01 00.. = AMR Hysteresis: 2.0 dB (4)
.... ..10 0000 .... = AMR Threshold: 16.0 dB (32)
.... 0100 = AMR Hysteresis: 2.0 dB (4)
</pre>
<pre>
GSM A-I/F DTAP - Assignment Failure
Protocol Discriminator: Radio Resources Management messages (6)
DTAP Radio Resources Management Message Type: Assignment Failure (0x2f)
RR Cause
RR cause value: Channel mode unacceptable (9)
</pre>
<pre>
20221103200919685 DCHAN DEBUG lchan(3-0-1-SDCCH8-0)[0x55b6c3e79310]{ESTABLISHED}: (type=SDCCH) SAPI=0 DATA INDICATION (abis_rsl.c:2528)
20221103200919685 DCHAN DEBUG lchan(3-0-1-SDCCH8-0)[0x55b6c3e79310]{ESTABLISHED}: (type=SDCCH) Rx ASSIGNMENT FAILURE (gsm_04_08_rr.c:985)
20221103200919685 DAS DEBUG assignment(msc0-conn16_subscr-IMSI-334070000000890-TMSI-0x11dc2226_3-0-2-TCH_H-0)[0x55b6c3e91b40]{WAIT_RR_ASS_COMPLETE}: Received Event ASSIGNMENT_EV_RR_ASSIGNMENT_FAIL (gsm_04_08_rr.c:1031)
20221103200919685 DAS DEBUG assignment(msc0-conn16_subscr-IMSI-334070000000890-TMSI-0x11dc2226_3-0-2-TCH_H-0)[0x55b6c3e91b40]{WAIT_RR_ASS_COMPLETE}: (bts=3,trx=0,ts=2,ss=0) incrementing rate counter: assignment:failed Received Assignment Failure message (assignment_fsm.c:738)
20221103200919685 DAS DEBUG assignment(msc0-conn16_subscr-IMSI-334070000000890-TMSI-0x11dc2226_3-0-2-TCH_H-0)[0x55b6c3e91b40]{WAIT_RR_ASS_COMPLETE}: (bts=3,trx=0,ts=2,ss=0) incrementing rate counter: bts3 assignment:failed_speech Received Assignment Failure message on speech lchan (assignment_fsm.c:738)
20221103200919685 DAS ERROR assignment(msc0-conn16_subscr-IMSI-334070000000890-TMSI-0x11dc2226_3-0-2-TCH_H-0)[0x55b6c3e91b40]{WAIT_RR_ASS_COMPLETE}: (bts=3,trx=0,ts=2,ss=0) Assignment failed in state WAIT_RR_ASS_COMPLETE, cause RADIO INTERFACE MESSAGE FAILURE: Rx RR Assignment Failure (assignment_fsm.c:739)
20221103200919685 DAS DEBUG assignment(msc0-conn16_subscr-IMSI-334070000000890-TMSI-0x11dc2226_3-0-2-TCH_H-0)[0x55b6c3e91b40]{WAIT_RR_ASS_COMPLETE}: (bts=3,trx=0,ts=2,ss=0) result rate counter already recorded, NOT counting as: assignment:error Assignment failed for other reason (assignment_fsm.c:739)
20221103200919685 DMSC INFO Tx MSC: BSSMAP: ASSIGNMENT FAIL (osmo_bsc_sigtran.c:380)
</pre> OsmoSGSN - Bug #5725 (Resolved): Assert failed mm->gb.mm_state_fsm->state != ST_MM_IDLE sgsn_libg...https://osmocom.org/issues/57252022-10-24T19:16:44Zkeith
<p>Just happened to notice a coredump due to hitting this in sgsn_libgtp.c:771</p>
<pre><code class="c syntaxhl"><span class="n">OSMO_ASSERT</span><span class="p">(</span><span class="n">mm</span><span class="o">-></span><span class="n">gb</span><span class="p">.</span><span class="n">mm_state_fsm</span><span class="o">-></span><span class="n">state</span> <span class="o">!=</span> <span class="n">ST_MM_IDLE</span><span class="p">);</span>
</code></pre> OsmoBSC - Bug #5717 (Resolved): ARFCN wrong in meas report system in multi-band BSShttps://osmocom.org/issues/57172022-10-17T20:53:03Zkeith
<p>If you setup osmo-bsc with two BTS in one band and a third BTS in another band, then it seems that something is messed up with the index to arfcn translation. The meas report system reports the wrong ARFCN. AS much internally as in the meas feed.</p>
<p>It seems to affect Handover, as in HO then doesn't work.</p>
<p>I think it has something to do with this:<br /><pre><code class="c syntaxhl">
<span class="kt">int</span> <span class="nf">gsm48_parse_meas_rep</span><span class="p">(</span><span class="k">struct</span> <span class="n">gsm_meas_rep</span> <span class="o">*</span><span class="n">rep</span><span class="p">,</span> <span class="k">struct</span> <span class="n">msgb</span> <span class="o">*</span><span class="n">msg</span><span class="p">)</span>
<span class="p">{</span>
<span class="k">struct</span> <span class="n">gsm48_hdr</span> <span class="o">*</span><span class="n">gh</span> <span class="o">=</span> <span class="n">msgb_l3</span><span class="p">(</span><span class="n">msg</span><span class="p">);</span>
<span class="kt">uint8_t</span> <span class="o">*</span><span class="n">data</span> <span class="o">=</span> <span class="n">gh</span><span class="o">-></span><span class="n">data</span><span class="p">;</span>
<span class="k">struct</span> <span class="n">gsm_bts</span> <span class="o">*</span><span class="n">bts</span> <span class="o">=</span> <span class="n">msg</span><span class="o">-></span><span class="n">lchan</span><span class="o">-></span><span class="n">ts</span><span class="o">-></span><span class="n">trx</span><span class="o">-></span><span class="n">bts</span><span class="p">;</span>
<span class="k">struct</span> <span class="n">bitvec</span> <span class="o">*</span><span class="n">nbv</span> <span class="o">=</span> <span class="o">&</span><span class="n">bts</span><span class="o">-></span><span class="n">si_common</span><span class="p">.</span><span class="n">neigh_list</span><span class="p">;</span>
<span class="k">struct</span> <span class="n">gsm_meas_rep_cell</span> <span class="o">*</span><span class="n">mrc</span><span class="p">;</span>
<span class="cm">/* SNIP SNIP */</span>
<span class="n">mrc</span> <span class="o">=</span> <span class="o">&</span><span class="n">rep</span><span class="o">-></span><span class="n">cell</span><span class="p">[</span><span class="mi">0</span><span class="p">];</span>
<span class="n">mrc</span><span class="o">-></span><span class="n">rxlev</span> <span class="o">=</span> <span class="n">data</span><span class="p">[</span><span class="mi">3</span><span class="p">]</span> <span class="o">&</span> <span class="mh">0x3f</span><span class="p">;</span>
<span class="n">mrc</span><span class="o">-></span><span class="n">neigh_idx</span> <span class="o">=</span> <span class="n">data</span><span class="p">[</span><span class="mi">4</span><span class="p">]</span> <span class="o">>></span> <span class="mi">3</span><span class="p">;</span>
<span class="n">mrc</span><span class="o">-></span><span class="n">arfcn</span> <span class="o">=</span> <span class="n">bitvec_get_nth_set_bit</span><span class="p">(</span><span class="n">nbv</span><span class="p">,</span> <span class="n">mrc</span><span class="o">-></span><span class="n">neigh_idx</span> <span class="o">+</span> <span class="mi">1</span><span class="p">);</span>
<span class="cm">/*SNIP SNIP */</span>
<span class="p">}</span>
</code></pre></p>
<p>Is that neigh_list getting setup ordered by band or something? I don't really grok all that bitvec.</p> OsmoBSC - Bug #5712 (New): LCLS FSM; Not possible to get out from NO_LONGER_LShttps://osmocom.org/issues/57122022-10-14T23:39:23Zkeith
<p>While working on implementing LCLS Control from a SIP PBX attached to osmo sipcon and osmo-msc, I stumbled here:</p>
<p>With an Active (mobile to mobile) Call, and after having sent SIP re-Invites to take the PBX out of the Loop, the resulting LCLS Connect Control Messages are sent from MSC to connect, osmo-bsc has both call legs in ST_LOCALLY_SWITCHED. All Good. :-)</p>
<p>Now we will issue SIP re-Invites to put the PBX back into the loop, osmo-bsc will get LCLS-CONN-CTRL with control set to GSM0808_LCLS_CSC_RELEASE_LCLS (for both legs), and here the FSM works fine, We get the RELEASE for LEG A and go to LOCALLY_SWITCHED_WAIT_OTHER_BREAK then osmo-msc sends the other release and then both legs are in ST_NO_LONGER_LS. Once again, All good.</p>
<p>Now, let's issue again a SIP re-Invite to take the PBX back out of the loop (we finished playback of "your credit is low" or whatever):</p>
<p>So just to recap:</p>
<p>bssmap_handle_lcls_connect_ctrl() is ALWAYS going to call:</p>
<p>lcls_update_config()</p>
<p>followed by</p>
<p>lcls_apply_config();</p>
<p>OK, so now Leg A gets a GSM0808_LCLS_CSC_CONNECT, we update the config and we get to lcls_no_longer_ls_fn() where:<br />We call lcls_enable_possible() which returns false, because:</p>
<pre><code class="c syntaxhl"> <span class="k">if</span> <span class="p">(</span><span class="n">other_conn</span><span class="o">-></span><span class="n">lcls</span><span class="p">.</span><span class="n">control</span> <span class="o">!=</span> <span class="n">GSM0808_LCLS_CSC_CONNECT</span><span class="p">)</span> <span class="p">{</span>
<span class="n">LOGPFSM</span><span class="p">(</span><span class="n">conn</span><span class="o">-></span><span class="n">lcls</span><span class="p">.</span><span class="n">fi</span><span class="p">,</span> <span class="s">"Not enabling LS due to insufficient other control</span><span class="se">\n</span><span class="s">"</span><span class="p">);</span>
<span class="k">return</span> <span class="nb">false</span><span class="p">;</span>
<span class="p">}</span>
</code></pre><br />we break out of the FSM function here without having done anything, no state change<br />Next we come to apply the config. <br />As we are still in ST_NO_LONGER_LS, we fall off the end of the switch and hit the ASSERT :-(
<p>Now, If I comment that ASSERT it actually works, because when the LCLS_CONN_CTRL for the B-leg comes in right afterwards, we have already changed the config in the A leg (which is now other) and so lcls_enable_possible() returns true, we change to ST_LOCALLY_SWITCHED and fire LCLS_EV_OTHER_ENABLED at the A leg, which, you remember is still in ST_NO_LONGER_LS and now once again we do lcls_enable_possible(), which passes and both legs are now ST_LOCALLY_SWITCHED<br />Yay!</p>
<p>I see various solutions? here:</p>
<ol>
<li>I'm doing something wrong on the MSC side and sending LCLS_CONN_CTRL that osmo-bsc does not and should not expect [1]</li>
<li>The FSM should handle LCLS_EV_APPLY_CFG_CSC in ST_NO_LONGER_LS [2]</li>
<li>We change the state of the A leg to ST_NO_LCLS when lcls_enable_possible() fails? [3]</li>
<li>something else?</li>
</ol>
<p>[1] so BTW, osmo_bsc_lcls.c is peppered with OSMO_ASSERT() - I found out while hacking on this that a misbehaving MSC can very easily crash it with the "wrong" LCLS CONNECT CONTROL messages. Should it not be a little more robust?</p>
<p>[2] Isn't this wrong, if there's no handler for LCLS_EV_APPLY_CFG_CSC in lcls_no_longer_ls_fn() ??<br /><pre><code class="c syntaxhl"> <span class="p">[</span><span class="n">ST_NO_LONGER_LS</span><span class="p">]</span> <span class="o">=</span> <span class="p">{</span>
<span class="p">.</span><span class="n">in_event_mask</span> <span class="o">=</span> <span class="n">S</span><span class="p">(</span><span class="n">LCLS_EV_UPDATE_CFG_CSC</span><span class="p">)</span> <span class="o">|</span>
<span class="n">S</span><span class="p">(</span><span class="n">LCLS_EV_APPLY_CFG_CSC</span><span class="p">)</span> <span class="o">|</span> <span class="cm">/* <- we don't handle this in the action function */</span>
<span class="n">S</span><span class="p">(</span><span class="n">LCLS_EV_CORRELATED</span><span class="p">)</span> <span class="o">|</span>
<span class="n">S</span><span class="p">(</span><span class="n">LCLS_EV_OTHER_ENABLED</span><span class="p">)</span> <span class="o">|</span>
<span class="n">S</span><span class="p">(</span><span class="n">LCLS_EV_OTHER_DEAD</span><span class="p">),</span>
<span class="p">.</span><span class="n">out_state_mask</span> <span class="o">=</span> <span class="n">S</span><span class="p">(</span><span class="n">ST_NO_LONGER_LS</span><span class="p">)</span> <span class="o">|</span>
<span class="n">S</span><span class="p">(</span><span class="n">ST_REQ_LCLS_NOT_SUPP</span><span class="p">)</span> <span class="o">|</span>
<span class="n">S</span><span class="p">(</span><span class="n">ST_LOCALLY_SWITCHED</span><span class="p">),</span>
<span class="p">.</span><span class="n">name</span> <span class="o">=</span> <span class="s">"NO_LONGER_LS"</span><span class="p">,</span>
<span class="p">.</span><span class="n">action</span> <span class="o">=</span> <span class="n">lcls_no_longer_ls_fn</span><span class="p">,</span>
</code></pre></p>
<p>[3] currently the FSM won't allow it.</p> Ericsson RBS 6xxx - Feature #5593 (Resolved): Let's not log at level ERROR due to Fault Reports.https://osmocom.org/issues/55932022-06-28T02:38:38Zkeith
<p>For no real reason other than it is annoying me to have logging at level ERROR:<br />I attach two pcaps of observed Fault Reports that deny the current code.</p>
<p>This one:<br /><pre>
DNM DEBUG abis_om2000.c:2796 Rx MO=CF/00/ff/00 Fault Report, MO State: STARTED
DNM DEBUG abis_om2000.c:2843 Rx MO=CF/00/ff/00 Fault Report: External Condition Map Class 2 (6)
DNM DEBUG abis_om2000.c:2843 Rx MO=CF/00/ff/00 Fault Report: Replacement Unit Map (15)
DNM DEBUG abis_om2000.c:2843 Rx MO=CF/00/ff/00 Fault Report: Internal Fault Map Class 2A Extension (10,21)
DNM ERROR abis_om2000.c:2898 Rx MO=CF/00/ff/00 Fault Report: invalid tlv element!
</pre><br />and this one:<br /><pre>
Jun 20 13:36:54 huautla-bsc osmo-bsc[12475]: DNM ERROR abis_om2000.c:2888 Rx MO=TRXC/00/ff/03 Fault Report: too many tlv elements!
Jun 20 13:36:54 huautla-bsc osmo-bsc[12475]: DNM DEBUG abis_om2000.c:1111 Tx MO=TRXC/00/ff/03 Fault Report ACK
</pre></p>
<p>I have been unable unable to find documentation on TLV element 0xd2</p> libosmo-abis - Bug #5592 (Resolved): E1 pcap: Syscall param write(buf) points to uninitialised by...https://osmocom.org/issues/55922022-06-26T03:27:47Zkeith
<p>I just happened to notice this running osmo-bsc under valgrind.</p>
<pre>
==20097== Syscall param write(buf) points to uninitialised byte(s)
==20097== at 0x4E48471: write (write.c:26)
==20097== by 0x4DA8DE9: osmo_pcap_lapd_write (lapd_pcap.c:168)
==20097== by 0x4DA8433: send_ph_data_req (lapd.c:628)
==20097== by 0x4C94F5C: lapd_send_rej (lapd_core.c:536)
==20097== by 0x4C9A08A: lapd_rx_i (lapd_core.c:1574)
==20097== by 0x4C9AA8F: lapd_ph_data_ind (lapd_core.c:1708)
==20097== by 0x4DA7C55: lapd_receive (lapd.c:496)
==20097== by 0x4D96B2C: e1inp_rx_ts_lapd (e1_input.c:778)
==20097== by 0x4D9C97C: handle_ts_sign_read (e1d.c:78)
==20097== by 0x4D9D908: e1d_fd_cb (e1d.c:281)
==20097== by 0x4D1281B: poll_disp_fds (select.c:361)
==20097== by 0x4D12928: _osmo_select_main (select.c:399)
==20097== Address 0x1ffefffed7 is on thread 1's stack
==20097== in frame #1, created by osmo_pcap_lapd_write (lapd_pcap.c:129)
==20097==
</pre> OsmoBSC - Feature #5586 (New): Ericsson RBS could recover Unlocked state without osmo-bsc restarthttps://osmocom.org/issues/55862022-06-21T22:23:37Zkeith
<p>It seems something can happen and we get into a Administrative Locked state.</p>
<p>I'm not sure if there may be a way to fully reset all FSMs and restart the BTS with some vty commands, but even if there is, this requires manual intervention.</p>
<p>Maybe there is some way we could automatically re-trigger a full FSM reset and reinitialisation in the case that we see something like whatever happened in this log snippet at Jun 21 15:17:28</p>
<p>In this case there was nothing to do other than restart osmo-msc anyway, as all TRX were Locked.</p>
<pre>
Jun 21 15:16:46 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: call (re-)establishment (ra=0x45, neci=0x01, chreq_reason=0x02)
Jun 21 15:16:46 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:1257 lchan(0-1-7-TCH_F-0)[0x5637f32cef60]{WAIT_RF_RELEASE_ACK}: (type=TCH_F) CONNECTION FAIL (cause=Remote Transco
Jun 21 15:16:48 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:623 -> ASSIGNMENT COMMAND tch_mode=0x01
Jun 21 15:16:50 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 2 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:16:51 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: call (re-)establishment (ra=0x4d, neci=0x01, chreq_reason=0x02)
Jun 21 15:16:51 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: answer to paging (ra=0x82, neci=0x01, chreq_reason=0x01)
Jun 21 15:16:52 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: call (re-)establishment (ra=0x43, neci=0x01, chreq_reason=0x02)
Jun 21 15:16:52 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:623 -> ASSIGNMENT COMMAND tch_mode=0x01
Jun 21 15:16:52 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:623 -> ASSIGNMENT COMMAND tch_mode=0x01
Jun 21 15:16:53 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x1a, neci=0x01, chreq_reason=0x04)
Jun 21 15:16:53 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x13, neci=0x01, chreq_reason=0x04)
Jun 21 15:16:55 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 2 RR-Cause: 0x0 'Normal event'
Jun 21 15:16:55 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: call (re-)establishment (ra=0x4f, neci=0x01, chreq_reason=0x02)
Jun 21 15:16:56 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: Location updating (ra=0x0c, neci=0x01, chreq_reason=0x03)
Jun 21 15:16:56 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:623 -> ASSIGNMENT COMMAND tch_mode=0x01
Jun 21 15:16:57 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:1257 lchan(0-1-6-TCH_F-0)[0x5637f32cd1c0]{WAIT_BEFORE_RF_RELEASE}: (type=TCH_F) CONNECTION FAIL (cause=Remote Tran
Jun 21 15:16:57 huautla-bsc osmo-bsc[12475]: DLMGCP ERROR mgcp_client_fsm.c:281 MGCP_CONN(to-MSC)[0x5637f33996a0]{ST_CRCX_RESP}: MGW/CRCX: response yields error: 540 FAIL
Jun 21 15:16:57 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: answer to paging (ra=0x89, neci=0x01, chreq_reason=0x01)
Jun 21 15:16:57 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 4 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:16:58 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 2 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:16:58 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: Location updating (ra=0x09, neci=0x01, chreq_reason=0x03)
Jun 21 15:16:59 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: answer to paging (ra=0x9d, neci=0x01, chreq_reason=0x01)
Jun 21 15:16:59 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:623 -> ASSIGNMENT COMMAND tch_mode=0x01
Jun 21 15:16:59 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x16, neci=0x01, chreq_reason=0x04)
Jun 21 15:16:59 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 2 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:00 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:2494 lchan(0-2-3-SDCCH8-1)[0x5637f32cab50]{ESTABLISHED}: (type=SDCCH) ERROR INDICATION cause=Timer T200 expired (N
Jun 21 15:17:01 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 3 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:01 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x1f, neci=0x01, chreq_reason=0x04)
Jun 21 15:17:01 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: Location updating (ra=0x06, neci=0x01, chreq_reason=0x03)
Jun 21 15:17:02 huautla-bsc osmo-bsc[12475]: DAS ERROR assignment_fsm.c:984 assignment(msc0-conn104282_subscr-IMSI-334020509263036-TMSI-0x67cc9114_0-3-7-TCH_F-0)[0x5637f341f770]{WAIT
Jun 21 15:17:02 huautla-bsc osmo-bsc[12475]: DAS ERROR assignment_fsm.c:162 assignment(msc0-conn104282_subscr-IMSI-334020509263036-TMSI-0x67cc9114_0-3-7-TCH_F-0)[0x5637f341f770]{WAIT
Jun 21 15:17:02 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 1 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:02 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:2494 lchan(0-3-0-SDCCH8-0)[0x5637f32c3df0]{ESTABLISHED}: (type=SDCCH) ERROR INDICATION cause=Timer T200 expired (N
Jun 21 15:17:02 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 2 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:03 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:03 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:03 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 2 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:03 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:1257 lchan(0-1-2-TCH_F-0)[0x5637f32c91c0]{ESTABLISHED}: (type=TCH_F) CONNECTION FAIL (cause=Remote Transcoder Fail
Jun 21 15:17:03 huautla-bsc osmo-bsc[12475]: DMSC ERROR osmo_bsc_bssap.c:1284 SUBSCR_CONN(msc0-conn104284_subscr-IMSI-334020437435608-TMSI-0x7343ead6)[0x5637f33decc0]{WAIT_CLEAR_CMD}
Jun 21 15:17:03 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 2 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:04 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 2 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:04 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:2494 lchan(0-3-0-SDCCH8-0)[0x5637f32c3df0]{WAIT_BEFORE_RF_RELEASE}: (type=SDCCH) ERROR INDICATION cause=Timer T200
Jun 21 15:17:04 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x10, neci=0x01, chreq_reason=0x04)
Jun 21 15:17:04 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:04 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:1257 lchan(0-2-7-TCH_F-0)[0x5637f32ced20]{WAIT_BEFORE_RF_RELEASE}: (type=TCH_F) CONNECTION FAIL (cause=Remote Tran
Jun 21 15:17:05 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(66) greater than 63
Jun 21 15:17:05 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:1257 lchan(0-3-6-TCH_F-0)[0x5637f32cd910]{WAIT_BEFORE_RF_RELEASE}: (type=TCH_F) CONNECTION FAIL (cause=Remote Tran
Jun 21 15:17:06 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 4 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:06 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:06 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:2494 lchan(0-2-3-SDCCH8-4)[0x5637f32c9020]{ESTABLISHED}: (type=SDCCH) ERROR INDICATION cause=Timer T200 expired (N
Jun 21 15:17:06 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: answer to paging (ra=0x84, neci=0x01, chreq_reason=0x01)
Jun 21 15:17:07 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:08 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: call (re-)establishment (ra=0x45, neci=0x01, chreq_reason=0x02)
Jun 21 15:17:08 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:08 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:08 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 2 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:08 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 2 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:09 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:623 -> ASSIGNMENT COMMAND tch_mode=0x01
Jun 21 15:17:09 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:10 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:1257 lchan(0-1-4-TCH_F-0)[0x5637f32cb980]{WAIT_BEFORE_RF_RELEASE}: (type=TCH_F) CONNECTION FAIL (cause=Remote Tran
Jun 21 15:17:10 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:11 huautla-bsc osmo-bsc[12475]: DAS ERROR assignment_fsm.c:737 assignment(msc0-conn104292_subscr-IMSI-334020349378157-TMSI-0x20694a35_0-3-7-TCH_F-0)[0x5637f33321d0]{WAIT
Jun 21 15:17:11 huautla-bsc osmo-bsc[12475]: DAS ERROR assignment_fsm.c:162 assignment(msc0-conn104292_subscr-IMSI-334020349378157-TMSI-0x20694a35_0-3-7-TCH_F-0)[0x5637f33321d0]{WAIT
Jun 21 15:17:11 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 1 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:12 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x16, neci=0x01, chreq_reason=0x04)
Jun 21 15:17:13 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x17, neci=0x01, chreq_reason=0x04)
Jun 21 15:17:17 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(66) greater than 63
Jun 21 15:17:17 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x14, neci=0x01, chreq_reason=0x04)
Jun 21 15:17:18 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(66) greater than 63
Jun 21 15:17:18 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 2 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:18 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: answer to paging (ra=0x92, neci=0x01, chreq_reason=0x01)
Jun 21 15:17:19 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 0 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:19 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:19 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: answer to paging (ra=0x89, neci=0x01, chreq_reason=0x01)
Jun 21 15:17:19 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: call (re-)establishment (ra=0x43, neci=0x01, chreq_reason=0x02)
Jun 21 15:17:19 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 1 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:20 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 2 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:20 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:20 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:1257 lchan(0-1-5-TCH_F-0)[0x5637f32ccaa0]{WAIT_BEFORE_RF_RELEASE}: (type=TCH_F) CONNECTION FAIL (cause=Remote Tran
Jun 21 15:17:20 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:1257 lchan(0-3-2-TCH_F-0)[0x5637f32c9500]{WAIT_BEFORE_RF_RELEASE}: (type=TCH_F) CONNECTION FAIL (cause=Remote Tran
Jun 21 15:17:20 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 3 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:21 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:21 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:623 -> ASSIGNMENT COMMAND tch_mode=0x01
Jun 21 15:17:21 huautla-bsc osmo-bsc[12475]: DLMGCP ERROR mgcp_client_fsm.c:281 MGCP_CONN(to-MSC)[0x5637f32d5330]{ST_CRCX_RESP}: MGW/CRCX: response yields error: 540 FAIL
Jun 21 15:17:21 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: Location updating (ra=0x04, neci=0x01, chreq_reason=0x03)
Jun 21 15:17:22 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x16, neci=0x01, chreq_reason=0x04)
Jun 21 15:17:22 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:23 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(67) greater than 63
Jun 21 15:17:24 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1923 (bts=0) Ignoring CHAN RQD: Access Delay(66) greater than 63
Jun 21 15:17:25 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: call (re-)establishment (ra=0x40, neci=0x01, chreq_reason=0x02)
Jun 21 15:17:25 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: call (re-)establishment (ra=0x4f, neci=0x01, chreq_reason=0x02)
Jun 21 15:17:26 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: answer to paging (ra=0x92, neci=0x01, chreq_reason=0x01)
Jun 21 15:17:26 huautla-bsc osmo-bsc[12475]: DAS ERROR assignment_fsm.c:984 assignment(msc0-conn104298_subscr-IMSI-334020534773701-TMSI-0x41be1d16_0-3-7-TCH_F-0)[0x5637f3337310]{WAIT
Jun 21 15:17:26 huautla-bsc osmo-bsc[12475]: DAS ERROR assignment_fsm.c:162 assignment(msc0-conn104298_subscr-IMSI-334020534773701-TMSI-0x41be1d16_0-3-7-TCH_F-0)[0x5637f3337310]{WAIT
Jun 21 15:17:28 huautla-bsc osmo-bsc[12475]: DLMGCP ERROR mgcp_client_endpoint_fsm.c:626 Invalid MGW endpoint request: no ci
Jun 21 15:17:28 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x1f, neci=0x01, chreq_reason=0x04)
Jun 21 15:17:28 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:28 huautla-bsc osmo-bsc[12475]: DRSL NOTICE osmo_bsc_main.c:322 (bts=0,trx=0) bootstrapping RSL on ARFCN 247 using MCC-MNC 334-07 LAC=274 CID=100 BSIC=63
Jun 21 15:17:28 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 Serving cell: 241 245 247 251
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI2 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI5 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI1: 55 06 19 8e 78 8a 20 00 00 00 00 00 00 00 00 00 00 00 00 e5 04 00 6b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI2: 59 06 1a 8e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 ff e5 04 00
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI2bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI2ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI2quater: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI3: 49 06 1b 00 64 33 f4 70 01 12 c8 03 05 27 43 40 e5 04 00 29 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI4: 31 06 1c 33 f4 70 01 12 43 40 e5 04 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI5: 06 1d 9e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI6: 06 1e 00 64 33 f4 70 01 12 27 ff 3b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-0-0-CCCH)[0x5637f3295b20]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-0-1-SDCCH8)[0x5637f32962a0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-0-2-SDCCH8)[0x5637f3296aa0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-0-3-TCH_F)[0x5637f32972a0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-0-4-TCH_F)[0x5637f3297aa0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-0-5-TCH_F)[0x5637f3298330]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-0-6-TCH_F)[0x5637f3298bc0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-0-7-TCH_F)[0x5637f3299450]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=3,ss=0): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DCHAN ERROR lchan_fsm.c:1803 lchan(0-3-7-TCH_F-0)[0x5637f32cf2a0]{WAIT_RF_RELEASE_ACK}: (type=TCH_F) lchan failure in state WAIT_RF_RELEA
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=2,ts=3,ss=0): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=0,ss=4): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: call (re-)establishment (ra=0x46, neci=0x01, chreq_reason=0x02)
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=2,ts=3,ss=1): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=4,ss=0): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL INFO abis_rsl.c:1932 (bts=0) CHAN RQD: reason: other (ra=0x18, neci=0x01, chreq_reason=0x04)
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=0,ss=5): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=5,ss=0): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DCHAN ERROR abis_rsl.c:2494 lchan(0-3-0-SDCCH8-6)[0x5637f32c7c20]{ESTABLISHED}: (type=SDCCH) ERROR INDICATION cause=Timer T200 expired (N
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 6 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=0,ss=1): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG gsm_04_08_rr.c:329 Sending Channel Release: Chan: Number: 2 Type: 1 RR-Cause: 0x0 'Normal event'
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=0,ss=2): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL NOTICE osmo_bsc_main.c:322 (bts=0,trx=3) bootstrapping RSL on ARFCN 245 using MCC-MNC 334-07 LAC=274 CID=100 BSIC=63
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI5 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI5: 06 1d 9e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI6: 06 1e 00 64 33 f4 70 01 12 27 ff 3b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-0-SDCCH8)[0x5637f32abeb0]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-1-TCH_F)[0x5637f32ac330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-2-TCH_F)[0x5637f32acb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-3-TCH_F)[0x5637f32ad330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-4-TCH_F)[0x5637f32adb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-5-TCH_F)[0x5637f32ae330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-6-TCH_F)[0x5637f32aeb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-7-TCH_F)[0x5637f32af3c0]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL NOTICE osmo_bsc_main.c:322 (bts=0,trx=3) bootstrapping RSL on ARFCN 245 using MCC-MNC 334-07 LAC=274 CID=100 BSIC=63
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI5 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI5: 06 1d 9e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI6: 06 1e 00 64 33 f4 70 01 12 27 ff 3b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-0-SDCCH8)[0x5637f32abeb0]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-1-TCH_F)[0x5637f32ac330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-2-TCH_F)[0x5637f32acb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-3-TCH_F)[0x5637f32ad330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-4-TCH_F)[0x5637f32adb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-5-TCH_F)[0x5637f32ae330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-6-TCH_F)[0x5637f32aeb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-7-TCH_F)[0x5637f32af3c0]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=4,ss=0): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL NOTICE osmo_bsc_main.c:322 (bts=0,trx=2) bootstrapping RSL on ARFCN 251 using MCC-MNC 334-07 LAC=274 CID=100 BSIC=63
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI5 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI5: 06 1d 9e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI6: 06 1e 00 64 33 f4 70 01 12 27 ff 3b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-0-SDCCH8)[0x5637f32a53a0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-1-SDCCH8)[0x5637f32a5820]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-2-SDCCH8)[0x5637f32a6020]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-3-SDCCH8)[0x5637f32a6820]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-4-TCH_F)[0x5637f32a7020]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-5-TCH_F)[0x5637f32a7820]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-6-TCH_F)[0x5637f32a8020]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-7-TCH_F)[0x5637f32a88b0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=0,ss=2): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL NOTICE osmo_bsc_main.c:322 (bts=0,trx=2) bootstrapping RSL on ARFCN 251 using MCC-MNC 334-07 LAC=274 CID=100 BSIC=63
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI5 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI5: 06 1d 9e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI6: 06 1e 00 64 33 f4 70 01 12 27 ff 3b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-0-SDCCH8)[0x5637f32a53a0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-1-SDCCH8)[0x5637f32a5820]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-2-SDCCH8)[0x5637f32a6020]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-3-SDCCH8)[0x5637f32a6820]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-4-TCH_F)[0x5637f32a7020]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-5-TCH_F)[0x5637f32a7820]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-6-TCH_F)[0x5637f32a8020]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-7-TCH_F)[0x5637f32a88b0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=1,ss=0): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=0,ss=4): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=0,ss=5): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL NOTICE osmo_bsc_main.c:322 (bts=0,trx=2) bootstrapping RSL on ARFCN 251 using MCC-MNC 334-07 LAC=274 CID=100 BSIC=63
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI5 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI5: 06 1d 9e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI6: 06 1e 00 64 33 f4 70 01 12 27 ff 3b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-0-SDCCH8)[0x5637f32a53a0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-1-SDCCH8)[0x5637f32a5820]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-2-SDCCH8)[0x5637f32a6020]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-3-SDCCH8)[0x5637f32a6820]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-4-TCH_F)[0x5637f32a7020]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-5-TCH_F)[0x5637f32a7820]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-6-TCH_F)[0x5637f32a8020]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-7-TCH_F)[0x5637f32a88b0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=0,ss=1): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL NOTICE osmo_bsc_main.c:322 (bts=0,trx=2) bootstrapping RSL on ARFCN 251 using MCC-MNC 334-07 LAC=274 CID=100 BSIC=63
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI5 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI5: 06 1d 9e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI6: 06 1e 00 64 33 f4 70 01 12 27 ff 3b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-0-SDCCH8)[0x5637f32a53a0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-1-SDCCH8)[0x5637f32a5820]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-2-SDCCH8)[0x5637f32a6020]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-3-SDCCH8)[0x5637f32a6820]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-4-TCH_F)[0x5637f32a7020]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-5-TCH_F)[0x5637f32a7820]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-6-TCH_F)[0x5637f32a8020]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-2-7-TCH_F)[0x5637f32a88b0]{UNUSED}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLGLOBAL ERROR write_queue.c:127 wqueue(0x5637f2460180) is full. Rejecting msgb
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DMEAS ERROR meas_feed.c:88 meas_feed (bts=0,trx=3,ts=0,ss=3): sending measurement report failed
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM NOTICE bts_ericsson_rbs2000.c:47 bootstrapping OML for TRX 0/2
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM NOTICE bts_ericsson_rbs2000.c:47 bootstrapping OML for TRX 0/2
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL NOTICE osmo_bsc_main.c:322 (bts=0,trx=3) bootstrapping RSL on ARFCN 245 using MCC-MNC 334-07 LAC=274 CID=100 BSIC=63
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI5 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI5: 06 1d 9e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI6: 06 1e 00 64 33 f4 70 01 12 27 ff 3b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-0-SDCCH8)[0x5637f32abeb0]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-1-TCH_F)[0x5637f32ac330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-2-TCH_F)[0x5637f32acb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-3-TCH_F)[0x5637f32ad330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-4-TCH_F)[0x5637f32adb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-5-TCH_F)[0x5637f32ae330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-6-TCH_F)[0x5637f32aeb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-7-TCH_F)[0x5637f32af3c0]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DNM DEBUG bts_ericsson_rbs2000.c:120 inp_sig_cb(): Input signal 'TEI-UP' received
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRSL NOTICE osmo_bsc_main.c:322 (bts=0,trx=3) bootstrapping RSL on ARFCN 245 using MCC-MNC 334-07 LAC=274 CID=100 BSIC=63
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR INFO system_information.c:725 SI5 Neighbour cells in same band: 249
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI5: 06 1d 9e 7c 80 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5bis: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:355 SI5ter: OFF
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DRR DEBUG bts_trx.c:353 SI6: 06 1e 00 64 33 f4 70 01 12 27 ff 3b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-0-SDCCH8)[0x5637f32abeb0]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-1-TCH_F)[0x5637f32ac330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-2-TCH_F)[0x5637f32acb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-3-TCH_F)[0x5637f32ad330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-4-TCH_F)[0x5637f32adb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-5-TCH_F)[0x5637f32ae330]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-6-TCH_F)[0x5637f32aeb30]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DTS ERROR osmo_bsc_main.c:359 timeslot(0-3-7-TCH_F)[0x5637f32af3c0]{IN_USE}: Event TS_EV_RSL_READY not permitted
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=1) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=0) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=1) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=2) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=3) discarding RSL message received in locked administrative state
Jun 21 15:17:29 huautla-bsc osmo-bsc[12475]: DLMI ERROR e1_config.c:133 (bts=0,trx=0) discarding RSL message received in locked administrative state
</pre> OsmoMGW - Bug #5577 (Rejected): Not able to find a free endpointhttps://osmocom.org/issues/55772022-06-12T15:33:04Zkeith
<pre>
20220612103006461 DLMGCP ERROR (trunk:0) Not able to find a free endpoint (mgcp_endp.c:290)
20220612103006461 DLMGCP NOTICE CRCX: cannot find endpoint "rtpbridge/*@mgw", cause=403 -- trying to identify trunk... (mgcp_protocol.c:398)
20220612103006461 DLMGCP NOTICE endpoint:none CRCX: creating new connection ... (mgcp_protocol.c:855)
20220612103006461 DLMGCP ERROR endpoint:none CRCX: no free endpoints available! (mgcp_protocol.c:860)
</pre>
<p>Indeed, "show mgcp active" shows all EP in use, but there are zero active calls.</p> OsmoBSC - Bug #5572 (Resolved): segfault with osmo-BSC in osmo_mgcpc_ep_ci_request (rare)https://osmocom.org/issues/55722022-05-26T02:43:08Zkeith
<p>The line that crashed was added in <a class="external" href="https://cgit.osmocom.org/osmo-mgw/commit/?id=3ff71284fa90e5c26963db860590054f41169970">https://cgit.osmocom.org/osmo-mgw/commit/?id=3ff71284fa90e5c26963db860590054f41169970</a></p>
<p>We can run for a few days before hitting this.</p>
<p>I don't have much relevant lead-up log captured at this time, only a backtrace.<br />Last Log line on the console is:<br /><pre>
DMSC ERROR osmo_bsc_bssap.c:1284 SUBSCR_CONN(msc0-conn43820_subscr-IMSI-334020218960160-TMSI-0x6919a240)[0x555555aded00]{WAIT_CLEAR_CMD}: Event MT_DTAP not permitted
</pre></p>
<pre>
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff79ebd6d in osmo_mgcpc_ep_ci_request (ci=0x555555b2d570, verb=MGCP_VERB_DLCX, verb_info=0x0, notify=0x0, event_success=0, event_failure=0, notify_data=0x0)
at mgcp_client_endpoint_fsm.c:665
665 LOG_CI_VERB(ci, LOGL_DEBUG, "notify=%s\n", osmo_fsm_inst_name(ci->notify.fi));
(gdb) bt
#0 0x00007ffff79ebd6d in osmo_mgcpc_ep_ci_request (ci=0x555555b2d570, verb=MGCP_VERB_DLCX, verb_info=0x0, notify=0x0, event_success=0, event_failure=0, notify_data=0x0)
at mgcp_client_endpoint_fsm.c:665
#1 0x000055555559d52d in osmo_mgcpc_ep_ci_dlcx (ci=0x555555b2d570) at /usr/local/include/osmocom/mgcp_client/mgcp_client_endpoint_fsm.h:42
#2 0x000055555559d802 in assignment_reset (conn=0x555555b367c0) at assignment_fsm.c:134
#3 0x00005555555c84ad in gscon_release_lchans (conn=0x555555b367c0, do_rr_release=true, cause_rr=GSM48_RR_CAUSE_NORMAL) at bsc_subscr_conn_fsm.c:260
#4 0x00005555555c824e in gscon_fsm_wait_sccp_rlsd_onenter (fi=0x555555aded00, prev_state=6) at bsc_subscr_conn_fsm.c:215
#5 0x00007ffff7ad09d4 in state_chg (fi=0x555555aded00, new_state=7, keep_timer=false, timeout_ms=60000, T=-4, file=0x5555556b8876 "bsc_subscr_conn_fsm.c", line=971)
at fsm.c:694
#6 0x00007ffff7ad0a37 in _osmo_fsm_inst_state_chg (fi=0x555555aded00, new_state=7, timeout_secs=60, T=-4, file=0x5555556b8876 "bsc_subscr_conn_fsm.c", line=971) at fsm.c:743
#7 0x00007ffff7aebe4b in _osmo_tdef_fsm_inst_state_chg (fi=0x555555aded00, state=7, timeouts_array=0x55555571d300 <conn_fsm_timeouts>,
tdefs=0x5555557281a0 <gsm_network_T_defs>, default_timeout=-1, file=0x5555556b8876 "bsc_subscr_conn_fsm.c", line=971) at tdef.c:357
#8 0x00005555555cc763 in gscon_fsm_allstate (fi=0x555555aded00, event=4, data=0x7fffffffcd1c) at bsc_subscr_conn_fsm.c:971
#9 0x00007ffff7ad133e in _osmo_fsm_inst_dispatch (fi=0x555555aded00, event=4, data=0x7fffffffcd1c, file=0x5555556e8c96 "osmo_bsc_bssap.c", line=438) at fsm.c:860
#10 0x000055555566f32b in bssmap_handle_clear_cmd (conn=0x555555b367c0, msg=0x555555b19d00, length=4) at osmo_bsc_bssap.c:438
#11 0x0000555555673a0e in bssmap_rcvmsg_dt1 (conn=0x555555b367c0, msg=0x555555b19d00, length=4) at osmo_bsc_bssap.c:1172
#12 0x0000555555674997 in bsc_handle_dt (conn=0x555555b367c0, msg=0x555555b19d00, len=6) at osmo_bsc_bssap.c:1360
#13 0x000055555567fb3a in handle_data_from_msc (conn=0x555555b367c0, msg=0x555555b19d00) at osmo_bsc_sigtran.c:141
#14 0x0000555555680598 in sccp_sap_up (oph=0x555555b19d88, _scu=0x555555a61ca0) at osmo_bsc_sigtran.c:256
#15 0x00007ffff7a1acd4 in sccp_user_prim_up (scu=0x555555a61ca0, prim=0x555555b19d88) at sccp_user.c:177
#16 0x00007ffff7a17da2 in scu_gen_encode_and_send (conn=0x555555b3e690, event=11, xua=0x555555b189f0, primitive=1, operation=PRIM_OP_INDICATION) at sccp_scoc.c:805
#17 0x00007ffff7a188ee in scoc_fsm_active (fi=0x555555aaf730, event=11, data=0x555555b189f0) at sccp_scoc.c:1124
#18 0x00007ffff7ad162d in _osmo_fsm_inst_dispatch (fi=0x555555aaf730, event=11, data=0x555555b189f0, file=0x7ffff7a3bc68 "sccp_scoc.c", line=1698) at fsm.c:872
#19 0x00007ffff7a19daa in sccp_scoc_rx_from_scrc (inst=0x555555a61b00, xua=0x555555b189f0) at sccp_scoc.c:1698
#20 0x00007ffff7a150fd in scrc_rx_mtp_xfer_ind_xua (inst=0x555555a61b00, xua=0x555555b189f0) at sccp_scrc.c:479
#21 0x00007ffff7a1ae48 in mtp_user_prim_cb (oph=0x555555af8cc8, ctx=0x555555a61b00) at sccp_user.c:202
#22 0x00007ffff7a294a6 in deliver_to_mtp_user (osu=0x555555a61b48, xua=0x555555ad1120) at osmo_ss7_hmrt.c:95
#23 0x00007ffff7a29673 in hmdt_message_for_distribution (inst=0x555555a2b3c0, xua=0x555555ad1120) at osmo_ss7_hmrt.c:134
#24 0x00007ffff7a2a0a7 in m3ua_hmdc_rx_from_l2 (inst=0x555555a2b3c0, xua=0x555555ad1120) at osmo_ss7_hmrt.c:278
#25 0x00007ffff7a0b37f in m3ua_rx_xfer (asp=0x555555a602d0, xua=0x555555ad1120) at m3ua.c:577
#26 0x00007ffff7a0bb9b in m3ua_rx_msg (asp=0x555555a602d0, msg=0x555555adb750) at m3ua.c:732
#27 0x00007ffff7a27668 in xua_cli_read_cb (conn=0x555555a60bd0) at osmo_ss7.c:1950
#28 0x00007ffff7a96a3d in osmo_stream_cli_read (cli=0x555555a60bd0) at stream.c:327
#29 0x00007ffff7a9717f in osmo_stream_cli_fd_cb (ofd=0x555555a60bd0, what=1) at stream.c:446
#30 0x00007ffff7ac881c in poll_disp_fds (n_fd=12) at select.c:361
#31 0x00007ffff7ac8929 in _osmo_select_main (polling=0) at select.c:399
#32 0x00007ffff7ac8997 in osmo_select_main_ctx (polling=0) at select.c:455
#33 0x00005555555797f9 in main (argc=3, argv=0x7fffffffe4b8) at osmo_bsc_main.c:1043
</pre>
<pre>
(gdb) info locals
ep = 0x555555b2d350
fi = 0x555555b18960
cleared_ci = {ep = 0x555555b2d350, occupied = true, label = '\000' <repeats 63 times>, mgcp_client_fi = 0x0, pending = false, sent = false, verb = MGCP_VERB_DLCX, verb_info = {
addr = '\000' <repeats 45 times>, port = 0, endpoint = '\000' <repeats 511 times>, call_id = 0, ptime = 0, codecs = {CODEC_PCMU_8000_1, CODEC_PCMU_8000_1,
CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1}, codecs_len = 0,
ptmap = {{codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {
codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {
codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}}, ptmap_len = 0, x_osmo_ign = 0, x_osmo_osmux_use = false, x_osmo_osmux_cid = 0,
conn_mode = MGCP_CONN_NONE, param_present = false, param = {amr_octet_aligned_present = false, amr_octet_aligned = false}}, notify = {entry = {next = 0x0, prev = 0x0},
fi = 0x0, success = 0, failure = 0, data = 0x0}, got_port_info = false, rtp_info = {addr = '\000' <repeats 45 times>, port = 0, endpoint = '\000' <repeats 511 times>,
call_id = 0, ptime = 0, codecs = {CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1,
CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1}, codecs_len = 0, ptmap = {{codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {
codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {
codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}}, ptmap_len = 0,
x_osmo_ign = 0, x_osmo_osmux_use = false, x_osmo_osmux_cid = 0, conn_mode = MGCP_CONN_NONE, param_present = false, param = {amr_octet_aligned_present = false,
amr_octet_aligned = false}}, mgcp_ci_str = '\000' <repeats 32 times>}
(gdb) p ci
$1 = (struct osmo_mgcpc_ep_ci *) 0x555555b2d570
(gdb) p *ci
$2 = {ep = 0x555555b2d350, occupied = true, label = '\000' <repeats 63 times>, mgcp_client_fi = 0x0, pending = false, sent = false, verb = MGCP_VERB_DLCX, verb_info = {
addr = '\000' <repeats 45 times>, port = 0, endpoint = '\000' <repeats 511 times>, call_id = 0, ptime = 0, codecs = {CODEC_PCMU_8000_1, CODEC_PCMU_8000_1,
CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1}, codecs_len = 0,
ptmap = {{codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {
codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {
codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}}, ptmap_len = 0, x_osmo_ign = 0, x_osmo_osmux_use = false, x_osmo_osmux_cid = 0,
conn_mode = MGCP_CONN_NONE, param_present = false, param = {amr_octet_aligned_present = false, amr_octet_aligned = false}}, notify = {entry = {next = 0x0, prev = 0x0},
fi = 0x0, success = 0, failure = 0, data = 0x0}, got_port_info = false, rtp_info = {addr = '\000' <repeats 45 times>, port = 0, endpoint = '\000' <repeats 511 times>,
call_id = 0, ptime = 0, codecs = {CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1,
CODEC_PCMU_8000_1, CODEC_PCMU_8000_1, CODEC_PCMU_8000_1}, codecs_len = 0, ptmap = {{codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {
codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {
codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}, {codec = CODEC_PCMU_8000_1, pt = 0}}, ptmap_len = 0,
x_osmo_ign = 0, x_osmo_osmux_use = false, x_osmo_osmux_cid = 0, conn_mode = MGCP_CONN_NONE, param_present = false, param = {amr_octet_aligned_present = false,
amr_octet_aligned = false}}, mgcp_ci_str = '\000' <repeats 32 times>}
(gdb) p ci->notify
$3 = {entry = {next = 0x0, prev = 0x0}, fi = 0x0, success = 0, failure = 0, data = 0x0}
</pre> Ericsson RBS 6xxx - Bug #5571 (New): DUG can come up, but with Avail: "Power Off"https://osmocom.org/issues/55712022-05-24T01:48:54Zkeith
<p>Sometimes, after starting osmo-bsc, The BTS will transmit, we even start to get Channel requests, but this is the status: <br /><pre>
OsmoBSC# show trx
TRX 0 of BTS 0 is on ARFCN 251
RF Nominal Power: 37 dBm, reduced by 0 dB, resulting BS power: 37 dBm
Radio Carrier NM State: Oper 'NULL', Admin 'Unlocked', Avail 'Power off'
RSL State: connected
Baseband Transceiver NM State: Oper 'NULL', Admin 'Locked', Avail 'Power off'
E1 Signalling Link:
E1 Line 0, Type e1d: Timeslot 1, Mode RSL
E1 TEI 0, SAPI 0
</pre></p>
<p>and of course we get such as this:</p>
<pre>
DRSL NOTICE <0003> abis_rsl.c:2193 (bts=0) CHAN RQD[Location updating]: no resources for SDCCH 0x4, retrying with TCH_F
DRLL DEBUG <0000> lchan_select.c:299 (bts=0) lchan_select_by_type(TCH_F)
DRLL DEBUG <0000> lchan_select.c:233 (bts=0) lchan_avail_by_type(TCH_F)
DRLL DEBUG <0000> lchan_select.c:65 looking for lchan TCH/F: (bts=0,trx=0) trx not usable
DRLL DEBUG <0000> lchan_select.c:65 looking for lchan TCH/F_PDCH as TCH/F without pchan switch: (bts=0,trx=0) trx not usable
DRLL DEBUG <0000> lchan_select.c:65 looking for lchan TCH/F_PDCH as TCH/F: (bts=0,trx=0) trx not usable
DRLL DEBUG <0000> lchan_select.c:65 looking for lchan TCH/F_TCH/H_SDCCH8_PDCH as TCH/F without pchan switch: (bts=0,trx=0) trx not usable
DRLL DEBUG <0000> lchan_select.c:65 looking for lchan TCH/F_TCH/H_SDCCH8_PDCH as TCH/F: (bts=0,trx=0) trx not usable
DRLL NOTICE <0000> lchan_select.c:305 (bts=0) Failed to select TCH_F channel
</pre>
<p>Stopping and restarting osmo-bsc will sooner ( or later :-/ ) get the TRX up....</p>
<p>Attached is osmo-bsc.log of the bring-up and pcap of same.</p>
<p>I suspect there is something happening in a certain order sometimes that causes this?</p> OsmoMSC - Bug #5559 (Stalled): OsmoMSC at 100% CPU and unresponsive for up to several minutes!https://osmocom.org/issues/55592022-05-12T23:22:09Zkeith
<p>Not much more to say than the title I'm afraid.</p>
<p>So far, I've actually only noticed it on a system using the RBS and osmo-e1d. But I do not have conclusive proof that it is exclusively happening here.</p>
<p>I'm assuming a culprit might be the sms queue, but I'm not convinced because I'm not seeing it on other systems with more messages in the queue in the sqlite db - and this can be upwards of 1,000 SMS queued.</p> OsmoMGW - Bug #5533 (Resolved): MGW memory leak?https://osmocom.org/issues/55332022-04-17T22:59:29Zkeith
<p>Running for about 12 hours:</p>
<pre>
OsmoMGW# show talloc-context application brief
talloc report on 'mgcp-callagent' (total 2421492238 bytes in 8180552 blocks)
telnet_connection contains 265 bytes in 4 blocks (ref 0) 0x5618bbc01c50
/etc/osmocom/osmo-mgw.cfg contains 26 bytes in 1 blocks (ref 0) 0x5618bbbfe670
struct sched_vty_opts contains 72 bytes in 1 blocks (ref 0) 0x5618bbbf7720
abis contains 48772 bytes in 8 blocks (ref 0) 0x5618bbb093e0
logging contains 5246 bytes in 16 blocks (ref 0) 0x5618bbb08d60
msgb contains 2421437856 bytes in 8180521 blocks (ref 0) 0x5618bbb08cf0
</pre>
<pre>
OsmoMGW# show talloc-context application full
full talloc report on 'mgcp-callagent' (total 2431021650 bytes in 8212742 blocks)
telnet_connection contains 89 bytes in 2 blocks (ref 0) 0x5618bbc01c50
struct telnet_connection contains 88 bytes in 1 blocks (ref 0) 0x5618d7e71a50
/etc/osmocom/osmo-mgw.cfg contains 26 bytes in 1 blocks (ref 0) 0x5618bbbfe670
struct sched_vty_opts contains 72 bytes in 1 blocks (ref 0) 0x5618bbbf7720
abis contains 48772 bytes in 8 blocks (ref 0) 0x5618bbb093e0
unixsocket contains 1 bytes in 1 blocks (ref 0) 0x5618bbb09630
ipa contains 1 bytes in 1 blocks (ref 0) 0x5618bbb095c0
e1inp contains 48770 bytes in 5 blocks (ref 0) 0x5618bbb09450
struct e1inp_line contains 48768 bytes in 3 blocks (ref 0) 0x5618bbc02470
struct osmo_use_count_entry contains 40 bytes in 1 blocks (ref 0) 0x5618bbc02350
rate_ctr.c:230 contains 440 bytes in 1 blocks (ref 0) 0x5618bbb47160
e1inp_sign_link contains 1 bytes in 1 blocks (ref 0) 0x5618bbb094c0
logging contains 4818 bytes in 12 blocks (ref 0) 0x5618bbb08d60
vty_logp_doc_str contains 1095 bytes in 1 blocks (ref 0) 0x5618bbb62090
vty_logp_cmd_str contains 208 bytes in 1 blocks (ref 0) 0x5618bbb61f50
vty_log_level_doc_str contains 888 bytes in 1 blocks (ref 0) 0x5618bbb488f0
vty_log_level_cmd_str contains 184 bytes in 1 blocks (ref 0) 0x5618bbb487d0
vty_log_level_doc_str contains 1023 bytes in 1 blocks (ref 0) 0x5618bbb46500
vty_log_level_cmd_str contains 205 bytes in 1 blocks (ref 0) 0x5618bbb463c0
struct log_target contains 310 bytes in 3 blocks (ref 0) 0x5618bbb09230
struct osmo_wqueue contains 96 bytes in 1 blocks (ref 0) 0x7f40194b0090
struct log_category contains 54 bytes in 1 blocks (ref 0) 0x5618bbb09340
struct log_info contains 904 bytes in 2 blocks (ref 0) 0x5618bbb08dd0
struct log_info_cat contains 864 bytes in 1 blocks (ref 0) 0x5618bbb08e60
msgb contains 2430967872 bytes in 8212717 blocks (ref 0) 0x5618bbb08cf0
E1D Raw TS contains 296 bytes in 1 blocks (ref 0) 0x5619b39bab40
E1D Raw TS contains 296 bytes in 1 blocks (ref 0) 0x5619b39ba9b0
E1D Raw TS contains 296 bytes in 1 blocks (ref 0) 0x5619b39ba820
[!! SNIP... SNIP 8,212,740 lines similar to above 3 !!]
E1D Raw TS contains 296 bytes in 1 blocks (ref 0) 0x5618bbc57b20
E1D Raw TS contains 296 bytes in 1 blocks (ref 0) 0x5618bbb443a0
E1D Raw TS contains 296 bytes in 1 blocks (ref 0) 0x5618bbb46c80
mgcp-msg contains 4232 bytes in 1 blocks (ref 0) 0x5618bbc4f790
</pre> OsmoMSC - Bug #5532 (Resolved): Assert failed osmo_use_count_get_put()https://osmocom.org/issues/55322022-04-17T07:10:44Zkeith
<pre>
Apr 16 20:41:30 huautla-bsc osmo-msc[17647]: DMSC ERROR msc_a.c:1685 (IMSI-334020349750006:MSISDN-69610126097:TMSI-0x30156FAD) Cannot tx event to MSC-I, no such role defined
Apr 16 20:41:30 huautla-bsc osmo-msc[17647]: DBSSAP ERROR msc_a.c:881 msc_a(IMSI-334020162777078:MSISDN-69610141108:TMSI-0x4ADE6C87:GERAN-A-112952:CM_SERVICE_REQ)[0x56363376a020]{MSC_A_ST_AUTHENTICATED}: Deallocating active transactions failed
Apr 16 20:41:30 huautla-bsc osmo-msc[17647]: DBSSAP ERROR msc_a.c:881 msc_a(IMSI-334020501994454:MSISDN-69610124271:TMSI-0xB068C7BB:GERAN-A-112949:CM_SERVICE_REQ)[0x5636358a43b0]{MSC_A_ST_AUTHENTICATED}: Deallocating active transactions failed
Apr 16 20:41:30 huautla-bsc osmo-msc[17647]: DBSSAP ERROR msc_a.c:881 msc_a(IMSI-334020547509057:MSISDN-69610143481:TMSI-0x3E52487F:GERAN-A-112942:CM_SERVICE_REQ)[0x563638968e20]{MSC_A_ST_AUTHENTICATED}: Deallocating active transactions failed
Apr 16 20:41:30 huautla-bsc osmo-msc[17647]: DVLR ERROR vlr.c:916 SUBSCR(IMSI-334030256923813:MSISDN-69610142437:TMSI-0x9189A257) Rx GSUP LU Result without LU in progress
Apr 16 20:41:35 huautla-bsc osmo-msc[17647]: DBSSAP ERROR msub.c:360 msc_a(TMSI-0xA8049D6D:GERAN-A-112959:CM_SERVICE_REQ)[0x563635db18d0]{MSC_A_ST_VALIDATE_L3}: Cannot associate with VLR subscr, another connection is already active at IMSI-334020544609239:MSISDN-69610133008:TMSI-0xA8049D6D:GERAN-A-112944:CM_SERVICE_REQ
Apr 16 20:41:35 huautla-bsc osmo-msc[17647]: DBSSAP ERROR msub.c:362 msc_a(IMSI-334020544609239:MSISDN-69610133008:TMSI-0xA8049D6D:GERAN-A-112944:CM_SERVICE_REQ)[0x56363471c6f0]{MSC_A_ST_AUTHENTICATED}: Attempt to associate a second subscriber connection at TMSI-0xA8049D6D:GERAN-A-112959:CM_SERVICE_REQ
Apr 16 20:41:35 huautla-bsc osmo-msc[17647]: DBSSAP ERROR gsm_04_08.c:817 msc_a(TMSI-0xA8049D6D:GERAN-A-112959:CM_SERVICE_REQ)[0x563635db18d0]{MSC_A_ST_RELEASING}: subscriber not allowed to do a CM Service Request
Apr 16 20:41:35 huautla-bsc osmo-msc[17647]: DBSSAP ERROR msc_a.c:1630 msc_a(TMSI-0xA8049D6D:GERAN-A-112959:CM_SERVICE_REQ)[0x563635db18d0]{MSC_A_ST_RELEASING}: RAN decode error (rc=-5) for COMPL_L3 from MSC-I
Apr 16 20:41:36 huautla-bsc osmo-msc[17647]: DMM ERROR gsm_04_08.c:696 msc_a(TMSI-0x3FD0B53C:GERAN-A-112960:CM_SERVICE_REQ)[0x56363689ab60]{MSC_A_ST_COMMUNICATING}: CM Service Request with mismatching mobile identity: TMSI-0x3FD0B53C
Apr 16 20:41:36 huautla-bsc osmo-msc[17647]: Assert failed osmo_use_count_get_put(&msc_a->use_count, msc_a_cm_service_type_to_use(cm_service_type), -1) == 0 gsm_04_08.c:1516
</pre>
<p>Possibly related to problems arising from #5530<br />Of course, It would be nice to recover from whatever this is without a restart of the MSC, as that is quite disruptive.</p> OsmoMSC - Bug #5529 (Resolved): Inter BSC HO fails due to lack of MSC Preferred Codecs IEhttps://osmocom.org/issues/55292022-04-14T09:30:47Zkeith
<p>Since <a class="external" href="https://gerrit.osmocom.org/c/osmo-bsc/+/27405">https://gerrit.osmocom.org/c/osmo-bsc/+/27405</a> osmo-bsc requires the MSC Preferred Codec List IE in an incoming handover request as it should according to 3GPP TS 48.008 3.2.1.8</p>
<p>However, osmo-msc does not send it. TTCN3 tests are passing because the test suite generates the IE but does not require it.</p>
<p>It is suggested on the mailing list that the possible (probable?) easier? better? solution to generating this IE in osmo-msc is to work on the neels/codecs branch. <br />Unfortunately, further to neels' refactoring work on the commits, plus an osmodevcall, it is still maybe representing quite some work load to get that through code review.</p>
<p>A possible workaround (for a locally working system) would be to revert<br /> <a class="external" href="https://cgit.osmocom.org/osmo-bsc/commit/?id=826ec9ff758c8a40fca2eaf6cca7989ff6471c83">https://cgit.osmocom.org/osmo-bsc/commit/?id=826ec9ff758c8a40fca2eaf6cca7989ff6471c83</a></p>