Hi Harald,

I see. What was communicated to me was that NITB channel configuration TCH/F_TCH/H_PDCH is not supported with nanoBTS.

I will have in mind that nanoBTS does not support HR (v1) codec.

Thank you.

Regards, Ivaylo

On 03.02.2017 20:14, Harald Welte wrote:

Hi Ivaylo,

thanks for your test report.

On Fri, Feb 03, 2017 at 05:00:03PM +0100, Ivaylo Kostov wrote:

...

During a weekly test of nanoBTS model:165G, an issue has been discovered. It is reported in redmine: https://osmocom.org/issues/1933

Short description: It was found that the initiated voice call drops immediately after B subscriber accepts the call, when nanoBTS (model 165G) and NITB is configured with dynamic channels: 3 TCH/H and 3 PDCH. Default voice codec tch-h hr has been selected.

Why is there again an attempt to use HR (v1) with the nanoBTS? It is a codec that this BTS hardware is known to never have supported. I am quite sure this has been discussed before. Was there some miscommunication / mis-definition of the test cases?

Regards, Harald

Hi Neels,

Yes. I do have TCH/F_PDCH dynamic timeslots in the test procedure.

regards, Ivaylo

On 08.02.2017 16:26, Neels Hofmeyr wrote:

(found this mail stuck in my outbox, sending late)

On Mon, Feb 06, 2017 at 10:09:23AM +0100, Ivaylo Kostov wrote:

...

Hi Harald,

I see. What was communicated to me was that NITB channel configuration TCH/F_TCH/H_PDCH is not supported with nanoBTS.

I will have in mind that nanoBTS does not support HR (v1) codec.

Yes, we discussed TCH/F_TCH/H_PDCH for the nanoBTS. I remember to be surprised because from some discussion it appeared that the nanoBTS supports HR, and I was expecting TCH/F only.

While talking about codecs, the ip.access nanoBTS *should* in fact support the TCH/F_PDCH dynamic timeslots. Ivaylo, could you check whether that is part of your testing procedure and add it if not?

~N

--

------------------------------ - Ivaylo Kostov ikostov@sysmocom.de mailto:ikostov@sysmocom.de 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 ------------------------------

On Wed, Feb 08, 2017 at 04:45:57PM +0100, Harald Welte wrote:

libbsc should be extended to handle those restrictions, i.e. reject a configuration containing HR codec or a osmocom-style dynamic channel on a bts model 'nanobts'.

i.e. checks on the VTY level.

Seems like we want an issue for that: https://osmocom.org/issues/1946

~N

Hi Alexander,

On 03.02.2017 21:42, Alexander Chemeris wrote:

Hi Ivaylo,

Please could you share the goal and scope of these tests? And is there a publicly available definition of the test cases?

The main goal of these weekly tests is to verify whether our actual software works as intended. The basic (traffic) cases are given below.

- Location Update - Voice call between two subscribers using supported voice codecs - Mobile originating / Mobile terminating SMS - Mobile terminating SMS during ongoing voice call - GPRS test: displaying web site and pinging MS from Core network - USSD request: *#100#

Timeslots configurations are:

3 TCH/F, 3 PDCH 3 TCH/H, 3 PDCH 6 TCH/F_PDCH (ip.access style dynamic timeslots) 6 TCH/F_TCH/H_PDCH (Osmocom style dynamic timeslots)

I have sent the first week test report to OpenBSC mailing list. In case issue is found, then ticket will be open in osmocom.org redmine. We are in a process of tunning and finalizing of our weekly tests and related reports.

Regards, Ivaylo

Please excuse typos. Written with a touchscreen keyboard.

-- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co

On Feb 3, 2017 5:00 PM, "Ivaylo Kostov" <ikostov@sysmocom.de mailto:ikostov@sysmocom.de> wrote:

Hi,

Please find BTS test report, week5 2017.

BTSes which has been tested with OsmoNITB are:

- sysmoBTS1002
- octasic BTS3500
- ettus B200
- nanoBTS model:165G


sysmoBTS1002 has been tested with the following 4 channel
configurations:

6 TCH/F_TCH/H_PDCH (Osmocom style dynamic timeslots)
3 TCH/F, 3 PDCH
3 TCH/H, 3 PDCH
6 TCH/F_PDCH (ip.access style dynamic timeslots)

All test cases passed.

----------------------------------------------------
octasic BTS3500 has been tested with the next 2 channel configurations:

3 TCH/F, 3 PDCH
3 TCH/H, 3 PDCH

All test cases passed.

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

ettus B200 has been tested with below channel configurations:

6 TCH/F_TCH/H_PDCH (Osmocom style dynamic timeslots)
3 TCH/F, 3 PDCH
3 TCH/H, 3 PDCH
6 TCH/F_PDCH (ip.access style dynamic timeslots)

All test cases passed.

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

During a weekly test of nanoBTS model:165G, an issue has been
discovered. It is reported in redmine:
https://osmocom.org/issues/1933 <https://osmocom.org/issues/1933>

Short description: It was found that the initiated voice call drops
immediately after B subscriber accepts the call, when nanoBTS (model
165G) and NITB is configured with dynamic channels: 3 TCH/H and 3
PDCH. Default voice codec tch-h hr has been selected.

Remaining test cases passed.

regards,
Ivaylo

--
------------------------------
- Ivaylo Kostov <ikostov@sysmocom.de <mailto:ikostov@sysmocom.de>>
<mailto:ikostov@sysmocom.de <mailto:ikostov@sysmocom.de>>
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
------------------------------