Open Source Mobile Communications: Issues
https://projects.osmocom.org/
https://projects.osmocom.org/favicon.ico?1664741409
2017-02-15T13:45:24Z
Open Source Mobile Communications
Redmine
OsmoTRX - Bug #1951 (Rejected): Location update is hard to be performed using osmo-bts-trx and US...
https://projects.osmocom.org/issues/1951
2017-02-15T13:45:24Z
wirelesss
<p>Two different time-slots configuration has been used while attempts for Location update have been done.<br />It is not possible to perform LU, while using Osmocom style dynamic time-slots.<br />Just one of the test phones (BlackBerry) has attached successfully to NITB, but just for a few moment after this phone has been disconnected from the network. In this case I have used 3 TCH/F, 3 PDCH timeslots configuration for NITB.</p>
<p>I have run B200 with external 10Mhz ref. clock source from GPS Disciplined Oscilator (BG7TBL), but there was no difference to be seen.</p>
<p>Described issue has not been seen with sysmoBTS,nanoBTS and OCTBTS.</p>
<p>hashes: <br />libosmo-abis: 254745880bb2ff7f17fe158fb7bfb5e1dc530906<br />libosmo-netif: 5fd93e02f818aecfc73db66e8064858442122959<br />libosmo-sccp: 0c72c1c0d313321f65fd272840ed8e8ae69a04cd<br />libosmocore: 96c8bc6e76ba1200c96085ecce2ce80ee257a6aa<br />libsmpp34: 63d562c099f11c4d11a952a03bc54659f8b82319<br />openbsc: b726c2c72b5e94d6723fefd04daf21be61eab5a5<br />openggsn: 68d244d3022d41a170f83ddec5050d659aef0bcd<br />osmo-bts-oct: b390dfb90dfd0b38d17cea931ec0d0e194e2a4a1<br />osmo-bts: b390dfb90dfd0b38d17cea931ec0d0e194e2a4a1<br />osmo-pcu: 78ce59137fa0bd0e6b11bfc9ea24c93e6b2a8d2a<br />osmo-trx: 2dee3e996e777b67aa3185f7456c041765f0d71f</p>
OsmoNITB - Bug #1933 (Rejected): voice call drops after B subscriber accepts the call
https://projects.osmocom.org/issues/1933
2017-01-30T17:19:11Z
wirelesss
During the test of nanoBTS (model 165G) and NITB configured with dynamic channels: 3 TCH/H and 3 PDCH, it was found that the initiated voice call drops immediately after B subscriber accepts the call.
<ul>
<li>Selected default voice codec is: tch-h hr.</li>
</ul>
<p>In the eth_tarce.pcap following is shown:</p>
<pre><code>Frame # 41: MODE MODIFY REQuest (0x29)<br /> Channel Mode IE:<br /> Speech coding algorithm: GSM speech coding algorithm version 1: GSM FR or GSM HR (1)
# 42: MODE MODIFY Negative ACKnowledge (0x2b)<br /> Cause IE:<br /> Class: Protocol error (6) <br /> ...
# 45: GSM A-bis OML, Baseband Transceiver(00,00,ff) Failure Event Report <br /> FOM Message Type: Failure Event Report<br /> FOM Attribute ID: Event Type<br /> FOM Attribute Length: 1<br /> Event Type: Processor Failure (0x02)
# 48 Event Type: Processor Failure (0x02)<br /> GSM A-bis OML, Baseband Transceiver(00,00,ff) Failure Event Report</code></pre>
<p>the NITB log file shows :<br /><pre>
...
Mon Jan 30 16:13:42 2017 DRLL <0000> chan_alloc.c:352 (bts=0,trx=0,ts=2,pchan=TCH/H) Allocating lchan=0 as TCH_H
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:1819 (bts=0,trx=0,ts=2,ss=0) Activating ARFCN(870) SS(0) lctype TCH_H r=CALL ra=0x41 ta=0
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:580 (bts=0,trx=0,ts=2,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=0) state NONE -> ACTIVATION REQUESTED
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:1546 (bts=0,trx=0,ts=2,ss=0) CHANNEL ACTIVATE ACK
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=0) state ACTIVATION REQUESTED -> ACTIVE
Mon Jan 30 16:13:42 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 ESTABLISH INDICATION
Mon Jan 30 16:13:42 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=5
Mon Jan 30 16:13:42 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:43 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:43 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=3
Mon Jan 30 16:13:43 2017 DMSC <000a> bsc_api.c:402 Sending ChanModify for speech: SPEECH_V1 on channel TCH_H
Mon Jan 30 16:13:43 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:43 2017 DRSL <0004> abis_rsl.c:2226 (bts=0,trx=0,ts=2,ss=0) IPAC_BIND speech_mode=0x13 RTP_PAYLOAD=96
Mon Jan 30 16:13:43 2017 DRSL <0004> abis_rsl.c:1570 (bts=0,trx=0,ts=2,ss=0) CHANNEL MODE MODIFY NACK
Mon Jan 30 16:13:43 2017 DRSL <0004> abis_rsl.c:2413 (bts=0,trx=0,ts=2,ss=0) IPAC_CRCX_NACK
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:852Unrecognised Cause value.
Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:575## T M/O Pass Failure Reason
Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 0 6 Man FALSE 0858_IE_VALUE_RFU
Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 1 7 Opt Not parsed
Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 2 53 Opt Not parsed
Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 3 54 Opt Not parsed
Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_main.c:399L3 msg parse failure. New msg (0x306) destroyed.
Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01
Mon Jan 30 16:13:44 2017 DRLL <0000> chan_alloc.c:352 (bts=0,trx=0,ts=2,pchan=TCH/H) Allocating lchan=1 as TCH_H
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:1819 (bts=0,trx=0,ts=2,ss=1) Activating ARFCN(870) SS(1) lctype TCH_H r=PAGING ra=0x2a ta=0
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:580 (bts=0,trx=0,ts=2,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=1) state NONE -> ACTIVATION REQUESTED
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:1546 (bts=0,trx=0,ts=2,ss=1) CHANNEL ACTIVATE ACK
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=1) state ACTIVATION REQUESTED -> ACTIVE
Mon Jan 30 16:13:45 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=1) SAPI=0 ESTABLISH INDICATION
Mon Jan 30 16:13:45 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=6
Mon Jan 30 16:13:45 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=1) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:45 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=1) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:45 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=3
Mon Jan 30 16:13:45 2017 DMSC <000a> bsc_api.c:402 Sending ChanModify for speech: SPEECH_V1 on channel TCH_H
Mon Jan 30 16:13:45 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=1) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:45 2017 DRSL <0004> abis_rsl.c:2226 (bts=0,trx=0,ts=2,ss=1) IPAC_BIND speech_mode=0x13 RTP_PAYLOAD=96
Mon Jan 30 16:13:45 2017 DRSL <0004> abis_rsl.c:1570 (bts=0,trx=0,ts=2,ss=1) CHANNEL MODE MODIFY NACK
Mon Jan 30 16:13:45 2017 DRSL <0004> abis_rsl.c:2413 (bts=0,trx=0,ts=2,ss=1) IPAC_CRCX_NACK
</pre></p>
<p>Package: libosmocore<br />Version: 0.9.0-5</p>
<p>hashes:<br />libosmo-abis: 254745880bb2ff7f17fe158fb7bfb5e1dc530906<br />libosmo-netif: 8d3384290ba7c79b290b492dd1279041fb578a9c<br />libosmo-sccp: 0c72c1c0d313321f65fd272840ed8e8ae69a04cd<br />libosmocore: 48f55833476439fc45fa4eaa4327beccdc92d44b<br />libsmpp34: 63d562c099f11c4d11a952a03bc54659f8b82319<br />openbsc: 3f940fc9eea40873185a240e68992e70a3e8abb4</p>
OsmoSGSN - Support #1891 (Closed): Review of user manuals and update of wiki in relation to auth-...
https://projects.osmocom.org/issues/1891
2016-12-20T12:09:47Z
wirelesss
<p>The user manuals review and wiki update to be done with information on all four auth-policy modes:<br />accept-all, closed, acl-only and remote, together with respective examples.</p>
pySim - Bug #1836 (Closed): Re-Synchronization does not work as described in sysmousim-manual
https://projects.osmocom.org/issues/1836
2016-11-03T13:20:15Z
wirelesss
<p>As per received information from our customer in RT# 6830, Re-Synchronization does not work as described in <a class="external" href="https://www.sysmocom.de/downloads/sysmousim-manual.pdf">https://www.sysmocom.de/downloads/sysmousim-manual.pdf</a> <br />Issue has been reproduced and log file attached.</p>
<p>Package: libosmocore<br />Version: 0.9.3.20</p>
OsmoNITB - Bug #1830 (Closed): Sending SMS via VTY after 'silent-call' command provoked multiple ...
https://projects.osmocom.org/issues/1830
2016-10-19T16:54:46Z
wirelesss
<p>During test of a 'silent-call' command followed by sending of SMS via VTY, provoked multiple copies of the same text message to be send to the MS.</p>
<p>Package: libosmocore<br />Version: 0.9.3.20160930<br />APT-Sources: <a class="external" href="http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0">http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0</a> ./ Packages<br />Description: Open Source MObile COMmunications CORE library</p>
<p>Related commands are given below:</p>
<pre>
OpenBSC> subscriber imsi 1640000000071 silent-call start sdcch
OpenBSC> % silent call on ARFCN 870 timeslot 0
OpenBSC> subscriber imsi 1640000000071 sms sender imsi 901700000007802 send .testing_sms_during _silent _call1 <--- after this command multiple copies of SMS ".testing_sms_during _silent _call1" is received.
OpenBSC> subscriber imsi 1640000000071 sms sender imsi 901700000007802 send .testing_sms_during _silent _call2
OpenBSC> subscriber imsi 1640000000071 sms sender imsi 901700000007802 send .testing_sms_during _silent _call3
OpenBSC> subscriber imsi 1640000000071 sms sender imsi 901700000007802 send .testing_sms_during _silent _call4
OpenBSC> subscriber imsi 1640000000071 sms sender imsi 901700000007802 send .testing_sms_during _silent _call5
OpenBSC> subscriber imsi 1640000000071 ussd-notify 1 .probe
OpenBSC> subscriber imsi 1640000000071 sms sender imsi 901700000007802 send .testing_sms_during _silent _call5
OpenBSC> subscriber imsi 1640000000071 silent-call stop <--- command 'silent-call stop' stopped receipt of the SMSs.
</pre>
<p>pcap file is attached.</p>
<p>This behavior is detected using Black Berry Curve 8520 and Sony Ericsson G705u.</p>