From laforge at gnumonks.org Fri Jul 1 10:21:04 2016 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 1 Jul 2016 12:21:04 +0200 Subject: osmo-bts: Repository write acces / Gerrit migration In-Reply-To: References: Message-ID: <20160701102104.GG3992@nataraja> Dear Tom, I hope you don't mind me Cc'ing the list, as this question might come up again. On Fri, Jul 01, 2016 at 02:42:25AM -0700, Tom Tsou wrote: > I appear to no longer have write access to the osmo-bts repository. > "ERROR:gitosis.serve.main:Repository write access denied" > Can I have write access restored? As decided at the Osmocom Developer Conference in April 2016, we have started to use gerrit for a more formalized tool for code review. The advantages are plentiful, among other things submitted patches are running through 'make distcheck' on several supported platforms before even being eligible to merge. Please see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for a short intro in how to use it. There are instructions both for submitting patches against master, as well as for pushing to user-private branches. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From tom at tsou.cc Fri Jul 1 12:46:37 2016 From: tom at tsou.cc (Tom Tsou) Date: Fri, 1 Jul 2016 05:46:37 -0700 Subject: osmo-bts: Repository write acces / Gerrit migration In-Reply-To: <20160701102104.GG3992@nataraja> References: <20160701102104.GG3992@nataraja> Message-ID: On Fri, Jul 1, 2016 at 3:21 AM, Harald Welte wrote: > I hope you don't mind me Cc'ing the list, as this question might come up > again. No worries. > Please see > https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit > for a short intro in how to use it. There are instructions both for > submitting patches against master, as well as for pushing to > user-private branches. OK, thanks for the info. I had noticed the Gerrit changes, but was not aware that pushing to user-private branches was also affected. -TT From sebastian.stumpf87 at googlemail.com Fri Jul 1 13:06:38 2016 From: sebastian.stumpf87 at googlemail.com (Sebastian Stumpf) Date: Fri, 1 Jul 2016 15:06:38 +0200 Subject: osmo-nitb/osmo-bts-trx: Logging traffic on A-bis interface Message-ID: Hi all, I wanted to check if the bts - bsc communication works properly with my configuration. For example, if my osmo-nitb does send the system information messages to the bts. I tried the vty logging interface of osmo-bts and logged some messages, but they were not the messages I expected. I configured the groups rsl, oml, rll, rr and abis to "notice", all to "everything" and everything else to "error" and got following log output (lots of these and nothing else): ... <0006> scheduler.c:405 PH-RTS.ind: chan=CCCH chan_nr=0x90 link_id=0x00 fn=993588 ts=0 trx=0 <0006> scheduler.c:341 PH-DATA.req: chan_nr=0x90 link_id=0x00 fn=993588 ts=0 trx=0 ... PH-RTS.ind and PH-DATA.req seem to come from layer1 SAP, the osmo-trx and have probably nothing to do with the SI messages. Is traffic on abis generally not logged or is my log config faulty? I ended up configuring the gsmtap interface for osmo-bts and could so see the uplink/downlink in wireshark and could see that the SI information is properly sent. But gsmtap only works for the air interface. What is the best way for logging/sniffing the communication on the A-bis interface? With kind regards, Sebastian Stumpf -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.chemeris at gmail.com Fri Jul 1 13:40:20 2016 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Fri, 1 Jul 2016 16:40:20 +0300 Subject: osmo-nitb/osmo-bts-trx: Logging traffic on A-bis interface In-Reply-To: References: Message-ID: Sebastian, On Jul 1, 2016 4:06 PM, "Sebastian Stumpf" < sebastian.stumpf87 at googlemail.com> wrote: > I ended up configuring the gsmtap interface for osmo-bts and could so see the uplink/downlink in wireshark and could see that the SI information is properly sent. But gsmtap only works for the air interface. > > What is the best way for logging/sniffing the communication on the A-bis interface? A-bis (OML/RSL) are using usual TCP socket. Wireshark should detect and decode messages sent over this socket automatically. Please excuse typos. Written with a touchscreen keyboard. -- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co -------------- next part -------------- An HTML attachment was scrubbed... URL: From msuraev at sysmocom.de Fri Jul 1 13:41:46 2016 From: msuraev at sysmocom.de (Max) Date: Fri, 1 Jul 2016 15:41:46 +0200 Subject: osmo-nitb/osmo-bts-trx: Logging traffic on A-bis interface In-Reply-To: References: Message-ID: <5776731A.1010201@sysmocom.de> Indeed. There are even convenient wireshark display filters gsm_abis_rsl and gsm_abis_oml. On 07/01/2016 03:40 PM, Alexander Chemeris wrote: > > Sebastian, > > On Jul 1, 2016 4:06 PM, "Sebastian Stumpf" > > wrote: > > I ended up configuring the gsmtap interface for osmo-bts and could > so see the uplink/downlink in wireshark and could see that the SI > information is properly sent. But gsmtap only works for the air interface. > > > > What is the best way for logging/sniffing the communication on the > A-bis interface? > > A-bis (OML/RSL) are using usual TCP socket. Wireshark should detect > and decode messages sent over this socket automatically. > > Please excuse typos. Written with a touchscreen keyboard. > > -- > Regards, > Alexander Chemeris > CEO Fairwaves, Inc. > https://fairwaves.co > -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From laforge at gnumonks.org Fri Jul 1 19:47:02 2016 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 1 Jul 2016 21:47:02 +0200 Subject: Is there a maximum separation in Mhz for ARFCNs on one BTS? In-Reply-To: <57744CD8.8080402@rhizomatica.org> References: <57744CD8.8080402@rhizomatica.org> Message-ID: <20160701194702.GB3879@nataraja> On Wed, Jun 29, 2016 at 11:34:00PM +0100, Keith Whyte wrote: > I'm wondering if there's any issue in GSM running a dual TRX BTS with > two ARFCNs on opposite ends of the band? There shouldn't be any issue, you can have it anywhere you want. Imagine you had frequency hopping, then the phone would have to hop all over the band, not only during channel assignment but between _every_ burst it transmits. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From msuraev at sysmocom.de Mon Jul 4 13:40:00 2016 From: msuraev at sysmocom.de (Max) Date: Mon, 4 Jul 2016 15:40:00 +0200 Subject: freebsd and jenkins Message-ID: <577A6730.3080309@sysmocom.de> Hi. Yet again I've hit an issue with jenkins build failing on freebsd only: http://jenkins.osmocom.org/jenkins/job/libosmocore-gerrit/label=FreeBSD_amd64/101/console No warnings, no errors, just a failure which I'm unable to reproduce locally as I do not have access to any machine with freebsd. If we can't make freebsd tests optional (which I personally would prefer) can we at least configure jenkins in a way that it runs "cat tests/testsuite.log" so it's available via "console output" part of jenkins web ui? Or somehow else provide access to build artifacts. That will give at least some clue as to what exactly is broken on freebsd. Any ideas as to why build fails are highly appreciated as well. -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From holger at freyther.de Mon Jul 4 14:11:38 2016 From: holger at freyther.de (Holger Freyther) Date: Mon, 4 Jul 2016 16:11:38 +0200 Subject: freebsd and jenkins In-Reply-To: <577A6730.3080309@sysmocom.de> References: <577A6730.3080309@sysmocom.de> Message-ID: <87A5D699-133D-40E0-A841-CE8740AED5B0@freyther.de> > On 04 Jul 2016, at 15:40, Max wrote: > > Hi. Hi! > Yet again I've hit an issue with jenkins build failing on freebsd only: > http://jenkins.osmocom.org/jenkins/job/libosmocore-gerrit/label=FreeBSD_amd64/101/console > > No warnings, no errors, just a failure which I'm unable to reproduce > locally as I do not have access to any machine with freebsd. If we can't > make freebsd tests optional (which I personally would prefer) can we at > least configure jenkins in a way that it runs "cat tests/testsuite.log" > so it's available via "console output" part of jenkins web ui? Or > somehow else provide access to build artifacts. That will give at least > some clue as to what exactly is broken on freebsd. a.) We/you add the cat to contrib/jenkins.sh b.) if your build is the last one, you can (after you logged in) inspect the workspace[1]. My internet is too slow right now to look for the specific entry. holger [1] http://jenkins.osmocom.org/jenkins/job/libosmocore-gerrit/label=FreeBSD_amd64/ws/ From msuraev at sysmocom.de Mon Jul 4 14:53:24 2016 From: msuraev at sysmocom.de (Max) Date: Mon, 4 Jul 2016 16:53:24 +0200 Subject: freebsd and jenkins In-Reply-To: <87A5D699-133D-40E0-A841-CE8740AED5B0@freyther.de> References: <577A6730.3080309@sysmocom.de> <87A5D699-133D-40E0-A841-CE8740AED5B0@freyther.de> Message-ID: <577A7864.5060500@sysmocom.de> Thanks for the link. My buils is last one (#101) but there's no testsuite.log in workspace although in console output it ways that "testsuite.log was created." Any ideas what happened to it? On 07/04/2016 04:11 PM, Holger Freyther wrote: >> On 04 Jul 2016, at 15:40, Max wrote: >> >> Hi. > Hi! > > >> Yet again I've hit an issue with jenkins build failing on freebsd only: >> http://jenkins.osmocom.org/jenkins/job/libosmocore-gerrit/label=FreeBSD_amd64/101/console >> >> No warnings, no errors, just a failure which I'm unable to reproduce >> locally as I do not have access to any machine with freebsd. If we can't >> make freebsd tests optional (which I personally would prefer) can we at >> least configure jenkins in a way that it runs "cat tests/testsuite.log" >> so it's available via "console output" part of jenkins web ui? Or >> somehow else provide access to build artifacts. That will give at least >> some clue as to what exactly is broken on freebsd. > > a.) We/you add the cat to contrib/jenkins.sh > > b.) if your build is the last one, you can (after you logged in) inspect the workspace[1]. My internet is too slow right now to look for the specific entry. > > > holger > > > [1] http://jenkins.osmocom.org/jenkins/job/libosmocore-gerrit/label=FreeBSD_amd64/ws/ -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From holger at freyther.de Mon Jul 4 15:00:27 2016 From: holger at freyther.de (Holger Freyther) Date: Mon, 4 Jul 2016 17:00:27 +0200 Subject: freebsd and jenkins In-Reply-To: <577A7864.5060500@sysmocom.de> References: <577A6730.3080309@sysmocom.de> <87A5D699-133D-40E0-A841-CE8740AED5B0@freyther.de> <577A7864.5060500@sysmocom.de> Message-ID: <9E3A2369-00A0-4F2B-936E-BB3F9EF599EC@freyther.de> > On 04 Jul 2016, at 16:53, Max wrote: > > Thanks for the link. My buils is last one (#101) but there's no > testsuite.log in workspace although in console output it ways that > "testsuite.log was created." Any ideas what happened to it? make distcheck failed so you need to go to libosmocore-.../_build/tests.. http://jenkins.osmocom.org/jenkins/job/libosmocore-gerrit/label=FreeBSD_amd64/ws/libosmocore-0.9.0.193-44d4/_build/tests/testsuite.log and the specific failing test http://jenkins.osmocom.org/jenkins/job/libosmocore-gerrit/label=FreeBSD_amd64/ws/libosmocore-0.9.0.193-44d4/_build/tests/testsuite.dir/08/testsuite.log From nhofmeyr at sysmocom.de Tue Jul 5 09:42:41 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 5 Jul 2016 11:42:41 +0200 Subject: error install openbsc In-Reply-To: References: Message-ID: <20160705094241.GA1727@ass40.sysmocom.de> On Sat, Jun 18, 2016 at 05:27:59PM +0430, sms makhof wrote: > Hi all > I am installing OpenBSC.I just following > http://openbsc.osmocom.org/trac/wiki/Building_OpenBSC > (I am just Building libosmocore, Building libosmo-abis, Building > libosmo-netif, Building OpenBSC and install library.) > But when I tried to run OpenBSC,I encounter with this error(problem). > > user12 at ubuntu:~$ cd '/home/user12/openbsc/openbsc/src/osmo-nitb' > user12 at ubuntu:~/openbsc/openbsc/src/osmo-nitb$ sudo ./osmo-nitb > <0005> bsc_init.c:492 Failed to parse the config file: 'openbsc.cfg' Were you able to resolve this issue? osmo-nitb should tell you what part of openbsc.cfg it didn't like. It seems you did not provide the entire error message from osmo-nitb, nor did you send your openbsc.cfg, so we can't help you further. BTW, there is usually no need to run osmo-nitb as root. ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Tue Jul 5 09:57:35 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 5 Jul 2016 11:57:35 +0200 Subject: dynamic traffic channels In-Reply-To: <20160629173733.GG3894@nataraja> References: <20160628080528.GE3849@nataraja> <20160628132547.GC31948@ass40.sysmocom.de> <20160629173733.GG3894@nataraja> Message-ID: <20160705095735.GB1727@ass40.sysmocom.de> On Wed, Jun 29, 2016 at 07:37:33PM +0200, Harald Welte wrote: > Hi Neels, > > On Tue, Jun 28, 2016 at 03:25:48PM +0200, Neels Hofmeyr wrote: > > On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote: > > > [translated from german] > > > is it certain that we switch a channel to PDCH only when > > > gprs mode != none? > > I'm not sure if your response covers the question I raised. I see, I mistook the 'gprs mode' for the internal TS flag whether GPRS is currently active on a TCH_F_PDCH, but you mean the VTY config item. > What if you have a openbsc.cfg with a bts that has 'gprs mode none' but > still has a timeslot in GSM_PCHAN_TCH_F_PDCH mode? The intended > operation in that case is that it will be treated as a pure TCH/F, and > no attempts to switch to PDCH are made. Indeed, we would switch to PDCH anyway. Aside from it being meaningless to have GSM_PCHAN_TCH_F_PDCH time slots with 'gprs mode none', I agree that we shouldn't send PDCH ACT in that case. It's easy to work around: just configure TS as GSM_PCHAN_TCH_F. So I'm not putting this high up on the todo list. http://osmocom.org/issues/1765 ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Tue Jul 5 10:14:38 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 5 Jul 2016 12:14:38 +0200 Subject: osmo-bts: Repository write acces / Gerrit migration In-Reply-To: References: <20160701102104.GG3992@nataraja> Message-ID: <20160705101438.GC1727@ass40.sysmocom.de> On Fri, Jul 01, 2016 at 05:46:37AM -0700, Tom Tsou wrote: > OK, thanks for the info. I had noticed the Gerrit changes, but was not > aware that pushing to user-private branches was also affected. Hi Tom, I've just added tom at tsou.cc to the list of known users in gerrit, which gives you permission to push private branches to the gerrit repository. So instead of using the git.osmocom.org repositories, use gerrit as push target, described at http://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit If anyone else is denied access to push private branches, please bump me or this list, so I can add you to the list of known users. ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Tue Jul 5 11:00:17 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 5 Jul 2016 13:00:17 +0200 Subject: [PATCH 1/2] add basic .gitignore In-Reply-To: <1467716418-7551-1-git-send-email-nhofmeyr@sysmocom.de> References: <1467716418-7551-1-git-send-email-nhofmeyr@sysmocom.de> Message-ID: <1467716418-7551-2-git-send-email-nhofmeyr@sysmocom.de> From: Neels Hofmeyr --- .gitignore | 44 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 .gitignore diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..e15c19b --- /dev/null +++ b/.gitignore @@ -0,0 +1,44 @@ +# build results +*.o +*.lo +*.la +Transceiver52M/osmo-trx + +# tests +CommonLibs/BitVectorTest +CommonLibs/ConfigurationTest +CommonLibs/F16Test +CommonLibs/InterthreadTest +CommonLibs/LogTest +CommonLibs/RegexpTest +CommonLibs/SocketsTest +CommonLibs/TimevalTest +CommonLibs/URLEncodeTest +CommonLibs/VectorTest + +# automake/autoconf +*.in +.deps +.libs +.dirstamp +*~ +Makefile +config.log +config.status +config.h +config.guess +config.sub +config/* +configure +compile +aclocal.m4 +autom4te.cache +depcomp +install-sh +libtool +ltmain.sh +missing +stamp-h1 + +# vim +*.sw? -- 2.1.4 From nhofmeyr at sysmocom.de Tue Jul 5 11:00:16 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 5 Jul 2016 13:00:16 +0200 Subject: [PATCH 0/2] osmo-trx: add .gitignore, add a configure check Message-ID: <1467716418-7551-1-git-send-email-nhofmeyr@sysmocom.de> From: Neels Hofmeyr Rebased the patches onto updated master, added a binary to .gitignore. Neels Hofmeyr (2): add basic .gitignore configure.ac: check for boost/config.hpp header .gitignore | 44 ++++++++++++++++++++++++++++++++++++++++++++ configure.ac | 3 +++ 2 files changed, 47 insertions(+) create mode 100644 .gitignore -- 2.1.4 From nhofmeyr at sysmocom.de Tue Jul 5 11:00:18 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 5 Jul 2016 13:00:18 +0200 Subject: [PATCH 2/2] configure.ac: check for boost/config.hpp header In-Reply-To: <1467716418-7551-1-git-send-email-nhofmeyr@sysmocom.de> References: <1467716418-7551-1-git-send-email-nhofmeyr@sysmocom.de> Message-ID: <1467716418-7551-3-git-send-email-nhofmeyr@sysmocom.de> From: Neels Hofmeyr --- configure.ac | 3 +++ 1 file changed, 3 insertions(+) diff --git a/configure.ac b/configure.ac index ad6bf9a..7e394c2 100644 --- a/configure.ac +++ b/configure.ac @@ -120,6 +120,9 @@ AM_CONDITIONAL(ARCH_ARM_A15, [test "x$with_neon_vfpv4" = "xyes"]) PKG_CHECK_MODULES(LIBUSB, libusb-1.0) +AC_CHECK_HEADER([boost/config.hpp],[], + [AC_MSG_ERROR([boost/config.hpp not found, install e.g. libboost-dev])]) + dnl Output files AC_CONFIG_FILES([\ Makefile \ -- 2.1.4 From nhofmeyr at sysmocom.de Tue Jul 5 11:35:29 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 5 Jul 2016 13:35:29 +0200 Subject: osmo-bts-trx error logs -- was: GPRS on osmo-trx not working In-Reply-To: References: <20160628154548.GA19189@ass40.sysmocom.de> <20160629153130.GB1873@dub6> Message-ID: <20160705113529.GA6890@ass40.sysmocom.de> On Wed, Jun 29, 2016 at 12:02:56PM -0700, Tom Tsou wrote: > I see various error messages that occur in different layers at > startup. I can definitely confirm that some of these messages are > caused by initial Tx/Rx chain and device synchronization. Given that > these initialization errors (e.g. early stale bursts, dropped packets) > are harmless as long as they only happen once, I'm OK with ignoring > them for now. > > I assume there are other effects and similar concerns that take place > higher up the chain. > > > 20160629171522824 DL1C <0006> scheduler_trx.c:1420 GSM clock skew: old fn=463983, new fn=463888 > > 20160629171523170 DL1C <0006> scheduler_trx.c:1420 GSM clock skew: old fn=463963, new fn=463888 > > 20160629171523817 DL1C <0006> scheduler.c:240 Prim for trx=0 ts=0 at fn=464004 is out of range, or channel already disabled. If this happens in conjunction with PCU, increase 'rts-advance' by 5. (current fn=464010) > > > > Ignoring it for now. > > With different log settings I do see the 'rts-advance' messages. I'm > ignoring these for now as well. > > Another non-startup error message I found is bad PDTCH and PTCCH and > blocks under ideal RF signal conditions. It appears that you have seen > this behavior as well. > > DL1C <0006> scheduler_trx.c:835 Received bad data frame at fn=372020 > (12/104) for PTCCH > DL1C <0006> scheduler_trx.c:918 Received bad PDTCH block ending at > fn=310516 (76/104) for PDTCH For completeness sake... My osmo-trx setup is working well now: GPRS and voice are both functional, but I do see a *lot* of error messages in the osmo-bts-trx log. I've pasted a 5-odd minute long log below. Most logs are errors. I'm ignoring the error logs, because all seems to be working well. But it certainly looks like some things want to either be fixed or be shut up about. Possibly some remote mobile devices, other than my two test phones on the desk, are transmitting just above noise level and causing erratic frames and blocks? Note that the log level for DL1C is 'notice', so these are quite prominent log messages in terms if log priority. Is there really something wrong? Otherwise I'd suggest moving these to log level 'info' or 'debug' even. ~Neels 20160705131650139 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2368772 (68/104) for PDTCH 20160705131650139 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2368772 (68/104) for PDTCH 20160705131650229 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2368791 toa=2.93 20160705131650229 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2368791 (45/51) 20160705131650418 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2368833 toa=-2.66 20160705131650418 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2368833 (36/51) 20160705131650524 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2368854 (46/104) for PDTCH 20160705131650524 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2368854 (46/104) for PDTCH 20160705131653716 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2369547 (11/104) for PDTCH 20160705131653716 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2369547 (11/104) for PDTCH 20160705131654463 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2369709 toa=-1.34 20160705131654463 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2369709 (45/51) 20160705131656282 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2370103 toa=5.27 20160705131656282 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2370103 (31/51) 20160705131656841 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2370223 (63/104) for PDTCH 20160705131656841 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2370223 (63/104) for PDTCH 20160705131657927 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2370459 toa=4.99 20160705131657928 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2370459 (30/51) 20160705131658086 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2370494 toa=5.08 20160705131658086 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2370494 (14/51) 20160705131658101 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2370496 (24/104) for PDTCH 20160705131658101 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2370496 (24/104) for PDTCH 20160705131658795 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2370647 toa=-1.25 20160705131658795 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2370647 (14/51) 20160705131701905 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2371320 (16/104) for PDTCH 20160705131701905 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2371320 (16/104) for PDTCH 20160705131702893 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2371535 toa=1.77 20160705131702893 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2371535 (35/51) 20160705131702924 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2371541 (29/104) for PDTCH 20160705131702924 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2371541 (29/104) for PDTCH 20160705131703460 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2371658 (42/104) for PDTCH 20160705131703460 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2371658 (42/104) for PDTCH 20160705131704365 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2371853 (29/104) for PDTCH 20160705131704365 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2371853 (29/104) for PDTCH 20160705131710116 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2373100 toa=1.93 20160705131710116 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2373100 (19/51) 20160705131710501 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2373183 (7/104) for PDTCH 20160705131710501 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2373183 (7/104) for PDTCH 20160705131714342 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2374015 (7/104) for PDTCH 20160705131714342 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2374015 (7/104) for PDTCH 20160705131716040 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2374384 toa=1.59 20160705131716041 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2374384 (28/51) 20160705131716342 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2374448 (24/104) for PDTCH 20160705131717180 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2374631 toa=1.36 20160705131717180 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2374631 (20/51) 20160705131717701 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2374744 toa=-2.93 20160705131717701 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2374744 (31/51) 20160705131718161 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2374843 toa=1.14 20160705131718161 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2374843 (28/51) 20160705131719135 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375055 toa=0.97 20160705131719135 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375055 (36/51) 20160705131720237 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375293 toa=0.73 20160705131720237 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375293 (19/51) 20160705131720938 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2375445 (85/104) for PDTCH 20160705131720939 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2375445 (85/104) for PDTCH 20160705131721233 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375508 toa=0.54 20160705131721233 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375508 (30/51) 20160705131722289 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375737 toa=0.34 20160705131722289 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375737 (4/51) 20160705131723323 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375961 toa=0.10 20160705131723323 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375961 (24/51) 20160705131723580 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2376017 (33/104) for PDTCH 20160705131723580 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2376017 (33/104) for PDTCH 20160705131724531 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2376223 toa=1.06 20160705131724531 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2376223 (31/51) 20160705131726131 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2376570 toa=-0.41 20160705131726131 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2376570 (21/51) 20160705131726357 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2376619 (11/104) for PDTCH 20160705131726358 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2376619 (11/104) for PDTCH 20160705131727112 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2376782 toa=-0.60 20160705131727112 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2376782 (29/51) 20160705131728040 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2376983 (63/104) for PDTCH 20160705131728041 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2376983 (63/104) for PDTCH 20160705131728169 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377012 toa=-0.81 20160705131728501 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377083 (59/104) for PDTCH 20160705131728516 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377087 (63/104) for PDTCH 20160705131728538 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377092 (68/104) for PDTCH 20160705131728561 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377096 (72/104) for PDTCH 20160705131728576 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377100 (76/104) for PDTCH 20160705131728599 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377105 (81/104) for PDTCH 20160705131728621 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377109 (85/104) for PDTCH 20160705131728637 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377113 (89/104) for PDTCH 20160705131728651 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2372460 (12/104) for PTCCH 20160705131728652 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2372460 (12/104) for PTCCH 20160705131728659 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377118 (94/104) for PDTCH 20160705131728682 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377122 (98/104) for PDTCH 20160705131728697 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377126 (102/104) for PDTCH 20160705131728720 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377131 (3/104) for PDTCH 20160705131728742 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377135 (7/104) for PDTCH 20160705131728757 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377139 (11/104) for PDTCH 20160705131728780 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377144 (16/104) for PDTCH 20160705131728803 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377148 (20/104) for PDTCH 20160705131728818 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377152 (24/104) for PDTCH 20160705131728840 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377157 (29/104) for PDTCH 20160705131728863 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377161 (33/104) for PDTCH 20160705131728878 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377165 (37/104) for PDTCH 20160705131728901 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377170 (42/104) for PDTCH 20160705131728923 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377174 (46/104) for PDTCH 20160705131728938 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377178 (50/104) for PDTCH 20160705131728961 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377183 (55/104) for PDTCH 20160705131728984 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377187 (59/104) for PDTCH 20160705131728999 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377191 (63/104) for PDTCH 20160705131729021 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377196 (68/104) for PDTCH 20160705131729044 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377200 (72/104) for PDTCH 20160705131729059 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377204 (76/104) for PDTCH 20160705131729082 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377209 (81/104) for PDTCH 20160705131729097 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377213 (85/104) for PDTCH 20160705131729120 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377217 (89/104) for PDTCH 20160705131729127 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2377140 (12/104) for PTCCH 20160705131729142 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377222 (94/104) for PDTCH 20160705131729157 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377226 (98/104) for PDTCH 20160705131729180 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377230 (102/104) for PDTCH 20160705131729203 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377235 (3/104) for PDTCH 20160705131729218 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377239 (7/104) for PDTCH 20160705131729240 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377243 (11/104) for PDTCH 20160705131729263 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377248 (16/104) for PDTCH 20160705131729278 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377252 (20/104) for PDTCH 20160705131729301 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377256 (24/104) for PDTCH 20160705131729323 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377261 (29/104) for PDTCH 20160705131729338 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377265 (33/104) for PDTCH 20160705131729361 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377269 (37/104) for PDTCH 20160705131729384 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377274 (42/104) for PDTCH 20160705131729399 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377278 (46/104) for PDTCH 20160705131729421 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377282 (50/104) for PDTCH 20160705131729444 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377287 (55/104) for PDTCH 20160705131729459 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377291 (59/104) for PDTCH 20160705131729482 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377295 (63/104) for PDTCH 20160705131729504 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377300 (68/104) for PDTCH 20160705131729520 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377304 (72/104) for PDTCH 20160705131729542 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377308 (76/104) for PDTCH 20160705131729565 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377313 (81/104) for PDTCH 20160705131729580 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377317 (85/104) for PDTCH 20160705131729731 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377350 toa=-0.57 20160705131729731 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377350 (36/51) 20160705131729821 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377369 toa=3.35 20160705131729821 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377369 (4/51) 20160705131730621 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377543 toa=4.32 20160705131730622 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377543 (25/51) 20160705131730833 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377588 toa=-0.77 20160705131730833 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377588 (19/51) 20160705131731852 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377809 toa=-0.98 20160705131731852 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377809 (36/51) 20160705131732757 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2378006 (46/104) for PDTCH 20160705131732757 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378006 (46/104) for PDTCH 20160705131732946 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378047 toa=-1.16 20160705131732946 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2378047 (19/51) 20160705131732976 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378053 toa=1.18 20160705131732976 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2378053 (25/51) 20160705131733844 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2378240 (72/104) for PDTCH 20160705131733844 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378240 (72/104) for PDTCH 20160705131733942 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378262 toa=-1.34 20160705131733942 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2378262 (30/51) 20160705131735044 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378501 toa=-1.52 20160705131735323 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378561 (81/104) for PDTCH 20160705131735339 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378565 (85/104) for PDTCH 20160705131735361 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378569 (89/104) for PDTCH 20160705131735369 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2377244 (12/104) for PTCCH 20160705131735384 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378574 (94/104) for PDTCH 20160705131735399 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378578 (98/104) for PDTCH 20160705131735421 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378582 (102/104) for PDTCH 20160705131735444 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378587 (3/104) for PDTCH 20160705131735459 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378591 (7/104) for PDTCH 20160705131735482 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378595 (11/104) for PDTCH 20160705131735504 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378600 (16/104) for PDTCH 20160705131735519 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378604 (20/104) for PDTCH 20160705131735542 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378608 (24/104) for PDTCH 20160705131735565 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378613 (29/104) for PDTCH 20160705131735580 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378617 (33/104) for PDTCH 20160705131735602 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378621 (37/104) for PDTCH 20160705131735625 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378626 (42/104) for PDTCH 20160705131735640 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378630 (46/104) for PDTCH 20160705131735655 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378634 (50/104) for PDTCH 20160705131735685 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378639 (55/104) for PDTCH 20160705131735701 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378643 (59/104) for PDTCH 20160705131735716 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378647 (63/104) for PDTCH 20160705131735746 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378652 (68/104) for PDTCH 20160705131735761 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378656 (72/104) for PDTCH 20160705131735776 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378660 (76/104) for PDTCH 20160705131735799 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378665 (81/104) for PDTCH 20160705131735821 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378669 (85/104) for PDTCH 20160705131735836 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378673 (89/104) for PDTCH 20160705131735852 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2378596 (12/104) for PTCCH 20160705131735859 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378678 (94/104) for PDTCH 20160705131735882 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378682 (98/104) for PDTCH 20160705131735897 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378686 (102/104) for PDTCH 20160705131735919 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378691 (3/104) for PDTCH 20160705131735942 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378695 (7/104) for PDTCH 20160705131735957 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378699 (11/104) for PDTCH 20160705131735980 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378704 (16/104) for PDTCH 20160705131736002 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378708 (20/104) for PDTCH 20160705131736018 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378712 toa=1.30 20160705131736018 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis 20160705131736018 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378712 (24/104) for PDTCH 20160705131736018 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL CHAN_ACTIV 20160705131736018 DRSL <0000> rsl.c:880 chan_nr=0x20 type=0x00 mode=0x00 20160705131736018 DL1C <0006> scheduler.c:1310 Activating SDCCH/4(0) on trx=0 ts=0 20160705131736018 DL1C <0006> scheduler.c:1310 Activating SACCH/4(0) on trx=0 ts=0 20160705131736018 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on SDCCH/4(0) of trx=0 ts=0 20160705131736018 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SDCCH/4(0) on trx=0 ts=0 20160705131736018 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 20160705131736018 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 20160705131736018 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 20160705131736018 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK 20160705131736018 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD 20160705131736040 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378717 (29/104) for PDTCH 20160705131736063 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378721 (33/104) for PDTCH 20160705131736078 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378725 (37/104) for PDTCH 20160705131736101 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378730 (42/104) for PDTCH 20160705131736123 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378734 (46/104) for PDTCH 20160705131736138 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378738 (50/104) for PDTCH 20160705131736161 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378743 (55/104) for PDTCH 20160705131736184 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378747 (59/104) for PDTCH 20160705131736199 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378751 (63/104) for PDTCH 20160705131736221 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378756 (68/104) for PDTCH 20160705131736244 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378760 (72/104) for PDTCH 20160705131736259 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378764 (76/104) for PDTCH 20160705131736282 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378769 (81/104) for PDTCH 20160705131736304 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378773 (85/104) for PDTCH 20160705131736319 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378777 (89/104) for PDTCH 20160705131736327 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2378700 (12/104) for PTCCH 20160705131736342 DLLAPD <0011> lapd_core.c:899 Store content res. 20160705131736342 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis 20160705131736342 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378782 (94/104) for PDTCH 20160705131736357 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378786 (98/104) for PDTCH 20160705131736380 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378790 (102/104) for PDTCH 20160705131736402 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378795 (3/104) for PDTCH 20160705131736433 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131736531 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378824 toa=-1.00 20160705131736576 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705131736765 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378873 (81/104) for PDTCH 20160705131736780 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378877 (85/104) for PDTCH 20160705131736802 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378881 (89/104) for PDTCH 20160705131736810 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=0 (0/104) for PTCCH 20160705131736825 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378886 (94/104) for PDTCH 20160705131736840 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378890 (98/104) for PDTCH 20160705131736863 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378894 (102/104) for PDTCH 20160705131736886 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378899 (3/104) for PDTCH 20160705131736901 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378903 (7/104) for PDTCH 20160705131736901 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131736916 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378907 (11/104) for PDTCH 20160705131736946 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378912 (16/104) for PDTCH 20160705131736961 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378916 (20/104) for PDTCH 20160705131736976 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378920 (24/104) for PDTCH 20160705131736999 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378925 (29/104) for PDTCH 20160705131737021 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378929 (33/104) for PDTCH 20160705131737036 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378933 (37/104) for PDTCH 20160705131737059 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378938 (42/104) for PDTCH 20160705131737082 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378942 (46/104) for PDTCH 20160705131737097 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378946 (50/104) for PDTCH 20160705131737120 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378951 (55/104) for PDTCH 20160705131737142 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378955 (59/104) for PDTCH 20160705131737157 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378959 (63/104) for PDTCH 20160705131737180 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378964 (68/104) for PDTCH 20160705131737202 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378968 (72/104) for PDTCH 20160705131737218 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378972 (76/104) for PDTCH 20160705131737240 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378977 (81/104) for PDTCH 20160705131737263 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378981 (85/104) for PDTCH 20160705131737278 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378985 (89/104) for PDTCH 20160705131737285 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2378908 (12/104) for PTCCH 20160705131737301 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378990 (94/104) for PDTCH 20160705131737323 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378994 (98/104) for PDTCH 20160705131737338 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378998 (102/104) for PDTCH 20160705131737361 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379003 (3/104) for PDTCH 20160705131737376 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131737384 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379007 (7/104) for PDTCH 20160705131737399 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379011 (11/104) for PDTCH 20160705131737421 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379016 (16/104) for PDTCH 20160705131737444 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379020 (20/104) for PDTCH 20160705131737459 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379024 (24/104) for PDTCH 20160705131737482 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379029 (29/104) for PDTCH 20160705131737504 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379033 (33/104) for PDTCH 20160705131737519 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705131737520 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379037 (37/104) for PDTCH 20160705131737542 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379042 (42/104) for PDTCH 20160705131737557 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379046 (46/104) for PDTCH 20160705131737580 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379050 (50/104) for PDTCH 20160705131737602 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379055 (55/104) for PDTCH 20160705131737618 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379059 (59/104) for PDTCH 20160705131737640 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379063 (63/104) for PDTCH 20160705131737663 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379068 (68/104) for PDTCH 20160705131737678 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379072 (72/104) for PDTCH 20160705131737701 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379076 (76/104) for PDTCH 20160705131737723 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379081 (81/104) for PDTCH 20160705131737738 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379085 (85/104) for PDTCH 20160705131737753 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705131737761 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379089 (89/104) for PDTCH 20160705131737768 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2379012 (12/104) for PTCCH 20160705131737784 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379094 (94/104) for PDTCH 20160705131737844 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131737950 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379130 toa=-0.05 20160705131738199 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379185 (81/104) for PDTCH 20160705131738221 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705131738221 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL DEACTIVATE_SACCH 20160705131738221 DL1C <0006> scheduler.c:1310 Deactivating SACCH/4(0) on trx=0 ts=0 20160705131738229 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379189 (85/104) for PDTCH 20160705131738236 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379193 (89/104) for PDTCH 20160705131738267 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2378700 (12/104) for PTCCH 20160705131738267 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379198 (94/104) for PDTCH 20160705131738282 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379202 (98/104) for PDTCH 20160705131738312 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379206 (102/104) for PDTCH 20160705131738319 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379211 (3/104) for PDTCH 20160705131738342 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379215 (7/104) for PDTCH 20160705131738387 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379224 (16/104) for PDTCH 20160705131738425 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379232 (24/104) for PDTCH 20160705131738463 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379241 (33/104) for PDTCH 20160705131738508 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379250 (42/104) for PDTCH 20160705131738546 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379258 (50/104) for PDTCH 20160705131738599 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2379271 (63/104) for PDTCH 20160705131738599 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379271 (63/104) for PDTCH 20160705131738848 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379326 toa=2.93 20160705131738848 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2379326 (23/51) 20160705131738931 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis 20160705131738931 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL RF_CHAN_REL 20160705131738931 DL1C <0006> scheduler.c:1310 Deactivating SDCCH/4(0) on trx=0 ts=0 20160705131738931 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=0,ss=0) Tx RF CHAN REL ACK 20160705131739602 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379489 toa=1.25 20160705131739814 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379535 toa=-4.99 20160705131739814 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2379535 (28/51) 20160705131739882 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=2) 20160705131741021 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379797 toa=4.64 20160705131741021 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2379797 (35/51) 20160705131741119 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379818 toa=1.52 20160705131741610 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2379220 (12/104) for PTCCH 20160705131741610 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2379012 (12/104) for PTCCH 20160705131741829 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379969 (33/104) for PDTCH 20160705131742561 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2379948 (12/104) for PTCCH 20160705131742561 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2379948 (12/104) for PTCCH 20160705131742568 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2379220 (12/104) for PTCCH 20160705131743052 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2379220 (12/104) for PTCCH 20160705131744304 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2380507 toa=1.05 20160705131744304 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2380507 (31/51) 20160705131745421 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2380749 (85/104) for PDTCH 20160705131745422 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2380749 (85/104) for PDTCH 20160705131746576 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381000 toa=1.00 20160705131746818 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381052 (76/104) for PDTCH 20160705131746818 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381052 (76/104) for PDTCH 20160705131747127 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381119 toa=1.64 20160705131747316 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381160 toa=5.25 20160705131747316 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2381160 (21/51) 20160705131747444 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381187 (3/104) for PDTCH 20160705131747444 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381187 (3/104) for PDTCH 20160705131747753 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381255 toa=0.83 20160705131747919 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381291 (3/104) for PDTCH 20160705131747920 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381291 (3/104) for PDTCH 20160705131748123 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381334 (46/104) for PDTCH 20160705131748123 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381334 (46/104) for PDTCH 20160705131748402 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381395 (3/104) for PDTCH 20160705131749172 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381562 toa=1.80 20160705131749285 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2380364 (12/104) for PTCCH 20160705131749406 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381611 (11/104) for PDTCH 20160705131750252 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2381612 (12/104) for PTCCH 20160705131750252 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2381612 (12/104) for PTCCH 20160705131750282 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381802 (98/104) for PDTCH 20160705131751165 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381993 (81/104) for PDTCH 20160705131751799 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2382131 (11/104) for PDTCH 20160705131751799 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2382131 (11/104) for PDTCH 20160705131752048 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2382183 (63/104) for PDTCH 20160705131752772 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2382342 toa=5.17 20160705131752772 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2382342 (30/51) 20160705131753127 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2382340 (12/104) for PTCCH 20160705131753187 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2382430 (102/104) for PDTCH 20160705131753685 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2382540 toa=-5.30 20160705131753685 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2382540 (24/51) 20160705131754025 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2382612 (76/104) for PDTCH 20160705131756885 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2383234 toa=1.10 20160705131757287 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=2) 20160705131757550 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2383377 toa=1.10 20160705131757927 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2382340 (12/104) for PTCCH 20160705131759285 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2383748 (68/104) for PDTCH 20160705131759285 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2383748 (68/104) for PDTCH 20160705131759285 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2383752 (72/104) for PDTCH 20160705131759368 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2383484 (12/104) for PTCCH 20160705131759368 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2383484 (12/104) for PTCCH 20160705131759859 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2383877 toa=-2.85 20160705131759859 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2383877 (35/51) 20160705131800168 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2383943 (55/104) for PDTCH 20160705131800327 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2383796 (12/104) for PTCCH 20160705131800327 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2383796 (12/104) for PTCCH 20160705131800810 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2384004 (12/104) for PTCCH 20160705131801768 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2384108 (12/104) for PTCCH 20160705131803210 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2384524 (12/104) for PTCCH 20160705131803331 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2384627 (11/104) for PDTCH 20160705131804168 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2384628 (12/104) for PTCCH 20160705131805127 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2384628 (12/104) for PTCCH 20160705131805610 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385044 (12/104) for PTCCH 20160705131806568 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2385148 (12/104) for PTCCH 20160705131806568 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385148 (12/104) for PTCCH 20160705131807051 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385356 (12/104) for PTCCH 20160705131807504 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2385533 (85/104) for PDTCH 20160705131807527 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2385537 (89/104) for PDTCH 20160705131807527 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385460 (12/104) for PTCCH 20160705131808485 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385668 (12/104) for PTCCH 20160705131808968 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385772 (12/104) for PTCCH 20160705131809927 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2385772 (12/104) for PTCCH 20160705131810410 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386084 (12/104) for PTCCH 20160705131810885 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386188 (12/104) for PTCCH 20160705131811368 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386292 (12/104) for PTCCH 20160705131811851 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386396 (12/104) for PTCCH 20160705131812810 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2386500 (12/104) for PTCCH 20160705131812810 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386500 (12/104) for PTCCH 20160705131813285 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386708 (12/104) for PTCCH 20160705131813768 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386812 (12/104) for PTCCH 20160705131814070 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2386954 (50/104) for PDTCH 20160705131814727 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2386916 (12/104) for PTCCH 20160705131814727 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386916 (12/104) for PTCCH 20160705131815210 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387124 (12/104) for PTCCH 20160705131815685 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387228 (12/104) for PTCCH 20160705131816168 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387332 (12/104) for PTCCH 20160705131816613 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2387508 toa=-1.73 20160705131816614 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2387508 (45/51) 20160705131816651 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387436 (12/104) for PTCCH 20160705131816757 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2387539 (11/104) for PDTCH 20160705131816757 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2387539 (11/104) for PDTCH 20160705131816923 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2387574 (46/104) for PDTCH 20160705131817127 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387540 (12/104) for PTCCH 20160705131817610 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387644 (12/104) for PTCCH 20160705131818568 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387852 (12/104) for PTCCH 20160705131819526 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2387956 (12/104) for PTCCH 20160705131819527 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387956 (12/104) for PTCCH 20160705131820485 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2388164 (12/104) for PTCCH 20160705131820485 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2388164 (12/104) for PTCCH 20160705131822410 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2388580 (12/104) for PTCCH 20160705131823270 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2388948 (68/104) for PDTCH 20160705131823270 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2388948 (68/104) for PDTCH 20160705131823368 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2388788 (12/104) for PTCCH 20160705131823368 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2388788 (12/104) for PTCCH 20160705131825285 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2389204 (12/104) for PTCCH 20160705131825285 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2389204 (12/104) for PTCCH 20160705131825927 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2389525 toa=5.14 20160705131825927 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2389525 (22/51) 20160705131827685 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2389620 (12/104) for PTCCH 20160705131827851 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2389943 toa=-0.93 20160705131827851 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2389943 (32/51) 20160705131827927 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2389957 (37/104) for PDTCH 20160705131828017 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2389978 toa=1.29 20160705131828017 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis 20160705131828017 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL CHAN_ACTIV 20160705131828017 DRSL <0000> rsl.c:880 chan_nr=0x0a type=0x00 mode=0x00 20160705131828017 DL1C <0006> scheduler.c:1310 Activating TCH/F on trx=0 ts=2 20160705131828017 DL1C <0006> scheduler.c:1310 Activating SACCH/TF on trx=0 ts=2 20160705131828017 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on TCH/F of trx=0 ts=2 20160705131828017 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PDTCH of trx=0 ts=2 20160705131828017 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PTCCH of trx=0 ts=2 20160705131828017 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for TCH/F on trx=0 ts=2 20160705131828017 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/TF on trx=0 ts=2 20160705131828017 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for TCH/F on trx=0 ts=2 20160705131828017 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/TF on trx=0 ts=2 20160705131828017 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=2,ss=0) Tx CHAN ACT ACK 20160705131828018 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD 20160705131828802 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2390148 (20/104) for PDTCH 20160705131828802 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2390148 (20/104) for PDTCH 20160705131829127 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2389932 (12/104) for PTCCH 20160705131829466 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2390293 toa=4.02 20160705131829466 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2390293 (25/51) 20160705131831527 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2390556 (12/104) for PTCCH 20160705131831527 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2390556 (12/104) for PTCCH 20160705131831708 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2390776 (24/104) for PDTCH 20160705131832485 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2390764 (12/104) for PTCCH 20160705131832485 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2390764 (12/104) for PTCCH 20160705131832628 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2390976 (16/104) for PDTCH 20160705131832734 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2391001 toa=4.05 20160705131832734 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2391001 (19/51) 20160705131833451 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2390972 (12/104) for PTCCH 20160705131833451 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2390972 (12/104) for PTCCH 20160705131834364 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2391353 (81/104) for PDTCH 20160705131834364 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2391353 (81/104) for PDTCH 20160705131837338 DL1C <0006> scheduler_trx.c:982 Received incomplete TCH frame ending at fn=2391998 (102/104) for TCH/F 20160705131837338 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705131837338 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2391998 for TCH/F 20160705131838018 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL DEACTIVATE_SACCH 20160705131838018 DL1C <0006> scheduler.c:1310 Deactivating SACCH/TF on trx=0 ts=2 20160705131838018 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL RF_CHAN_REL 20160705131838018 DL1C <0006> scheduler.c:1310 Deactivating TCH/F on trx=0 ts=2 20160705131838018 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=2,ss=0) Tx RF CHAN REL ACK 20160705131838138 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2392172 toa=4.85 20160705131838138 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2392172 (17/51) 20160705131839406 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2392440 (24/104) for PDTCH 20160705131839406 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2392440 (24/104) for PDTCH 20160705131839406 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2392445 (29/104) for PDTCH 20160705131841481 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2392895 (63/104) for PDTCH 20160705131841481 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2392895 (63/104) for PDTCH 20160705131848221 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2394356 (68/104) for PDTCH 20160705131849322 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2394594 (98/104) for PDTCH 20160705131849323 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2394594 (98/104) for PDTCH 20160705131849700 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2394676 toa=4.82 20160705131849700 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2394676 (22/51) 20160705131851073 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2394974 toa=4.29 20160705131851073 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2394974 (14/51) 20160705131853783 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2395560 (24/104) for PDTCH 20160705131853783 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2395560 (24/104) for PDTCH 20160705131855081 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2395843 toa=1.91 20160705131855081 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis 20160705131855081 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL CHAN_ACTIV 20160705131855081 DRSL <0000> rsl.c:880 chan_nr=0x20 type=0x00 mode=0x00 20160705131855081 DL1C <0006> scheduler.c:1310 Activating SDCCH/4(0) on trx=0 ts=0 20160705131855081 DL1C <0006> scheduler.c:1310 Activating SACCH/4(0) on trx=0 ts=0 20160705131855081 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on SDCCH/4(0) of trx=0 ts=0 20160705131855081 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SDCCH/4(0) on trx=0 ts=0 20160705131855081 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 20160705131855081 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 20160705131855081 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 20160705131855081 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK 20160705131855081 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD 20160705131855428 DLLAPD <0011> lapd_core.c:899 Store content res. 20160705131855428 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis 20160705131855518 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131855662 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705131855994 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131856462 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131856839 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705131856937 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131857073 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705131857315 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705131857405 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131857549 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705131857873 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131858349 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131858817 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131859285 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131859360 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2396769 (89/104) for PDTCH 20160705131859760 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131900228 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705131900429 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL DEACTIVATE_SACCH 20160705131900429 DL1C <0006> scheduler.c:1310 Deactivating SACCH/4(0) on trx=0 ts=0 20160705131901081 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis 20160705131901081 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL RF_CHAN_REL 20160705131901081 DL1C <0006> scheduler.c:1310 Deactivating SDCCH/4(0) on trx=0 ts=0 20160705131901081 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=0,ss=0) Tx RF CHAN REL ACK 20160705131902666 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2397484 (76/104) for PDTCH 20160705131902847 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2397525 toa=-1.76 20160705131902847 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2397525 (15/51) 20160705131904326 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2397845 toa=-4.00 20160705131904326 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis 20160705131904326 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL CHAN_ACTIV 20160705131904326 DRSL <0000> rsl.c:880 chan_nr=0x0a type=0x00 mode=0x00 20160705131904326 DL1C <0006> scheduler.c:1310 Activating TCH/F on trx=0 ts=2 20160705131904326 DL1C <0006> scheduler.c:1310 Activating SACCH/TF on trx=0 ts=2 20160705131904326 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on TCH/F of trx=0 ts=2 20160705131904326 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PDTCH of trx=0 ts=2 20160705131904326 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PTCCH of trx=0 ts=2 20160705131904326 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for TCH/F on trx=0 ts=2 20160705131904326 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/TF on trx=0 ts=2 20160705131904326 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for TCH/F on trx=0 ts=2 20160705131904326 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/TF on trx=0 ts=2 20160705131904327 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=2,ss=0) Tx CHAN ACT ACK 20160705131904327 DL1C <0006> scheduler.c:240 Prim for trx=0 ts=2 at fn=2392173 is out of range, or channel already disabled. If this happens in conjunction with PCU, increase 'rts-advance' by 5. (current fn=2397871) 20160705131904327 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD 20160705131905043 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398001 toa=-2.08 20160705131905043 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398001 (32/51) 20160705131905722 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=0 (0/104) for SACCH/TF 20160705131905737 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398151 toa=-5.09 20160705131905737 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398151 (29/51) 20160705131907262 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2398481 (33/104) for PDTCH 20160705131907262 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2398481 (33/104) for PDTCH 20160705131907390 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398509 toa=3.02 20160705131907390 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398509 (30/51) 20160705131907413 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398514 toa=5.03 20160705131907413 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398514 (35/51) 20160705131907805 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398599 toa=-5.02 20160705131907805 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398599 (18/51) 20160705131909405 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2398945 (81/104) for PDTCH 20160705131909405 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2398945 (81/104) for PDTCH 20160705131911820 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2399470 toa=-0.12 20160705131911820 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2399470 (22/51) 20160705131912235 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2399556 (68/104) for PDTCH 20160705131912236 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2399556 (68/104) for PDTCH 20160705131912251 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2399560 (72/104) for PDTCH 20160705131912900 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2399703 (7/104) for PDTCH 20160705131912900 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2399703 (7/104) for PDTCH 20160705131914327 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL DEACTIVATE_SACCH 20160705131914327 DL1C <0006> scheduler.c:1310 Deactivating SACCH/TF on trx=0 ts=2 20160705131914327 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL RF_CHAN_REL 20160705131914327 DL1C <0006> scheduler.c:1310 Deactivating TCH/F on trx=0 ts=2 20160705131914327 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=2,ss=0) Tx RF CHAN REL ACK 20160705131914718 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2400097 (89/104) for PDTCH 20160705131914719 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2400097 (89/104) for PDTCH 20160705131918718 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2400964 (20/104) for PDTCH 20160705131918719 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2400964 (20/104) for PDTCH 20160705131920145 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2401272 (16/104) for PDTCH 20160705131920145 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2401272 (16/104) for PDTCH 20160705131921322 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2401527 (63/104) for PDTCH 20160705131921322 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2401527 (63/104) for PDTCH 20160705131928514 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2403086 toa=3.82 20160705131928515 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2403086 (17/51) 20160705131928741 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2403135 (7/104) for PDTCH 20160705131928741 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2403135 (7/104) for PDTCH 20160705131928779 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2403143 toa=4.36 20160705131928779 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2403143 (23/51) 20160705131936839 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2404890 (98/104) for PDTCH 20160705131936839 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2404890 (98/104) for PDTCH 20160705131937246 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2404978 toa=-4.82 20160705131937246 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2404978 (22/51) 20160705131937820 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2405102 (102/104) for PDTCH 20160705131937820 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2405102 (102/104) for PDTCH 20160705131938401 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2405228 (20/104) for PDTCH 20160705131938401 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2405228 (20/104) for PDTCH 20160705131938461 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2405242 toa=-3.10 20160705131938462 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2405242 (31/51) 20160705131941941 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2405995 (59/104) for PDTCH 20160705131941941 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2405995 (59/104) for PDTCH 20160705131944839 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2406624 toa=5.18 20160705131944839 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2406624 (36/51) 20160705131946484 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2406979 (3/104) for PDTCH 20160705131946484 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2406979 (3/104) for PDTCH 20160705131949473 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2407628 toa=0.16 20160705131949473 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2407628 (20/51) 20160705131950982 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2407954 (42/104) for PDTCH 20160705131950982 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2407954 (42/104) for PDTCH 20160705131951050 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2407969 toa=4.50 20160705131951050 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2407969 (4/51) 20160705131952741 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2408336 toa=-4.04 20160705131952741 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2408336 (14/51) 20160705131954197 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2408651 (11/104) for PDTCH 20160705131954197 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2408651 (11/104) for PDTCH 20160705131955178 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2408864 toa=-1.39 20160705131955178 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2408864 (32/51) 20160705132000944 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2410112 (16/104) for PDTCH 20160705132000944 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2410112 (16/104) for PDTCH 20160705132001767 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2399188 (12/104) for PTCCH 20160705132001767 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2399188 (12/104) for PTCCH 20160705132006438 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2411303 (63/104) for PDTCH 20160705132006439 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2411303 (63/104) for PDTCH 20160705132008001 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2385148 (12/104) for PTCCH 20160705132008001 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385148 (12/104) for PTCCH 20160705132009261 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2411914 (50/104) for PDTCH 20160705132009261 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2411914 (50/104) for PDTCH 20160705132010378 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2412157 (85/104) for PDTCH 20160705132010378 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2412157 (85/104) for PDTCH 20160705132013035 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2412732 toa=4.27 20160705132013035 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2412732 (24/51) 20160705132013503 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2412833 (33/104) for PDTCH 20160705132013503 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2412833 (33/104) for PDTCH 20160705132013820 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2412902 (102/104) for PDTCH 20160705132013820 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2412902 (102/104) for PDTCH 20160705132014401 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2413029 toa=4.13 20160705132014401 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2413029 (15/51) 20160705132017420 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2413682 toa=1.53 20160705132017420 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis 20160705132017420 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL CHAN_ACTIV 20160705132017420 DRSL <0000> rsl.c:880 chan_nr=0x20 type=0x00 mode=0x00 20160705132017420 DL1C <0006> scheduler.c:1310 Activating SDCCH/4(0) on trx=0 ts=0 20160705132017420 DL1C <0006> scheduler.c:1310 Activating SACCH/4(0) on trx=0 ts=0 20160705132017420 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on SDCCH/4(0) of trx=0 ts=0 20160705132017420 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SDCCH/4(0) on trx=0 ts=0 20160705132017420 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 20160705132017420 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 20160705132017420 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 20160705132017420 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK 20160705132017420 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD 20160705132017601 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2399188 (12/104) for PTCCH 20160705132017812 DLLAPD <0011> lapd_core.c:899 Store content res. 20160705132017812 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis 20160705132017903 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132018046 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132018378 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132018438 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2413904 toa=-0.55 20160705132018438 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2413904 (23/51) 20160705132018522 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132018756 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132018846 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132018989 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132019321 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132019465 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132019465 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL DEACTIVATE_SACCH 20160705132019465 DL1C <0006> scheduler.c:1310 Deactivating SACCH/4(0) on trx=0 ts=0 20160705132019933 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414224 (72/104) for PDTCH 20160705132020167 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis 20160705132020179 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL RF_CHAN_REL 20160705132020179 DL1C <0006> scheduler.c:1310 Deactivating SDCCH/4(0) on trx=0 ts=0 20160705132020179 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=0,ss=0) Tx RF CHAN REL ACK 20160705132020350 DL1C <0006> scheduler.c:240 Prim for trx=0 ts=0 at fn=2414311 is out of range, or channel already disabled. If this happens in conjunction with PCU, increase 'rts-advance' by 5. (current fn=2414342) 20160705132020763 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2414406 (46/104) for PDTCH 20160705132020763 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414406 (46/104) for PDTCH 20160705132020838 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2414423 toa=1.62 20160705132021050 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414462 (102/104) for PDTCH 20160705132021050 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414467 (3/104) for PDTCH 20160705132022189 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414714 (42/104) for PDTCH 20160705132024521 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2415221 toa=5.38 20160705132024521 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2415221 (14/51) 20160705132025284 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2415386 toa=1.88 20160705132025759 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2415489 (89/104) for PDTCH 20160705132025759 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2415489 (89/104) for PDTCH 20160705132028551 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416095 toa=1.68 20160705132028552 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis 20160705132028552 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL CHAN_ACTIV 20160705132028552 DRSL <0000> rsl.c:880 chan_nr=0x20 type=0x00 mode=0x00 20160705132028552 DL1C <0006> scheduler.c:1310 Activating SDCCH/4(0) on trx=0 ts=0 20160705132028552 DL1C <0006> scheduler.c:1310 Activating SACCH/4(0) on trx=0 ts=0 20160705132028552 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on SDCCH/4(0) of trx=0 ts=0 20160705132028552 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SDCCH/4(0) on trx=0 ts=0 20160705132028552 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 20160705132028552 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 20160705132028552 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 20160705132028552 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK 20160705132028552 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD 20160705132028853 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416160 toa=-3.87 20160705132028853 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2416160 (35/51) 20160705132028876 DLLAPD <0011> lapd_core.c:899 Store content res. 20160705132028876 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis 20160705132029110 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132029208 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132029419 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416282 toa=-5.05 20160705132029419 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2416282 (4/51) 20160705132029586 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132029676 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132029819 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132030053 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132030144 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132030491 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416514 toa=0.51 20160705132030491 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2416514 (32/51) 20160705132030522 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132030522 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL DEACTIVATE_SACCH 20160705132030522 DL1C <0006> scheduler.c:1310 Deactivating SACCH/4(0) on trx=0 ts=0 20160705132031231 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis 20160705132031231 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL RF_CHAN_REL 20160705132031231 DL1C <0006> scheduler.c:1310 Deactivating SDCCH/4(0) on trx=0 ts=0 20160705132031231 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=0,ss=0) Tx RF CHAN REL ACK 20160705132031910 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416822 toa=1.85 20160705132032159 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=8) 20160705132033752 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2417218 (50/104) for PDTCH 20160705132034144 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2417305 (33/104) for PDTCH 20160705132034144 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2417305 (33/104) for PDTCH 20160705132034408 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2414684 (12/104) for PTCCH 20160705132034408 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2414684 (12/104) for PTCCH 20160705132034589 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2417400 (24/104) for PDTCH 20160705132037532 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2418041 toa=1.53 20160705132039540 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2418475 toa=1.54 20160705132039540 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis 20160705132039540 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL CHAN_ACTIV 20160705132039540 DRSL <0000> rsl.c:880 chan_nr=0x0a type=0x00 mode=0x00 20160705132039540 DL1C <0006> scheduler.c:1310 Activating TCH/F on trx=0 ts=2 20160705132039540 DL1C <0006> scheduler.c:1310 Activating SACCH/TF on trx=0 ts=2 20160705132039540 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on TCH/F of trx=0 ts=2 20160705132039540 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PDTCH of trx=0 ts=2 20160705132039540 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PTCCH of trx=0 ts=2 20160705132039540 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for TCH/F on trx=0 ts=2 20160705132039540 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/TF on trx=0 ts=2 20160705132039540 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for TCH/F on trx=0 ts=2 20160705132039540 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/TF on trx=0 ts=2 20160705132039540 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=2,ss=0) Tx CHAN ACT ACK 20160705132039541 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD 20160705132039545 DL1C <0006> scheduler.c:240 Prim for trx=0 ts=2 at fn=2400038 is out of range, or channel already disabled. If this happens in conjunction with PCU, increase 'rts-advance' by 5. (current fn=2418502) 20160705132039880 DLLAPD <0011> lapd_core.c:899 Store content res. 20160705132039880 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis 20160705132040121 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132040280 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 20160705132040280 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132040438 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 20160705132040680 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=1, V(R)=2 20160705132040763 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132040838 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=1, V(R)=2 20160705132040921 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132041080 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=2, V(R)=3 20160705132041238 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=2, V(R)=3 20160705132041238 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132041321 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132041480 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=3, V(R)=4 20160705132041638 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=3, V(R)=4 20160705132041714 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132041721 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132041880 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=4, V(R)=5 20160705132042038 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=4, V(R)=5 20160705132042204 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132042216 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL PAGING_CMD 20160705132042216 DPAG <0005> paging.c:213 Add paging to queue (group=2, queue_len=1) 20160705132042219 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132042219 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL MODE_MODIFY_REQ 20160705132042219 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on TCH/F of trx=0 ts=2 20160705132042219 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on PDTCH of trx=0 ts=2 20160705132042219 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on PTCCH of trx=0 ts=2 20160705132042219 DRSL <0000> rsl.c:1077 (bts=0,trx=0,ts=2,ss=0) Tx MODE MODIF ACK 20160705132042219 DRSL <0000> rsl.c:2211 (bts=0,trx=0,ts=2,ss=0) Rx RSL IPAC_CRCX 20160705132042219 DRSL <0000> rsl.c:1465 CRCX does not specify a remote IP 20160705132042219 DRSL <0000> rsl.c:1470 CRCX does not specify a remote port 20160705132042220 DRSL <0000> rsl.c:1289 (bts=0,trx=0,ts=2,ss=0) RSL Tx IPAC_CRCX_ACK (local 127.0.0.1:59068, remote 127.0.0.42:0) 20160705132042378 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=5, V(R)=6 20160705132042536 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=5, V(R)=6 20160705132042680 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132042716 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL PAGING_CMD 20160705132042717 DPAG <0005> paging.c:195 Ignoring duplicate paging 20160705132042963 DPAG <0005> paging.c:512 Removed paging record, queue_len=0 20160705132043155 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2419259 toa=1.39 20160705132043155 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis 20160705132043163 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132043179 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=3,ss=0) Rx RSL CHAN_ACTIV 20160705132043179 DRSL <0000> rsl.c:880 chan_nr=0x0b type=0x00 mode=0x00 20160705132043179 DL1C <0006> scheduler.c:1310 Activating TCH/F on trx=0 ts=3 20160705132043179 DL1C <0006> scheduler.c:1310 Activating SACCH/TF on trx=0 ts=3 20160705132043179 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on TCH/F of trx=0 ts=3 20160705132043179 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PDTCH of trx=0 ts=3 20160705132043179 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PTCCH of trx=0 ts=3 20160705132043179 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for TCH/F on trx=0 ts=3 20160705132043179 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/TF on trx=0 ts=3 20160705132043179 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for TCH/F on trx=0 ts=3 20160705132043179 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/TF on trx=0 ts=3 20160705132043179 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=3,ss=0) Tx CHAN ACT ACK 20160705132043180 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD 20160705132043219 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL PAGING_CMD 20160705132043219 DPAG <0005> paging.c:213 Add paging to queue (group=2, queue_len=1) 20160705132043397 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132043397 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2419311 for TCH/F 20160705132043420 DLLAPD <0011> lapd_core.c:899 Store content res. 20160705132043420 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis 20160705132043638 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132043661 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132043698 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=0 (0/104) for SACCH/TF 20160705132043842 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 20160705132044083 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=1, V(R)=2 20160705132044121 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132044144 DPAG <0005> paging.c:512 Removed paging record, queue_len=0 20160705132044181 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132044318 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=2, V(R)=3 20160705132044559 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=3, V(R)=4 20160705132044604 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132044619 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132044664 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132044801 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=4, V(R)=5 20160705132044861 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132044906 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2419638 toa=4.75 20160705132044906 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2419638 (45/51) 20160705132045042 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=5, V(R)=6 20160705132045080 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132045102 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132045140 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132045284 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=6, V(R)=7 20160705132045359 DL1C <0006> gsm0503_coding.c:689 tch_fr_decode(): error decoding FACCH frame (228/456 bits) 20160705132045359 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2419736 for TCH/F 20160705132045374 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132045375 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=3,ss=0) Rx RSL MODE_MODIFY_REQ 20160705132045375 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on TCH/F of trx=0 ts=3 20160705132045375 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on PDTCH of trx=0 ts=3 20160705132045375 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on PTCCH of trx=0 ts=3 20160705132045375 DRSL <0000> rsl.c:1077 (bts=0,trx=0,ts=3,ss=0) Tx MODE MODIF ACK 20160705132045375 DRSL <0000> rsl.c:2211 (bts=0,trx=0,ts=3,ss=0) Rx RSL IPAC_CRCX 20160705132045375 DRSL <0000> rsl.c:1465 CRCX does not specify a remote IP 20160705132045375 DRSL <0000> rsl.c:1470 CRCX does not specify a remote port 20160705132045375 DRSL <0000> rsl.c:1289 (bts=0,trx=0,ts=3,ss=0) RSL Tx IPAC_CRCX_ACK (local 127.0.0.1:37448, remote 127.0.0.42:0) 20160705132045517 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=7, V(R)=0 20160705132045563 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132045616 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132045623 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2419715 (51/104) for SACCH/TF 20160705132045759 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 20160705132046038 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132046098 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132046521 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132046582 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132046702 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2420026 (50/104) for PDTCH 20160705132046702 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2420026 (50/104) for PDTCH 20160705132047004 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132047065 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132047480 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132047540 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132047646 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2420232 toa=5.49 20160705132047646 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2420232 (27/51) 20160705132047963 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132048023 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132048438 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132048499 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132048921 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132048982 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132049404 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132049465 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132049880 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132049940 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132050363 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132050423 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132050838 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132050899 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132051321 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132051381 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132051804 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132051865 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132052280 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132052340 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132052544 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132052544 DRSL <0000> rsl.c:2211 (bts=0,trx=0,ts=3,ss=0) Rx RSL IPAC_MDCX 20160705132052544 DRSL <0000> rsl.c:1289 (bts=0,trx=0,ts=3,ss=0) RSL Tx IPAC_MDCX_ACK (local 127.0.0.1:37448, remote 127.0.0.1:59068) 20160705132052544 DRSL <0000> rsl.c:2211 (bts=0,trx=0,ts=2,ss=0) Rx RSL IPAC_MDCX 20160705132052544 DRSL <0000> rsl.c:1289 (bts=0,trx=0,ts=2,ss=0) RSL Tx IPAC_MDCX_ACK (local 127.0.0.1:59068, remote 127.0.0.1:37448) 20160705132052717 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=1, V(R)=2 20160705132052763 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132052778 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132052823 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132052869 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2421388. 20160705132052911 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2421397. 20160705132052921 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132052921 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2421374 for TCH/F 20160705132052936 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=6, V(R)=7 20160705132052952 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2421406. 20160705132053072 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2421432. 20160705132053072 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2421432. 20160705132053102 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=6, V(R)=7 20160705132053229 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2421466. 20160705132053238 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132053299 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132053721 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132053781 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132054204 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132054264 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132054680 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132054740 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132055163 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132055223 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132055638 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132055699 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132055880 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132055880 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422015 for TCH/F 20160705132056033 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422073. 20160705132056038 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132056038 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422050 for TCH/F 20160705132056121 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132056181 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132056194 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422108. 20160705132056604 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132056664 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132057080 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132057140 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132057562 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132057623 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132058000 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2422475 toa=4.22 20160705132058000 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2422475 (26/51) 20160705132058038 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132058098 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132058521 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132058581 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132059004 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132059019 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059019 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422696 for TCH/F 20160705132059064 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059065 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422704 for TCH/F 20160705132059065 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132059080 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059080 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422709 for TCH/F 20160705132059102 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059102 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422713 for TCH/F 20160705132059125 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059125 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422717 for TCH/F 20160705132059140 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059140 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422722 for TCH/F 20160705132059173 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422753. 20160705132059215 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422762. 20160705132059233 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422766. 20160705132059253 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059253 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422743 for TCH/F 20160705132059257 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422771. 20160705132059261 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059261 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422748 for TCH/F 20160705132059275 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422775. 20160705132059276 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059276 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422752 for TCH/F 20160705132059293 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422779. 20160705132059359 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059359 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422769 for TCH/F 20160705132059382 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame 20160705132059382 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422774 for TCH/F 20160705132059395 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422801. 20160705132059413 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422805. 20160705132059434 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422810. 20160705132059480 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132059513 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422827. 20160705132059531 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422831. 20160705132059540 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132059963 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132100023 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132100378 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132100438 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132100498 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP 20160705132100516 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423044. 20160705132100536 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=7, V(R)=0 20160705132100657 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132100673 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423078. 20160705132100702 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=7, V(R)=0 20160705132100703 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=3,ss=0) Rx RSL DEACTIVATE_SACCH 20160705132100703 DL1C <0006> scheduler.c:1310 Deactivating SACCH/TF on trx=0 ts=3 20160705132100768 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423100. 20160705132100777 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis 20160705132100785 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL DEACTIVATE_SACCH 20160705132100785 DL1C <0006> scheduler.c:1310 Deactivating SACCH/TF on trx=0 ts=2 20160705132100831 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423113. 20160705132100838 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=2, V(R)=3 20160705132100910 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423130. 20160705132100943 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 20160705132100993 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2423148. 20160705132101034 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis 20160705132101035 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL RF_CHAN_REL 20160705132101035 DRSL <0000> rsl.c:1256 (bts=0,trx=0,ts=2,ss=0) Sending RTP delete indication: cause = Normal event, unspecified 20160705132101035 DL1C <0006> scheduler.c:1310 Deactivating TCH/F on trx=0 ts=2 20160705132101035 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=2,ss=0) Tx RF CHAN REL ACK 20160705132101067 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423165. 20160705132101155 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis 20160705132101155 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=3,ss=0) Rx RSL RF_CHAN_REL 20160705132101155 DRSL <0000> rsl.c:1256 (bts=0,trx=0,ts=3,ss=0) Sending RTP delete indication: cause = Normal event, unspecified 20160705132101155 DL1C <0006> scheduler.c:1310 Deactivating TCH/F on trx=0 ts=3 20160705132101155 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=3,ss=0) Tx RF CHAN REL ACK 20160705132101555 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2423245 toa=1.57 20160705132101713 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2423279 toa=1.43 20160705132101766 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2385148 (12/104) for PTCCH 20160705132102249 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2423316 (12/104) for PTCCH 20160705132102249 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2423316 (12/104) for PTCCH 20160705132102732 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2423316 (12/104) for PTCCH 20160705132102906 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423536 (24/104) for PDTCH 20160705132103004 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2423558 (46/104) for PDTCH 20160705132103019 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423562 (50/104) for PDTCH 20160705132103208 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2402828 (12/104) for PTCCH 20160705132103525 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423671 (55/104) for PDTCH 20160705132104166 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2423628 (12/104) for PTCCH 20160705132104166 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2423628 (12/104) for PTCCH 20160705132104280 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423835 (11/104) for PDTCH 20160705132104370 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423853 (29/104) for PDTCH 20160705132104544 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2423893 toa=-5.47 20160705132104544 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2423893 (16/51) 20160705132105132 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2423836 (12/104) for PTCCH 20160705132105132 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2423836 (12/104) for PTCCH 20160705132105464 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2424091 (59/104) for PDTCH 20160705132107909 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2424622 toa=1.82 20160705132109517 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2424971 toa=1.97 20160705132110038 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2425083 (11/104) for PDTCH 20160705132110038 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2425083 (11/104) for PDTCH 20160705132113275 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2425785 toa=-1.23 20160705132113276 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2425785 (21/51) 20160705132115419 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2426249 (33/104) for PDTCH 20160705132115721 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2426314 (98/104) for PDTCH 20160705132115721 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2426314 (98/104) for PDTCH 20160705132117479 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2426696 toa=5.06 20160705132117479 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2426696 (14/51) 20160705132121985 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2427671 toa=4.16 20160705132121985 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2427671 (20/51) 20160705132124943 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2428312 (16/104) for PDTCH 20160705132124943 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2428312 (16/104) for PDTCH 20160705132127705 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2428911 toa=-0.82 20160705132127706 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2428911 (36/51) 20160705132128543 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2429092 (68/104) for PDTCH 20160705132128543 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2429092 (68/104) for PDTCH 20160705132133404 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2430145 (81/104) for PDTCH 20160705132133404 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2430145 (81/104) for PDTCH 20160705132133736 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2430218 toa=4.20 20160705132133736 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2430218 (17/51) 20160705132133879 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2430249 (81/104) for PDTCH 20160705132133879 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2430249 (81/104) for PDTCH 20160705132135441 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2430587 toa=-3.74 20160705132135441 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2430587 (29/51) 20160705132136800 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2430881 (89/104) for PDTCH 20160705132136800 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2430881 (89/104) for PDTCH 20160705132138302 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2431206 (102/104) for PDTCH 20160705132138302 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2431206 (102/104) for PDTCH 20160705132149185 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2433564 (68/104) for PDTCH 20160705132150203 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2433785 (81/104) for PDTCH 20160705132150203 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2433785 (81/104) for PDTCH 20160705132152953 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=2) 20160705132156747 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2435204 toa=1.67 20160705132156747 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2435204 (5/51) 20160705132158067 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2435490 toa=3.12 20160705132158067 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2435490 (36/51) 20160705132159614 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2435825 toa=1.45 20160705132200180 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2435947 (59/104) for PDTCH 20160705132200181 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2435947 (59/104) for PDTCH 20160705132200701 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2436060 (68/104) for PDTCH 20160705132200701 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2436060 (68/104) for PDTCH 20160705132201282 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2436185 (89/104) for PDTCH 20160705132201282 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2436185 (89/104) for PDTCH 20160705132201818 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2436303 toa=4.69 20160705132201818 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2436303 (33/51) 20160705132202943 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2436545 (33/104) for PDTCH 20160705132202943 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2436545 (33/104) for PDTCH 20160705132203720 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2436714 (98/104) for PDTCH 20160705132203720 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2436714 (98/104) for PDTCH 20160705132205380 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437074 (42/104) for PDTCH 20160705132205380 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437074 (42/104) for PDTCH 20160705132206973 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2437419 toa=3.79 20160705132206973 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2437419 (27/51) 20160705132207260 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437481 (33/104) for PDTCH 20160705132207260 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437481 (33/104) for PDTCH 20160705132207863 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437611 (59/104) for PDTCH 20160705132207863 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437611 (59/104) for PDTCH 20160705132208022 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437646 (94/104) for PDTCH 20160705132208022 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437646 (94/104) for PDTCH 20160705132208980 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437854 (94/104) for PDTCH 20160705132208980 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437854 (94/104) for PDTCH 20160705132209320 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2437928 toa=2.26 20160705132209320 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2437928 (26/51) 20160705132209622 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437992 (24/104) for PDTCH 20160705132209622 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437992 (24/104) for PDTCH 20160705132210663 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2438218 (42/104) for PDTCH 20160705132210663 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2438218 (42/104) for PDTCH 20160705132211177 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2438330 (50/104) for PDTCH 20160705132211177 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2438330 (50/104) for PDTCH 20160705132217611 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=2) 20160705132218029 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2439814 toa=5.12 20160705132218029 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2439814 (25/51) 20160705132219531 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2428932 (12/104) for PTCCH 20160705132221554 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2440579 toa=-1.89 20160705132221554 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2440579 (25/51) 20160705132223108 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2440915 toa=3.21 20160705132223108 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2440915 (4/51) 20160705132224399 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2441195 (3/104) for PDTCH 20160705132224399 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2441195 (3/104) for PDTCH 20160705132224754 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2441272 toa=-4.42 20160705132224754 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2441272 (4/51) 20160705132226686 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2441690 toa=1.34 20160705132227939 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2441962 (42/104) for PDTCH 20160705132227939 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2441962 (42/104) for PDTCH 20160705132232195 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2442884 toa=2.04 20160705132232195 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2442884 (35/51) 20160705132238052 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2444153 toa=-1.35 20160705132238052 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2444153 (29/51) 20160705132241372 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2444873 toa=5.39 20160705132241373 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2444873 (35/51) 20160705132241538 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2444908 (76/104) for PDTCH 20160705132241539 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2444908 (76/104) for PDTCH 20160705132241539 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2444909 toa=4.71 20160705132241539 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2444909 (20/51) 20160705132243727 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2445383 toa=0.05 20160705132243727 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2445383 (35/51) 20160705132244874 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2445631 toa=3.91 20160705132244874 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2445631 (28/51) 20160705132244882 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2445632 (72/104) for PDTCH 20160705132251720 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2447114 toa=1.12 20160705132251720 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2447114 (32/51) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From laforge at gnumonks.org Tue Jul 5 12:15:52 2016 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 5 Jul 2016 14:15:52 +0200 Subject: dynamic traffic channels In-Reply-To: <20160705095735.GB1727@ass40.sysmocom.de> References: <20160628080528.GE3849@nataraja> <20160628132547.GC31948@ass40.sysmocom.de> <20160629173733.GG3894@nataraja> <20160705095735.GB1727@ass40.sysmocom.de> Message-ID: <20160705121552.GA5472@nataraja> Hi Neels, On Tue, Jul 05, 2016 at 11:57:35AM +0200, Neels Hofmeyr wrote: > > What if you have a openbsc.cfg with a bts that has 'gprs mode none' but > > still has a timeslot in GSM_PCHAN_TCH_F_PDCH mode? The intended > > operation in that case is that it will be treated as a pure TCH/F, and > > no attempts to switch to PDCH are made. > > Indeed, we would switch to PDCH anyway. Aside from it being meaningless > to have GSM_PCHAN_TCH_F_PDCH time slots with 'gprs mode none', I agree > that we shouldn't send PDCH ACT in that case. The point is that when you enable/disable GPRS services on a cell, you want to modify the one (intuitive) 'gprs mode' statment in your config, and not have to remember that you also need to change the configuration of every timeslot on that BTS. I think particularly in testing scenarios (BTS used as tester for modems/m2m devices) or in research or education type applications this is a very frequent use case. > It's easy to work around: just configure TS as GSM_PCHAN_TCH_F. So I'm not > putting this high up on the todo list. > http://osmocom.org/issues/1765 Given that it should be super simple to fix (like a handful of if statements?), I'd rather do it soon than forget about the ticekt... -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From keith at rhizomatica.org Tue Jul 5 14:49:15 2016 From: keith at rhizomatica.org (Keith Whyte) Date: Tue, 5 Jul 2016 15:49:15 +0100 Subject: SS MM Messages (Call forwarding etc) Message-ID: <02c1ee83-ec65-7cb2-a597-ea0dfbe12411@rhizomatica.org> Hi All, A few weeks ago, I wrote to the list about a handset that was opening and holding an lchan after doing IMSI attach. After some investigation I see this phone is querying the network for call forwarding status. This phone then cannot send any more USSD codes, or make calls, although it can receive, but for some reason insists on doing the query again after call termination. Doing the same from other handsets, by dialling such codes as *#21# in each case gives the same result of eternal lchan usage, although some (more modern) phones seem to eventually timeout, releasing the channel while others do not. I connected numerous phones and did the same on each one and pretty soon I have a kind of DOS situation on the network in that SDCCH is at capacity. The last log message resulting from the request is /openbsc/openbsc/src/libmsc/gsm_04_08.c:3586 Dispatching 04.08 message, pdisc=11 although strangely with one phone, this is followed shortly by: libosmocore/src/gsm/gsm0480.c:219 USSD Request is too short. openbsc/openbsc/src/libmsc/ussd.c:55 Unhandled SS so for that one phone, it would seem handle_rcv_ussd() is being called from gsm0408_dispatch() I have been going through the code, basically adding more debug output to try to verify what is being called from where, and I also found the functionality in libosmocore such as gsm0480_decode_ss_request(), although this is not called at anytime from the nitb. This is an enormous project! I notice these lines in openbsc/openbsc/src/linmsc/gsm_04_08.c in gsm48_rx_mm_serv_req() /* we will send a MM message soon */ conn->expire_timer_stopped = 1; It would seem that we don't ever send this MM message. It's not clear to me where I might try to check again on the status of this MM request, or if the problem is a lack of full implementation of these supplementary service requests. Would anybody be interested in working on this with me? Keith. From holger at freyther.de Tue Jul 5 16:32:33 2016 From: holger at freyther.de (Holger Freyther) Date: Tue, 5 Jul 2016 18:32:33 +0200 Subject: SS MM Messages (Call forwarding etc) In-Reply-To: <02c1ee83-ec65-7cb2-a597-ea0dfbe12411@rhizomatica.org> References: <02c1ee83-ec65-7cb2-a597-ea0dfbe12411@rhizomatica.org> Message-ID: > On 05 Jul 2016, at 16:49, Keith Whyte wrote: > > Hi All, Hi! > I have been going through the code, basically adding more debug output > to try to verify what is being called from where, and I also found the > functionality in libosmocore such as gsm0480_decode_ss_request(), > although this is not called at anytime from the nitb. > This is an enormous project! > > I notice these lines in openbsc/openbsc/src/linmsc/gsm_04_08.c in > gsm48_rx_mm_serv_req() > > /* we will send a MM message soon */ > conn->expire_timer_stopped = 1; > > It would seem that we don't ever send this MM message. > > It's not clear to me where I might try to check again on the status of > this MM request, or if the problem is a lack of full implementation of > these supplementary service requests. > > Would anybody be interested in working on this with me? sure. Can you extract that USSD query dialogue in a pcap file for us? The "expire timer stopped" is related to periodic LUs[1] and most likely not linked to anything you are seeing. I don't know the SS codes by heart but your phone most likely queries for something like call barring, forwarding state and waits for an answer and we are happy to keep the channel open. Which means the "invokeId" is blocked in the phone.. which most likely means it will not try to use a different invokeId for the next call. The right way is to reject it. But once we have the PCAP file we can see which message to reject (or returnResultLast to). holger [1] With periodic LU a phone needs to report every X interval to the system unless it had some form of contact in between. We use expire_timer_stopped to remember that we had contact and when the subscriber connection is gone/closed we update the DB with NOW + X interval (+ margin) as the time we want to expire the subscriber. From keith at rhizomatica.org Tue Jul 5 17:48:14 2016 From: keith at rhizomatica.org (Keith Whyte) Date: Tue, 5 Jul 2016 18:48:14 +0100 Subject: SS MM Messages (Call forwarding etc) In-Reply-To: References: <02c1ee83-ec65-7cb2-a597-ea0dfbe12411@rhizomatica.org> Message-ID: <577BF2DE.3070700@rhizomatica.org> On 05/07/16 17:32, Holger Freyther wrote: > sure. Can you extract that USSD query dialogue in a pcap file for us? The "expire timer stopped" is related to periodic LUs[1] and most likely not linked to anything you are seeing. > > I don't know the SS codes by heart but your phone most likely queries for something like call barring, forwarding state and waits for an answer and we are happy to keep the channel open. Which means the "invokeId" is blocked in the phone.. which most likely means it will not try to use a different invokeId for the next call. Great, here are two pcap files. krzr.pcap is the motorola KRZR K3 as I switch aeroplane mode off and then on again. - You see interrogate SS right after the attach. Nokia.cap is sending *#21# on a nokia 6070, following by powering off as it sits at the requesting.... screen > > The right way is to reject it. But once we have the PCAP file we can see which message to reject (or returnResultLast to). :-) Looking forward to seeing how this is done, after all the code analysis I did today, it'll be very rewarding! thanks, k/ -------------- next part -------------- A non-text attachment was scrubbed... Name: krzr.pcap Type: application/vnd.tcpdump.pcap Size: 8932 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nokia.pcap Type: application/vnd.tcpdump.pcap Size: 6179 bytes Desc: not available URL: From tom at tsou.cc Tue Jul 5 22:38:27 2016 From: tom at tsou.cc (Tom Tsou) Date: Tue, 5 Jul 2016 15:38:27 -0700 Subject: osmo-bts-trx error logs -- was: GPRS on osmo-trx not working In-Reply-To: <20160705113529.GA6890@ass40.sysmocom.de> References: <20160628154548.GA19189@ass40.sysmocom.de> <20160629153130.GB1873@dub6> <20160705113529.GA6890@ass40.sysmocom.de> Message-ID: On Tue, Jul 5, 2016 at 4:35 AM, Neels Hofmeyr wrote: > My osmo-trx setup is working well now: GPRS and voice are both functional, but > I do see a *lot* of error messages in the osmo-bts-trx log. I've pasted a 5-odd > minute long log below. Most logs are errors. The errors are failed CRC checks. Over a 5 minute interval there *should* be a large number of CRC failures because of the large number of bursts that we pass from osmo-trx to osmo-bts. The receive burst gating in osmo-trx will filter out over 99% of non-active bursts, but that still leaves a very high number of false detections that need to be further gated by the CRC check in osmo-bts. For testing purposes where low SNR detection is not a concern, increasing the detection threshold in osmo-trx will reduce the false detections and CRC checks. diff --git a/Transceiver52M/Transceiver.cpp b/Transceiver52M/Transceiver.cpp index a1d0f49..b5f6ee5 100644 --- a/Transceiver52M/Transceiver.cpp +++ b/Transceiver52M/Transceiver.cpp @@ -51,7 +51,7 @@ using namespace GSM; * correlated synchronization sequences. Lower values pass more bursts up * to upper layers but will increase the false detection rate. */ -#define BURST_THRESH 4.0 +#define BURST_THRESH 10.0 TransceiverState::TransceiverState() : mRetrans(false), mNoiseLev(0.0), mNoises(NOISE_CNT), mPower(0.0) Alexander has suggested that the detection threshold should be configurable from the socket control interface. I tend to agree. > I'm ignoring the error logs, because all seems to be working well. But it > certainly looks like some things want to either be fixed or be shut up about. > > Note that the log level for DL1C is 'notice', so these are quite prominent log > messages in terms if log priority. Is there really something wrong? Otherwise > I'd suggest moving these to log level 'info' or 'debug' even. Our current strategy is to pass more bursts to osmo-bts, not less, and let the CRC determine whether a burst is valid or not. Downgrading the CRC failure to 'debug' makes sense with this approach. -TT From tom at tsou.cc Tue Jul 5 22:47:30 2016 From: tom at tsou.cc (Tom Tsou) Date: Tue, 5 Jul 2016 15:47:30 -0700 Subject: osmo-bts: Repository write acces / Gerrit migration In-Reply-To: <20160705101438.GC1727@ass40.sysmocom.de> References: <20160701102104.GG3992@nataraja> <20160705101438.GC1727@ass40.sysmocom.de> Message-ID: On Tue, Jul 5, 2016 at 3:14 AM, Neels Hofmeyr wrote: > I've just added tom at tsou.cc to the list of known users in gerrit, which > gives you permission to push private branches to the gerrit repository. Thanks Neels. It's working now. -TT From nhofmeyr at sysmocom.de Wed Jul 6 11:03:10 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 6 Jul 2016 13:03:10 +0200 Subject: dynamic PDCH Message-ID: <20160706110310.GA2560@dub6> > I am Tiger. Glad to connect with you.From osmo-bts commitment I see you are > working on dynamic PDCH which I think is a breakthrough. Is it working now? > It looks like only support PDCH and Full TCH switch,right? Hi Tiger, thanks for your comments and enquiry! I am still working on TCH/F <-> PDCH switching for the osmo-bts-trx SDR platform, but for ip.access nanobts, SysmoBTS and the litecell15, dynamic TCH/F <-> PDCH switching is already functional. TCH/F <-> PDCH could be called the ip.access compatibility mode, as it uses ip.access vendor specific messages to activate and deactivate PDCH on a TCH/F_PDCH timeslot. There are plans to include TCH/H as well, using a different vendor specific extension. Though development has not commenced yet, which will depend on funding by interested parties. See: http://osmocom.org/issues/1565 http://osmocom.org/issues/1757 BTW, Tiger, you have contacted my private email address. Instead, I'm replying from my sysmocom address, Bcc to you and copying to our mailing list, which would be the most appropriate place for questions on osmocom development. ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Wed Jul 6 14:07:04 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 6 Jul 2016 16:07:04 +0200 Subject: osmo-bts-trx error logs -- was: GPRS on osmo-trx not working In-Reply-To: References: <20160628154548.GA19189@ass40.sysmocom.de> <20160629153130.GB1873@dub6> <20160705113529.GA6890@ass40.sysmocom.de> Message-ID: <20160706140704.GA9710@dub6> On Tue, Jul 05, 2016 at 03:38:27PM -0700, Tom Tsou wrote: > Our current strategy is to pass more bursts to osmo-bts, not less, and > let the CRC determine whether a burst is valid or not. Downgrading the > CRC failure to 'debug' makes sense with this approach. Thanks for your comments! Submitted as 472 and 473: https://gerrit.osmocom.org/473 ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From linghu.yi at afarcom.com Wed Jul 6 14:06:28 2016 From: linghu.yi at afarcom.com (Tiger.Yi) Date: Wed, 06 Jul 2016 22:06:28 +0800 Subject: =?UTF-8?B?5Zue5aSN77yaZHluYW1pYyBQRENI?= In-Reply-To: 20160706110310.GA2560@dub6 References: 20160706110310.GA2560@dub6 Message-ID: <38ec14d1-7ad1-4c48-a2ab-255388c1b965.linghu.yi@afarcom.com> Thanks,Neel.It helps. ------------------------------------------------------------------????Neels Hofmeyr ?????2016?7?6?(???) 19:03????openbsc ????dynamic PDCH >?I?am?Tiger.??Glad?to?connect?with?you.From?osmo-bts?commitment?I?see?you?are >?working?on?dynamic?PDCH?which?I?think?is?a?breakthrough.???Is?it?working?now? >?It?looks?like?only?support?PDCH?and?Full?TCH?switch,right? Hi?Tiger, thanks?for?your?comments?and?enquiry! I?am?still?working?on?TCH/F?<->?PDCH?switching?for?the?osmo-bts-trx?SDR platform,?but?for?ip.access?nanobts,?SysmoBTS?and?the?litecell15,?dynamic TCH/F?<->?PDCH?switching?is?already?functional. TCH/F?<->?PDCH?could?be?called?the?ip.access?compatibility?mode,?as?it?uses ip.access?vendor?specific?messages?to?activate?and?deactivate?PDCH?on?a TCH/F_PDCH?timeslot. There?are?plans?to?include?TCH/H?as?well,?using?a?different?vendor?specific extension.?Though?development?has?not?commenced?yet,?which?will?depend?on funding?by?interested?parties. See: http://osmocom.org/issues/1565 http://osmocom.org/issues/1757 BTW,?Tiger,?you?have?contacted?my?private?email?address.?Instead,?I'm?replying from?my?sysmocom?address,?Bcc?to?you?and?copying?to?our?mailing?list,?which would?be?the?most?appropriate?place?for?questions?on?osmocom?development. ~Neels --? -?Neels?Hofmeyr???????????http://www.sysmocom.de/ ======================================================================= *?sysmocom?-?systems?for?mobile?communications?GmbH *?Alt-Moabit?93 *?10559?Berlin,?Germany *?Sitz?/?Registered?office:?Berlin,?HRB?134158?B *?Gesch?ftsf?hrer?/?Managing?Directors:?Harald?Welte -------------- next part -------------- An HTML attachment was scrubbed... URL: From nhofmeyr at sysmocom.de Wed Jul 6 16:17:37 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 6 Jul 2016 18:17:37 +0200 Subject: osmo-bts: Repository write acces / Gerrit migration In-Reply-To: References: <20160701102104.GG3992@nataraja> <20160705101438.GC1727@ass40.sysmocom.de> <20160706114935.GB2560@dub6> Message-ID: <20160706161737.GD9710@dub6> On Wed, Jul 06, 2016 at 04:15:08PM +0300, Alexander Chemeris wrote: > Username: ipse > Full Name: Alexander Chemeris Misunderstanding: this is your osmocom.org redmine account. Please also register with gerrit.osmocom.org for commit access. You may do so using above osmocom.org account as OpenID provider: http://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit#Configuring-GerritAccount ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Wed Jul 6 16:58:40 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 6 Jul 2016 18:58:40 +0200 Subject: merging iu specific branches to master Message-ID: <20160706165840.GA3989@dub6> Hi 3G folks, I would like to make our osmocom jenkins build openbsc with --enable-iu, which still requires use of non-master branches in aper-prefix, libosmo-sccp and libosmo-netif. I will at first make the jenkins build use these branches to build 3G, but since we'd like them to be merged to master anyway, let's try to push this forward. Here are the remaining tasks again, as from the openbsc@ mail on Feb 19, 2016: http://lists.osmocom.org/pipermail/openbsc/2016-February/007906.html ( <20160219083519.GA4570 at nataraja> ) First the good news for libosmo-sccp: On Fri, Feb 19, 2016 at 09:35:19AM +0100, Harald Welte wrote: > > libosmo-sccp: * laforge/wip > > My main problem with this patch set is naming. We are creating an 'SCCP > User SAP' which should look the same no matter what the underlying > transport protocol stacking is. [...] This boils down to a mere rename of opaque structs osmo_sua_link and osmo_sua_user, which I've started to submit. https://gerrit.osmocom.org/477 > > asn1c: * aper-prefix First of all, it looks like we imported from svn, but Lev Walkin later did another migration to git, which we fetched as well. So our master is on our old svn import, while the upstream master has different hashes in its history. Our aper-prefix branch is based on the upstream history, not our "stale" master, which made a rebase a bit easier. Furthermore, on https://github.com/vlm/asn1c/commits/master there are scores of new commits we don't have in our asn1c. our last commit from Lev Walkin is from 2015-04-28, "?= was confusing some environments", 62913d8b8e1eb96d74315ff I have thus: * fetched upstream master from github's vlm/asn1c, pushed as new branch vlm/master to our git.osmocom.org/asn1c * rebased our aper-prefix branch to that master (with minor conflicts), pushed as new branch aper-prefix-onto-upstream We should probably: * reset --hard our master to vlm/master * reset --hard our aper-prefix to aper-prefix-onto-upstream (after testing) Agreed? Then follows: On Fri, Feb 19, 2016 at 09:35:19AM +0100, Harald Welte wrote: > > If you look at the aper code I took from OpenAirInterface and re-based, For the record: https://gitlab.eurecom.fr/oai/openair-cn/tree/master/SRC/S1AP/MESSAGES/ASN1 https://gitlab.eurecom.fr/oai/openair-cn/blob/master/SRC/S1AP/MESSAGES/ASN1/asn1cpatch.p0 https://gitlab.eurecom.fr/oai/openair-cn/blob/master/SRC/S1AP/MESSAGES/ASN1/asn1tostruct.py > you will see that it does not look 100% complete and would > probably not yet qualify for submitting it to the upstream asn1c > project. The situation is not made better by my hackish way to > implement the type prefixing on top of it by means of an environment > variable. > > Specifically, it > * contains commented-out code which might just have been a work-around > of some buggy code, rather than fit for removal in general > * contains TODO comments like "/* TODO: act upon NOTE in #18.7 for > canonical PER */" which hints that it is not properly implementing > parts of the PER specification > * contrary to the rest of asn1c, it does not come with a comprehensive > test suiet for the APER encoding and decoding routines of all types > > Any help in cleaning this code up (it could be done for the type > prefixing independent of the APER support) would be much appreciated. > The goal is to get this merged in asn1c, after all. > > It might also be worth to contact the OpenAirInterface guys about their > thoughts on moving this code forward. I fear there might be none, as > they are using an ancient version of asn1c to begin with. But they are > a much larger project and might be convinced to put some resources on > doing this properly? I've written to the openair-cn-devel list. https://lists.eurecom.fr/sympa/arc/openaircn-devel/2016-07/msg00001.html > Unless we think something is ready for pushing to upstream asn1c, we > should keep it out of our local master, too. > > libosmo-netif: * sysmocom/sctp > > commit d484b0593112222cef3f106da654df07c3d40919 (hash changed after rebases) > basically just > prints some messages to the log file in case there are association state > changes like UP and LOST. This is clearly not the intended behavior. > > The application should be notified accordintly in such events, > particularly in 'connection lost' events that can be communicated in the > same way as they can for e.g. TCP sockets. > > Only after that is resolved, we can merge it to master. This doesn't look like a lot of work, though I'm not familiar with how exactly this should be done. ret = sctp_recvmsg(conn->ofd.fd, msgb_data(msg), msgb_tailroom(msg), NULL, NULL, &sinfo, &flags); if (flags & MSG_NOTIFICATION) { union sctp_notification *notif = (union sctp_notification *) msgb_data(msg); LOGP(DLINP, LOGL_DEBUG, "NOTIFICATION %u flags=0x%x\n", notif->sn_header.sn_type, switch (notif->sn_header.sn_type) { case SCTP_ASSOC_CHANGE: LOGP(DLINP, LOGL_DEBUG, "===> ASSOC CHANGE:"); switch (notif->sn_assoc_change.sac_state) { case SCTP_COMM_UP: LOGPC(DLINP, LOGL_DEBUG, " UP\n"); call accept_cb? break; case SCTP_COMM_LOST: LOGPC(DLINP, LOGL_DEBUG, " LOST\n"); osmo_stream_srv_destroy() ? break; case SCTP_RESTART: LOGPC(DLINP, LOGL_DEBUG, " RESTART\n"); break; case SCTP_SHUTDOWN_COMP: LOGPC(DLINP, LOGL_DEBUG, " SHUTDOWN COMP\n"); break; case SCTP_CANT_STR_ASSOC: LOGPC(DLINP, LOGL_DEBUG, " CANT STR ASSOC\n"); break; } break; case SCTP_PEER_ADDR_CHANGE: LOGP(DLINP, LOGL_DEBUG, "===> PEER ADDR CHANGE\n"); break; case SCTP_SHUTDOWN_EVENT: LOGP(DLINP, LOGL_DEBUG, "===> SHUTDOWN EVT\n"); /* Handle this like a regular disconnect */ osmo_stream_srv_destroy() ? return 0; break; } return -EAGAIN; Thanks for any thoughts or even help :) ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From tom at tsou.cc Wed Jul 6 19:13:39 2016 From: tom at tsou.cc (Tom Tsou) Date: Wed, 6 Jul 2016 12:13:39 -0700 Subject: [PATCH 0/2] osmo-trx: add .gitignore, add a configure check In-Reply-To: <1467716418-7551-1-git-send-email-nhofmeyr@sysmocom.de> References: <1467716418-7551-1-git-send-email-nhofmeyr@sysmocom.de> Message-ID: Merged. -TT On Tue, Jul 5, 2016 at 4:00 AM, Neels Hofmeyr wrote: > From: Neels Hofmeyr > > Rebased the patches onto updated master, added a binary to .gitignore. > > Neels Hofmeyr (2): > add basic .gitignore > configure.ac: check for boost/config.hpp header > > .gitignore | 44 ++++++++++++++++++++++++++++++++++++++++++++ > configure.ac | 3 +++ > 2 files changed, 47 insertions(+) > create mode 100644 .gitignore > > -- > 2.1.4 > From tom at tsou.cc Thu Jul 7 04:58:33 2016 From: tom at tsou.cc (Tom Tsou) Date: Wed, 6 Jul 2016 21:58:33 -0700 Subject: OsmoTRX / BER, RSSI and Link Quality In-Reply-To: References: <20160621085134.GF5199@nataraja> Message-ID: On Tue, Jun 21, 2016 at 11:36 AM, Alexander Chemeris wrote: > I introduced BER calculations in osmo-bts-trx some time ago for DATA, > so the data is there - see gsm0503_coding.c, *_decode() functions. I > also updated the code to pass this information to upper layers - see > rx_tchf_fn(), rx_tchh_fn(), rx_pdtch_fn() in scheduler_trx.c. I tested > that the data actually gets to measurement reports for TCH and SDDCH, > but I don't remember if we tested this for GPRS. Are you sure it > doesn't work with the current master? If so, it probably got broken > during the rebase or after that. Measurement reports do appear to be going out through l1if_process_meas_res(), but the BER calculation is incorrect because of puncturing, which is significant for higher CS/MCS values. The full BER calculation takes the re-coded and re-punctured sequence (performed after decoding and CRC verification) and compares to the decision sliced receive sequence. But, the full calculation may be unnecessary. A close and simple approximation to the full BER calculation treats all zero valued soft bits as punctured bits and removes them from the calculation. @@ -509,6 +509,8 @@ int osmo_conv_decode_ber(const struct osmo_conv_code if (n_errors) { *n_errors = 0; for (i=0; i< *n_bits_total; i++) { + if (!input[i]) + continue; if (! ((recoded[i] && input[i]<0) || (!recoded[i] && input[i]>0)) ) *n_errors += 1; I think this is a reasonable approach to make the current BER measurement sane. > I didn't do that for RACH, because currently RACH gating is performed > in osmo-trx and works pretty well as far as I can tell, so > osmo-bts-trx gets RACH's which are valid with high probability. > > We can introduce an option to turn osmo-trx built-in RACH gating and > rely on osmo-bts instead and then compare which one works better. That > should be a minor change - I'm happy to implement this a bit later. We will always have some level of burst gating in the TRX to remove clearly invalid or unrecoverable bursts (e.g. unrealistic TOA values). One option is to reduce the detection threshold close to zero so that any 'reasonable' burst is passed. This seems like another reason to add configurable burst threshold detection to osmo-bts-trx. -TT From alexander.chemeris at gmail.com Thu Jul 7 05:19:23 2016 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Thu, 7 Jul 2016 08:19:23 +0300 Subject: OsmoTRX / BER, RSSI and Link Quality In-Reply-To: References: <20160621085134.GF5199@nataraja> Message-ID: Hi Tom, On Jul 7, 2016 7:58 AM, "Tom Tsou" wrote: > > On Tue, Jun 21, 2016 at 11:36 AM, Alexander Chemeris > wrote: > > I introduced BER calculations in osmo-bts-trx some time ago for DATA, > > so the data is there - see gsm0503_coding.c, *_decode() functions. I > > also updated the code to pass this information to upper layers - see > > rx_tchf_fn(), rx_tchh_fn(), rx_pdtch_fn() in scheduler_trx.c. I tested > > that the data actually gets to measurement reports for TCH and SDDCH, > > but I don't remember if we tested this for GPRS. Are you sure it > > doesn't work with the current master? If so, it probably got broken > > during the rebase or after that. > > Measurement reports do appear to be going out through > l1if_process_meas_res(), but the BER calculation is incorrect because > of puncturing, which is significant for higher CS/MCS values. > > The full BER calculation takes the re-coded and re-punctured sequence > (performed after decoding and CRC verification) Why after CRC? > and compares to the > decision sliced receive sequence. But, the full calculation may be > unnecessary. > > A close and simple approximation to the full BER calculation treats > all zero valued soft bits as punctured bits and removes them from the > calculation. > > I think this is a reasonable approach to make the current BER measurement sane. Why do you think re-puncturing is not a good approach - because of the added CPU load? > > I didn't do that for RACH, because currently RACH gating is performed > > in osmo-trx and works pretty well as far as I can tell, so > > osmo-bts-trx gets RACH's which are valid with high probability. > > > > We can introduce an option to turn osmo-trx built-in RACH gating and > > rely on osmo-bts instead and then compare which one works better. That > > should be a minor change - I'm happy to implement this a bit later. > > We will always have some level of burst gating in the TRX to remove > clearly invalid or unrecoverable bursts (e.g. unrealistic TOA values). > One option is to reduce the detection threshold close to zero so that > any 'reasonable' burst is passed. This seems like another reason to > add configurable burst threshold detection to osmo-bts-trx. Sounds like a good approach. Please excuse typos. Written with a touchscreen keyboard. -- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alexander.Chemeris at fairwaves.co Thu Jul 7 05:36:06 2016 From: Alexander.Chemeris at fairwaves.co (Alexander Chemeris) Date: Thu, 7 Jul 2016 08:36:06 +0300 Subject: osmo-bts: Repository write acces / Gerrit migration In-Reply-To: <20160706161737.GD9710@dub6> References: <20160701102104.GG3992@nataraja> <20160705101438.GC1727@ass40.sysmocom.de> <20160706114935.GB2560@dub6> <20160706161737.GD9710@dub6> Message-ID: On Jul 6, 2016 7:17 PM, "Neels Hofmeyr" wrote: > > On Wed, Jul 06, 2016 at 04:15:08PM +0300, Alexander Chemeris wrote: > > Username: ipse > > Full Name: Alexander Chemeris > > Misunderstanding: this is your osmocom.org redmine account. > Please also register with gerrit.osmocom.org for commit access. Believe it or not, but that's the information from my Gerrit user info page. > You may do so using above osmocom.org account as OpenID provider: > http://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit#Configuring-GerritAccount That's exactly what I use. Please excuse typos. Written with a touchscreen keyboard. -- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co -------------- next part -------------- An HTML attachment was scrubbed... URL: From nhofmeyr at sysmocom.de Thu Jul 7 11:40:17 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 7 Jul 2016 13:40:17 +0200 Subject: osmo-bts: Repository write acces / Gerrit migration In-Reply-To: References: <20160701102104.GG3992@nataraja> <20160705101438.GC1727@ass40.sysmocom.de> <20160706114935.GB2560@dub6> <20160706161737.GD9710@dub6> Message-ID: <20160707114017.GD1523@dub6> On Thu, Jul 07, 2016 at 08:36:06AM +0300, Alexander Chemeris wrote: > Believe it or not, but that's the information from my Gerrit user info page. Thanks for your patience -- the Gerrit UI for some weird reason refuses to offer your account's name in the group editing dialog. I took a close look at the database to find out why, but could find no difference to other accounts. For the record, simply entering the user ID (10000NN number) in the dialog worked, despite the user not being offered by the UI. So providing the gerrit user ID is indeed the easiest and most fool proof way. In short, Alexander, you should finally be a known user and may push private branches now. You may verify that using the sandbox repository: git clone ssh://$USERNAME at gerrit.osmocom.org:29418/sandbox.git ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From holger at freyther.de Thu Jul 7 12:39:57 2016 From: holger at freyther.de (Holger Freyther) Date: Thu, 7 Jul 2016 14:39:57 +0200 Subject: SS MM Messages (Call forwarding etc) In-Reply-To: <577BF2DE.3070700@rhizomatica.org> References: <02c1ee83-ec65-7cb2-a597-ea0dfbe12411@rhizomatica.org> <577BF2DE.3070700@rhizomatica.org> Message-ID: <47DF1FB6-0D3D-488D-8C98-BDF6DEC55149@freyther.de> > On 05 Jul 2016, at 19:48, Keith Whyte wrote: > > > Nokia.cap is sending *#21# on a nokia 6070, following by powering off as > it sits at the requesting.... screen thank you. The ussd.c has "reject" calls in many of the paths but I don't see a response at all. I will start by adding your payload to the libosmocore ussd decoding test and see how much we handle that message and then move forward to use the Smalltalk BTS to simulate that CM Service Request + facility message. holger From tom at tsou.cc Thu Jul 7 20:24:38 2016 From: tom at tsou.cc (Tom Tsou) Date: Thu, 7 Jul 2016 13:24:38 -0700 Subject: OsmoTRX / BER, RSSI and Link Quality In-Reply-To: References: <20160621085134.GF5199@nataraja> Message-ID: On Wed, Jul 6, 2016 at 10:19 PM, Alexander Chemeris wrote: > On Jul 7, 2016 7:58 AM, "Tom Tsou" wrote: >> The full BER calculation takes the re-coded and re-punctured sequence >> (performed after decoding and CRC verification) > > Why after CRC? Assume that we lower the detection threshold in the TRX and allow the OsmoBTS to perform most of the burst gating based on the CRC. If we calculate BER before the CRC, then the BER will be computed mostly on garbage data. >> A close and simple approximation to the full BER calculation treats >> all zero valued soft bits as punctured bits and removes them from the >> calculation. >> >> I think this is a reasonable approach to make the current BER measurement >> sane. > > Why do you think re-puncturing is not a good approach - because of the added > CPU load? Yes, there is overhead. But, more simply, re-puncturing doesn't gain very much. If we increase the accuracy of our BER calculation by some fraction of a percent, will that really improve UE performance? -TT From laforge at gnumonks.org Sat Jul 9 17:07:33 2016 From: laforge at gnumonks.org (Harald Welte) Date: Sat, 9 Jul 2016 19:07:33 +0200 Subject: merging iu specific branches to master In-Reply-To: <20160706165840.GA3989@dub6> References: <20160706165840.GA3989@dub6> Message-ID: <20160709170733.GA7873@nataraja> On Wed, Jul 06, 2016 at 06:58:40PM +0200, Neels Hofmeyr wrote: > We should probably: > * reset --hard our master to vlm/master > * reset --hard our aper-prefix to aper-prefix-onto-upstream (after testing) > > Agreed? ACK. > > commit > d484b0593112222cef3f106da654df07c3d40919 (hash changed after rebases) > > basically just > > prints some messages to the log file in case there are association state > > changes like UP and LOST. This is clearly not the intended behavior. > > > > The application should be notified accordintly in such events, > > particularly in 'connection lost' events that can be communicated in the > > same way as they can for e.g. TCP sockets. > > > > Only after that is resolved, we can merge it to master. > > This doesn't look like a lot of work, though I'm not familiar with how exactly > this should be done. That's exactly the "hard" question and it probably needs a number of test cases and trial+error to find out. A TCP socket is diffent in that once it is closed, it is closed, and the client can only re-connect, which means a new FD will be accept()ed on the server. In SCTP, the association can go UP and DOWN any number of times during its lifetime, and the file descriptors stay the same. I'd say the minimum level for getting it merged is that a SUA-using application on both server and client side continues to work correctly after any of the events (e.g. an DOWN notification followed by UP notification). Also, if the socket is SHUTDOWN, the application should deal with it in a meaningful way. Basically, whatever happens "legally" on the SCTP side should not make a client or server application stuck in some weird state. One could also imagine that any more complete signalling gateway would actually be interested in all fine-grained event, so having a mechanism in which any SCTP notifications more or less transparently up to the user might be a good idea. But that could be an unrelated future improvement patch. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From sipos.csaba at kvk.uni-obuda.hu Sun Jul 10 16:43:51 2016 From: sipos.csaba at kvk.uni-obuda.hu (Sipos Csaba) Date: Sun, 10 Jul 2016 18:43:51 +0200 (CEST) Subject: Full state machine implementation In-Reply-To: <354879786.6794759.1468168663068.JavaMail.zimbra@kvk.uni-obuda.hu> Message-ID: <306806706.6794993.1468169031672.JavaMail.zimbra@kvk.uni-obuda.hu> Dear Harald, Just seen your branch regarding FSM: http://cgit.osmocom.org/openbsc/log/?h=laforge/om2000-fsm Do you think this is also doable for the Nokia Site BTS series? Because if you think its doable, based on your work I a would like to try and implement this for Nokia support too, as even between different Site versions (InSite, Metro and UltraStie), there are some differences in the OML initialization (especially in the timing of it) which is now handled by hard coded values, instead of a proper state machine. Regards, Csaba From laforge at gnumonks.org Sun Jul 10 19:55:30 2016 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 10 Jul 2016 21:55:30 +0200 Subject: Full state machine implementation In-Reply-To: <306806706.6794993.1468169031672.JavaMail.zimbra@kvk.uni-obuda.hu> References: <354879786.6794759.1468168663068.JavaMail.zimbra@kvk.uni-obuda.hu> <306806706.6794993.1468169031672.JavaMail.zimbra@kvk.uni-obuda.hu> Message-ID: <20160710195530.GC26877@nataraja> Hi Sipos, On Sun, Jul 10, 2016 at 06:43:51PM +0200, Sipos Csaba wrote: > Just seen your branch regarding FSM: > > http://cgit.osmocom.org/openbsc/log/?h=laforge/om2000-fsm I'm happy at least somebody notices this work :) It's not complete yet (hence the WIP), and it currently only implements the initialization as set of hierarchical state machines. The FSMs terminate once initialization is done. This could and should probably be further extended to having the BSC-side per-MO FSMs running persistently and tracking the state of their counterparts in the BTS. I also committed the OM2000 MO initialization sequences messace sequence charts to osmo-gsm-manuals, in case you're curious to see how code corresponds the protocol messages. > Do you think this is also doable for the Nokia Site BTS series? Of course, why not? I've never looked too deep at the Nokia OML dialect/flavor though. I think for most users the more important part would be the generic one for the TS 12.21 managed objects, which then helps for nanoBTS, OsmoBTS and BS-11. > Because if you think its doable, based on your work I a would like to > try and implement this for Nokia support too, as even between > different Site versions (InSite, Metro and UltraStie), there are some > differences in the OML initialization (especially in the timing of it) > which is now handled by hard coded values, instead of a proper state > machine. Sure, I think it would make a lot of sense, technically. I'm just not sure how many OpenBSC useres with Nokia BTS are out there. But that shouldn't keep you from doing it, if you feel an urge to do so :) -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From sipos.csaba at kvk.uni-obuda.hu Sun Jul 10 20:45:13 2016 From: sipos.csaba at kvk.uni-obuda.hu (Sipos Csaba) Date: Sun, 10 Jul 2016 22:45:13 +0200 (CEST) Subject: Full state machine implementation In-Reply-To: <20160710195530.GC26877@nataraja> References: <354879786.6794759.1468168663068.JavaMail.zimbra@kvk.uni-obuda.hu> <306806706.6794993.1468169031672.JavaMail.zimbra@kvk.uni-obuda.hu> <20160710195530.GC26877@nataraja> Message-ID: <1895125296.6810311.1468183513471.JavaMail.zimbra@kvk.uni-obuda.hu> Hi Harald, > I'm happy at least somebody notices this work :) I am reading the code on a daily basis, so no change is unnoticed :-) I am also reading your blog and watched most of your presentations on CCC. But back on the topic. I went through the code and for the first time I thought that the OM2000 code is somewhat generic and can be reused of the Nokia part. Then I realised that only the high level of the OML is standardised, the information elements for example do not, and the stuff in OM2000 files are specific to the RBS2000. Anyway, will take a closer look an try to figure out how this can be implemented for the Nokia part. Maybe this one will be a bit more interesting: there is a chance I can put my hands on a DBS3900 with a 2G baseband card in it :-) I am not sure how similar Huawei's IP Abis implementation is to what we have now, but I can certainly take a look :-) There's also some outstanding commits for Nokia regarding hopping, will try to rebase them for the current state of the BSC code and send it to you. Regards, Csaba ----- Eredeti ?zenet ----- Felad?: "Harald Welte" C?mzett: "Sipos Csaba" M?solatot kap: "OpenBSC Mailing List" Elk?ld?tt ?zenetek: Vas?rnap, 2016. J?lius 10. 21:55:30 T?rgy: Re: Full state machine implementation Hi Sipos, On Sun, Jul 10, 2016 at 06:43:51PM +0200, Sipos Csaba wrote: > Just seen your branch regarding FSM: > > http://cgit.osmocom.org/openbsc/log/?h=laforge/om2000-fsm I'm happy at least somebody notices this work :) It's not complete yet (hence the WIP), and it currently only implements the initialization as set of hierarchical state machines. The FSMs terminate once initialization is done. This could and should probably be further extended to having the BSC-side per-MO FSMs running persistently and tracking the state of their counterparts in the BTS. I also committed the OM2000 MO initialization sequences messace sequence charts to osmo-gsm-manuals, in case you're curious to see how code corresponds the protocol messages. > Do you think this is also doable for the Nokia Site BTS series? Of course, why not? I've never looked too deep at the Nokia OML dialect/flavor though. I think for most users the more important part would be the generic one for the TS 12.21 managed objects, which then helps for nanoBTS, OsmoBTS and BS-11. > Because if you think its doable, based on your work I a would like to > try and implement this for Nokia support too, as even between > different Site versions (InSite, Metro and UltraStie), there are some > differences in the OML initialization (especially in the timing of it) > which is now handled by hard coded values, instead of a proper state > machine. Sure, I think it would make a lot of sense, technically. I'm just not sure how many OpenBSC useres with Nokia BTS are out there. But that shouldn't keep you from doing it, if you feel an urge to do so :) -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From msuraev at sysmocom.de Mon Jul 11 11:24:36 2016 From: msuraev at sysmocom.de (Max) Date: Mon, 11 Jul 2016 13:24:36 +0200 Subject: osmo-bts-trx error logs -- was: GPRS on osmo-trx not working In-Reply-To: <20160705113529.GA6890@ass40.sysmocom.de> References: <20160628154548.GA19189@ass40.sysmocom.de> <20160629153130.GB1873@dub6> <20160705113529.GA6890@ass40.sysmocom.de> Message-ID: <578381F4.2010500@sysmocom.de> Which voice codecs are you using? Have you tried AMR? On 07/05/2016 01:35 PM, Neels Hofmeyr wrote: > On Wed, Jun 29, 2016 at 12:02:56PM -0700, Tom Tsou wrote: >> I see various error messages that occur in different layers at >> startup. I can definitely confirm that some of these messages are >> caused by initial Tx/Rx chain and device synchronization. Given that >> these initialization errors (e.g. early stale bursts, dropped packets) >> are harmless as long as they only happen once, I'm OK with ignoring >> them for now. >> >> I assume there are other effects and similar concerns that take place >> higher up the chain. >> >>> 20160629171522824 DL1C <0006> scheduler_trx.c:1420 GSM clock skew: old fn=463983, new fn=463888 >>> 20160629171523170 DL1C <0006> scheduler_trx.c:1420 GSM clock skew: old fn=463963, new fn=463888 >>> 20160629171523817 DL1C <0006> scheduler.c:240 Prim for trx=0 ts=0 at fn=464004 is out of range, or channel already disabled. If this happens in conjunction with PCU, increase 'rts-advance' by 5. (current fn=464010) >>> >>> Ignoring it for now. >> With different log settings I do see the 'rts-advance' messages. I'm >> ignoring these for now as well. >> >> Another non-startup error message I found is bad PDTCH and PTCCH and >> blocks under ideal RF signal conditions. It appears that you have seen >> this behavior as well. >> >> DL1C <0006> scheduler_trx.c:835 Received bad data frame at fn=372020 >> (12/104) for PTCCH >> DL1C <0006> scheduler_trx.c:918 Received bad PDTCH block ending at >> fn=310516 (76/104) for PDTCH > For completeness sake... > > My osmo-trx setup is working well now: GPRS and voice are both functional, but > I do see a *lot* of error messages in the osmo-bts-trx log. I've pasted a 5-odd > minute long log below. Most logs are errors. > > I'm ignoring the error logs, because all seems to be working well. But it > certainly looks like some things want to either be fixed or be shut up about. > > Possibly some remote mobile devices, other than my two test phones on the desk, > are transmitting just above noise level and causing erratic frames and blocks? > > Note that the log level for DL1C is 'notice', so these are quite prominent log > messages in terms if log priority. Is there really something wrong? Otherwise > I'd suggest moving these to log level 'info' or 'debug' even. > > ~Neels > > > 20160705131650139 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2368772 (68/104) for PDTCH > 20160705131650139 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2368772 (68/104) for PDTCH > 20160705131650229 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2368791 toa=2.93 > 20160705131650229 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2368791 (45/51) > 20160705131650418 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2368833 toa=-2.66 > 20160705131650418 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2368833 (36/51) > 20160705131650524 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2368854 (46/104) for PDTCH > 20160705131650524 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2368854 (46/104) for PDTCH > 20160705131653716 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2369547 (11/104) for PDTCH > 20160705131653716 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2369547 (11/104) for PDTCH > 20160705131654463 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2369709 toa=-1.34 > 20160705131654463 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2369709 (45/51) > 20160705131656282 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2370103 toa=5.27 > 20160705131656282 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2370103 (31/51) > 20160705131656841 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2370223 (63/104) for PDTCH > 20160705131656841 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2370223 (63/104) for PDTCH > 20160705131657927 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2370459 toa=4.99 > 20160705131657928 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2370459 (30/51) > 20160705131658086 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2370494 toa=5.08 > 20160705131658086 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2370494 (14/51) > 20160705131658101 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2370496 (24/104) for PDTCH > 20160705131658101 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2370496 (24/104) for PDTCH > 20160705131658795 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2370647 toa=-1.25 > 20160705131658795 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2370647 (14/51) > 20160705131701905 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2371320 (16/104) for PDTCH > 20160705131701905 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2371320 (16/104) for PDTCH > 20160705131702893 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2371535 toa=1.77 > 20160705131702893 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2371535 (35/51) > 20160705131702924 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2371541 (29/104) for PDTCH > 20160705131702924 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2371541 (29/104) for PDTCH > 20160705131703460 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2371658 (42/104) for PDTCH > 20160705131703460 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2371658 (42/104) for PDTCH > 20160705131704365 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2371853 (29/104) for PDTCH > 20160705131704365 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2371853 (29/104) for PDTCH > 20160705131710116 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2373100 toa=1.93 > 20160705131710116 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2373100 (19/51) > 20160705131710501 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2373183 (7/104) for PDTCH > 20160705131710501 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2373183 (7/104) for PDTCH > 20160705131714342 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2374015 (7/104) for PDTCH > 20160705131714342 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2374015 (7/104) for PDTCH > 20160705131716040 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2374384 toa=1.59 > 20160705131716041 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2374384 (28/51) > 20160705131716342 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2374448 (24/104) for PDTCH > 20160705131717180 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2374631 toa=1.36 > 20160705131717180 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2374631 (20/51) > 20160705131717701 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2374744 toa=-2.93 > 20160705131717701 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2374744 (31/51) > 20160705131718161 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2374843 toa=1.14 > 20160705131718161 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2374843 (28/51) > 20160705131719135 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375055 toa=0.97 > 20160705131719135 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375055 (36/51) > 20160705131720237 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375293 toa=0.73 > 20160705131720237 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375293 (19/51) > 20160705131720938 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2375445 (85/104) for PDTCH > 20160705131720939 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2375445 (85/104) for PDTCH > 20160705131721233 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375508 toa=0.54 > 20160705131721233 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375508 (30/51) > 20160705131722289 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375737 toa=0.34 > 20160705131722289 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375737 (4/51) > 20160705131723323 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2375961 toa=0.10 > 20160705131723323 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2375961 (24/51) > 20160705131723580 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2376017 (33/104) for PDTCH > 20160705131723580 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2376017 (33/104) for PDTCH > 20160705131724531 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2376223 toa=1.06 > 20160705131724531 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2376223 (31/51) > 20160705131726131 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2376570 toa=-0.41 > 20160705131726131 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2376570 (21/51) > 20160705131726357 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2376619 (11/104) for PDTCH > 20160705131726358 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2376619 (11/104) for PDTCH > 20160705131727112 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2376782 toa=-0.60 > 20160705131727112 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2376782 (29/51) > 20160705131728040 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2376983 (63/104) for PDTCH > 20160705131728041 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2376983 (63/104) for PDTCH > 20160705131728169 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377012 toa=-0.81 > 20160705131728501 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377083 (59/104) for PDTCH > 20160705131728516 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377087 (63/104) for PDTCH > 20160705131728538 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377092 (68/104) for PDTCH > 20160705131728561 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377096 (72/104) for PDTCH > 20160705131728576 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377100 (76/104) for PDTCH > 20160705131728599 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377105 (81/104) for PDTCH > 20160705131728621 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377109 (85/104) for PDTCH > 20160705131728637 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377113 (89/104) for PDTCH > 20160705131728651 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2372460 (12/104) for PTCCH > 20160705131728652 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2372460 (12/104) for PTCCH > 20160705131728659 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377118 (94/104) for PDTCH > 20160705131728682 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377122 (98/104) for PDTCH > 20160705131728697 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377126 (102/104) for PDTCH > 20160705131728720 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377131 (3/104) for PDTCH > 20160705131728742 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377135 (7/104) for PDTCH > 20160705131728757 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377139 (11/104) for PDTCH > 20160705131728780 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377144 (16/104) for PDTCH > 20160705131728803 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377148 (20/104) for PDTCH > 20160705131728818 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377152 (24/104) for PDTCH > 20160705131728840 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377157 (29/104) for PDTCH > 20160705131728863 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377161 (33/104) for PDTCH > 20160705131728878 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377165 (37/104) for PDTCH > 20160705131728901 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377170 (42/104) for PDTCH > 20160705131728923 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377174 (46/104) for PDTCH > 20160705131728938 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377178 (50/104) for PDTCH > 20160705131728961 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377183 (55/104) for PDTCH > 20160705131728984 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377187 (59/104) for PDTCH > 20160705131728999 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377191 (63/104) for PDTCH > 20160705131729021 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377196 (68/104) for PDTCH > 20160705131729044 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377200 (72/104) for PDTCH > 20160705131729059 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377204 (76/104) for PDTCH > 20160705131729082 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377209 (81/104) for PDTCH > 20160705131729097 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377213 (85/104) for PDTCH > 20160705131729120 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377217 (89/104) for PDTCH > 20160705131729127 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2377140 (12/104) for PTCCH > 20160705131729142 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377222 (94/104) for PDTCH > 20160705131729157 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377226 (98/104) for PDTCH > 20160705131729180 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377230 (102/104) for PDTCH > 20160705131729203 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377235 (3/104) for PDTCH > 20160705131729218 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377239 (7/104) for PDTCH > 20160705131729240 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377243 (11/104) for PDTCH > 20160705131729263 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377248 (16/104) for PDTCH > 20160705131729278 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377252 (20/104) for PDTCH > 20160705131729301 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377256 (24/104) for PDTCH > 20160705131729323 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377261 (29/104) for PDTCH > 20160705131729338 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377265 (33/104) for PDTCH > 20160705131729361 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377269 (37/104) for PDTCH > 20160705131729384 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377274 (42/104) for PDTCH > 20160705131729399 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377278 (46/104) for PDTCH > 20160705131729421 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377282 (50/104) for PDTCH > 20160705131729444 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377287 (55/104) for PDTCH > 20160705131729459 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377291 (59/104) for PDTCH > 20160705131729482 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377295 (63/104) for PDTCH > 20160705131729504 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377300 (68/104) for PDTCH > 20160705131729520 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377304 (72/104) for PDTCH > 20160705131729542 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377308 (76/104) for PDTCH > 20160705131729565 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377313 (81/104) for PDTCH > 20160705131729580 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2377317 (85/104) for PDTCH > 20160705131729731 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377350 toa=-0.57 > 20160705131729731 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377350 (36/51) > 20160705131729821 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377369 toa=3.35 > 20160705131729821 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377369 (4/51) > 20160705131730621 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377543 toa=4.32 > 20160705131730622 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377543 (25/51) > 20160705131730833 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377588 toa=-0.77 > 20160705131730833 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377588 (19/51) > 20160705131731852 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2377809 toa=-0.98 > 20160705131731852 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2377809 (36/51) > 20160705131732757 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2378006 (46/104) for PDTCH > 20160705131732757 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378006 (46/104) for PDTCH > 20160705131732946 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378047 toa=-1.16 > 20160705131732946 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2378047 (19/51) > 20160705131732976 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378053 toa=1.18 > 20160705131732976 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2378053 (25/51) > 20160705131733844 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2378240 (72/104) for PDTCH > 20160705131733844 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378240 (72/104) for PDTCH > 20160705131733942 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378262 toa=-1.34 > 20160705131733942 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2378262 (30/51) > 20160705131735044 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378501 toa=-1.52 > 20160705131735323 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378561 (81/104) for PDTCH > 20160705131735339 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378565 (85/104) for PDTCH > 20160705131735361 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378569 (89/104) for PDTCH > 20160705131735369 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2377244 (12/104) for PTCCH > 20160705131735384 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378574 (94/104) for PDTCH > 20160705131735399 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378578 (98/104) for PDTCH > 20160705131735421 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378582 (102/104) for PDTCH > 20160705131735444 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378587 (3/104) for PDTCH > 20160705131735459 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378591 (7/104) for PDTCH > 20160705131735482 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378595 (11/104) for PDTCH > 20160705131735504 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378600 (16/104) for PDTCH > 20160705131735519 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378604 (20/104) for PDTCH > 20160705131735542 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378608 (24/104) for PDTCH > 20160705131735565 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378613 (29/104) for PDTCH > 20160705131735580 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378617 (33/104) for PDTCH > 20160705131735602 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378621 (37/104) for PDTCH > 20160705131735625 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378626 (42/104) for PDTCH > 20160705131735640 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378630 (46/104) for PDTCH > 20160705131735655 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378634 (50/104) for PDTCH > 20160705131735685 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378639 (55/104) for PDTCH > 20160705131735701 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378643 (59/104) for PDTCH > 20160705131735716 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378647 (63/104) for PDTCH > 20160705131735746 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378652 (68/104) for PDTCH > 20160705131735761 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378656 (72/104) for PDTCH > 20160705131735776 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378660 (76/104) for PDTCH > 20160705131735799 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378665 (81/104) for PDTCH > 20160705131735821 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378669 (85/104) for PDTCH > 20160705131735836 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378673 (89/104) for PDTCH > 20160705131735852 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2378596 (12/104) for PTCCH > 20160705131735859 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378678 (94/104) for PDTCH > 20160705131735882 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378682 (98/104) for PDTCH > 20160705131735897 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378686 (102/104) for PDTCH > 20160705131735919 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378691 (3/104) for PDTCH > 20160705131735942 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378695 (7/104) for PDTCH > 20160705131735957 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378699 (11/104) for PDTCH > 20160705131735980 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378704 (16/104) for PDTCH > 20160705131736002 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378708 (20/104) for PDTCH > 20160705131736018 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378712 toa=1.30 > 20160705131736018 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis > 20160705131736018 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378712 (24/104) for PDTCH > 20160705131736018 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL CHAN_ACTIV > 20160705131736018 DRSL <0000> rsl.c:880 chan_nr=0x20 type=0x00 mode=0x00 > 20160705131736018 DL1C <0006> scheduler.c:1310 Activating SDCCH/4(0) on trx=0 ts=0 > 20160705131736018 DL1C <0006> scheduler.c:1310 Activating SACCH/4(0) on trx=0 ts=0 > 20160705131736018 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on SDCCH/4(0) of trx=0 ts=0 > 20160705131736018 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SDCCH/4(0) on trx=0 ts=0 > 20160705131736018 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 > 20160705131736018 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 > 20160705131736018 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 > 20160705131736018 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK > 20160705131736018 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD > 20160705131736040 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378717 (29/104) for PDTCH > 20160705131736063 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378721 (33/104) for PDTCH > 20160705131736078 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378725 (37/104) for PDTCH > 20160705131736101 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378730 (42/104) for PDTCH > 20160705131736123 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378734 (46/104) for PDTCH > 20160705131736138 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378738 (50/104) for PDTCH > 20160705131736161 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378743 (55/104) for PDTCH > 20160705131736184 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378747 (59/104) for PDTCH > 20160705131736199 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378751 (63/104) for PDTCH > 20160705131736221 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378756 (68/104) for PDTCH > 20160705131736244 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378760 (72/104) for PDTCH > 20160705131736259 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378764 (76/104) for PDTCH > 20160705131736282 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378769 (81/104) for PDTCH > 20160705131736304 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378773 (85/104) for PDTCH > 20160705131736319 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378777 (89/104) for PDTCH > 20160705131736327 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2378700 (12/104) for PTCCH > 20160705131736342 DLLAPD <0011> lapd_core.c:899 Store content res. > 20160705131736342 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis > 20160705131736342 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378782 (94/104) for PDTCH > 20160705131736357 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378786 (98/104) for PDTCH > 20160705131736380 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378790 (102/104) for PDTCH > 20160705131736402 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378795 (3/104) for PDTCH > 20160705131736433 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131736531 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2378824 toa=-1.00 > 20160705131736576 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705131736765 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378873 (81/104) for PDTCH > 20160705131736780 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378877 (85/104) for PDTCH > 20160705131736802 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378881 (89/104) for PDTCH > 20160705131736810 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=0 (0/104) for PTCCH > 20160705131736825 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378886 (94/104) for PDTCH > 20160705131736840 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378890 (98/104) for PDTCH > 20160705131736863 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378894 (102/104) for PDTCH > 20160705131736886 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378899 (3/104) for PDTCH > 20160705131736901 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378903 (7/104) for PDTCH > 20160705131736901 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131736916 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378907 (11/104) for PDTCH > 20160705131736946 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378912 (16/104) for PDTCH > 20160705131736961 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378916 (20/104) for PDTCH > 20160705131736976 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378920 (24/104) for PDTCH > 20160705131736999 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378925 (29/104) for PDTCH > 20160705131737021 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378929 (33/104) for PDTCH > 20160705131737036 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378933 (37/104) for PDTCH > 20160705131737059 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378938 (42/104) for PDTCH > 20160705131737082 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378942 (46/104) for PDTCH > 20160705131737097 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378946 (50/104) for PDTCH > 20160705131737120 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378951 (55/104) for PDTCH > 20160705131737142 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378955 (59/104) for PDTCH > 20160705131737157 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378959 (63/104) for PDTCH > 20160705131737180 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378964 (68/104) for PDTCH > 20160705131737202 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378968 (72/104) for PDTCH > 20160705131737218 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378972 (76/104) for PDTCH > 20160705131737240 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378977 (81/104) for PDTCH > 20160705131737263 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378981 (85/104) for PDTCH > 20160705131737278 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378985 (89/104) for PDTCH > 20160705131737285 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2378908 (12/104) for PTCCH > 20160705131737301 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378990 (94/104) for PDTCH > 20160705131737323 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378994 (98/104) for PDTCH > 20160705131737338 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2378998 (102/104) for PDTCH > 20160705131737361 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379003 (3/104) for PDTCH > 20160705131737376 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131737384 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379007 (7/104) for PDTCH > 20160705131737399 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379011 (11/104) for PDTCH > 20160705131737421 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379016 (16/104) for PDTCH > 20160705131737444 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379020 (20/104) for PDTCH > 20160705131737459 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379024 (24/104) for PDTCH > 20160705131737482 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379029 (29/104) for PDTCH > 20160705131737504 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379033 (33/104) for PDTCH > 20160705131737519 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705131737520 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379037 (37/104) for PDTCH > 20160705131737542 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379042 (42/104) for PDTCH > 20160705131737557 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379046 (46/104) for PDTCH > 20160705131737580 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379050 (50/104) for PDTCH > 20160705131737602 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379055 (55/104) for PDTCH > 20160705131737618 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379059 (59/104) for PDTCH > 20160705131737640 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379063 (63/104) for PDTCH > 20160705131737663 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379068 (68/104) for PDTCH > 20160705131737678 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379072 (72/104) for PDTCH > 20160705131737701 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379076 (76/104) for PDTCH > 20160705131737723 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379081 (81/104) for PDTCH > 20160705131737738 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379085 (85/104) for PDTCH > 20160705131737753 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705131737761 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379089 (89/104) for PDTCH > 20160705131737768 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2379012 (12/104) for PTCCH > 20160705131737784 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379094 (94/104) for PDTCH > 20160705131737844 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131737950 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379130 toa=-0.05 > 20160705131738199 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379185 (81/104) for PDTCH > 20160705131738221 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705131738221 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL DEACTIVATE_SACCH > 20160705131738221 DL1C <0006> scheduler.c:1310 Deactivating SACCH/4(0) on trx=0 ts=0 > 20160705131738229 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379189 (85/104) for PDTCH > 20160705131738236 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379193 (89/104) for PDTCH > 20160705131738267 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2378700 (12/104) for PTCCH > 20160705131738267 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379198 (94/104) for PDTCH > 20160705131738282 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379202 (98/104) for PDTCH > 20160705131738312 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379206 (102/104) for PDTCH > 20160705131738319 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379211 (3/104) for PDTCH > 20160705131738342 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379215 (7/104) for PDTCH > 20160705131738387 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379224 (16/104) for PDTCH > 20160705131738425 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379232 (24/104) for PDTCH > 20160705131738463 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379241 (33/104) for PDTCH > 20160705131738508 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379250 (42/104) for PDTCH > 20160705131738546 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379258 (50/104) for PDTCH > 20160705131738599 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2379271 (63/104) for PDTCH > 20160705131738599 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379271 (63/104) for PDTCH > 20160705131738848 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379326 toa=2.93 > 20160705131738848 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2379326 (23/51) > 20160705131738931 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis > 20160705131738931 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL RF_CHAN_REL > 20160705131738931 DL1C <0006> scheduler.c:1310 Deactivating SDCCH/4(0) on trx=0 ts=0 > 20160705131738931 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=0,ss=0) Tx RF CHAN REL ACK > 20160705131739602 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379489 toa=1.25 > 20160705131739814 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379535 toa=-4.99 > 20160705131739814 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2379535 (28/51) > 20160705131739882 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=2) > 20160705131741021 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379797 toa=4.64 > 20160705131741021 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2379797 (35/51) > 20160705131741119 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2379818 toa=1.52 > 20160705131741610 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2379220 (12/104) for PTCCH > 20160705131741610 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2379012 (12/104) for PTCCH > 20160705131741829 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2379969 (33/104) for PDTCH > 20160705131742561 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2379948 (12/104) for PTCCH > 20160705131742561 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2379948 (12/104) for PTCCH > 20160705131742568 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2379220 (12/104) for PTCCH > 20160705131743052 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2379220 (12/104) for PTCCH > 20160705131744304 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2380507 toa=1.05 > 20160705131744304 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2380507 (31/51) > 20160705131745421 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2380749 (85/104) for PDTCH > 20160705131745422 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2380749 (85/104) for PDTCH > 20160705131746576 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381000 toa=1.00 > 20160705131746818 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381052 (76/104) for PDTCH > 20160705131746818 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381052 (76/104) for PDTCH > 20160705131747127 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381119 toa=1.64 > 20160705131747316 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381160 toa=5.25 > 20160705131747316 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2381160 (21/51) > 20160705131747444 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381187 (3/104) for PDTCH > 20160705131747444 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381187 (3/104) for PDTCH > 20160705131747753 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381255 toa=0.83 > 20160705131747919 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381291 (3/104) for PDTCH > 20160705131747920 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381291 (3/104) for PDTCH > 20160705131748123 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381334 (46/104) for PDTCH > 20160705131748123 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381334 (46/104) for PDTCH > 20160705131748402 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2381395 (3/104) for PDTCH > 20160705131749172 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2381562 toa=1.80 > 20160705131749285 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2380364 (12/104) for PTCCH > 20160705131749406 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381611 (11/104) for PDTCH > 20160705131750252 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2381612 (12/104) for PTCCH > 20160705131750252 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2381612 (12/104) for PTCCH > 20160705131750282 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381802 (98/104) for PDTCH > 20160705131751165 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2381993 (81/104) for PDTCH > 20160705131751799 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2382131 (11/104) for PDTCH > 20160705131751799 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2382131 (11/104) for PDTCH > 20160705131752048 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2382183 (63/104) for PDTCH > 20160705131752772 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2382342 toa=5.17 > 20160705131752772 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2382342 (30/51) > 20160705131753127 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2382340 (12/104) for PTCCH > 20160705131753187 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2382430 (102/104) for PDTCH > 20160705131753685 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2382540 toa=-5.30 > 20160705131753685 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2382540 (24/51) > 20160705131754025 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2382612 (76/104) for PDTCH > 20160705131756885 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2383234 toa=1.10 > 20160705131757287 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=2) > 20160705131757550 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2383377 toa=1.10 > 20160705131757927 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2382340 (12/104) for PTCCH > 20160705131759285 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2383748 (68/104) for PDTCH > 20160705131759285 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2383748 (68/104) for PDTCH > 20160705131759285 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2383752 (72/104) for PDTCH > 20160705131759368 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2383484 (12/104) for PTCCH > 20160705131759368 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2383484 (12/104) for PTCCH > 20160705131759859 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2383877 toa=-2.85 > 20160705131759859 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2383877 (35/51) > 20160705131800168 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2383943 (55/104) for PDTCH > 20160705131800327 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2383796 (12/104) for PTCCH > 20160705131800327 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2383796 (12/104) for PTCCH > 20160705131800810 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2384004 (12/104) for PTCCH > 20160705131801768 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2384108 (12/104) for PTCCH > 20160705131803210 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2384524 (12/104) for PTCCH > 20160705131803331 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2384627 (11/104) for PDTCH > 20160705131804168 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2384628 (12/104) for PTCCH > 20160705131805127 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2384628 (12/104) for PTCCH > 20160705131805610 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385044 (12/104) for PTCCH > 20160705131806568 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2385148 (12/104) for PTCCH > 20160705131806568 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385148 (12/104) for PTCCH > 20160705131807051 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385356 (12/104) for PTCCH > 20160705131807504 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2385533 (85/104) for PDTCH > 20160705131807527 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2385537 (89/104) for PDTCH > 20160705131807527 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385460 (12/104) for PTCCH > 20160705131808485 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385668 (12/104) for PTCCH > 20160705131808968 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385772 (12/104) for PTCCH > 20160705131809927 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2385772 (12/104) for PTCCH > 20160705131810410 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386084 (12/104) for PTCCH > 20160705131810885 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386188 (12/104) for PTCCH > 20160705131811368 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386292 (12/104) for PTCCH > 20160705131811851 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386396 (12/104) for PTCCH > 20160705131812810 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2386500 (12/104) for PTCCH > 20160705131812810 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386500 (12/104) for PTCCH > 20160705131813285 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386708 (12/104) for PTCCH > 20160705131813768 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386812 (12/104) for PTCCH > 20160705131814070 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2386954 (50/104) for PDTCH > 20160705131814727 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2386916 (12/104) for PTCCH > 20160705131814727 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2386916 (12/104) for PTCCH > 20160705131815210 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387124 (12/104) for PTCCH > 20160705131815685 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387228 (12/104) for PTCCH > 20160705131816168 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387332 (12/104) for PTCCH > 20160705131816613 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2387508 toa=-1.73 > 20160705131816614 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2387508 (45/51) > 20160705131816651 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387436 (12/104) for PTCCH > 20160705131816757 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2387539 (11/104) for PDTCH > 20160705131816757 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2387539 (11/104) for PDTCH > 20160705131816923 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2387574 (46/104) for PDTCH > 20160705131817127 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387540 (12/104) for PTCCH > 20160705131817610 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387644 (12/104) for PTCCH > 20160705131818568 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387852 (12/104) for PTCCH > 20160705131819526 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2387956 (12/104) for PTCCH > 20160705131819527 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2387956 (12/104) for PTCCH > 20160705131820485 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2388164 (12/104) for PTCCH > 20160705131820485 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2388164 (12/104) for PTCCH > 20160705131822410 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2388580 (12/104) for PTCCH > 20160705131823270 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2388948 (68/104) for PDTCH > 20160705131823270 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2388948 (68/104) for PDTCH > 20160705131823368 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2388788 (12/104) for PTCCH > 20160705131823368 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2388788 (12/104) for PTCCH > 20160705131825285 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2389204 (12/104) for PTCCH > 20160705131825285 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2389204 (12/104) for PTCCH > 20160705131825927 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2389525 toa=5.14 > 20160705131825927 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2389525 (22/51) > 20160705131827685 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2389620 (12/104) for PTCCH > 20160705131827851 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2389943 toa=-0.93 > 20160705131827851 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2389943 (32/51) > 20160705131827927 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2389957 (37/104) for PDTCH > 20160705131828017 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2389978 toa=1.29 > 20160705131828017 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis > 20160705131828017 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL CHAN_ACTIV > 20160705131828017 DRSL <0000> rsl.c:880 chan_nr=0x0a type=0x00 mode=0x00 > 20160705131828017 DL1C <0006> scheduler.c:1310 Activating TCH/F on trx=0 ts=2 > 20160705131828017 DL1C <0006> scheduler.c:1310 Activating SACCH/TF on trx=0 ts=2 > 20160705131828017 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on TCH/F of trx=0 ts=2 > 20160705131828017 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PDTCH of trx=0 ts=2 > 20160705131828017 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PTCCH of trx=0 ts=2 > 20160705131828017 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for TCH/F on trx=0 ts=2 > 20160705131828017 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/TF on trx=0 ts=2 > 20160705131828017 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for TCH/F on trx=0 ts=2 > 20160705131828017 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/TF on trx=0 ts=2 > 20160705131828017 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=2,ss=0) Tx CHAN ACT ACK > 20160705131828018 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD > 20160705131828802 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2390148 (20/104) for PDTCH > 20160705131828802 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2390148 (20/104) for PDTCH > 20160705131829127 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2389932 (12/104) for PTCCH > 20160705131829466 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2390293 toa=4.02 > 20160705131829466 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2390293 (25/51) > 20160705131831527 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2390556 (12/104) for PTCCH > 20160705131831527 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2390556 (12/104) for PTCCH > 20160705131831708 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2390776 (24/104) for PDTCH > 20160705131832485 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2390764 (12/104) for PTCCH > 20160705131832485 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2390764 (12/104) for PTCCH > 20160705131832628 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2390976 (16/104) for PDTCH > 20160705131832734 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2391001 toa=4.05 > 20160705131832734 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2391001 (19/51) > 20160705131833451 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2390972 (12/104) for PTCCH > 20160705131833451 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2390972 (12/104) for PTCCH > 20160705131834364 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2391353 (81/104) for PDTCH > 20160705131834364 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2391353 (81/104) for PDTCH > 20160705131837338 DL1C <0006> scheduler_trx.c:982 Received incomplete TCH frame ending at fn=2391998 (102/104) for TCH/F > 20160705131837338 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705131837338 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2391998 for TCH/F > 20160705131838018 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL DEACTIVATE_SACCH > 20160705131838018 DL1C <0006> scheduler.c:1310 Deactivating SACCH/TF on trx=0 ts=2 > 20160705131838018 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL RF_CHAN_REL > 20160705131838018 DL1C <0006> scheduler.c:1310 Deactivating TCH/F on trx=0 ts=2 > 20160705131838018 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=2,ss=0) Tx RF CHAN REL ACK > 20160705131838138 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2392172 toa=4.85 > 20160705131838138 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2392172 (17/51) > 20160705131839406 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2392440 (24/104) for PDTCH > 20160705131839406 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2392440 (24/104) for PDTCH > 20160705131839406 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2392445 (29/104) for PDTCH > 20160705131841481 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2392895 (63/104) for PDTCH > 20160705131841481 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2392895 (63/104) for PDTCH > 20160705131848221 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2394356 (68/104) for PDTCH > 20160705131849322 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2394594 (98/104) for PDTCH > 20160705131849323 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2394594 (98/104) for PDTCH > 20160705131849700 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2394676 toa=4.82 > 20160705131849700 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2394676 (22/51) > 20160705131851073 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2394974 toa=4.29 > 20160705131851073 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2394974 (14/51) > 20160705131853783 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2395560 (24/104) for PDTCH > 20160705131853783 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2395560 (24/104) for PDTCH > 20160705131855081 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2395843 toa=1.91 > 20160705131855081 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis > 20160705131855081 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL CHAN_ACTIV > 20160705131855081 DRSL <0000> rsl.c:880 chan_nr=0x20 type=0x00 mode=0x00 > 20160705131855081 DL1C <0006> scheduler.c:1310 Activating SDCCH/4(0) on trx=0 ts=0 > 20160705131855081 DL1C <0006> scheduler.c:1310 Activating SACCH/4(0) on trx=0 ts=0 > 20160705131855081 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on SDCCH/4(0) of trx=0 ts=0 > 20160705131855081 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SDCCH/4(0) on trx=0 ts=0 > 20160705131855081 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 > 20160705131855081 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 > 20160705131855081 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 > 20160705131855081 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK > 20160705131855081 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD > 20160705131855428 DLLAPD <0011> lapd_core.c:899 Store content res. > 20160705131855428 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis > 20160705131855518 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131855662 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705131855994 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131856462 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131856839 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705131856937 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131857073 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705131857315 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705131857405 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131857549 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705131857873 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131858349 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131858817 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131859285 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131859360 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2396769 (89/104) for PDTCH > 20160705131859760 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131900228 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705131900429 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL DEACTIVATE_SACCH > 20160705131900429 DL1C <0006> scheduler.c:1310 Deactivating SACCH/4(0) on trx=0 ts=0 > 20160705131901081 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis > 20160705131901081 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL RF_CHAN_REL > 20160705131901081 DL1C <0006> scheduler.c:1310 Deactivating SDCCH/4(0) on trx=0 ts=0 > 20160705131901081 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=0,ss=0) Tx RF CHAN REL ACK > 20160705131902666 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2397484 (76/104) for PDTCH > 20160705131902847 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2397525 toa=-1.76 > 20160705131902847 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2397525 (15/51) > 20160705131904326 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2397845 toa=-4.00 > 20160705131904326 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis > 20160705131904326 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL CHAN_ACTIV > 20160705131904326 DRSL <0000> rsl.c:880 chan_nr=0x0a type=0x00 mode=0x00 > 20160705131904326 DL1C <0006> scheduler.c:1310 Activating TCH/F on trx=0 ts=2 > 20160705131904326 DL1C <0006> scheduler.c:1310 Activating SACCH/TF on trx=0 ts=2 > 20160705131904326 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on TCH/F of trx=0 ts=2 > 20160705131904326 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PDTCH of trx=0 ts=2 > 20160705131904326 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PTCCH of trx=0 ts=2 > 20160705131904326 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for TCH/F on trx=0 ts=2 > 20160705131904326 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/TF on trx=0 ts=2 > 20160705131904326 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for TCH/F on trx=0 ts=2 > 20160705131904326 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/TF on trx=0 ts=2 > 20160705131904327 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=2,ss=0) Tx CHAN ACT ACK > 20160705131904327 DL1C <0006> scheduler.c:240 Prim for trx=0 ts=2 at fn=2392173 is out of range, or channel already disabled. If this happens in conjunction with PCU, increase 'rts-advance' by 5. (current fn=2397871) > 20160705131904327 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD > 20160705131905043 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398001 toa=-2.08 > 20160705131905043 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398001 (32/51) > 20160705131905722 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=0 (0/104) for SACCH/TF > 20160705131905737 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398151 toa=-5.09 > 20160705131905737 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398151 (29/51) > 20160705131907262 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2398481 (33/104) for PDTCH > 20160705131907262 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2398481 (33/104) for PDTCH > 20160705131907390 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398509 toa=3.02 > 20160705131907390 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398509 (30/51) > 20160705131907413 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398514 toa=5.03 > 20160705131907413 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398514 (35/51) > 20160705131907805 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2398599 toa=-5.02 > 20160705131907805 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2398599 (18/51) > 20160705131909405 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2398945 (81/104) for PDTCH > 20160705131909405 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2398945 (81/104) for PDTCH > 20160705131911820 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2399470 toa=-0.12 > 20160705131911820 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2399470 (22/51) > 20160705131912235 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2399556 (68/104) for PDTCH > 20160705131912236 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2399556 (68/104) for PDTCH > 20160705131912251 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2399560 (72/104) for PDTCH > 20160705131912900 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2399703 (7/104) for PDTCH > 20160705131912900 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2399703 (7/104) for PDTCH > 20160705131914327 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL DEACTIVATE_SACCH > 20160705131914327 DL1C <0006> scheduler.c:1310 Deactivating SACCH/TF on trx=0 ts=2 > 20160705131914327 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL RF_CHAN_REL > 20160705131914327 DL1C <0006> scheduler.c:1310 Deactivating TCH/F on trx=0 ts=2 > 20160705131914327 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=2,ss=0) Tx RF CHAN REL ACK > 20160705131914718 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2400097 (89/104) for PDTCH > 20160705131914719 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2400097 (89/104) for PDTCH > 20160705131918718 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2400964 (20/104) for PDTCH > 20160705131918719 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2400964 (20/104) for PDTCH > 20160705131920145 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2401272 (16/104) for PDTCH > 20160705131920145 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2401272 (16/104) for PDTCH > 20160705131921322 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2401527 (63/104) for PDTCH > 20160705131921322 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2401527 (63/104) for PDTCH > 20160705131928514 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2403086 toa=3.82 > 20160705131928515 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2403086 (17/51) > 20160705131928741 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2403135 (7/104) for PDTCH > 20160705131928741 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2403135 (7/104) for PDTCH > 20160705131928779 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2403143 toa=4.36 > 20160705131928779 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2403143 (23/51) > 20160705131936839 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2404890 (98/104) for PDTCH > 20160705131936839 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2404890 (98/104) for PDTCH > 20160705131937246 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2404978 toa=-4.82 > 20160705131937246 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2404978 (22/51) > 20160705131937820 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2405102 (102/104) for PDTCH > 20160705131937820 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2405102 (102/104) for PDTCH > 20160705131938401 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2405228 (20/104) for PDTCH > 20160705131938401 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2405228 (20/104) for PDTCH > 20160705131938461 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2405242 toa=-3.10 > 20160705131938462 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2405242 (31/51) > 20160705131941941 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2405995 (59/104) for PDTCH > 20160705131941941 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2405995 (59/104) for PDTCH > 20160705131944839 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2406624 toa=5.18 > 20160705131944839 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2406624 (36/51) > 20160705131946484 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2406979 (3/104) for PDTCH > 20160705131946484 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2406979 (3/104) for PDTCH > 20160705131949473 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2407628 toa=0.16 > 20160705131949473 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2407628 (20/51) > 20160705131950982 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2407954 (42/104) for PDTCH > 20160705131950982 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2407954 (42/104) for PDTCH > 20160705131951050 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2407969 toa=4.50 > 20160705131951050 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2407969 (4/51) > 20160705131952741 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2408336 toa=-4.04 > 20160705131952741 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2408336 (14/51) > 20160705131954197 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2408651 (11/104) for PDTCH > 20160705131954197 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2408651 (11/104) for PDTCH > 20160705131955178 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2408864 toa=-1.39 > 20160705131955178 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2408864 (32/51) > 20160705132000944 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2410112 (16/104) for PDTCH > 20160705132000944 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2410112 (16/104) for PDTCH > 20160705132001767 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2399188 (12/104) for PTCCH > 20160705132001767 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2399188 (12/104) for PTCCH > 20160705132006438 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2411303 (63/104) for PDTCH > 20160705132006439 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2411303 (63/104) for PDTCH > 20160705132008001 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2385148 (12/104) for PTCCH > 20160705132008001 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2385148 (12/104) for PTCCH > 20160705132009261 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2411914 (50/104) for PDTCH > 20160705132009261 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2411914 (50/104) for PDTCH > 20160705132010378 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2412157 (85/104) for PDTCH > 20160705132010378 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2412157 (85/104) for PDTCH > 20160705132013035 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2412732 toa=4.27 > 20160705132013035 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2412732 (24/51) > 20160705132013503 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2412833 (33/104) for PDTCH > 20160705132013503 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2412833 (33/104) for PDTCH > 20160705132013820 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2412902 (102/104) for PDTCH > 20160705132013820 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2412902 (102/104) for PDTCH > 20160705132014401 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2413029 toa=4.13 > 20160705132014401 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2413029 (15/51) > 20160705132017420 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2413682 toa=1.53 > 20160705132017420 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis > 20160705132017420 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL CHAN_ACTIV > 20160705132017420 DRSL <0000> rsl.c:880 chan_nr=0x20 type=0x00 mode=0x00 > 20160705132017420 DL1C <0006> scheduler.c:1310 Activating SDCCH/4(0) on trx=0 ts=0 > 20160705132017420 DL1C <0006> scheduler.c:1310 Activating SACCH/4(0) on trx=0 ts=0 > 20160705132017420 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on SDCCH/4(0) of trx=0 ts=0 > 20160705132017420 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SDCCH/4(0) on trx=0 ts=0 > 20160705132017420 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 > 20160705132017420 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 > 20160705132017420 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 > 20160705132017420 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK > 20160705132017420 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD > 20160705132017601 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2399188 (12/104) for PTCCH > 20160705132017812 DLLAPD <0011> lapd_core.c:899 Store content res. > 20160705132017812 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis > 20160705132017903 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132018046 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132018378 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132018438 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2413904 toa=-0.55 > 20160705132018438 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2413904 (23/51) > 20160705132018522 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132018756 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132018846 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132018989 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132019321 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132019465 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132019465 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL DEACTIVATE_SACCH > 20160705132019465 DL1C <0006> scheduler.c:1310 Deactivating SACCH/4(0) on trx=0 ts=0 > 20160705132019933 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414224 (72/104) for PDTCH > 20160705132020167 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis > 20160705132020179 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL RF_CHAN_REL > 20160705132020179 DL1C <0006> scheduler.c:1310 Deactivating SDCCH/4(0) on trx=0 ts=0 > 20160705132020179 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=0,ss=0) Tx RF CHAN REL ACK > 20160705132020350 DL1C <0006> scheduler.c:240 Prim for trx=0 ts=0 at fn=2414311 is out of range, or channel already disabled. If this happens in conjunction with PCU, increase 'rts-advance' by 5. (current fn=2414342) > 20160705132020763 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2414406 (46/104) for PDTCH > 20160705132020763 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414406 (46/104) for PDTCH > 20160705132020838 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2414423 toa=1.62 > 20160705132021050 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414462 (102/104) for PDTCH > 20160705132021050 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414467 (3/104) for PDTCH > 20160705132022189 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2414714 (42/104) for PDTCH > 20160705132024521 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2415221 toa=5.38 > 20160705132024521 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2415221 (14/51) > 20160705132025284 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2415386 toa=1.88 > 20160705132025759 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2415489 (89/104) for PDTCH > 20160705132025759 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2415489 (89/104) for PDTCH > 20160705132028551 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416095 toa=1.68 > 20160705132028552 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis > 20160705132028552 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL CHAN_ACTIV > 20160705132028552 DRSL <0000> rsl.c:880 chan_nr=0x20 type=0x00 mode=0x00 > 20160705132028552 DL1C <0006> scheduler.c:1310 Activating SDCCH/4(0) on trx=0 ts=0 > 20160705132028552 DL1C <0006> scheduler.c:1310 Activating SACCH/4(0) on trx=0 ts=0 > 20160705132028552 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on SDCCH/4(0) of trx=0 ts=0 > 20160705132028552 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SDCCH/4(0) on trx=0 ts=0 > 20160705132028552 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 > 20160705132028552 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 > 20160705132028552 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 > 20160705132028552 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK > 20160705132028552 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD > 20160705132028853 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416160 toa=-3.87 > 20160705132028853 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2416160 (35/51) > 20160705132028876 DLLAPD <0011> lapd_core.c:899 Store content res. > 20160705132028876 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis > 20160705132029110 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132029208 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132029419 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416282 toa=-5.05 > 20160705132029419 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2416282 (4/51) > 20160705132029586 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132029676 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132029819 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132030053 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132030144 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132030491 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416514 toa=0.51 > 20160705132030491 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2416514 (32/51) > 20160705132030522 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132030522 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL DEACTIVATE_SACCH > 20160705132030522 DL1C <0006> scheduler.c:1310 Deactivating SACCH/4(0) on trx=0 ts=0 > 20160705132031231 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis > 20160705132031231 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=0,ss=0) Rx RSL RF_CHAN_REL > 20160705132031231 DL1C <0006> scheduler.c:1310 Deactivating SDCCH/4(0) on trx=0 ts=0 > 20160705132031231 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=0,ss=0) Tx RF CHAN REL ACK > 20160705132031910 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2416822 toa=1.85 > 20160705132032159 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=8) > 20160705132033752 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2417218 (50/104) for PDTCH > 20160705132034144 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2417305 (33/104) for PDTCH > 20160705132034144 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2417305 (33/104) for PDTCH > 20160705132034408 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2414684 (12/104) for PTCCH > 20160705132034408 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2414684 (12/104) for PTCCH > 20160705132034589 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2417400 (24/104) for PDTCH > 20160705132037532 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2418041 toa=1.53 > 20160705132039540 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2418475 toa=1.54 > 20160705132039540 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis > 20160705132039540 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL CHAN_ACTIV > 20160705132039540 DRSL <0000> rsl.c:880 chan_nr=0x0a type=0x00 mode=0x00 > 20160705132039540 DL1C <0006> scheduler.c:1310 Activating TCH/F on trx=0 ts=2 > 20160705132039540 DL1C <0006> scheduler.c:1310 Activating SACCH/TF on trx=0 ts=2 > 20160705132039540 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on TCH/F of trx=0 ts=2 > 20160705132039540 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PDTCH of trx=0 ts=2 > 20160705132039540 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PTCCH of trx=0 ts=2 > 20160705132039540 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for TCH/F on trx=0 ts=2 > 20160705132039540 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/TF on trx=0 ts=2 > 20160705132039540 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for TCH/F on trx=0 ts=2 > 20160705132039540 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/TF on trx=0 ts=2 > 20160705132039540 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=2,ss=0) Tx CHAN ACT ACK > 20160705132039541 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD > 20160705132039545 DL1C <0006> scheduler.c:240 Prim for trx=0 ts=2 at fn=2400038 is out of range, or channel already disabled. If this happens in conjunction with PCU, increase 'rts-advance' by 5. (current fn=2418502) > 20160705132039880 DLLAPD <0011> lapd_core.c:899 Store content res. > 20160705132039880 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis > 20160705132040121 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132040280 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 > 20160705132040280 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132040438 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 > 20160705132040680 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=1, V(R)=2 > 20160705132040763 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132040838 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=1, V(R)=2 > 20160705132040921 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132041080 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=2, V(R)=3 > 20160705132041238 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=2, V(R)=3 > 20160705132041238 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132041321 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132041480 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=3, V(R)=4 > 20160705132041638 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=3, V(R)=4 > 20160705132041714 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132041721 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132041880 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=4, V(R)=5 > 20160705132042038 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=4, V(R)=5 > 20160705132042204 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132042216 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL PAGING_CMD > 20160705132042216 DPAG <0005> paging.c:213 Add paging to queue (group=2, queue_len=1) > 20160705132042219 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132042219 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL MODE_MODIFY_REQ > 20160705132042219 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on TCH/F of trx=0 ts=2 > 20160705132042219 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on PDTCH of trx=0 ts=2 > 20160705132042219 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on PTCCH of trx=0 ts=2 > 20160705132042219 DRSL <0000> rsl.c:1077 (bts=0,trx=0,ts=2,ss=0) Tx MODE MODIF ACK > 20160705132042219 DRSL <0000> rsl.c:2211 (bts=0,trx=0,ts=2,ss=0) Rx RSL IPAC_CRCX > 20160705132042219 DRSL <0000> rsl.c:1465 CRCX does not specify a remote IP > 20160705132042219 DRSL <0000> rsl.c:1470 CRCX does not specify a remote port > 20160705132042220 DRSL <0000> rsl.c:1289 (bts=0,trx=0,ts=2,ss=0) RSL Tx IPAC_CRCX_ACK (local 127.0.0.1:59068, remote 127.0.0.42:0) > 20160705132042378 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=5, V(R)=6 > 20160705132042536 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=5, V(R)=6 > 20160705132042680 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132042716 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL PAGING_CMD > 20160705132042717 DPAG <0005> paging.c:195 Ignoring duplicate paging > 20160705132042963 DPAG <0005> paging.c:512 Removed paging record, queue_len=0 > 20160705132043155 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2419259 toa=1.39 > 20160705132043155 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=0,ss=4) Fwd RLL msg CHAN_RQD from LAPDm to A-bis > 20160705132043163 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132043179 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=3,ss=0) Rx RSL CHAN_ACTIV > 20160705132043179 DRSL <0000> rsl.c:880 chan_nr=0x0b type=0x00 mode=0x00 > 20160705132043179 DL1C <0006> scheduler.c:1310 Activating TCH/F on trx=0 ts=3 > 20160705132043179 DL1C <0006> scheduler.c:1310 Activating SACCH/TF on trx=0 ts=3 > 20160705132043179 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on TCH/F of trx=0 ts=3 > 20160705132043179 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PDTCH of trx=0 ts=3 > 20160705132043179 DL1C <0006> scheduler.c:1359 Set mode 3, 0, handover 0 on PTCCH of trx=0 ts=3 > 20160705132043179 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for TCH/F on trx=0 ts=3 > 20160705132043179 DL1C <0006> scheduler.c:1424 Set a5/0 uplink for SACCH/TF on trx=0 ts=3 > 20160705132043179 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for TCH/F on trx=0 ts=3 > 20160705132043179 DL1C <0006> scheduler.c:1424 Set a5/0 downlink for SACCH/TF on trx=0 ts=3 > 20160705132043179 DRSL <0000> rsl.c:583 (bts=0,trx=0,ts=3,ss=0) Tx CHAN ACT ACK > 20160705132043180 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD > 20160705132043219 DRSL <0000> rsl.c:2058 (bts=0,trx=0,ts=0,ss=0) Rx RSL PAGING_CMD > 20160705132043219 DPAG <0005> paging.c:213 Add paging to queue (group=2, queue_len=1) > 20160705132043397 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132043397 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2419311 for TCH/F > 20160705132043420 DLLAPD <0011> lapd_core.c:899 Store content res. > 20160705132043420 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg EST_IND from LAPDm to A-bis > 20160705132043638 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132043661 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132043698 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=0 (0/104) for SACCH/TF > 20160705132043842 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 > 20160705132044083 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=1, V(R)=2 > 20160705132044121 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132044144 DPAG <0005> paging.c:512 Removed paging record, queue_len=0 > 20160705132044181 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132044318 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=2, V(R)=3 > 20160705132044559 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=3, V(R)=4 > 20160705132044604 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132044619 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132044664 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132044801 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=4, V(R)=5 > 20160705132044861 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132044906 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2419638 toa=4.75 > 20160705132044906 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2419638 (45/51) > 20160705132045042 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=5, V(R)=6 > 20160705132045080 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132045102 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132045140 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132045284 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=6, V(R)=7 > 20160705132045359 DL1C <0006> gsm0503_coding.c:689 tch_fr_decode(): error decoding FACCH frame (228/456 bits) > 20160705132045359 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2419736 for TCH/F > 20160705132045374 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132045375 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=3,ss=0) Rx RSL MODE_MODIFY_REQ > 20160705132045375 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on TCH/F of trx=0 ts=3 > 20160705132045375 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on PDTCH of trx=0 ts=3 > 20160705132045375 DL1C <0006> scheduler.c:1359 Set mode 1, 1, handover 0 on PTCCH of trx=0 ts=3 > 20160705132045375 DRSL <0000> rsl.c:1077 (bts=0,trx=0,ts=3,ss=0) Tx MODE MODIF ACK > 20160705132045375 DRSL <0000> rsl.c:2211 (bts=0,trx=0,ts=3,ss=0) Rx RSL IPAC_CRCX > 20160705132045375 DRSL <0000> rsl.c:1465 CRCX does not specify a remote IP > 20160705132045375 DRSL <0000> rsl.c:1470 CRCX does not specify a remote port > 20160705132045375 DRSL <0000> rsl.c:1289 (bts=0,trx=0,ts=3,ss=0) RSL Tx IPAC_CRCX_ACK (local 127.0.0.1:37448, remote 127.0.0.42:0) > 20160705132045517 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=7, V(R)=0 > 20160705132045563 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132045616 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132045623 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2419715 (51/104) for SACCH/TF > 20160705132045759 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 > 20160705132046038 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132046098 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132046521 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132046582 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132046702 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2420026 (50/104) for PDTCH > 20160705132046702 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2420026 (50/104) for PDTCH > 20160705132047004 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132047065 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132047480 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132047540 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132047646 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2420232 toa=5.49 > 20160705132047646 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2420232 (27/51) > 20160705132047963 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132048023 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132048438 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132048499 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132048921 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132048982 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132049404 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132049465 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132049880 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132049940 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132050363 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132050423 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132050838 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132050899 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132051321 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132051381 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132051804 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132051865 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132052280 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132052340 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132052544 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132052544 DRSL <0000> rsl.c:2211 (bts=0,trx=0,ts=3,ss=0) Rx RSL IPAC_MDCX > 20160705132052544 DRSL <0000> rsl.c:1289 (bts=0,trx=0,ts=3,ss=0) RSL Tx IPAC_MDCX_ACK (local 127.0.0.1:37448, remote 127.0.0.1:59068) > 20160705132052544 DRSL <0000> rsl.c:2211 (bts=0,trx=0,ts=2,ss=0) Rx RSL IPAC_MDCX > 20160705132052544 DRSL <0000> rsl.c:1289 (bts=0,trx=0,ts=2,ss=0) RSL Tx IPAC_MDCX_ACK (local 127.0.0.1:59068, remote 127.0.0.1:37448) > 20160705132052717 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=1, V(R)=2 > 20160705132052763 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132052778 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132052823 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132052869 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2421388. > 20160705132052911 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2421397. > 20160705132052921 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132052921 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2421374 for TCH/F > 20160705132052936 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=6, V(R)=7 > 20160705132052952 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2421406. > 20160705132053072 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2421432. > 20160705132053072 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2421432. > 20160705132053102 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=6, V(R)=7 > 20160705132053229 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2421466. > 20160705132053238 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132053299 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132053721 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132053781 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132054204 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132054264 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132054680 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132054740 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132055163 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132055223 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132055638 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132055699 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132055880 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132055880 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422015 for TCH/F > 20160705132056033 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422073. > 20160705132056038 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132056038 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422050 for TCH/F > 20160705132056121 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132056181 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132056194 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422108. > 20160705132056604 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132056664 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132057080 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132057140 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132057562 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132057623 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132058000 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2422475 toa=4.22 > 20160705132058000 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2422475 (26/51) > 20160705132058038 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132058098 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132058521 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132058581 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132059004 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132059019 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059019 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422696 for TCH/F > 20160705132059064 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059065 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422704 for TCH/F > 20160705132059065 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132059080 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059080 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422709 for TCH/F > 20160705132059102 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059102 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422713 for TCH/F > 20160705132059125 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059125 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422717 for TCH/F > 20160705132059140 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059140 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422722 for TCH/F > 20160705132059173 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422753. > 20160705132059215 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422762. > 20160705132059233 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422766. > 20160705132059253 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059253 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422743 for TCH/F > 20160705132059257 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422771. > 20160705132059261 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059261 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422748 for TCH/F > 20160705132059275 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422775. > 20160705132059276 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059276 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422752 for TCH/F > 20160705132059293 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422779. > 20160705132059359 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059359 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422769 for TCH/F > 20160705132059382 DL1C <0006> gsm0503_coding.c:705 tch_fr_decode(): error checking CRC8 for the FR part of an FR frame > 20160705132059382 DL1C <0006> scheduler_trx.c:1032 Received bad TCH frame ending at fn=2422774 for TCH/F > 20160705132059395 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422801. > 20160705132059413 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422805. > 20160705132059434 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422810. > 20160705132059480 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132059513 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422827. > 20160705132059531 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2422831. > 20160705132059540 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132059963 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132100023 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132100378 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132100438 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=2,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132100498 DRSL <0000> rsl.c:2025 (bts=0,trx=0,ts=3,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP > 20160705132100516 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423044. > 20160705132100536 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=7, V(R)=0 > 20160705132100657 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132100673 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423078. > 20160705132100702 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=7, V(R)=0 > 20160705132100703 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=3,ss=0) Rx RSL DEACTIVATE_SACCH > 20160705132100703 DL1C <0006> scheduler.c:1310 Deactivating SACCH/TF on trx=0 ts=3 > 20160705132100768 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423100. > 20160705132100777 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg DATA_IND from LAPDm to A-bis > 20160705132100785 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL DEACTIVATE_SACCH > 20160705132100785 DL1C <0006> scheduler.c:1310 Deactivating SACCH/TF on trx=0 ts=2 > 20160705132100831 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423113. > 20160705132100838 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=2, V(R)=3 > 20160705132100910 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423130. > 20160705132100943 DLLAPD <0011> lapd_core.c:1511 N(S) sequence error: N(S)=0, V(R)=1 > 20160705132100993 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=2 at fn=2423148. > 20160705132101034 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=2,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis > 20160705132101035 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=2,ss=0) Rx RSL RF_CHAN_REL > 20160705132101035 DRSL <0000> rsl.c:1256 (bts=0,trx=0,ts=2,ss=0) Sending RTP delete indication: cause = Normal event, unspecified > 20160705132101035 DL1C <0006> scheduler.c:1310 Deactivating TCH/F on trx=0 ts=2 > 20160705132101035 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=2,ss=0) Tx RF CHAN REL ACK > 20160705132101067 DL1C <0006> scheduler_trx.c:440 TCH/F Transmitting 'bad FR frame' trx=0 ts=3 at fn=2423165. > 20160705132101155 DRSL <0000> rsl.c:2031 (bts=0,trx=0,ts=3,ss=0) Fwd RLL msg REL_IND from LAPDm to A-bis > 20160705132101155 DRSL <0000> rsl.c:2112 (bts=0,trx=0,ts=3,ss=0) Rx RSL RF_CHAN_REL > 20160705132101155 DRSL <0000> rsl.c:1256 (bts=0,trx=0,ts=3,ss=0) Sending RTP delete indication: cause = Normal event, unspecified > 20160705132101155 DL1C <0006> scheduler.c:1310 Deactivating TCH/F on trx=0 ts=3 > 20160705132101155 DRSL <0000> rsl.c:551 (bts=0,trx=0,ts=3,ss=0) Tx RF CHAN REL ACK > 20160705132101555 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2423245 toa=1.57 > 20160705132101713 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2423279 toa=1.43 > 20160705132101766 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2385148 (12/104) for PTCCH > 20160705132102249 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2423316 (12/104) for PTCCH > 20160705132102249 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2423316 (12/104) for PTCCH > 20160705132102732 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2423316 (12/104) for PTCCH > 20160705132102906 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423536 (24/104) for PDTCH > 20160705132103004 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2423558 (46/104) for PDTCH > 20160705132103019 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423562 (50/104) for PDTCH > 20160705132103208 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2402828 (12/104) for PTCCH > 20160705132103525 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423671 (55/104) for PDTCH > 20160705132104166 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2423628 (12/104) for PTCCH > 20160705132104166 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2423628 (12/104) for PTCCH > 20160705132104280 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423835 (11/104) for PDTCH > 20160705132104370 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2423853 (29/104) for PDTCH > 20160705132104544 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2423893 toa=-5.47 > 20160705132104544 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2423893 (16/51) > 20160705132105132 DL1C <0006> scheduler_trx.c:822 Received incomplete data frame at fn=2423836 (12/104) for PTCCH > 20160705132105132 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2423836 (12/104) for PTCCH > 20160705132105464 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2424091 (59/104) for PDTCH > 20160705132107909 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2424622 toa=1.82 > 20160705132109517 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2424971 toa=1.97 > 20160705132110038 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2425083 (11/104) for PDTCH > 20160705132110038 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2425083 (11/104) for PDTCH > 20160705132113275 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2425785 toa=-1.23 > 20160705132113276 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2425785 (21/51) > 20160705132115419 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2426249 (33/104) for PDTCH > 20160705132115721 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2426314 (98/104) for PDTCH > 20160705132115721 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2426314 (98/104) for PDTCH > 20160705132117479 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2426696 toa=5.06 > 20160705132117479 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2426696 (14/51) > 20160705132121985 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2427671 toa=4.16 > 20160705132121985 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2427671 (20/51) > 20160705132124943 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2428312 (16/104) for PDTCH > 20160705132124943 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2428312 (16/104) for PDTCH > 20160705132127705 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2428911 toa=-0.82 > 20160705132127706 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2428911 (36/51) > 20160705132128543 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2429092 (68/104) for PDTCH > 20160705132128543 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2429092 (68/104) for PDTCH > 20160705132133404 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2430145 (81/104) for PDTCH > 20160705132133404 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2430145 (81/104) for PDTCH > 20160705132133736 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2430218 toa=4.20 > 20160705132133736 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2430218 (17/51) > 20160705132133879 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2430249 (81/104) for PDTCH > 20160705132133879 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2430249 (81/104) for PDTCH > 20160705132135441 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2430587 toa=-3.74 > 20160705132135441 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2430587 (29/51) > 20160705132136800 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2430881 (89/104) for PDTCH > 20160705132136800 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2430881 (89/104) for PDTCH > 20160705132138302 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2431206 (102/104) for PDTCH > 20160705132138302 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2431206 (102/104) for PDTCH > 20160705132149185 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2433564 (68/104) for PDTCH > 20160705132150203 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2433785 (81/104) for PDTCH > 20160705132150203 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2433785 (81/104) for PDTCH > 20160705132152953 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=2) > 20160705132156747 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2435204 toa=1.67 > 20160705132156747 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2435204 (5/51) > 20160705132158067 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2435490 toa=3.12 > 20160705132158067 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2435490 (36/51) > 20160705132159614 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2435825 toa=1.45 > 20160705132200180 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2435947 (59/104) for PDTCH > 20160705132200181 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2435947 (59/104) for PDTCH > 20160705132200701 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2436060 (68/104) for PDTCH > 20160705132200701 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2436060 (68/104) for PDTCH > 20160705132201282 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2436185 (89/104) for PDTCH > 20160705132201282 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2436185 (89/104) for PDTCH > 20160705132201818 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2436303 toa=4.69 > 20160705132201818 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2436303 (33/51) > 20160705132202943 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2436545 (33/104) for PDTCH > 20160705132202943 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2436545 (33/104) for PDTCH > 20160705132203720 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2436714 (98/104) for PDTCH > 20160705132203720 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2436714 (98/104) for PDTCH > 20160705132205380 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437074 (42/104) for PDTCH > 20160705132205380 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437074 (42/104) for PDTCH > 20160705132206973 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2437419 toa=3.79 > 20160705132206973 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2437419 (27/51) > 20160705132207260 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437481 (33/104) for PDTCH > 20160705132207260 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437481 (33/104) for PDTCH > 20160705132207863 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437611 (59/104) for PDTCH > 20160705132207863 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437611 (59/104) for PDTCH > 20160705132208022 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437646 (94/104) for PDTCH > 20160705132208022 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437646 (94/104) for PDTCH > 20160705132208980 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437854 (94/104) for PDTCH > 20160705132208980 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437854 (94/104) for PDTCH > 20160705132209320 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2437928 toa=2.26 > 20160705132209320 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2437928 (26/51) > 20160705132209622 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2437992 (24/104) for PDTCH > 20160705132209622 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2437992 (24/104) for PDTCH > 20160705132210663 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2438218 (42/104) for PDTCH > 20160705132210663 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2438218 (42/104) for PDTCH > 20160705132211177 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2438330 (50/104) for PDTCH > 20160705132211177 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2438330 (50/104) for PDTCH > 20160705132217611 DPAG <0005> paging.c:254 Add IMM.ASS to queue (group=2) > 20160705132218029 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2439814 toa=5.12 > 20160705132218029 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2439814 (25/51) > 20160705132219531 DL1C <0006> scheduler_trx.c:838 Received bad data frame at fn=2428932 (12/104) for PTCCH > 20160705132221554 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2440579 toa=-1.89 > 20160705132221554 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2440579 (25/51) > 20160705132223108 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2440915 toa=3.21 > 20160705132223108 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2440915 (4/51) > 20160705132224399 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2441195 (3/104) for PDTCH > 20160705132224399 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2441195 (3/104) for PDTCH > 20160705132224754 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2441272 toa=-4.42 > 20160705132224754 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2441272 (4/51) > 20160705132226686 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2441690 toa=1.34 > 20160705132227939 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2441962 (42/104) for PDTCH > 20160705132227939 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2441962 (42/104) for PDTCH > 20160705132232195 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2442884 toa=2.04 > 20160705132232195 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2442884 (35/51) > 20160705132238052 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2444153 toa=-1.35 > 20160705132238052 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2444153 (29/51) > 20160705132241372 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2444873 toa=5.39 > 20160705132241373 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2444873 (35/51) > 20160705132241538 DL1C <0006> scheduler_trx.c:907 Received incomplete PDTCH block ending at fn=2444908 (76/104) for PDTCH > 20160705132241539 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2444908 (76/104) for PDTCH > 20160705132241539 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2444909 toa=4.71 > 20160705132241539 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2444909 (20/51) > 20160705132243727 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2445383 toa=0.05 > 20160705132243727 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2445383 (35/51) > 20160705132244874 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2445631 toa=3.91 > 20160705132244874 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2445631 (28/51) > 20160705132244882 DL1C <0006> scheduler_trx.c:921 Received bad PDTCH block ending at fn=2445632 (72/104) for PDTCH > 20160705132251720 DL1C <0006> scheduler_trx.c:722 Received Access Burst on RACH fn=2447114 toa=1.12 > 20160705132251720 DL1C <0006> scheduler_trx.c:728 Received bad AB frame at fn=2447114 (32/51) > > -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From nhofmeyr at sysmocom.de Mon Jul 11 13:15:00 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 11 Jul 2016 15:15:00 +0200 Subject: Full state machine implementation In-Reply-To: <20160710195530.GC26877@nataraja> References: <354879786.6794759.1468168663068.JavaMail.zimbra@kvk.uni-obuda.hu> <306806706.6794993.1468169031672.JavaMail.zimbra@kvk.uni-obuda.hu> <20160710195530.GC26877@nataraja> Message-ID: <20160711131500.GA2579@dub6> On Sun, Jul 10, 2016 at 09:55:30PM +0200, Harald Welte wrote: > Hi Sipos, > > On Sun, Jul 10, 2016 at 06:43:51PM +0200, Sipos Csaba wrote: > > Just seen your branch regarding FSM: > > > > http://cgit.osmocom.org/openbsc/log/?h=laforge/om2000-fsm > > I'm happy at least somebody notices this work :) I've actually more than once yearned for the FSM, basically every time I'm fiddling with a request-response schema, tweaking timeout callbacks or trying to guard against messages coming in at the wrong time... To me it seems that the FSM would improve correctness, reliability and maintainability at pretty much every interface I'm dealing with so far :) I'm looking forward to the new HLR/VLR and seeing how it will work with Daniel's and my 3G CN stuff. ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Mon Jul 11 14:28:21 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 11 Jul 2016 16:28:21 +0200 Subject: osmo-bts-trx error logs -- was: GPRS on osmo-trx not working In-Reply-To: <578381F4.2010500@sysmocom.de> References: <20160628154548.GA19189@ass40.sysmocom.de> <20160629153130.GB1873@dub6> <20160705113529.GA6890@ass40.sysmocom.de> <578381F4.2010500@sysmocom.de> Message-ID: <20160711142820.GB2579@dub6> On Mon, Jul 11, 2016 at 01:24:36PM +0200, Max wrote: > Which voice codecs are you using? Have you tried AMR? Not sure, actually. So far the solution is switching these messages to DEBUG level. https://gerrit.osmocom.org/472 https://gerrit.osmocom.org/473 Apologies for not checking myself ... how do I configure to try AMR? Could be interesting to compare the log outputs. ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From msuraev at sysmocom.de Mon Jul 11 14:33:05 2016 From: msuraev at sysmocom.de (Max) Date: Mon, 11 Jul 2016 16:33:05 +0200 Subject: osmo-bts-trx error logs -- was: GPRS on osmo-trx not working In-Reply-To: <20160711142820.GB2579@dub6> References: <20160628154548.GA19189@ass40.sysmocom.de> <20160629153130.GB1873@dub6> <20160705113529.GA6890@ass40.sysmocom.de> <578381F4.2010500@sysmocom.de> <20160711142820.GB2579@dub6> Message-ID: <5783AE21.6000605@sysmocom.de> Add (or change) following to openbsc config top-level: mncc-int default-codec tch-f amr default-codec tch-h amr On 07/11/2016 04:28 PM, Neels Hofmeyr wrote: > On Mon, Jul 11, 2016 at 01:24:36PM +0200, Max wrote: >> Which voice codecs are you using? Have you tried AMR? > Not sure, actually. So far the solution is switching these messages to DEBUG > level. > https://gerrit.osmocom.org/472 > https://gerrit.osmocom.org/473 > > Apologies for not checking myself ... how do I configure to try AMR? > Could be interesting to compare the log outputs. > > ~Neels > -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From holger at freyther.de Tue Jul 12 16:03:08 2016 From: holger at freyther.de (Holger Freyther) Date: Tue, 12 Jul 2016 18:03:08 +0200 Subject: SS MM Messages (Call forwarding etc) In-Reply-To: <47DF1FB6-0D3D-488D-8C98-BDF6DEC55149@freyther.de> References: <02c1ee83-ec65-7cb2-a597-ea0dfbe12411@rhizomatica.org> <577BF2DE.3070700@rhizomatica.org> <47DF1FB6-0D3D-488D-8C98-BDF6DEC55149@freyther.de> Message-ID: > On 07 Jul 2016, at 14:39, Holger Freyther wrote: > Hi! >> Nokia.cap is sending *#21# on a nokia 6070, following by powering off as >> it sits at the requesting.... screen > > > thank you. The ussd.c has "reject" calls in many of the paths but I don't see a response at all. I will start by adding your payload to the libosmocore ussd decoding test and see how much we handle that message and then move forward to use the Smalltalk BTS to simulate that CM Service Request + facility message. can you please fetch this change https://gerrit.osmocom.org/503? The main issue is that our USSD/SS decoding does not distinguish between the ROS part (invoke, reject, return, returnLast) but is guessing about results or notifications based on having a "string". In case of interrogate SS there is no text.. feel free to either update the gerrit review or this ticket to see if this works. My BTS is still boxed so I did not try the resulting code myself. holger From jbarealopez at gmail.com Tue Jul 12 16:35:20 2016 From: jbarealopez at gmail.com (Juan Antonio Barea Lopez) Date: Tue, 12 Jul 2016 18:35:20 +0200 Subject: Error compiling libosmocore under Mac Osx Message-ID: Hello all, in order to try grgsm software, it asked for the libosmocore library and i proceed to configura and install it. Configure process went ok, but when trying to "make", it gets a error about unidentified symbols. I have been searching on the web and got several hints that it could be based on the 64bit version of gcc used. The error in question is this: **********Output error begins here********** /Applications/Xcode.app/Contents/Developer/usr/bin/make all-recursive Making all in include make[2]: Nothing to be done for `all'. Making all in src /Applications/Xcode.app/Contents/Developer/usr/bin/make all-am make[3]: Nothing to be done for `all-am'. Making all in src/vty make[2]: Nothing to be done for `all'. Making all in src/codec CCLD libosmocodec.la Undefined symbols for architecture x86_64: "_bitvec_get_bit_pos", referenced from: _osmo_fr_check_sid in gsm610.o "_bitvec_get_uint", referenced from: _osmo_hr_check_sid in gsm620.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [libosmocodec.la] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 *********End of output error************ I tried to also made a reconfigure -i but without success. Has anyone experienced this error or have an idea about what could be happening?. Thanks in advance!!!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From cinaed.simson at gmail.com Tue Jul 12 17:58:29 2016 From: cinaed.simson at gmail.com (Cinaed Simson) Date: Tue, 12 Jul 2016 10:58:29 -0700 Subject: Error compiling libosmocore under Mac Osx In-Reply-To: References: Message-ID: <173d495b-5534-457f-3aa5-e0a4f53dfe1d@GMail.COM> On 07/12/2016 09:35 AM, Juan Antonio Barea Lopez wrote: > Hello all, in order to try grgsm software, > Are you trying to build gr-gsm for gnuradio? > it asked for the libosmocore > library and i proceed to configura and install it. Configure process > went ok, but when trying to "make", it gets a error about unidentified > symbols. I have been searching on the web and got several hints that it > could be based on the 64bit version of gcc used. The error in question > is this: > > **********Output error begins here********** > /Applications/Xcode.app/Contents/Developer/usr/bin/make all-recursive > Making all in include > make[2]: Nothing to be done for `all'. > Making all in src > /Applications/Xcode.app/Contents/Developer/usr/bin/make all-am > make[3]: Nothing to be done for `all-am'. > Making all in src/vty > make[2]: Nothing to be done for `all'. > Making all in src/codec > CCLD libosmocodec.la > Undefined symbols for architecture x86_64: > "_bitvec_get_bit_pos", referenced from: > _osmo_fr_check_sid in gsm610.o > "_bitvec_get_uint", referenced from: > _osmo_hr_check_sid in gsm620.o > ld: symbol(s) not found for architecture x86_64 > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > make[2]: *** [libosmocodec.la ] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > *********End of output error************ > I tried to also made a reconfigure -i but without success. Has anyone > experienced this error or have an idea about what could be happening?. > Thanks in advance!!!! > From holger at freyther.de Wed Jul 13 11:51:20 2016 From: holger at freyther.de (Holger Freyther) Date: Wed, 13 Jul 2016 13:51:20 +0200 Subject: Profiling data of decoding EPDAN compressed bitmap In-Reply-To: <57861620.50909@sysmocom.de> References: <0E9A040D-A440-4B2C-8C89-E77B879E749B@freyther.de> <8E22EFFF-C582-40C0-9BE7-B9CB277CDBD0@freyther.de> <22249C3D-1004-49AA-AE77-F12C2B2D063F@freyther.de> <75AB52FB-ACE2-414E-ACD5-50C363626F51@freyther.de> <586CD5D3-1ED6-4D37-891D-782CF846029E@freyther.de> <57861620.50909@sysmocom.de> Message-ID: > On 13 Jul 2016, at 12:21, Max wrote: > Hi all, > After looking at the code, I don't think reusing table implementation > would be easy - the approaches are too different as well as underlying > data structures. okay. then we will need to use the tree based version and from my point of view we should do it the following way: * Remove osmo_t4_decode (and related routines) from libosmocore (last step) * Make the tree based decoder ready in terms of the surrounding style * Adopt/Clone the osmo_t4_decode tests and move them to the PCU (as part of the commit that adds the decoder to the PCU) @Me: After the infrastructure is in the PCU I will remove osmo_t4_decode (and tests) from libosmocore @Radisys: I am afraid the tree based decoding is not ready yet and as it impacts the upcoming encoder (and other RLE code as far as I understand) let me put it here. In osmo-pcu (and all other projects) we use libtalloc for memory allocations. This means the tree should use talloc with proper parent/child allocations. This way the destructor of the decoder will also free all nodes of the tree. There should be no call to malloc/free in the PCU. Please take the tests from libosmocore and make sure they work with the new decoder. Tests are the lifeline and we need more and not less of them. The decoder needs to be robust against invalid input. search_runlen can fail but the caller doesn't check for that. Please test with invalid/truncated or broken inputs to see we don't end in a never terminating while loop. Test using unit tests. Similar the current osmo_t4_decode can return an error that is propagated back to the compressed bitmap decoding and we should have the same. Reduce code duplication. With the decoder the only difference between the if/else is if the data is filled with 0x00 or 0xFF and which table/root to use. Instead of having code clones please parameterize either by having local variables in the beginning or by calling different (inline) functions. kind regards holger From nhofmeyr at sysmocom.de Wed Jul 13 13:12:32 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 13 Jul 2016 15:12:32 +0200 Subject: jenkins matrix + --enable-iu Message-ID: <20160713131232.GA1685@dub6> Hi list, I've got a jenkins job ready that adds --enable-iu to the openbsc build matrix. I'd like to verify with you guys: so far we had a build matrix of 2 x 2, so openbsc and all its dependencies are built four times over (~22 min). Adding --enable-iu doubles this matrix to eight times. This means that any new commit would take about 55 min to verify with jenkins, even if it is just a comment tweak. I assume we want to bring this time down a bit? I'd have these suggestions: (1) Just add --enable-iu, let jenkins build for hours and proliferate global warming, and care about this once it actually bugs us. (2) Limit the build matrix: Only build --enable-iu once, e.g. with --enable-smpp and --enable-mgcp-transcoding, not with all of the other combinations. (Would --disable-mgcp make more sense?) (3) Don't build all of the dependencies over and over. In pseudo sort of: dep_hashes = "" for dep in libosmo*: dep_hashes += "," + dep.get_current_git_hash() if dep.last_hashes == dep_hashes: dep."make install" continue dep.wipe_out() dep."autoreconf; configure; make check; make install" cat dep_hashes > "${dep.dir}/last_hashes" That would shorten the build time substantially, and we could keep the build matrix fully featured without taking too much time. I've so far spent 5 minutes on implementing something like this and could polish that up, maybe using a global dependencies workspace somewhere else on the build slave so the separate matrix items benefit from each other. But do we like that? I would consider re-using previous builds safe enough for our jenkins verifier, since all deps would be rebuilt even if only one dep's git hash changes; assuming that it *works*, of course. Do you guys agree? http://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit-test/ openbsc.git branches osmocom/jenkins-test and neels/speed_up_matrix_builds Thanks for your opinions! ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Wed Jul 13 13:26:06 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 13 Jul 2016 15:26:06 +0200 Subject: Error compiling libosmocore under Mac Osx In-Reply-To: References: Message-ID: <20160713132606.GB1685@dub6> Hi Juan, though I'm building on linux, I can assure you that the 64bit version of gcc is generally able to build libosmocore. To get proper help, you should provide the exact commands that lead to the error, so we don't need to guess on your environment's particulars. ~Neels On Tue, Jul 12, 2016 at 06:35:20PM +0200, Juan Antonio Barea Lopez wrote: > Hello all, in order to try grgsm software, it asked for the libosmocore > library and i proceed to configura and install it. Configure process went > ok, but when trying to "make", it gets a error about unidentified symbols. > I have been searching on the web and got several hints that it could be > based on the 64bit version of gcc used. The error in question is this: > > **********Output error begins here********** > /Applications/Xcode.app/Contents/Developer/usr/bin/make all-recursive > Making all in include > make[2]: Nothing to be done for `all'. > Making all in src > /Applications/Xcode.app/Contents/Developer/usr/bin/make all-am > make[3]: Nothing to be done for `all-am'. > Making all in src/vty > make[2]: Nothing to be done for `all'. > Making all in src/codec > CCLD libosmocodec.la > Undefined symbols for architecture x86_64: > "_bitvec_get_bit_pos", referenced from: > _osmo_fr_check_sid in gsm610.o > "_bitvec_get_uint", referenced from: > _osmo_hr_check_sid in gsm620.o > ld: symbol(s) not found for architecture x86_64 > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > make[2]: *** [libosmocodec.la] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > *********End of output error************ > I tried to also made a reconfigure -i but without success. Has anyone > experienced this error or have an idea about what could be happening?. > Thanks in advance!!!! -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Wed Jul 13 14:21:56 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 13 Jul 2016 16:21:56 +0200 Subject: include grouping Message-ID: <20160713142156.GA6273@dub6> Hi Max, in e.g. e6052c4cc756f7d3a5023a0ba57fe8d80783967c you have added #include in various files. I'd like to nitpick about the place where you put it: index 3cba5d1..3d7c244 100644 --- a/openbsc/include/openbsc/gsm_subscriber.h +++ b/openbsc/include/openbsc/gsm_subscriber.h @@ -5,6 +5,8 @@ #include #include +#include + (there are also some more instances) I'd prefer if we keep system headers grouped on top. Thanks :) ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From msuraev at sysmocom.de Wed Jul 13 14:24:48 2016 From: msuraev at sysmocom.de (Max) Date: Wed, 13 Jul 2016 16:24:48 +0200 Subject: include grouping In-Reply-To: <20160713142156.GA6273@dub6> References: <20160713142156.GA6273@dub6> Message-ID: <57864F30.8000304@sysmocom.de> I recall that I've seen both variants in source code - "system before our" and "our headers before system". I'm more inclined towards latter but I'm open for other opinions. On 07/13/2016 04:21 PM, Neels Hofmeyr wrote: > Hi Max, > > in e.g. e6052c4cc756f7d3a5023a0ba57fe8d80783967c you have added #include > in various files. > > I'd like to nitpick about the place where you put it: > > index 3cba5d1..3d7c244 100644 > --- a/openbsc/include/openbsc/gsm_subscriber.h > +++ b/openbsc/include/openbsc/gsm_subscriber.h > @@ -5,6 +5,8 @@ > #include > #include > > +#include > + > > (there are also some more instances) > > I'd prefer if we keep system headers grouped on top. > Thanks :) > > ~Neels > -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From nhofmeyr at sysmocom.de Wed Jul 13 15:53:55 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 13 Jul 2016 17:53:55 +0200 Subject: osmo-bts-trx: patch 498 Message-ID: <20160713155355.GA20068@dub6> Hi osmo-bts-trx folks, reviews on https://gerrit.osmocom.org/498 would be appreciated :) Thanks! ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Wed Jul 13 17:18:03 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 13 Jul 2016 19:18:03 +0200 Subject: fully dynamic TS, naming Message-ID: <20160713171803.GA21699@dub6> About http://osmocom.org/issues/1757#note-4 With the current naming scheme, the logical name for a fully dynamic TCH/F-TCH/H-PDCH channel would be GSM_PCHAN_TCH_F_TCH_H_PDCH timeslot 2 phys_chan_config TCH/F_TCH/H_PDCH Is it asking for trouble to just name it DYN instead? GSM_PCHAN_DYN timeslot 2 phys_chan_config DYN I'm in (at least) two minds about it, opinions welcome... ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From laforge at gnumonks.org Wed Jul 13 20:37:05 2016 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 13 Jul 2016 22:37:05 +0200 Subject: Full state machine implementation In-Reply-To: <20160711131500.GA2579@dub6> References: <354879786.6794759.1468168663068.JavaMail.zimbra@kvk.uni-obuda.hu> <306806706.6794993.1468169031672.JavaMail.zimbra@kvk.uni-obuda.hu> <20160710195530.GC26877@nataraja> <20160711131500.GA2579@dub6> Message-ID: <20160713203705.GE5596@nataraja> Hi Neels, On Mon, Jul 11, 2016 at 03:15:00PM +0200, Neels Hofmeyr wrote: > On Sun, Jul 10, 2016 at 09:55:30PM +0200, Harald Welte wrote: > > > > I'm happy at least somebody notices this work :) > > I've actually more than once yearned for the FSM, My comment above was not about the FSM, but about the OM2000 work, which is quite special-interest. > basically every time I'm fiddling with a request-response schema, > tweaking timeout callbacks or trying to guard against messages coming > in at the wrong time... Well, it's not going to be the grand unified theory that solves everything. It's an attempt at putting some more structure into some of the problems we need to solve, but I'm not sure if the first incarnation is already doing a good job at it. Implementing libvlr and OM2000 is sort of a test-ballon for it. While I like the "structured-ness" and the features about automatic clean-up of child FSMs, reporting of termination to the parent, ... there are also some parts that definitely leave much room for improvement. There's a lot of boilerplate code. I don't really like code generation that much, but maybe some macros could already help with that. > To me it seems that the FSM would improve correctness, reliability and > maintainability at pretty much every interface I'm dealing with so far :) Possibly, but the question is also one about 'how verbose / expressive is the code you need to do it' (I think too verbose / too little expressive yet with current osmo_fsm), and how easy is it to read. Finally, when handing in opaque structures as part of events, it all goes via 'void *' type casts. So a new class of problems could be introduced by this, one that we currently don't really have (except for osmocom-style signals) -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From alexander.chemeris at gmail.com Wed Jul 13 20:59:11 2016 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Wed, 13 Jul 2016 16:59:11 -0400 Subject: fully dynamic TS, naming In-Reply-To: <20160713171803.GA21699@dub6> References: <20160713171803.GA21699@dub6> Message-ID: On Wed, Jul 13, 2016 at 1:18 PM, Neels Hofmeyr wrote: > About http://osmocom.org/issues/1757#note-4 > > With the current naming scheme, the logical name for a fully dynamic > TCH/F-TCH/H-PDCH channel would be > > GSM_PCHAN_TCH_F_TCH_H_PDCH > > timeslot 2 > phys_chan_config TCH/F_TCH/H_PDCH I personally prefer this option, because it doesn't leave a place for doubt. And ti's not something you would type 100x a day, so making it short is not a real optimization. > Is it asking for trouble to just name it DYN instead? > > GSM_PCHAN_DYN > > timeslot 2 > phys_chan_config DYN Reading this, I would be asking myself "DYN - what is that? Dynamic? Ok, Dynamic what? Channels? Ok, which channels? Can it have SDCCH in there? Hmm.. Don't know. Let look into the docs. Docs say no. Can it be SDCCH in the next release of the software? Huh, don't know, I better to put something more specific here, so I'm sure what's happening. But how to do that?" Users who don't ask those questions will ask a lot of other questions like "I thought DYN is doing XYZ, but it not! Help!" -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co From alexander.chemeris at gmail.com Wed Jul 13 21:05:24 2016 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Wed, 13 Jul 2016 17:05:24 -0400 Subject: Full state machine implementation In-Reply-To: <20160710195530.GC26877@nataraja> References: <354879786.6794759.1468168663068.JavaMail.zimbra@kvk.uni-obuda.hu> <306806706.6794993.1468169031672.JavaMail.zimbra@kvk.uni-obuda.hu> <20160710195530.GC26877@nataraja> Message-ID: Harald, On Sun, Jul 10, 2016 at 3:55 PM, Harald Welte wrote: > On Sun, Jul 10, 2016 at 06:43:51PM +0200, Sipos Csaba wrote: >> Just seen your branch regarding FSM: >> >> http://cgit.osmocom.org/openbsc/log/?h=laforge/om2000-fsm > > I'm happy at least somebody notices this work :) Just want to say that I do notice this work and are eagerly waiting to see OML issues solved. But since I'm not a specialist in OML (at least yet), I just don't have anything to say. And in general I prefer to avoid speaking up when I don't have anything to say. This doesn't mean your work is going un-noticed and un-appreciated. :) -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co From laforge at gnumonks.org Thu Jul 14 00:40:10 2016 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 14 Jul 2016 02:40:10 +0200 Subject: fully dynamic TS, naming In-Reply-To: References: <20160713171803.GA21699@dub6> Message-ID: <20160714004010.GK5596@nataraja> Hi Alexander and others, On Wed, Jul 13, 2016 at 04:59:11PM -0400, Alexander Chemeris wrote: > > phys_chan_config TCH/F_TCH/H_PDCH > > I personally prefer this option, because it doesn't leave a place for > doubt. And ti's not something you would type 100x a day, so making it > short is not a real optimization. I also think it should be kept this way for consistency with other pchan names. From a VTY syntax POV, the '/' are ugly in the name, and we never use that anywhre else in the VTY but the channel config - but the '/' is part of the official specified names, so I chose to use them with the existing channel types when originally writing that code. > Reading this, I would be asking myself "DYN - what is that? Dynamic? > Ok, Dynamic what? Channels? Ok, which channels? Can it have SDCCH in > there? Hmm.. Don't know. Let look into the docs. Docs say no. Can it > be SDCCH in the next release of the software? Huh, don't know, I > better to put something more specific here, so I'm sure what's > happening. But how to do that?" The VTY offers a help string at tab-completion which could have the anwer to this, so I don't think that point is such an issue. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Thu Jul 14 00:36:40 2016 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 14 Jul 2016 02:36:40 +0200 Subject: include grouping In-Reply-To: <57864F30.8000304@sysmocom.de> References: <20160713142156.GA6273@dub6> <57864F30.8000304@sysmocom.de> Message-ID: <20160714003640.GJ5596@nataraja> On Wed, Jul 13, 2016 at 04:24:48PM +0200, Max wrote: > I recall that I've seen both variants in source code - "system before > our" and "our headers before system". I'm more inclined towards latter > but I'm open for other opinions. the standard omsoocm coding style is: * first the system include files * then the osmocom libraries * then any local includes within the project -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From nhofmeyr at sysmocom.de Thu Jul 14 01:32:38 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 14 Jul 2016 03:32:38 +0200 Subject: fully dynamic TS, naming In-Reply-To: <20160714004010.GK5596@nataraja> References: <20160713171803.GA21699@dub6> <20160714004010.GK5596@nataraja> Message-ID: <20160714013238.GA18344@dub6> On Thu, Jul 14, 2016 at 02:40:10AM +0200, Harald Welte wrote: > Hi Alexander and others, > > On Wed, Jul 13, 2016 at 04:59:11PM -0400, Alexander Chemeris wrote: > > > phys_chan_config TCH/F_TCH/H_PDCH > > > > I personally prefer this option, because it doesn't leave a place for > > doubt. > > I also think it should be kept this way for consistency with other pchan > names. Agreed. I thought, maybe we want to add more pchan types so having a shorter DYN name could be useful. But having a consistent, explicit, logical name is better. > From a VTY syntax POV, the '/' are ugly in the name Yeah, especially since it looks like "TCH or F_TCH or H_PDCH" :) But one gets used to it quickly. ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From holger at freyther.de Thu Jul 14 06:37:54 2016 From: holger at freyther.de (Holger Freyther) Date: Thu, 14 Jul 2016 08:37:54 +0200 Subject: include grouping In-Reply-To: <20160714003640.GJ5596@nataraja> References: <20160713142156.GA6273@dub6> <57864F30.8000304@sysmocom.de> <20160714003640.GJ5596@nataraja> Message-ID: <2FB48CF7-C4C9-4E88-80E7-0BA39B6BD87C@freyther.de> > On 14 Jul 2016, at 02:36, Harald Welte wrote: > > On Wed, Jul 13, 2016 at 04:24:48PM +0200, Max wrote: >> I recall that I've seen both variants in source code - "system before >> our" and "our headers before system". I'm more inclined towards latter >> but I'm open for other opinions. > > the standard omsoocm coding style is: > * first the system include files > * then the osmocom libraries > * then any local includes within the project and to add to bike shedding. If we have MODULE.h and MODULE.c., first thing MODULE.c should include is MODULE.h. This makes sure that MODULE.h has all the necessary includes to be included by itself. I would also sort system includes last (e.g. with X11 header they would pollute your namespace and define things one should not define). holger From gofs at live.be Thu Jul 14 23:34:51 2016 From: gofs at live.be (Gof .) Date: Fri, 15 Jul 2016 01:34:51 +0200 Subject: Problem with running omso-nitb Message-ID: Hello all, I am playing around with osmocom now for more then 2 years. i pretty much seen every possible error's when compiling and building stuff but i always used OpenBTS for running my network, but now a couple months back i wanted to try and do the same thing using openbsc I got most off the tools working on a Debian 8.5, but when i try to run osmo-nitb -c ~/.osmocom/open-bsc.cfg i get the an error Aborted since there is no more information about the error i can't seem to figure out what is wrong maybe something to do with ipaccess?Did anyone else also came up to this problem ?I tried many many times with a fresh installOn Ubuntu 12.04Debian 8.5Kali linux 2016.1also with kali in a docker container i got pretty far with doing it in docker, and osmo-nitb worked, until i installed all the rest and then when i needed to run osmo-nitb i also got back the error Aborted when trying to run it Please help me out Thanks in advance Develectron -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alexander.Chemeris at fairwaves.co Fri Jul 15 00:30:50 2016 From: Alexander.Chemeris at fairwaves.co (Alexander Chemeris) Date: Thu, 14 Jul 2016 20:30:50 -0400 Subject: osmo-bts: Repository write acces / Gerrit migration In-Reply-To: <20160707114017.GD1523@dub6> References: <20160701102104.GG3992@nataraja> <20160705101438.GC1727@ass40.sysmocom.de> <20160706114935.GB2560@dub6> <20160706161737.GD9710@dub6> <20160707114017.GD1523@dub6> Message-ID: On Thu, Jul 7, 2016 at 7:40 AM, Neels Hofmeyr wrote: > On Thu, Jul 07, 2016 at 08:36:06AM +0300, Alexander Chemeris wrote: >> Believe it or not, but that's the information from my Gerrit user info page. > > Thanks for your patience -- the Gerrit UI for some weird reason refuses to > offer your account's name in the group editing dialog. I took a close look at > the database to find out why, but could find no difference to other accounts. > > For the record, simply entering the user ID (10000NN number) in the dialog > worked, despite the user not being offered by the UI. So providing the gerrit > user ID is indeed the easiest and most fool proof way. > > In short, Alexander, you should finally be a known user and may push private > branches now. You may verify that using the sandbox repository: > git clone ssh://$USERNAME at gerrit.osmocom.org:29418/sandbox.git Thank you! Works like a charm now :) -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. Skype: Alexander.Chemeris Mobile: +1(424)400-7626 https://fairwaves.co Subscribe to Fairwaves news: http://eepurl.com/baL_pf From guptaayush48 at gmail.com Fri Jul 15 00:41:53 2016 From: guptaayush48 at gmail.com (ayush gupta) Date: Fri, 15 Jul 2016 06:11:53 +0530 Subject: Need Help In installing openBSC for establishing GSM network with EDGE support Message-ID: Hello everyone, i am noob to this field and currently trying to establishing a GSM network with EDGE support using this page as guide http://openbsc.osmocom.org/trac/wiki/Ettus_USRP_B2xx_family#no1 i am stuck at this command sudo osmo-nitb -C -c openbsc.conf -T -P -m its giving me following error There is no such command. Error occurred during reading below line: extension-prefix 0 % 'dtx-used' is now deprecated: use dtx * configuration options of BTS instead Fri Jul 15 05:35:26 2016 <0005> bsc_init.c:492 Failed to parse the config file: '/home/ryker/openbsc.conf' any help would be highly appreciated thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From msuraev at sysmocom.de Fri Jul 15 08:21:29 2016 From: msuraev at sysmocom.de (Max) Date: Fri, 15 Jul 2016 10:21:29 +0200 Subject: Problem with running omso-nitb In-Reply-To: References: Message-ID: <57889D09.6030603@sysmocom.de> You really should share waaay more details. At the very least - exact config you're using and detailed logs produced right before the abort message. On 07/15/2016 01:34 AM, Gof . wrote: > Hello all, > > I am playing around with osmocom now for more then 2 years. > > i pretty much seen every possible error's when compiling and building > stuff > but i always used OpenBTS for running my network, but now a couple > months back i wanted to try and do the same thing using openbsc > > I got most off the tools working on a Debian 8.5, but when i try to run > > osmo-nitb -c ~/.osmocom/open-bsc.cfg > > i get the an error Aborted > > since there is no more information about the error i can't seem to > figure out what is wrong > maybe something to do with ipaccess? > Did anyone else also came up to this problem ? > I tried many many times with a fresh install > On Ubuntu 12.04 > Debian 8.5 > Kali linux 2016.1 > also with kali in a docker container > i got pretty far with doing it in docker, and osmo-nitb worked, until > i installed all the rest and then when i needed to run osmo-nitb i > also got back the error Aborted when trying to run it > > Please help me out > > Thanks in advance > > Develectron -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From msuraev at sysmocom.de Fri Jul 15 08:24:03 2016 From: msuraev at sysmocom.de (Max) Date: Fri, 15 Jul 2016 10:24:03 +0200 Subject: Need Help In installing openBSC for establishing GSM network with EDGE support In-Reply-To: References: Message-ID: <57889DA3.5070409@sysmocom.de> Would you mind sharing your entire config? Btw, dtx-used is indeed deprecated now - if you want to enable DTX use dtxu or/and dtxd. If you don't know what DTX is than just remove this line. Having said that, it should not prevent the startup. You might want to check the documentation at http://ftp.osmocom.org/docs/latest/ On 07/15/2016 02:41 AM, ayush gupta wrote: > Hello everyone, > > i am noob to this field and currently trying to establishing a GSM > network with EDGE support > using this page as guide > http://openbsc.osmocom.org/trac/wiki/Ettus_USRP_B2xx_family#no1 > i am stuck at this command > > sudo osmo-nitb -C -c openbsc.conf -T -P -m > > its giving me following error > > There is no such command. > Error occurred during reading below line: > extension-prefix 0 > > % 'dtx-used' is now deprecated: use dtx * configuration options of BTS instead > Fri Jul 15 05:35:26 2016 <0005> bsc_init.c:492 Failed to parse the config file: '/home/ryker/openbsc.conf' > > any help would be highly appreciated > thanks -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From laforge at gnumonks.org Fri Jul 15 14:12:57 2016 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 15 Jul 2016 16:12:57 +0200 Subject: Problem with running omso-nitb In-Reply-To: References: Message-ID: <20160715141257.GJ12206@nataraja> Hi Gof, On Fri, Jul 15, 2016 at 01:34:51AM +0200, Gof . wrote: > I got most off the tools working on a Debian 8.5, but when i try to run If you're on debian, why not simply give the nightly debian packages a try, which we publish for our user base? At least as a first step, before trying to build the full stack yourself. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From tom at tsou.cc Fri Jul 15 18:36:31 2016 From: tom at tsou.cc (Tom Tsou) Date: Fri, 15 Jul 2016 11:36:31 -0700 Subject: Need Help In installing openBSC for establishing GSM network with EDGE support In-Reply-To: References: Message-ID: Hi Ayush, On Thu, Jul 14, 2016 at 5:41 PM, ayush gupta wrote: > i am noob to this field and currently trying to establishing a GSM network > with EDGE support > using this page as guide > http://openbsc.osmocom.org/trac/wiki/Ettus_USRP_B2xx_family#no1 Some parts of that wiki page are probably out of date. EDGE support in osmo-bts is currently in review. I am in the process of addressing review comments and updating wiki pages. In the meantime, the EGPRS branch for osmo-bts is required. git://git.osmocom.org/osmo-bts ttsou/egprs Sharing your configuration files would also be helpful. -TT From msuraev at sysmocom.de Mon Jul 18 08:15:54 2016 From: msuraev at sysmocom.de (Max) Date: Mon, 18 Jul 2016 10:15:54 +0200 Subject: jenkins matrix + --enable-iu In-Reply-To: <20160713131232.GA1685@dub6> References: <20160713131232.GA1685@dub6> Message-ID: <578C903A.5060101@sysmocom.de> Personally I don't mind waiting longer - it's background job which does not prevent me from working on smth else while build happens. On 07/13/2016 03:12 PM, Neels Hofmeyr wrote: > Hi list, > > I've got a jenkins job ready that adds --enable-iu to the openbsc build matrix. > > I'd like to verify with you guys: so far we had a build matrix of 2 x 2, so > openbsc and all its dependencies are built four times over (~22 min). > Adding --enable-iu doubles this matrix to eight times. > > This means that any new commit would take about 55 min to verify with jenkins, > even if it is just a comment tweak. > > I assume we want to bring this time down a bit? > > I'd have these suggestions: > > (1) > Just add --enable-iu, let jenkins build for hours and proliferate global > warming, and care about this once it actually bugs us. > > (2) > Limit the build matrix: Only build --enable-iu once, e.g. with --enable-smpp > and --enable-mgcp-transcoding, not with all of the other combinations. (Would > --disable-mgcp make more sense?) > > (3) > Don't build all of the dependencies over and over. In pseudo sort of: > > dep_hashes = "" > for dep in libosmo*: > dep_hashes += "," + dep.get_current_git_hash() > if dep.last_hashes == dep_hashes: > dep."make install" > continue > dep.wipe_out() > dep."autoreconf; configure; make check; make install" > cat dep_hashes > "${dep.dir}/last_hashes" > > That would shorten the build time substantially, and we could keep the build > matrix fully featured without taking too much time. > > I've so far spent 5 minutes on implementing something like this and could > polish that up, maybe using a global dependencies workspace somewhere else on > the build slave so the separate matrix items benefit from each other. > > But do we like that? I would consider re-using previous builds safe enough for > our jenkins verifier, since all deps would be rebuilt even if only one dep's > git hash changes; assuming that it *works*, of course. Do you guys agree? > > > http://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit-test/ > openbsc.git branches osmocom/jenkins-test and neels/speed_up_matrix_builds > > Thanks for your opinions! > > ~Neels > -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From nhofmeyr at sysmocom.de Mon Jul 18 11:01:32 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 18 Jul 2016 13:01:32 +0200 Subject: Need Help In installing openBSC for establishing GSM network with EDGE support In-Reply-To: References: Message-ID: <20160718110132.GA1760@dub6> On Fri, Jul 15, 2016 at 06:11:53AM +0530, ayush gupta wrote: > There is no such command. > Error occurred during reading below line: > extension-prefix 0 This means that the config file you used contains a line that osmo-nitb does not understand. Looking in the git logs, I could actually not find this config item anywhere in the past of our main line osmo-nitb. So maybe this config file once worked with a development branch of osmo-nitb. Sounds related to telephone numbers. I'd suggest simply removing the extension-prefix line from openbsc.conf. Also note that we've moved to redmine, and the page you referenced was migrated to http://osmocom.org/projects/cellular-infrastructure/wiki/Ettus_USRP_B2xx_family (which doesn't mean that anyone fixed it, though) Hope to have helped, ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Tue Jul 19 12:03:51 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 19 Jul 2016 14:03:51 +0200 Subject: range error in RSL_CHAN_SDCCH4_ACCH + lchan_nr? Message-ID: <20160719120351.GA7165@ass40.sysmocom.de> Yesterday I came across gsm_ts2chan_nr() in openbsc gsm_data_shared.c (which is used both in openbsc and osmo-bts). IIUC this case would expect lchan_nr to be in the range 0..3: case GSM_PCHAN_CCCH_SDCCH4: case GSM_PCHAN_CCCH_SDCCH4_CBCH: cbits = 0x04; cbits += lchan_nr; break; Because if we'd add 4 or more, we would be walking into this cbits space: case GSM_PCHAN_SDCCH8_SACCH8C: case GSM_PCHAN_SDCCH8_SACCH8C_CBCH: cbits = 0x08; cbits += lchan_nr; break; The thing is, I added an assert for lchan_nr < 4, and it hits. We're actually passing lchan_nr == 4 and thus use cbits = 0x08 for a GSM_PCHAN_CCCH_SDCCH4: wrong. This code in osmo-bts-*/oml.c:opstart_compl() activates lchan[4] of a CCCH+SDCCH4 ts: /* ugly hack to auto-activate all SAPIs for the BCCH/CCCH on TS0 */ if (mo->obj_class == NM_OC_CHANNEL && mo->obj_inst.trx_nr == 0 && mo->obj_inst.ts_nr == 0) { struct gsm_lchan *cbch = gsm_bts_get_cbch(mo->bts); DEBUGP(DL1C, "====> trying to activate lchans of BCCH\n"); mo->bts->c0->ts[0].lchan[4].rel_act_kind = LCHAN_REL_ACT_OML; lchan_activate(&mo->bts->c0->ts[0].lchan[4]); if (cbch) { cbch->rel_act_kind = LCHAN_REL_ACT_OML; lchan_activate(cbch); } } This [4] the first SDCCH4, because this has CCCH in the first [0..3], right? But then we should use lchan->nr - 4 to add to the cbits, right? It seems pretty much everyone, our code and various BTS models, are ignoring the erratic cbits, but would be good to fix. My SysmoBTS GSM cell still works if I pass cbits = 0x04 instead of 0x08, like this: case GSM_PCHAN_CCCH_SDCCH4: case GSM_PCHAN_CCCH_SDCCH4_CBCH: /* SDCCH4 is in lchan_nr 4..7, so subtract 4 before adding to * the cbits. */ if (lchan_nr >= 4) lchan_nr -= 4; OSMO_ASSERT(lchan_nr < 4); cbits = 0x04; cbits += lchan_nr; However, I guess passing 0x04 cbits for a CCCH lchan is wrong as well (0x04 is RSL_CHAN_SDCCH4_ACCH). Instead, we should pass RSL_CHAN_RACH (Uplink CCCH) or RSL_CHAN_PCH_AGCH (Downlink CCCH), right? How to decide which of the two? Thanks for any hints, ~Neels [[[ [...] <0001> oml.c:830 OC=CHANNEL(03) INST=(00,00,00) Rx OPSTART <0006> oml.c:500 (bts=0,trx=0,ts=0,ss=0) pchan=CCCH+SDCCH4 ts_connect_as(CCCH+SDCCH4) logChComb=4 ^ SDCCH4 <0007> l1_if.c:164 Tx L1 prim MPH-CONNECT.req <0001> oml.c:249 OC=CHANNEL INST=(00,00,00) AVAIL STATE Dependency -> OK <0001> oml.c:256 OC=CHANNEL INST=(00,00,00) OPER STATE Disabled -> Enabled <0001> oml.c:217 OC=CHANNEL INST=(00,00,00) Tx STATE CHG REP <0006> oml.c:285 ====> trying to activate lchans of BCCH <0006> lchan.c:31 (bts=0,trx=0,ts=0,ss=4) state NONE -> ACTIVATION REQUESTED ^ ss=4 means lchan->nr=4 <0006> oml.c:1040 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.req (hL2=0x000004bb, FCCH TxDL) <0007> l1_if.c:164 Tx L1 prim MPH-ACTIVATE.req <0006> oml.c:777 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.conf (FCCH TxDL) <0006> oml.c:783 Successful activation of L1 SAPI FCCH on TS 0 <0006> oml.c:1040 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.req (hL2=0x000004bb, SCH TxDL) <0007> l1_if.c:164 Tx L1 prim MPH-ACTIVATE.req <0006> oml.c:777 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.conf (SCH TxDL) <0006> oml.c:783 Successful activation of L1 SAPI SCH on TS 0 <0006> oml.c:1040 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.req (hL2=0x000004bb, BCCH TxDL) <0007> l1_if.c:164 Tx L1 prim MPH-ACTIVATE.req <0006> oml.c:777 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.conf (BCCH TxDL) <0006> oml.c:783 Successful activation of L1 SAPI BCCH on TS 0 <0006> oml.c:1040 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.req (hL2=0x000004bb, AGCH TxDL) <0007> l1_if.c:164 Tx L1 prim MPH-ACTIVATE.req <0006> oml.c:777 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.conf (AGCH TxDL) <0006> oml.c:783 Successful activation of L1 SAPI AGCH on TS 0 <0006> oml.c:1040 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.req (hL2=0x000004bb, PCH TxDL) <0007> l1_if.c:164 Tx L1 prim MPH-ACTIVATE.req <0006> oml.c:777 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.conf (PCH TxDL) <0006> oml.c:783 Successful activation of L1 SAPI PCH on TS 0 <0006> oml.c:1040 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.req (hL2=0x000004bb, RACH RxUL) <0007> l1_if.c:164 Tx L1 prim MPH-ACTIVATE.req <0006> oml.c:777 (bts=0,trx=0,ts=0,ss=4) MPH-ACTIVATE.conf (RACH RxUL) <0006> oml.c:783 Successful activation of L1 SAPI RACH on TS 0 <0006> lchan.c:31 (bts=0,trx=0,ts=0,ss=4) state ACTIVATION REQUESTED -> ACTIVE Assert failed lchan_nr < 4 gsm_data_shared.c:518 ^ from mph_info_chan_confirm(), lchan_nr == 4 (gdb) bt #0 0x47d47208 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x47d4ad8c in __GI_abort () at abort.c:89 #2 0x000186e4 in gsm_ts2chan_nr (ts=, lchan_nr=) at ../../../openbsc/openbsc/src/libcommon/gsm_data_shared.c:518 #3 0x00018710 in gsm_lchan2chan_nr (lchan=lchan at entry=0xb6d5b000) at ../../../openbsc/openbsc/src/libcommon/gsm_data_shared.c:540 #4 0x0000eb0c in mph_info_chan_confirm (lchan=0xb6d5b000, lchan at entry=0xb6d283c8, type=type at entry=PRIM_INFO_ACTIVATE, cause=cause at entry=0 '\000') at oml.c:56 #5 0x00010730 in sapi_activate_cb (lchan=0xb6d283c8, status=0) at oml.c:1080 #6 0x000108d4 in sapi_queue_dispatch (lchan=0x1, lchan at entry=0xb6d283c8, status=) at oml.c:729 #7 0x00010c2c in lchan_act_compl_cb (trx=, l1_msg=l1_msg at entry=0x4f850, data=) at oml.c:814 #8 0x0000da2c in l1if_handle_l1prim (wq=, fl1h=0xafdc0, msg=msg at entry=0x4f850) at l1_if.c:1037 ]]] -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From laforge at gnumonks.org Wed Jul 20 07:56:10 2016 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 20 Jul 2016 09:56:10 +0200 Subject: range error in RSL_CHAN_SDCCH4_ACCH + lchan_nr? In-Reply-To: <20160719120351.GA7165@ass40.sysmocom.de> References: <20160719120351.GA7165@ass40.sysmocom.de> Message-ID: <20160720075610.GL6258@nataraja> Hi Neels, On Tue, Jul 19, 2016 at 02:03:51PM +0200, Neels Hofmeyr wrote: > The thing is, I added an assert for lchan_nr < 4, and it hits. We're > actually passing lchan_nr == 4 and thus use cbits = 0x08 for a > GSM_PCHAN_CCCH_SDCCH4: wrong. > > This code in osmo-bts-*/oml.c:opstart_compl() activates lchan[4] of a > CCCH+SDCCH4 ts: > > /* ugly hack to auto-activate all SAPIs for the BCCH/CCCH on TS0 */ As the comment says, it is our BTS-internal "hack" to actiwate the L1 SAPIs for the BCCH/CCCH. The problem is bascially that 08.58 RSL specifies explicit activation for all the dedicated channels (SDCCH, TCH, ..) but doesn't specify any protocol-level activation for the common channels like CCCH. In the BTS code, we have this data structure where we basically define a list of L1 SAPIs (and associated directions) to activate for a given lchan (type). So the "logical" hack was to basically use the Combined BCCH lchan[4] (0...3 ar SDCCH, numbers 4 or higher are not used) to enable the common channel (PCH,AGCH,RACH, possibly CBCH, ...) at BTS start-up. Doing it this way means we only have one way of activating logical channels in the data model and in the code, rather than some special case code for the common channels, differing from the dedicated channels. This should be safe within our bts/trx/ts/lchan data model, and purely internal to the BTS, and is nothing that ever is exposed to RSL. > <0001> oml.c:830 OC=CHANNEL(03) INST=(00,00,00) Rx OPSTART > <0006> oml.c:500 (bts=0,trx=0,ts=0,ss=0) pchan=CCCH+SDCCH4 ts_connect_as(CCCH+SDCCH4) logChComb=4 > > ^ SDCCH4 > I see no issue here > <0007> l1_if.c:164 Tx L1 prim MPH-CONNECT.req > <0001> oml.c:249 OC=CHANNEL INST=(00,00,00) AVAIL STATE Dependency -> OK > <0001> oml.c:256 OC=CHANNEL INST=(00,00,00) OPER STATE Disabled -> Enabled > <0001> oml.c:217 OC=CHANNEL INST=(00,00,00) Tx STATE CHG REP > <0006> oml.c:285 ====> trying to activate lchans of BCCH > <0006> lchan.c:31 (bts=0,trx=0,ts=0,ss=4) state NONE -> ACTIVATION REQUESTED > > ^ ss=4 means lchan->nr=4 I see no issue here either. > <0006> lchan.c:31 (bts=0,trx=0,ts=0,ss=4) state ACTIVATION REQUESTED -> ACTIVE > Assert failed lchan_nr < 4 gsm_data_shared.c:518 > > ^ from mph_info_chan_confirm(), lchan_nr == 4 this is where it breaks. The introduction of the L1SAP interface uses RSL-style channel numbers in the primitive, and hence the assert. However, no RSL message is ever to be generated out of this chan-act.confirm. If we do, it is a bug Hope the above helps... -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Thu Jul 21 10:38:25 2016 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 21 Jul 2016 12:38:25 +0200 Subject: PDTCH and PTCCH activation In-Reply-To: <20160721102525.GA10843@ass40.sysmocom.de> References: <578FABD0.9060300@sysmocom.de> <20160721102525.GA10843@ass40.sysmocom.de> Message-ID: <20160721103825.GX6258@nataraja> Hi Neels, [posting to the openbsc mailing list, as this discussion is not GPRS related] On Thu, Jul 21, 2016 at 12:25:25PM +0200, Neels Hofmeyr wrote: > On Wed, Jul 20, 2016 at 06:50:24PM +0200, Max wrote: > > It's called from lchan_act_compl_cb() via sapi_queue_send() which is > > also in mph_send_activate_req() - I have hard time understanding how > > this works at all. Do we have this documented somewhere? > > Both the TCH/F_TCH/H_PDCH timeslot feature and the TCH/F_PDCH on osmo-trx > are stuck on some post-lchan_act_compl SAPI stuff. can you be more specific about what "stuff"? It's hard to be of assistance without details. Also, SAPIs exist completely separately on every SAP, such as the (M)PH-SAP of the physical layer and the (M)DL-SAP of LAPDm, wich is implemented via RSL. So it is useful to explicitly state which SAP we are talking about when mentioning "SAPI stuff". > So, I would also benefit from better understanding the actions after > lchan_act. I actually think the L1 SAPI activation/deactivation is rather simple. You have the tables that list the SAPI+Direction combinations needed for every lchan type (what I just quoted for PDCH in my recent mail), and then the code iterates over the list of SAPI+Direction at time of lchan activation or deactivation. > Apparently related: libosmocore/gsm/lapd*.c How are the SAPIs of the data link layer should be related to SAPIs of the physical layer? LAPDm is establishing reliable channels over the already established physical layer, and LAPDm is not by iself activating/deactivating any channels, i.e. not talking to the MPH-SAP. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From nhofmeyr at sysmocom.de Thu Jul 21 11:19:55 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 21 Jul 2016 13:19:55 +0200 Subject: PDTCH and PTCCH activation In-Reply-To: <20160721103825.GX6258@nataraja> References: <578FABD0.9060300@sysmocom.de> <20160721102525.GA10843@ass40.sysmocom.de> <20160721103825.GX6258@nataraja> Message-ID: <20160721111955.GA32754@ass40.sysmocom.de> On Thu, Jul 21, 2016 at 12:38:25PM +0200, Harald Welte wrote: > Hi Neels, > > [posting to the openbsc mailing list, as this discussion is not GPRS > related] > > On Thu, Jul 21, 2016 at 12:25:25PM +0200, Neels Hofmeyr wrote: > > On Wed, Jul 20, 2016 at 06:50:24PM +0200, Max wrote: > > > It's called from lchan_act_compl_cb() via sapi_queue_send() which is > > > also in mph_send_activate_req() - I have hard time understanding how > > > this works at all. Do we have this documented somewhere? > > > > Both the TCH/F_TCH/H_PDCH timeslot feature and the TCH/F_PDCH on osmo-trx > > are stuck on some post-lchan_act_compl SAPI stuff. > > can you be more specific about what "stuff"? It's hard to be of > assistance without details. Well, I kind of feel that I should be able to find out myself, so I kept my remark at a distance. But since you were so fast to reply and I am indeed a bit stuck in a stupid way... I'll focus on TCH/F_TCH/H_PDCH: GPRS works, but placing a TCH/H call doesn't. The pchan switchover dance is complete, but then the new TCH/H channel is not working. I notice that on a dyn TS just after switchover, log entries starting with "SAPI=0" are missing *on the BSC side*, when compared to a pure TCH/H: DRSL <0004> abis_rsl.c:1462 (bts=0,trx=0,ts=2,ss=0) CHANNEL ACTIVATE ACK DRSL <0004> abis_rsl.c:1133 (bts=0,trx=0,ts=2,ss=0) state ACTIVATION REQUESTED -> ACTIVE DRLL <0000> abis_rsl.c:1913 (bts=0,trx=0,ts=2,ss=0) SAPI=0 ESTABLISH INDICATION ^ missing for dyn TS DRLL <0000> gsm_04_08.c:3667 Dispatching 04.08 message, pdisc=5 DMM <0002> gsm_04_08.c:987 <- CM SERVICE REQUEST serv_type=0x01 MI(TMSI)=300151278 DMM <0002> gsm_04_08_utils.c:681 -> CM SERVICE ACK DRLL <0000> abis_rsl.c:1913 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION DRLL <0000> abis_rsl.c:1913 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION DRR <0003> bsc_api.c:647 BSC: Passing unknown 04.08 RR message type 0x60 to MSC DRLL <0000> gsm_04_08.c:3667 Dispatching 04.08 message, pdisc=6 DRR <0003> gsm_04_08.c:1281 MSC: Unimplemented GSM 04.08 RR msg type 0x60 DRLL <0000> abis_rsl.c:1913 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION DRLL <0000> abis_rsl.c:1913 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION The first one missing for a dyn TS is: DRLL <0000> abis_rsl.c:1913 (bts=0,trx=0,ts=2,ss=0) SAPI=0 ESTABLISH INDICATION So I tried to find its root. The log on the BSC is from receiving an RLL message from the BTS, so I tried to find out where it's sent in the BTS: * BSC: abis_rsl_rx_rll(): case RSL_MT_EST_IND * libosmocore/src/gsm/lapdm.c:421: send_rslms_dlsap(): case OSMO_PRIM(PRIM_DL_EST, PRIM_OP_INDICATION): [...] rll_msg = RSL_MT_EST_IND; * libosmocore/src/gsm/lapd_core.c:788: prim = PRIM_DL_EST; And there I seem to be in a very general area with lots of callers. I feel a bit stupid not to be able to see it, and my knowledge is really lacking... so I could use a noob nudge in the right direction there, or maybe a really coarse picture of what I'm talking about in the first place. My guess goes at sapi_queue_exeute() at the moment, but I'm not seeing the connections yet. BTW, the second TCH/H on a dynamic channel seems to be established successfully, so I'm probably clearing some lchan state during pchan switchover, but can't put my finger on it yet. Thanks, ~Neels > > > So, I would also benefit from better understanding the actions after > > lchan_act. > > I actually think the L1 SAPI activation/deactivation is rather simple. > You have the tables that list the SAPI+Direction combinations needed for > every lchan type (what I just quoted for PDCH in my recent mail), and > then the code iterates over the list of SAPI+Direction at time of lchan > activation or deactivation. > > > Apparently related: libosmocore/gsm/lapd*.c > > How are the SAPIs of the data link layer should be related to SAPIs of > the physical layer? > > LAPDm is establishing reliable channels over the already established > physical layer, and LAPDm is not by iself activating/deactivating any > channels, i.e. not talking to the MPH-SAP. > > -- > - Harald Welte http://laforge.gnumonks.org/ > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Thu Jul 21 12:18:43 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 21 Jul 2016 14:18:43 +0200 Subject: PDTCH and PTCCH activation In-Reply-To: <20160721111955.GA32754@ass40.sysmocom.de> References: <578FABD0.9060300@sysmocom.de> <20160721102525.GA10843@ass40.sysmocom.de> <20160721103825.GX6258@nataraja> <20160721111955.GA32754@ass40.sysmocom.de> Message-ID: <20160721121843.GA19460@ass40.sysmocom.de> On Thu, Jul 21, 2016 at 01:19:55PM +0200, Neels Hofmeyr wrote: > The first one missing for a dyn TS is: > > DRLL <0000> abis_rsl.c:1913 (bts=0,trx=0,ts=2,ss=0) SAPI=0 ESTABLISH INDICATION > > So I tried to find its root. The log on the BSC is from receiving an RLL > message from the BTS, so I tried to find out where it's sent in the BTS: DRSL <0000> rsl.c:2265 (bts=0,trx=0,ts=2,ss=1) Fwd RLL msg EST_IND from LAPDm to A-bis lapdm_rll_tx_cb() is sending, i.e. forwarding, the EST_IND. So it seems I'm not getting the EST_IND I need because of earlier misconfiguration of sorts. I hope to find it soon, especially because TCH/H slot 1 of a TS seems to work and only TCH/H slot 0 is failing, just after switchover. ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Thu Jul 21 13:21:09 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 21 Jul 2016 15:21:09 +0200 Subject: PDTCH and PTCCH activation In-Reply-To: <20160721121843.GA19460@ass40.sysmocom.de> References: <578FABD0.9060300@sysmocom.de> <20160721102525.GA10843@ass40.sysmocom.de> <20160721103825.GX6258@nataraja> <20160721111955.GA32754@ass40.sysmocom.de> <20160721121843.GA19460@ass40.sysmocom.de> Message-ID: <20160721132109.GB19460@ass40.sysmocom.de> On Thu, Jul 21, 2016 at 02:18:43PM +0200, Neels Hofmeyr wrote: > I hope to find it soon, especially because TCH/H slot 1 of a TS seems to > work and only TCH/H slot 0 is failing, just after switchover. As so often with these things, the solution is pretty simple... during channel switchover, I inadvertently throw away the lchan->rqd_ref, and thus no immediate assignment is sent. I was just looking in the wrong places... ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From laforge at gnumonks.org Thu Jul 21 14:47:32 2016 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 21 Jul 2016 16:47:32 +0200 Subject: PDTCH and PTCCH activation In-Reply-To: <20160721121843.GA19460@ass40.sysmocom.de> References: <578FABD0.9060300@sysmocom.de> <20160721102525.GA10843@ass40.sysmocom.de> <20160721103825.GX6258@nataraja> <20160721111955.GA32754@ass40.sysmocom.de> <20160721121843.GA19460@ass40.sysmocom.de> Message-ID: <20160721144731.GB6258@nataraja> Hi Neels, On Thu, Jul 21, 2016 at 02:18:43PM +0200, Neels Hofmeyr wrote: > I hope to find it soon, especially because TCH/H slot 1 of a TS seems to > work and only TCH/H slot 0 is failing, just after switchover. lchan[0] is what is also used as TCH/F or PDCH, while lchan[0] and lchan[1] are used in the TCH/H case. See my comment regarding re-initialization of the lchan array every time you switch the pchan type. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Thu Jul 21 14:43:40 2016 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 21 Jul 2016 16:43:40 +0200 Subject: PDTCH and PTCCH activation In-Reply-To: <20160721111955.GA32754@ass40.sysmocom.de> References: <578FABD0.9060300@sysmocom.de> <20160721102525.GA10843@ass40.sysmocom.de> <20160721103825.GX6258@nataraja> <20160721111955.GA32754@ass40.sysmocom.de> Message-ID: <20160721144340.GA6258@nataraja> Hi Neels, On Thu, Jul 21, 2016 at 01:19:55PM +0200, Neels Hofmeyr wrote: > I notice that on a dyn TS just after switchover, log entries starting with > "SAPI=0" are missing *on the BSC side*, when compared to a pure TCH/H: when switching the PCHAN type, do you also make sure to "re-configure' the data of the lchan array within that TS? I think some data in there might need to change, just from my memory. > DRLL <0000> abis_rsl.c:1913 (bts=0,trx=0,ts=2,ss=0) SAPI=0 ESTABLISH INDICATION > > So I tried to find its root. The log on the BSC is from receiving an RLL > message from the BTS, so I tried to find out where it's sent in the BTS: > > * BSC: abis_rsl_rx_rll(): case RSL_MT_EST_IND > * libosmocore/src/gsm/lapdm.c:421: send_rslms_dlsap(): > case OSMO_PRIM(PRIM_DL_EST, PRIM_OP_INDICATION): > [...] > rll_msg = RSL_MT_EST_IND; > * libosmocore/src/gsm/lapd_core.c:788: prim = PRIM_DL_EST; > > And there I seem to be in a very general area with lots of callers. an ESTABLISH INDICATION of LAPD(m) is triggered by a SABM frame on on LAPD(m). so you should try to trace the SABM frame from the MS over the radio interface (maybe confirm it using GSMTAP frames generated by the BTS) and trace it through the LAPD(m) code until on the upper side of the LAPDm code (towards RLL, which is part of RSL) it generates the ESTABLISH INDICATION > My guess goes at sapi_queue_exeute() at the moment, but I'm not seeing the > connections yet. I still don't see how this should at all relate to each other. As indicated, a pysical-layer SAPI has nothing to do with a data link-layer SAPI. It's like an IP address having nothing to do with an e-mail address. They're both called addresses, that's it. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From nhofmeyr at sysmocom.de Thu Jul 21 15:33:15 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 21 Jul 2016 17:33:15 +0200 Subject: TCH_H and TCH_F Message-ID: <20160721153315.GC19460@ass40.sysmocom.de> I have this problem: DCC <0001> gsm_04_08.c:1649 Cannot patch through call with different channel types: local = TCH_F, remote = TCH_H (At first I thought it was a bug in dynamic TCH_F/TCH_H/PDCH, but it's actually about any situation where both TCH/H and TCH/F are available. Tested with master:) If I configure the BSC to have both TCH_H and TCH_F slots, my two test phones try to call each other with mismatching TCH types. The CHANNEL REQUIRED messages send TCH/H and TCH/F, respectively. phones: Samsung S4 vs. Sony Ericsson SE K800i. If the CN is configured with only TCH/H or only TCH/F, the two phones talk to each other fine. So is this a missing feature in openbsc? In this sense: If one side started off in TCH/H, the other side should be urged towards TCH/H as well. This breaks the dynamic TS feature #1776: with fully dynamic TS, we're implicitly allowing both TCH/H and TCH/F, so if an MS asks for a TCH/F, it will get one before even considering a TCH/H, even if that mismatches the MS peer. So we should fix openbsc to "clamp" the callee to the caller's pchan type. We could also offer a limited TCH/H_PDCH type (or some other config to disable TCH/F on dyn TS, for example). ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Thu Jul 21 16:58:56 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 21 Jul 2016 18:58:56 +0200 Subject: TCH_H and TCH_F In-Reply-To: <20160721153315.GC19460@ass40.sysmocom.de> References: <20160721153315.GC19460@ass40.sysmocom.de> Message-ID: <20160721165856.GD19460@ass40.sysmocom.de> http://osmocom.org/issues/1778 ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From sipos.csaba at kvk.uni-obuda.hu Fri Jul 22 16:15:37 2016 From: sipos.csaba at kvk.uni-obuda.hu (Sipos Csaba) Date: Fri, 22 Jul 2016 18:15:37 +0200 (CEST) Subject: Need Help In installing openBSC for establishing GSM network with EDGE support In-Reply-To: References: Message-ID: <2145134474.7985057.1469204137155.JavaMail.zimbra@kvk.uni-obuda.hu> Dear Tom, > Some parts of that wiki page are probably out of date That is correct. I am more than happy to update the manual, just let me know when the Osmo-BTS and Osmo-TRX master branches are ready for use. If I remember correctly you said that some outstanding pathes are still not merged and you are working on it. Besides testing the latest (mainly EDGE related) modifications and swtich Osmo-BTS to the master branch, the manual is quite recent (compared to other parts of the wiki) and I tried it and it works. In time we can expand it with MCBTS and the SIP connector part (instead of the mISDN which increases the complexitiy of the installation process for new comers). So, just let me know when you think its ready, and I will retest and redo the outdated part of the Wiki. Regards, Csaba ----- Eredeti ?zenet ----- Felad?: "Tom Tsou" C?mzett: "ayush gupta" M?solatot kap: "OpenBSC Mailing List" Elk?ld?tt ?zenetek: P?ntek, 2016. J?lius 15. 20:36:31 T?rgy: Re: Need Help In installing openBSC for establishing GSM network with EDGE support Hi Ayush, On Thu, Jul 14, 2016 at 5:41 PM, ayush gupta wrote: > i am noob to this field and currently trying to establishing a GSM network > with EDGE support > using this page as guide > http://openbsc.osmocom.org/trac/wiki/Ettus_USRP_B2xx_family#no1 Some parts of that wiki page are probably out of date. EDGE support in osmo-bts is currently in review. I am in the process of addressing review comments and updating wiki pages. In the meantime, the EGPRS branch for osmo-bts is required. git://git.osmocom.org/osmo-bts ttsou/egprs Sharing your configuration files would also be helpful. -TT From nhofmeyr at sysmocom.de Sun Jul 24 11:11:33 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Sun, 24 Jul 2016 13:11:33 +0200 Subject: openbsc build broken due to new GSM_PCHAN value Message-ID: <20160724111133.GA10952@dub6> Just to let you know, the addition of GSM_PCHAN_TCH_F_TCH_H_PDCH in libosmocore implicitly broke the ctrl interface tests in openbsc. FAIL: testBtsChannelLoad (__main__.TestCtrlBSC) ---------------------------------------------------------------------- Traceback (most recent call last): File "./ctrl_test_runner.py", line 237, in testBtsChannelLoad self.assertEquals(r['value'], 'CCCH+SDCCH4,0,0 TCH/F,0,0 TCH/H,0,0 SDCCH8,0,0 TCH/F_PDCH,0,0 CCCH+SDCCH4+CBCH,0,0 SDCCH8+CBCH,0,0') AssertionError: 'CCCH+SDCCH4,0,0 TCH/F,0,0 TCH/H,0,0 SDCCH8,0,0 TCH/F_PDCH,0,0 CCCH+SDCCH4+CBCH,0,0 SDCCH8+CBCH,0,0 unknown 0xb,0,0' != 'CCCH+SDCCH4,0,0 TCH/F,0,0 TCH/H,0,0 SDCCH8,0,0 TCH/F_PDCH,0,0 CCCH+SDCCH4+CBCH,0,0 SDCCH8+CBCH,0,0' because this is unexpected output: "unknown 0xb,0,0" So *any* commit submitted to openbsc will currenty fail. I'll probably fix it shortly with a commit to openbsc... This also directed my attention towards the pchan_load mechanics. It always shows a TCH/F_PDCH entry, but in PDCH mode those would not have any load. I guess it makes sense in the current scheme of things, though it could make even more sense to record channel load not as separate TCH/F_PDCH but in the TCH/F slot, depending on current pchan mode? Similarly for upcoming TCH/F_TCH/H_PDCH: record in the TCH/F or TCH/H slot according to current pchan mode... (For now I'm focusing on completion of TCH/F_TCH/H_PDCH usability, if at all pchan_load tweaks would come later) ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Sun Jul 24 12:48:51 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Sun, 24 Jul 2016 14:48:51 +0200 Subject: openbsc build broken due to new GSM_PCHAN value In-Reply-To: <20160724111133.GA10952@dub6> References: <20160724111133.GA10952@dub6> Message-ID: <20160724124851.GA19143@dub6> Build fixed in 17a6bab150bd70954b00645c8d1f18ce3ccf8948 https://gerrit.osmocom.org/568 I pushed the commit through without peer review to fix the build, so maybe have a look whether I need to improve something. ~Neels On Sun, Jul 24, 2016 at 01:11:33PM +0200, Neels Hofmeyr wrote: > Just to let you know, the addition of GSM_PCHAN_TCH_F_TCH_H_PDCH in libosmocore > implicitly broke the ctrl interface tests in openbsc. > > > FAIL: testBtsChannelLoad (__main__.TestCtrlBSC) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "./ctrl_test_runner.py", line 237, in testBtsChannelLoad > self.assertEquals(r['value'], 'CCCH+SDCCH4,0,0 TCH/F,0,0 TCH/H,0,0 SDCCH8,0,0 TCH/F_PDCH,0,0 CCCH+SDCCH4+CBCH,0,0 SDCCH8+CBCH,0,0') > AssertionError: 'CCCH+SDCCH4,0,0 TCH/F,0,0 TCH/H,0,0 SDCCH8,0,0 TCH/F_PDCH,0,0 CCCH+SDCCH4+CBCH,0,0 SDCCH8+CBCH,0,0 unknown 0xb,0,0' != 'CCCH+SDCCH4,0,0 TCH/F,0,0 TCH/H,0,0 SDCCH8,0,0 TCH/F_PDCH,0,0 CCCH+SDCCH4+CBCH,0,0 SDCCH8+CBCH,0,0' > > because this is unexpected output: "unknown 0xb,0,0" > > So *any* commit submitted to openbsc will currenty fail. > I'll probably fix it shortly with a commit to openbsc... > > This also directed my attention towards the pchan_load mechanics. It always > shows a TCH/F_PDCH entry, but in PDCH mode those would not have any load. I > guess it makes sense in the current scheme of things, though it could make even > more sense to record channel load not as separate TCH/F_PDCH but in the TCH/F > slot, depending on current pchan mode? Similarly for upcoming > TCH/F_TCH/H_PDCH: record in the TCH/F or TCH/H slot according to current pchan > mode... (For now I'm focusing on completion of TCH/F_TCH/H_PDCH usability, if > at all pchan_load tweaks would come later) > > ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From holger at freyther.de Sun Jul 24 14:06:58 2016 From: holger at freyther.de (Holger Freyther) Date: Sun, 24 Jul 2016 22:06:58 +0800 Subject: openbsc build broken due to new GSM_PCHAN value In-Reply-To: <20160724124851.GA19143@dub6> References: <20160724111133.GA10952@dub6> <20160724124851.GA19143@dub6> Message-ID: <0F273C8C-6C64-4360-9410-B2321C47E6EC@freyther.de> > On 24 Jul 2016, at 20:48, Neels Hofmeyr wrote: > > Build fixed in 17a6bab150bd70954b00645c8d1f18ce3ccf8948 > https://gerrit.osmocom.org/568 > > I pushed the commit through without peer review to fix the build, so maybe have > a look whether I need to improve something. is it feasible to move the value_string array to libosmocore too? The VTY test would then still fail but that is okay(tm). holger From pmaier at sysmocom.de Mon Jul 25 08:26:33 2016 From: pmaier at sysmocom.de (Philipp Maier) Date: Mon, 25 Jul 2016 10:26:33 +0200 Subject: Looking for trace with GPRS XID / SNDCP-CID messages Message-ID: <5795CD39.2020001@sysmocom.de> Hi Folks, I am busy with implementing XID / SNDCP-XID parameter negotiation to use data and header compression with GPRS. It would be very helpful to have an example at hand that shows me how an SNDCP-XID is performed in real life. If someone of you has a GB-Interface trace at hand it would be very helpful for me. regards. Philipp From nhofmeyr at sysmocom.de Mon Jul 25 09:36:15 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 25 Jul 2016 11:36:15 +0200 Subject: gerrit: permission to submit Message-ID: <20160725093615.GA1768@dub6> I've added permission to submit a reviewed patch to the known users group, re: On Sun, Jul 24, 2016 at 04:08:35PM +0000, lynxis lazus wrote: > @Holger: I'm not allowed to do so on gerrit. On Mon, Jul 25, 2016 at 08:08:00AM +0000, Tom Tsou wrote: > Holger, Gerrit does not allow me to submit. ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Mon Jul 25 09:54:49 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 25 Jul 2016 11:54:49 +0200 Subject: openbsc build broken due to new GSM_PCHAN value In-Reply-To: <0F273C8C-6C64-4360-9410-B2321C47E6EC@freyther.de> References: <20160724111133.GA10952@dub6> <20160724124851.GA19143@dub6> <0F273C8C-6C64-4360-9410-B2321C47E6EC@freyther.de> Message-ID: <20160725095449.GA1462@dub6> On Sun, Jul 24, 2016 at 10:06:58PM +0800, Holger Freyther wrote: > > > On 24 Jul 2016, at 20:48, Neels Hofmeyr wrote: > > > > Build fixed in 17a6bab150bd70954b00645c8d1f18ce3ccf8948 > > https://gerrit.osmocom.org/568 > > > > I pushed the commit through without peer review to fix the build, so maybe have > > a look whether I need to improve something. > > > is it feasible to move the value_string array to libosmocore too? I'm pretty sure that it is... someone just needs to do it... I'd like to first put a lid on the dyn TS feature before adding more cosmetics. > The VTY test would then still fail but that is okay(tm). ...not failing anymore :) ~Neels -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Mon Jul 25 10:22:34 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 25 Jul 2016 12:22:34 +0200 Subject: osmo-bts: rach_ind.ra size Message-ID: <20160725102234.GA31552@dub6> I just came across this compiler warning: l1sap.c: In function 'gsmtap_ph_rach': l1sap.c:291:8: warning: assignment from incompatible pointer type [enabled by default] *data = &l1sap->u.rach_ind.ra; ^ It's a uint16_t ra and used like this in common/l1sap.c: static int gsmtap_ph_rach(struct osmo_phsap_prim *l1sap, uint8_t *chan_type, uint8_t *tn, uint8_t *ss, uint32_t *fn, uint8_t **data, int *len) { [...] *data = &l1sap->u.rach_ind.ra; *len = 1; A cast like this would fix the compiler warning and make sense if data is interpreted to point at a 16 bit data block, probably in host byte order though: *data = (uint8_t*)&l1sap->u.rach_ind.ra; *len = 1; But *len = 1 means that **data is an 8bit value? This is sent to gsmtap. Is *len = 1 something we should fix? ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From msuraev at sysmocom.de Mon Jul 25 10:31:22 2016 From: msuraev at sysmocom.de (Max) Date: Mon, 25 Jul 2016 12:31:22 +0200 Subject: osmo-bts: rach_ind.ra size In-Reply-To: <20160725102234.GA31552@dub6> References: <20160725102234.GA31552@dub6> Message-ID: <5795EA7A.2020705@sysmocom.de> That's probably related to https://gerrit.osmocom.org/#/c/427/3 If that's really the case than fix would be to check for is_11bit of ph_rach_ind_param and adjust length accordingly. On 07/25/2016 12:22 PM, Neels Hofmeyr wrote: > I just came across this compiler warning: > > l1sap.c: In function 'gsmtap_ph_rach': > l1sap.c:291:8: warning: assignment from incompatible pointer type [enabled by default] > *data = &l1sap->u.rach_ind.ra; > ^ > > It's a > uint16_t ra > and used like this in common/l1sap.c: > > static int gsmtap_ph_rach(struct osmo_phsap_prim *l1sap, uint8_t *chan_type, > uint8_t *tn, uint8_t *ss, uint32_t *fn, uint8_t **data, int *len) > { > [...] > *data = &l1sap->u.rach_ind.ra; > *len = 1; > > A cast like this would fix the compiler warning and make sense if data is > interpreted to point at a 16 bit data block, probably in host byte order > though: > > *data = (uint8_t*)&l1sap->u.rach_ind.ra; > *len = 1; > > But *len = 1 means that **data is an 8bit value? > This is sent to gsmtap. > > Is *len = 1 something we should fix? > > ~Neels > > -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From holger at freyther.de Mon Jul 25 10:34:11 2016 From: holger at freyther.de (Holger Freyther) Date: Mon, 25 Jul 2016 18:34:11 +0800 Subject: osmo-bts: rach_ind.ra size In-Reply-To: <5795EA7A.2020705@sysmocom.de> References: <20160725102234.GA31552@dub6> <5795EA7A.2020705@sysmocom.de> Message-ID: > On 25 Jul 2016, at 18:31, Max wrote: > > That's probably related to https://gerrit.osmocom.org/#/c/427/3 > If that's really the case than fix would be to check for is_11bit of > ph_rach_ind_param and adjust length accordingly. right, https://gerrit.osmocom.org/#/c/434/2/src/osmo-bts-sysmo/l1_if.c has the potential fix/update to it. I re-triggered the jenkins job right now. The BTS/PCU protocol is next, followed by the PCU. :) holger From keith at rhizomatica.org Mon Jul 25 12:19:39 2016 From: keith at rhizomatica.org (Keith) Date: Mon, 25 Jul 2016 14:19:39 +0200 Subject: NITB hangs if many subscribes and/or subsr. exists with empty extension in hlr Message-ID: <3c9e1f6c-2b13-9df6-2b2b-2732270c4e56@rhizomatica.org> Hi All, On one of our sites osmo-nitb was hanging a few seconds after startup. It took me a while to track it down, and I'm sorry I do not have log output as it has gone to scroll buffer heaven, and I do not want to break the system again right now to get another output, but I can say more or less what happens. If I see it again, I'll be sure to capture full debug log. I also have a backup of the state of the offending hlr, so I can bring it up locally and see if I can replicate and send the log. In fact, there was nothing out of the ordinary in the log anyway before nitb simply stops responding. (CTRL-C still shuts down cleanly if would seem) This 'bad' hlr has some 30,815 subscriber entries, one of them has empty string for extension. (We normally never get to anything near 30,000 as we purge inactive subscribers regularly, but the blank extension had broken our purge job) On this blank extension issue, i'm not sure it coincides with the hang, but I noted this error followed by DBI traceback from here: http://git.osmocom.org/openbsc/tree/openbsc/src/libmsc/db.c#n54 Error was non unique value for column extension, which makes sense of course, as we don't give it a value. Also seems we don't recover from this, as |db_subscriber_alloc_exten() will never be called? | I deleted some 28,000 subscriber entries that were not commissioned users, and the nitb then functions, so I'm at a loss to know where it might have been actually stuck, or if it might be related to the blank extension, or to the large amount of subscriber entries, or something else. Maybe it's obvious to somebody. I have of course deleted the blank extension entry now from the hlr. Thanks! Keith. -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at freyther.de Mon Jul 25 12:40:37 2016 From: holger at freyther.de (Holger Freyther) Date: Mon, 25 Jul 2016 20:40:37 +0800 Subject: osmo-bts: rach_ind.ra size In-Reply-To: <20160725102234.GA31552@dub6> References: <20160725102234.GA31552@dub6> Message-ID: <5ECE6079-8948-443B-A222-8E5D8BB8DA9B@freyther.de> > On 25 Jul 2016, at 18:22, Neels Hofmeyr wrote: > > I just came across this compiler warning: > > l1sap.c: In function 'gsmtap_ph_rach': > l1sap.c:291:8: warning: assignment from incompatible pointer type [enabled by default] > *data = &l1sap->u.rach_ind.ra; > ^ okay, I reviewed the patch that adds 11bit support for the sysmobts but l1sap.c is not addressed. Shall we revert the 11bit l1sap change for now or wait? holger PS: If we would disable the doxygen warnings and remove -Wall when compiling the dependencies the amount of warnings would go down and we might find such things earlier? From alexander.chemeris at gmail.com Mon Jul 25 15:11:07 2016 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Mon, 25 Jul 2016 11:11:07 -0400 Subject: NITB hangs if many subscribes and/or subsr. exists with empty extension in hlr In-Reply-To: <3c9e1f6c-2b13-9df6-2b2b-2732270c4e56@rhizomatica.org> References: <3c9e1f6c-2b13-9df6-2b2b-2732270c4e56@rhizomatica.org> Message-ID: Hi Keith, I can confirm that OpenBSC becomes extremely slow and almost hangs after a certain amount of subscribers or a large number of SMS (30,000 subs sounds like a number it should happen). I'm not 100% certain, but I think this is the real reason and not the empty extension. If you have a copy of the HLR - you should be able to reproduce that just by starting an OpenBSC with this HLR database. On Mon, Jul 25, 2016 at 8:19 AM, Keith wrote: > Hi All, > > On one of our sites osmo-nitb was hanging a few seconds after startup. It > took me a while to track it down, and I'm sorry I do not have log output as > it has gone to scroll buffer heaven, and I do not want to break the system > again right now to get another output, but I can say more or less what > happens. > > If I see it again, I'll be sure to capture full debug log. I also have a > backup of the state of the offending hlr, so I can bring it up locally and > see if I can replicate and send the log. > In fact, there was nothing out of the ordinary in the log anyway before nitb > simply stops responding. (CTRL-C still shuts down cleanly if would seem) > > This 'bad' hlr has some 30,815 subscriber entries, one of them has empty > string for extension. > > (We normally never get to anything near 30,000 as we purge inactive > subscribers regularly, but the blank extension had broken our purge job) > > On this blank extension issue, i'm not sure it coincides with the hang, but > I noted this error followed by DBI traceback from here: > http://git.osmocom.org/openbsc/tree/openbsc/src/libmsc/db.c#n54 > Error was non unique value for column extension, which makes sense of > course, as we don't give it a value. > Also seems we don't recover from this, as db_subscriber_alloc_exten() will > never be called? > > I deleted some 28,000 subscriber entries that were not commissioned users, > and the nitb then functions, so I'm at a loss to know where it might have > been actually stuck, or if it might be related to the blank extension, or to > the large amount of subscriber entries, or something else. > > Maybe it's obvious to somebody. I have of course deleted the blank extension > entry now from the hlr. > > Thanks! > > > Keith. > > > -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co From nhofmeyr at sysmocom.de Mon Jul 25 19:59:13 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 25 Jul 2016 21:59:13 +0200 Subject: HEADS UP: openbsc.git: force push on master Message-ID: <20160725195913.GA4875@dub6> Today, gerrit has merged four of my changesets twice for some reason (even though they had the very same Change-Id), meaning that openbsc.git master got four empty commits. It could end up being a stupid thing to do, but I thought if at all then right now and no later: I forced master HEAD back so that we don't have empty commits in it, back to d1c0e3755f2832270a16bdb2d350463409cad887. I apologize in advance for any inconvenience caused. If you need help to recover from a diverged master branch, don't hesitate to ask! ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Mon Jul 25 20:10:10 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 25 Jul 2016 22:10:10 +0200 Subject: HEADS UP: openbsc.git: force push on master In-Reply-To: <20160725195913.GA4875@dub6> References: <20160725195913.GA4875@dub6> Message-ID: <20160725201010.GB4875@dub6> Great, osmo-bts.git also has some empty revisions. They are not at master's tip, so I'm leaving those. Gerrit was causing trouble today when I wanted to merge a branch, and I tried to reapply a patch that had fixed branch submission earlier. I hope that patch caused the faulty submissions. I have put plain gerrit back without the patch. ~Neels On Mon, Jul 25, 2016 at 09:59:13PM +0200, Neels Hofmeyr wrote: > Today, gerrit has merged four of my changesets twice for some reason (even > though they had the very same Change-Id), meaning that openbsc.git master got > four empty commits. > > It could end up being a stupid thing to do, but I thought if at all then right > now and no later: I forced master HEAD back so that we don't have empty commits > in it, back to d1c0e3755f2832270a16bdb2d350463409cad887. > > I apologize in advance for any inconvenience caused. If you need help to > recover from a diverged master branch, don't hesitate to ask! > > ~Neels > > -- > - Neels Hofmeyr http://www.sysmocom.de/ > ======================================================================= > * sysmocom - systems for mobile communications GmbH > * Alt-Moabit 93 > * 10559 Berlin, Germany > * Sitz / Registered office: Berlin, HRB 134158 B > * Gesch?ftsf?hrer / Managing Directors: Harald Welte -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From shasan at fb.com Wed Jul 27 00:24:09 2016 From: shasan at fb.com (Shaddi Hasan) Date: Wed, 27 Jul 2016 00:24:09 +0000 Subject: New subscriber not created automatically with accept-all/subscriber-create-on-demand configuration Message-ID: Hi folks, I'm seeing some unexpected behavior from OsmoNITB. I am running from the Debian 8 nightly builds from July 25 for everything. My OpenBSC configuration is set as follows: network [...] auth policy accept-all [...] nitb subscriber-create-on-demand assign-tmsi [...] When a new phone tries to camp to the network, it's rejected as follows: https://gist.github.com/shaddi/7674680c329f14c0042fbeca5227962e ("Failed to find subscriber"). My full openbsc.cfg is in that gist as well. If I create the subscriber by IMSI via the VTY though, it camps fine and everything else works as expected. When I tested this this configuration a few weeks ago with an earlier build (sorry, can't recall which one), adding the subscriber manually wasn't necessary, and with the configuration above seems like it also shouldn't be necessary. Couple questions: - Is this the expected behavior for this configuration? - If so, is there currently a way to achieve the prior behavior (subscriber created automatically when a new phone tries to camp, rather than being rejected)? Thanks, Shaddi From msuraev at sysmocom.de Wed Jul 27 09:08:32 2016 From: msuraev at sysmocom.de (Max) Date: Wed, 27 Jul 2016 11:08:32 +0200 Subject: New subscriber not created automatically with accept-all/subscriber-create-on-demand configuration In-Reply-To: References: Message-ID: <57987A10.9020504@sysmocom.de> Could you run 'show network' on openbsc vty and copy-paste output here or add it to gist? On 07/27/2016 02:24 AM, Shaddi Hasan wrote: > Hi folks, I'm seeing some unexpected behavior from OsmoNITB. I am running from the Debian 8 nightly builds from July 25 for everything. > > My OpenBSC configuration is set as follows: > > network > [...] > auth policy accept-all > [...] > nitb > subscriber-create-on-demand > assign-tmsi > [...] > > When a new phone tries to camp to the network, it's rejected as follows: https://gist.github.com/shaddi/7674680c329f14c0042fbeca5227962e ("Failed to find subscriber"). My full openbsc.cfg is in that gist as well. > > If I create the subscriber by IMSI via the VTY though, it camps fine and everything else works as expected. When I tested this this configuration a few weeks ago with an earlier build (sorry, can't recall which one), adding the subscriber manually wasn't necessary, and with the configuration above seems like it also shouldn't be necessary. Couple questions: > > - Is this the expected behavior for this configuration? > - If so, is there currently a way to achieve the prior behavior (subscriber created automatically when a new phone tries to camp, rather than being rejected)? > > Thanks, > Shaddi -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From msuraev at sysmocom.de Wed Jul 27 10:03:59 2016 From: msuraev at sysmocom.de (Max) Date: Wed, 27 Jul 2016 12:03:59 +0200 Subject: New subscriber not created automatically with accept-all/subscriber-create-on-demand configuration In-Reply-To: References: Message-ID: <5798870F.7030801@sysmocom.de> Yepp, that's a bug, patch with fix will follow shortly. In a meantime please add following to your 'network' part of config as a workaround: ... authorized-regexp .* ... Thanks for reporting it! On 07/27/2016 02:24 AM, Shaddi Hasan wrote: > Hi folks, I'm seeing some unexpected behavior from OsmoNITB. I am running from the Debian 8 nightly builds from July 25 for everything. > > My OpenBSC configuration is set as follows: > > network > [...] > auth policy accept-all > [...] > nitb > subscriber-create-on-demand > assign-tmsi > [...] > > When a new phone tries to camp to the network, it's rejected as follows: https://gist.github.com/shaddi/7674680c329f14c0042fbeca5227962e ("Failed to find subscriber"). My full openbsc.cfg is in that gist as well. > > If I create the subscriber by IMSI via the VTY though, it camps fine and everything else works as expected. When I tested this this configuration a few weeks ago with an earlier build (sorry, can't recall which one), adding the subscriber manually wasn't necessary, and with the configuration above seems like it also shouldn't be necessary. Couple questions: > > - Is this the expected behavior for this configuration? > - If so, is there currently a way to achieve the prior behavior (subscriber created automatically when a new phone tries to camp, rather than being rejected)? > > Thanks, > Shaddi -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From nhofmeyr at sysmocom.de Wed Jul 27 12:21:08 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 27 Jul 2016 14:21:08 +0200 Subject: osmo-bts: rach_ind.ra size In-Reply-To: <5ECE6079-8948-443B-A222-8E5D8BB8DA9B@freyther.de> References: <20160725102234.GA31552@dub6> <5ECE6079-8948-443B-A222-8E5D8BB8DA9B@freyther.de> Message-ID: <20160727122108.GC4938@dub6> On Mon, Jul 25, 2016 at 08:40:37PM +0800, Holger Freyther wrote: > > > On 25 Jul 2016, at 18:22, Neels Hofmeyr wrote: > > > > I just came across this compiler warning: > > > > l1sap.c: In function 'gsmtap_ph_rach': > > l1sap.c:291:8: warning: assignment from incompatible pointer type [enabled by default] > > *data = &l1sap->u.rach_ind.ra; > > ^ > > okay, I reviewed the patch that adds 11bit support for the sysmobts but l1sap.c is not addressed. Shall we revert the 11bit l1sap change for now or wait? This "only" concerns gsmtap. Given the lengthy course of those patches, I'd give it some time and not add frustration with a revert... Bhagarva, are you reading this, and could you add gsmtap capability for 11 bit soon? > PS: If we would disable the doxygen warnings and remove -Wall when compiling the dependencies the amount of warnings would go down and we might find such things earlier? +1 for disabling doxygen warnings (or >/dev/null 2>&1 even) Otherwise, the way I notice warnings is mostly by running ':make' in vim and browsing the warnings. We don't have that many warnings with -Wall, do we? Most of them are usually '#warning' or deprecation warnings. I'd keep -Wall. ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From bbutterly at ernw.de Wed Jul 27 12:19:53 2016 From: bbutterly at ernw.de (Brian Butterly) Date: Wed, 27 Jul 2016 14:19:53 +0200 Subject: OsmoNITB + Asterisk Message-ID: Hi, has anyone recently put together a functional setup with OsmoNITB and Asterisk (+LCR)? I've got multiple errors while compiling LCR with Asterisk, mainly unknown definitions and a set of missing functions. My setup: -NanoBTS -current OpenBSC (running perfectly) -Ubuntu Xenial, 64Bit, VBox VM -current LCR from Osmocom Repos -Asterisk (build without any issues) --1.8.32.3 from Asterisk Page --1.6.2.24 from Asterisk Page --11.32.0 form Asterisk Page --last 13.x release vie apt I had expected the newer versions to be incompatible, still gave them a shot anyways. I've started fiddling with LCR, but before I go deeper into that, I just wanted to check if there was some defined approach which would get everything up and running. I'd be very thankful for any hint or maybe some information on which versions of what will actually work together. Thanks! Brian From holger at freyther.de Wed Jul 27 12:33:07 2016 From: holger at freyther.de (Holger Freyther) Date: Wed, 27 Jul 2016 20:33:07 +0800 Subject: OsmoNITB + Asterisk In-Reply-To: References: Message-ID: <848FD39F-8825-4069-91D6-60BBB17E5200@freyther.de> > On 27 Jul 2016, at 20:19, Brian Butterly wrote: > > Hi, Hi! > has anyone recently put together a functional setup with OsmoNITB and > Asterisk (+LCR)? why asterisk? why LCR? The osmo-sip-connector is a "trivial" piece of software that bridges MNCC to SIP (and back) and let's everyone else do the heavy lifting. In contrast to LCR it currently lacks: * Multi-party calls (a bit harder) * DTMF (quite easy but not done) holger From nhofmeyr at sysmocom.de Thu Jul 28 16:40:33 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 28 Jul 2016 18:40:33 +0200 Subject: [PATCH] remove INSTALL file to have a clean git status Message-ID: <1469724033-27105-1-git-send-email-nhofmeyr@sysmocom.de> From: Neels Hofmeyr The INSTALL file is being overwritten by autoreconf, but it is committed as empty file. As a result, the INSTALL file always shows as modified. Instead, remove INSTALL from git and ignore it. --- .gitignore | 1 + INSTALL | 0 2 files changed, 1 insertion(+) delete mode 100644 INSTALL diff --git a/.gitignore b/.gitignore index e15c19b..d1a0b33 100644 --- a/.gitignore +++ b/.gitignore @@ -39,6 +39,7 @@ libtool ltmain.sh missing stamp-h1 +INSTALL # vim *.sw? diff --git a/INSTALL b/INSTALL deleted file mode 100644 index e69de29..0000000 -- 2.1.4 From nhofmeyr at sysmocom.de Fri Jul 29 16:19:15 2016 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Fri, 29 Jul 2016 18:19:15 +0200 Subject: dyn TS tweaks and fixes Message-ID: <20160729161915.GA20317@dub6> Hi all, I have some patches that probably fix some corner cases of dynamic pchan switching. However, since I'm technically already in vacation, I will only be able to properly test them in about 10 days' time. If they should become interesting before that, the changes are pushed to branches called neels/dyn_fixes in openbsc and osmo-bts. ~Neels -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From msuraev at sysmocom.de Fri Jul 29 16:59:53 2016 From: msuraev at sysmocom.de (Max) Date: Fri, 29 Jul 2016 18:59:53 +0200 Subject: signal quality measurements in osmo-trx Message-ID: <7657973e-5062-c89e-f311-429b66260de6@sysmocom.de> Hi. I'm working on http://projects.osmocom.org/issues/1616 and wonder about $subj. In case of sysmobts, osmo-pcu obtain this data directly from DSP: * RSSI (dBm) * burst timing (in quarter of bits) * link quality (in dB) * BER The first and last value seems to be easy from what I see in src/osmo-bts-trx/scheduler_trx.c What about burst timing (necessary to compute TA in the absence of PTCCH) and link quality (measure of C / I where C is carrier and I is interference power) - how can I compute those or some estimator to those values? -- Max Suraev http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From alexander.chemeris at gmail.com Sat Jul 30 00:18:05 2016 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Fri, 29 Jul 2016 20:18:05 -0400 Subject: signal quality measurements in osmo-trx In-Reply-To: <7657973e-5062-c89e-f311-429b66260de6@sysmocom.de> References: <7657973e-5062-c89e-f311-429b66260de6@sysmocom.de> Message-ID: Burst timing is also passed from osmo-trx to osmo-bts, so should be trivial to pass through. For C/I we need a comment from Thomas. Currently we don't have it on the osmo-trx interface and I'm not even sure we calculate it. Please excuse typos. Written with a touchscreen keyboard. -- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co On Jul 29, 2016 12:59, "Max" wrote: > Hi. > > I'm working on http://projects.osmocom.org/issues/1616 and wonder about > $subj. > > In case of sysmobts, osmo-pcu obtain this data directly from DSP: > * RSSI (dBm) > * burst timing (in quarter of bits) > * link quality (in dB) > * BER > > The first and last value seems to be easy from what I see in > src/osmo-bts-trx/scheduler_trx.c What about burst timing (necessary to > compute TA in the absence of PTCCH) and link quality (measure of C / I > where C is carrier and I is interference power) - how can I compute > those or some estimator to those values? > > -- > Max Suraev http://www.sysmocom.de/ > ======================================================================= > * sysmocom - systems for mobile communications GmbH > * Alt-Moabit 93 > * 10559 Berlin, Germany > * Sitz / Registered office: Berlin, HRB 134158 B > * Geschaeftsfuehrer / Managing Director: Harald Welte > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.chemeris at gmail.com Sat Jul 30 00:19:26 2016 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Fri, 29 Jul 2016 20:19:26 -0400 Subject: [PATCH] remove INSTALL file to have a clean git status In-Reply-To: <1469724033-27105-1-git-send-email-nhofmeyr@sysmocom.de> References: <1469724033-27105-1-git-send-email-nhofmeyr@sysmocom.de> Message-ID: Really good idea. That has been annoying thing. Please excuse typos. Written with a touchscreen keyboard. -- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co On Jul 28, 2016 12:40, "Neels Hofmeyr" wrote: > From: Neels Hofmeyr > > The INSTALL file is being overwritten by autoreconf, but it is committed > as empty file. As a result, the INSTALL file always shows as modified. > Instead, remove INSTALL from git and ignore it. > --- > .gitignore | 1 + > INSTALL | 0 > 2 files changed, 1 insertion(+) > delete mode 100644 INSTALL > > diff --git a/.gitignore b/.gitignore > index e15c19b..d1a0b33 100644 > --- a/.gitignore > +++ b/.gitignore > @@ -39,6 +39,7 @@ libtool > ltmain.sh > missing > stamp-h1 > +INSTALL > > # vim > *.sw? > diff --git a/INSTALL b/INSTALL > deleted file mode 100644 > index e69de29..0000000 > -- > 2.1.4 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fanx07 at gmail.com Sat Jul 30 01:16:25 2016 From: fanx07 at gmail.com (Anonim Stefan) Date: Sat, 30 Jul 2016 04:16:25 +0300 Subject: OsmoNITB + Asterisk In-Reply-To: References: <848FD39F-8825-4069-91D6-60BBB17E5200@freyther.de> Message-ID: Hi, Is there any intention / interest among current community developers to implement the DTMF for osmo sip connector?! Thanks, Stefan On Jul 27, 2016 3:33 PM, "Holger Freyther" wrote: > On 27 Jul 2016, at 20:19, Brian Butterly wrote: > > Hi, Hi! > has anyone recently put together a functional setup with OsmoNITB and > Asterisk (+LCR)? why asterisk? why LCR? The osmo-sip-connector is a "trivial" piece of software that bridges MNCC to SIP (and back) and let's everyone else do the heavy lifting. In contrast to LCR it currently lacks: * Multi-party calls (a bit harder) * DTMF (quite easy but not done) holger -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbutterly at ernw.de Sat Jul 30 06:18:16 2016 From: bbutterly at ernw.de (Brian Butterly) Date: Sat, 30 Jul 2016 08:18:16 +0200 Subject: OsmoNITB + Asterisk In-Reply-To: <848FD39F-8825-4069-91D6-60BBB17E5200@freyther.de> References: <848FD39F-8825-4069-91D6-60BBB17E5200@freyther.de> Message-ID: Hi, thanks for the feedback. Actually the sip connector is just what I need! Thank you, Brian On 27.07.2016 14:33, Holger Freyther wrote: > >> On 27 Jul 2016, at 20:19, Brian Butterly wrote: >> >> Hi, > > Hi! > >> has anyone recently put together a functional setup with OsmoNITB and >> Asterisk (+LCR)? > > why asterisk? why LCR? The osmo-sip-connector is a "trivial" piece of software that bridges MNCC to SIP (and back) and let's everyone else do the heavy lifting. In contrast to LCR it currently lacks: > > * Multi-party calls (a bit harder) > * DTMF (quite easy but not done) > > holger > -- Brian Butterly ERNW GmbH - Carl-Bosch-Stra?e 4 - 69115 Heidelberg - www.ernw.de Tel. +49 6221 480390 - Fax +49 6221 419008 - Mobil +49 151 16227171 Handelsregister Mannheim: HRB 337135 Geschaeftsfuehrer: Enno Rey -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3648 bytes Desc: S/MIME Cryptographic Signature URL: From keith at rhizomatica.org Sun Jul 31 16:35:46 2016 From: keith at rhizomatica.org (Keith) Date: Sun, 31 Jul 2016 18:35:46 +0200 Subject: OsmoNITB + Asterisk In-Reply-To: References: <848FD39F-8825-4069-91D6-60BBB17E5200@freyther.de> Message-ID: <4a5475b9-9a98-2950-89d4-e32ca1f470e3@rhizomatica.org> On 30/07/2016 03:16, Anonim Stefan wrote: > Hi, > > Is there any intention / interest among current community developers to > implement the DTMF for osmo sip connector?! Yes, for rhizomatica there is. Keith.