Cellular Network Infrastructure » Radio Access Network » OsmoTRX

Testing with all LimeSDR-USB firmware,I found the firmware/gateware version: LimeSDR-USB_HW_1.3_r3.0.img and LimeSDR-USB_HW_1.4_r2.9.rbf from LimeSuite V.17.09.0 seems the most stable and having the best performance than any other releases or latest firmware.

Check with osmo-trx-lms also fine (after switched back from latest firmware to the version I mention) but compare to the osmo-trx legacy i had, the performance is better using the osmo-trx old one.

btw,
The old osmo-trx I have is more stable with the firmware I mention when using openbsc/osmo-nitb. it showing me has more accurate clock on RF for TX and RX which make more power so automatically get more distance TX and RX.

I hope this one can be fix and maybe can look from the old osmo-trx version that I attached which perform better.

This version also I get voice working sometimes with the new splits, but seems sdr failure with not the right firmware could be the problem?

Please check the firmware I mention and hope can make the osmo-trx-lms can build and support with oldest LimeSuite version meanwhile we wait Myriad to fix the latest firmware.

Thanks.

Osmocom New Splits stacks for voice is SOLVED and stable with LimeSDR!

Voice is working actually since back then, my fault is using only C117/118/Blackberry phone for test call all the time.
Now I just test using newer phone both Caller and Callee and voice is work perfectly!

I tested both osmo-trx-lms and osmo-trx legacy.
using osmo-trx legacy 0.20 also have better performance using the firmware/gateware version I mention here : firmware/gateware version: LimeSDR-USB_HW_1.3_r3.0.img and LimeSDR-USB_HW_1.4_r2.9.rbf from LimeSuite 17.09.0.

There is trace in wireshark when using old phone both handset as C117/118, the BTS always freeze and send Measurement Indication all the time when calling is made and answered, but with newer phone, the Indication is normal.

edit: tested with Blackberry, voice also not working. only with newer phone.

There is no need to duplicate the source code here, because we have http://git.osmocom.org.
You could just specify the exact commit: aa60dda99a22f6a60d5c6f9b08d50febe49757ef
In any case, the OsmoTRX version you attached had no LMS support (too old).

fixeria wrote:

There is no need to duplicate the source code here, because we have http://git.osmocom.org.
You could just specify the exact commit: aa60dda99a22f6a60d5c6f9b08d50febe49757ef
In any case, the OsmoTRX version you attached had no LMS support (too old).

old osmo-trx just for test, I also using new osmo-trx-lms from git. both are fine with me with newer phone.

PCAP file with using 2 Motorolla C117/118 is attached. (which voice not working with some specific phone, Old Blackberry Curve series also not working for voice)

laforge wrote:

On Wed, Sep 12, 2018 at 05:35:41PM +0000, duo_kali [REDMINE] wrote:

SOLVED!

it's great that you're making progress and keeping us updated.

Voice is working actually since back then, my fault is using only C117/118 for test call.
I just test using newer phone both Caller and Callee and voice is work perfectly!

But this means that we likely still have a bug - just that this bug only shows with
very specific phones.

When you say using C117/C118, you mean you used the normal phone firmware, rihgt?

I juts want to make sure you're not using OsmocomBB, because in that case it's likely
a OsmocomBB bug.

using osmo-trx legacy 0.20 also have better performance.

can you please elaborate what "better performance" means?

• longer stable runtime of osmo-trx?
• higher ration of successful calls?
• less distortion during a call?

It is important to be very specific here, so we can draw conclusions.

Yes, both C117/118 using original firmware of C117/118.

Both osmo-trx legacy (using UHD) and latest osmo-trx (using LMS) are stable with that firmware and running without any error all the time and I tested it 20 - 24 hour.
but osmo-trx legacy seems produce more power and extending the range of signal, as an example when using osmo-trx legacy in distance 30M, phone still camping fast and make call with less distortion, but when using osmo-trx-lms, phone only can camp in 15 meter and call (which mean signal is better using osmo-trx 0.20). seems saturation and power is better performance with osmo-trx 0.20.

note: old blackberry curve is fine (I will test more).
I also just ordered GPSDO (will arrive in 2 weeks) to make sure tracing the debug and testing LimeSDR more accurate. :-)

What I can see in your capture:

(01:01:44) fixeria: duo_kali: everything looks normal until packet #23475
(01:02:35) fixeria: I see '(CC) Connect' message, so  someone has accepted the call
(01:03:24) fixeria: but then I see '(CC) Disconnect' due to 'Recovery on timer expiry'
(01:12:22) fixeria: duo_kali: most likely this is because the callee didn't receive '(CC) Connect Acknowledge' in time
(01:13:23) fixeria: check out all logs, this is definitely not an Uplink problem

So please check your logs carefully. There should be the reason why both legs were not connected.

P.S. Please upload a filtered version of your capture. There are lots of TRX related UDP packets...

Here we go again the new test with config, capture and logs.

osmo-msc : https://pastebin.com/EzT4epM3
osmo-bsc : https://pastebin.com/iV2vaj06
osmo-mgw : https://pastebin.com/pQg0dJww

ok, sorry for not really carefully for making a state that osmo-trx legacy has more stable before, found my mistake is set trx gain is low when im using osmo-trx-lms. Now I can say osmo-trx-lms is more stable then the legacy (but osmo-trx 0.20 still has more power distance coverage). :-)

so the only and main problem here with new splits is testing the network using Motorolla C117/118 are still no voice as the new test and the trace to debug is attached above. this could be a bug.

This kind of announcement in the initial post should be done in mailing list.

Regarding the issue, I can call without issues between 2 phones connected to my LimeSDR-USB, and calls work fine in osmo-trx-uhd running in osmo-gsm-tester.

I think we can close this issue unless somebody states there's something more to be discussed here.

All is fine now.
osmo-trx-lms also fine with LimeSuite latest branch 18.10.

Solved!