Problem with SA in the mw version 0.10.0

[alessandro-lucco]

Describe the bug
with the latest middleware update (v0.10.0) it seems that the service announcement is not interpreted correctly.

To Reproduce
Steps to reproduce the behavior:

1. The signal is generated using the R&S chain (BSCC + SDE900 + TLU9) with hls video streams
2. The modem process starts successfully and has no errors
3. The middleware process have problems with the MD5 check (we attach below the output with the log level set to 1)

Expected behavior
With version 0.9 the SA is correctly recognized and the two flute streams are displayed (SA and HLS video)

Desktop and laptop:

• OS: Ubuntu 20.04
  (Same behavior was noticed with a PC running Ubuntu 22)

Log output

`sudo mw -l1
mw[19804]: 5g-mag-rt mw v0.10.0 starting up
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: Starting FLUTE receiver on 238.1.1.95:40085 for TSI 0
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: Creating File from FileEntry
mw[19804]: Allocating buffer
mw[19804]: received TOI 0 SBN 0 ID 0
mw[19804]: File with TOI 0 completed
mw[19804]: Received new FDT with instance ID 65:
<FDT-Instance Expires="3878639203"
xmlns="urn:IETF:metadata:2005:FLUTE:FDT"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:mbms2007="urn:3GPP:metadata:2007:MBMS:FLUTE:FDT"

mw[19804]: Destroying File
mw[19804]: Freeing buffer
mw[19804]: Starting reception for file with TOI 65: sa_multipart (multipart/related)
mw[19804]: Creating File from FileEntry
mw[19804]: Allocating buffer
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: received TOI 65 SBN 0 ID 0
mw[19804]: MD5 mismatch for TOI 65, discarding
mw[19804]: received TOI 65 SBN 0 ID 1
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: received TOI 65 SBN 0 ID 2
mw[19804]: received TOI 65 SBN 0 ID 3
mw[19804]: received TOI 65 SBN 0 ID 4
mw[19804]: received TOI 65 SBN 0 ID 5
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: received TOI 65 SBN 0 ID 6
mw[19804]: received TOI 65 SBN 0 ID 7
mw[19804]: received TOI 65 SBN 0 ID 8
mw[19804]: received TOI 65 SBN 0 ID 9
mw[19804]: request for /mw-api/files
mw[19804]: request for /mw-api/services
mw[19804]: received TOI 65 SBN 0 ID 10
mw[19804]: received TOI 65 SBN 0 ID 11
mw[19804]: received TOI 65 SBN 0 ID 12
mw[19804]: received TOI 65 SBN 0 ID 13

`

[dsilhavy]

@alessandro-lucco Can you please check again with the released version: https://github.com/5G-MAG/rt-mbms-mw/releases/tag/v0.10.0

Different configuration options are documented here: https://github.com/5G-MAG/Documentation-and-Architecture/wiki/Configuration-Quick-Start-Guide

[alessandro-lucco]

Hi Daniel, thank you, the problem occurs only with version 0.10, with 0.9 it works correctly.
I tried following your instructions by reinstalling the mw and updating the ngnix configuration, but the result is the same. I also tried changing all three possible service announcement formats in the configuration file
I always get the above log, it seems that once I get the SA related file it gets discarded due to the md5 check.
Receiving the same radio source with a similar PC with mw version 0.9 installed, it works correctly.

[dsilhavy]

@alessandro-lucco It looks like this is related to the development branch of the FLUTE library. We did not specify the main branch as the target in our .gitmodules of the MW

[submodule "lib/libflute"]
	path = lib/libflute
	url = https://github.com/5G-MAG/rt-libflute.git

Can you please navigate to lib/libflute and checkout the main branch: git checkout -b main origin/main. Then rebuild and confirm that the MD5 error is gone.

[alessandro-lucco]

Thanks @dsilhavy,
following your advice I managed to no longer get the MD5 error. Unfortunately the mw application always returns "segmentation fault" I attach the log.
I tried on two different PCs both running Ubuntu 20 and Ubuntu 22, I get the same error.
log_mw_seg-fault.txt

[dsilhavy]

@alessandro-lucco Did you try with all recordings or a specific one? I just checked with "MCS12_2MBIT_ReS_Transmitter.raw" and did not run into a segmentation fault.

[alessandro-lucco]

Hi Daniel, I was finally able to test several cases. Definitely the first problem was related to libflute. However, with the right branch of libflute, I tried with both a pc running Ubuntu 20 and Ubuntu 22 and the mw always returns the same error after trying to open the "BSCC Service".

mw[216306]: File with TOI 23 completed
mw[216306]: sa_multipart (TOI 23) has been received
mw[216306]: uri: http://TMGI-0x1009f165.sdp
mw[216306]: uri: http://10.54.131.210/outgoing/adaptive/hls/MISE1/mise1.m3u8
mw[216306]: uri: http://TMGI-0x1009f165.m3u8
mw[216306]: uri: http://TMGI-0x1009f165schedule.xml
mw[216306]: uri: http://usdBundle-1.xml
mw[216306]: Service name added: BSCC Service1 (EN-GB)
mw[216306]: Service name added: BSCC Dienst1 (DE-DE)
Segmentation fault (core dumped)

With the first file (#37 (comment)) of those registered it actually doesn't return the segmentation fault because it is probably too short and doesn't completely receive the first sa. I upload a longer registration to the portal.
Let me know if there is a way to gather more information about the error.
Thank you

[dsilhavy]

We are checking this again once the changes from @kuehnhammer who is working on version 1.0.0 and is implementing support for the latest SA format are merged.