<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="ltr">anyone know about rbs 2308 is supported yet or not...or still under experimental stage...<br>
</div>
<div dir="ltr">thanks <br>
</div>
<div dir="ltr">regards <br>
</div>
<div dir="ltr">rajitha peiris<br>
</div>
<div dir="ltr">sri Lanka<br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr"><br>
</div>
<div class="wps_signature">Sent from my Mi phone</div>
<div class="wps_quotion">On "openbsc-request@lists.osmocom.org" <openbsc-request@lists.osmocom.org>, Dec 7, 2016 11:11 PM wrote:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p></p>
<meta name="Generator" content="Microsoft Exchange Server">
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style><font size="2"><span style="font-size:10pt;">
<div class="PlainText">Send OpenBSC mailing list submissions to<br>
openbsc@lists.osmocom.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.osmocom.org/mailman/listinfo/openbsc" target="_BLANK">
https://lists.osmocom.org/mailman/listinfo/openbsc</a><br>
or, via email, send a message with subject or body 'help' to<br>
openbsc-request@lists.osmocom.org<br>
<br>
You can reach the person managing the list at<br>
openbsc-owner@lists.osmocom.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of OpenBSC digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Paging not answered in m2m call (Holger Freyther)<br>
2. Re: Paging not answered in m2m call (Kristian Martens)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 7 Dec 2016 18:13:10 +0100<br>
From: Holger Freyther <holger@freyther.de><br>
To: Kristian Martens <kristian.martens@ng4t.com><br>
Cc: openbsc@lists.osmocom.org<br>
Subject: Re: Paging not answered in m2m call<br>
Message-ID: <D782A7D5-AD0D-4BE0-9898-2AEC6151BAB0@freyther.de><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
<br>
> On 07 Dec 2016, at 17:52, Kristian Martens <kristian.martens@ng4t.com> wrote:<br>
> <br>
> Hello,<br>
<br>
Hi!<br>
<br>
> two UEs (A and B) are successfully registered in a network. Now A tries<br>
> to call B. B is paged by the core via A interface but the sysmoBSC/BTS<br>
> does not seem to page the UE (or UE does not answer paging). What could<br>
> be the reason for this behaviour? How could the problem be debugged?<br>
> Please find the attached pcap for your reference.<br>
<br>
<br>
nice MNC! The P-TMSI doesn't really look that random but it might be an<br>
index into an internal data structure?<br>
<br>
So on A this looks right. The LAI is 262-79-1 and this is where you are<br>
paging. In general it might be:<br>
<br>
* osmo-bsc doesn't translate this to actual paging. E.g. not linking/<br>
handling the location area identifier. You could trace the RSL protocol<br>
and see if a paging command is being sent (periodically) to the BTS?<br>
<br>
* The MS still has a radio channel open. I notice that clear command is<br>
being sent so this is unlikely to be the case. Also IMSI seems to be<br>
match.. maybe the MS still calculates the paging group wrongly? That is<br>
far fetched though.<br>
<br>
<br>
holger<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 7 Dec 2016 18:41:08 +0100<br>
From: Kristian Martens <kristian.martens@ng4t.com><br>
To: Holger Freyther <holger@freyther.de><br>
Cc: openbsc@lists.osmocom.org<br>
Subject: Re: Paging not answered in m2m call<br>
Message-ID: <9a4bcc68-e884-0f48-8a26-989b7edf5bca@ng4t.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi,<br>
<br>
I have captured a trace. Can you find something out?<br>
<br>
Thanks,<br>
<br>
Kristian<br>
<br>
<br>
<br>
Am 07.12.2016 um 18:13 schrieb Holger Freyther:<br>
>> On 07 Dec 2016, at 17:52, Kristian Martens <kristian.martens@ng4t.com> wrote:<br>
>><br>
>> Hello,<br>
> Hi!<br>
><br>
>> two UEs (A and B) are successfully registered in a network. Now A tries<br>
>> to call B. B is paged by the core via A interface but the sysmoBSC/BTS<br>
>> does not seem to page the UE (or UE does not answer paging). What could<br>
>> be the reason for this behaviour? How could the problem be debugged?<br>
>> Please find the attached pcap for your reference.<br>
><br>
> nice MNC! The P-TMSI doesn't really look that random but it might be an<br>
> index into an internal data structure?<br>
><br>
> So on A this looks right. The LAI is 262-79-1 and this is where you are<br>
> paging. In general it might be:<br>
><br>
> * osmo-bsc doesn't translate this to actual paging. E.g. not linking/<br>
> handling the location area identifier. You could trace the RSL protocol<br>
> and see if a paging command is being sent (periodically) to the BTS?<br>
><br>
> * The MS still has a radio channel open. I notice that clear command is<br>
> being sent so this is unlikely to be the case. Also IMSI seems to be<br>
> match.. maybe the MS still calculates the paging group wrongly? That is<br>
> far fetched though.<br>
><br>
><br>
> holger<br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: 20161207_nopaging.pcap<br>
Type: application/octet-stream<br>
Size: 26302 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.osmocom.org/pipermail/openbsc/attachments/20161207/dccfca29/attachment.obj" target="_BLANK">http://lists.osmocom.org/pipermail/openbsc/attachments/20161207/dccfca29/attachment.obj</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
OpenBSC mailing list<br>
OpenBSC@lists.osmocom.org<br>
<a href="https://lists.osmocom.org/mailman/listinfo/openbsc" target="_BLANK">https://lists.osmocom.org/mailman/listinfo/openbsc</a><br>
<br>
<br>
------------------------------<br>
<br>
End of OpenBSC Digest, Vol 26, Issue 7<br>
**************************************<br>
</div>
</span></font></blockquote>
</div>
</body>
</html>