OpenBSC Digest, Vol 26, Issue 7

historical

anyone know about rbs 2308 is supported yet or not...or still under experimental stage...
thanks
regards
rajitha peiris
sri Lanka

Sent from my Mi phone
On "openbsc-request at lists.osmocom.org" <openbsc-request at lists.osmocom.org>, Dec 7, 2016 11:11 PM wrote:

Send OpenBSC mailing list submissions to
        openbsc at lists.osmocom.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.osmocom.org/mailman/listinfo/openbsc
or, via email, send a message with subject or body 'help' to
        openbsc-request at lists.osmocom.org

You can reach the person managing the list at
        openbsc-owner at lists.osmocom.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of OpenBSC digest..."

Today's Topics:

   1. Re: Paging not answered in m2m call (Holger Freyther)
   2. Re: Paging not answered in m2m call (Kristian Martens)

----------------------------------------------------------------------

Message: 1
Date: Wed, 7 Dec 2016 18:13:10 +0100
From: Holger Freyther <holger at freyther.de>
To: Kristian Martens <kristian.martens at ng4t.com>
Cc: openbsc at lists.osmocom.org
Subject: Re: Paging not answered in m2m call
Message-ID: <D782A7D5-AD0D-4BE0-9898-2AEC6151BAB0 at freyther.de>
Content-Type: text/plain; charset=us-ascii

> On 07 Dec 2016, at 17:52, Kristian Martens <kristian.martens at ng4t.com> wrote:
>
> Hello,

Hi!

> two UEs (A and B) are successfully registered in a network. Now A tries
> to call B. B is paged by the core via A interface but the sysmoBSC/BTS
> does not seem to page the UE (or UE does not answer paging). What could
> be the reason for this behaviour? How could the problem be debugged?
> Please find the attached pcap for your reference.

nice MNC! The P-TMSI doesn't really look that random but it might be an
index into an internal data structure?

So on A this looks right. The LAI is 262-79-1 and this is where you are
paging. In general it might be:

* osmo-bsc doesn't translate this to actual paging. E.g. not linking/
handling the location area identifier. You could trace the RSL protocol
and see if a paging command is being sent (periodically) to the BTS?

* The MS still has a radio channel open. I notice that clear command is
being sent so this is unlikely to be the case. Also IMSI seems to be
match.. maybe the MS still calculates the paging group wrongly? That is
far fetched though.

holger

------------------------------

Message: 2
Date: Wed, 7 Dec 2016 18:41:08 +0100
From: Kristian Martens <kristian.martens at ng4t.com>
To: Holger Freyther <holger at freyther.de>
Cc: openbsc at lists.osmocom.org
Subject: Re: Paging not answered in m2m call
Message-ID: <9a4bcc68-e884-0f48-8a26-989b7edf5bca at ng4t.com>
Content-Type: text/plain; charset="utf-8"

Hi,

I have captured a trace. Can you find something out?

Thanks,

Kristian

Am 07.12.2016 um 18:13 schrieb Holger Freyther:
>> On 07 Dec 2016, at 17:52, Kristian Martens <kristian.martens at ng4t.com> wrote:
>>
>> Hello,
> Hi!
>
>> two UEs (A and B) are successfully registered in a network. Now A tries
>> to call B. B is paged by the core via A interface but the sysmoBSC/BTS
>> does not seem to page the UE (or UE does not answer paging). What could
>> be the reason for this behaviour? How could the problem be debugged?
>> Please find the attached pcap for your reference.
>
> nice MNC! The P-TMSI doesn't really look that random but it might be an
> index into an internal data structure?
>
> So on A this looks right. The LAI is 262-79-1 and this is where you are
> paging. In general it might be:
>
> * osmo-bsc doesn't translate this to actual paging. E.g. not linking/
> handling the location area identifier. You could trace the RSL protocol
> and see if a paging command is being sent (periodically) to the BTS?
>
> * The MS still has a radio channel open. I notice that clear command is
> being sent so this is unlikely to be the case. Also IMSI seems to be
> match.. maybe the MS still calculates the paging group wrongly? That is
> far fetched though.
>
>
> holger

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20161207_nopaging.pcap
Type: application/octet-stream
Size: 26302 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20161207/dccfca29/attachment.obj>

------------------------------

Subject: Digest Footer

_______________________________________________
OpenBSC mailing list
OpenBSC at lists.osmocom.org
https://lists.osmocom.org/mailman/listinfo/openbsc

------------------------------

End of OpenBSC Digest, Vol 26, Issue 7
**************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20161208/5e1bbda1/attachment.htm>