Persistent Uplink activity from Moto KRZR K3

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Alexander Chemeris alexander.chemeris at gmail.com
Tue May 10 08:01:26 UTC 2016


Hi Keith,

On May 5, 2016 6:02 PM, "Keith" <keith at rhizomatica.org> wrote:
>
> They generate constant bursts on the uplink, and this is what I can see
> that corresponds from osmo-bts log output:
>
> <0000> ../../../../osmo-bts/src/common/rsl.c:1642
> (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS
REP
> <0000> ../../../../osmo-bts/src/common/rsl.c:1592
> (bts=0,trx=0,ts=0,ss=0) Tx MEAS RES

MEAS RES means that there is an open logical channel between the phone and
the BTS. Have you looked at the list of open channels at the NITB VTY?

> I might also mention that this phone fails the USSD *#100# own number
> request - The message "Not Successful"  appears on the screen very
> quickly if not immediately after pressing send. There is no network
> communication that I can detect.

Just a suggestion - is the phone network or SIM locked?

If it's locked, it may try to send some message to the network to verify
that it's connected to an allowed operator.

A useful log would be a pcap trace of communication between OpenBSC and
OsmoBTS (make sure osmo-trx communication is filtered out).

--
Regards,
Alexander Chemeris
CEO Fairwaves, Inc.
https://fairwaves.co
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160510/3fc739ea/attachment.htm>


More information about the OpenBSC mailing list