TTCN-3 tests for MME

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-net-gprs@lists.osmocom.org/.

Harald Welte laforge at osmocom.org
Mon Oct 25 15:46:40 UTC 2021


On Fri, Oct 22, 2021 at 02:12:03PM +0200, Mirko Kovacevic wrote:
> Protocol-IEs, MMEname and ENBname, cant be decoded\encoded properly,
> definitely.

one would have to check if the encoding problem already exists in the BER version
(as generated by TITAN natively) or if it happens at the BER <-> PER transcoding
inside the [unfortunately] non-public libfftranscode, generated by ffasn1c.

I you can build a small, self contained test case that shows a problem in 
BER <-> PER transcoding using the libfftranscode API directly (removing all of TITAN, etc.)
then we may have a chance of either solving it at sysmocom or by asking
the ffasn1c author to have a look

> Amazing progress with S1AP emulation, congrats.

thanks.  Please keep us posted about any progress.  We're happy to merge any
related patches  you may have for adding more test cases, fixing bugs, etc.

I never found the time for it, but the general idea always was to automatically
run this testsuite in jenkins.osmocom.org against the open5gs-mme, like we do
for or own osmocom software.

Regards,
	Harald
-- 
- Harald Welte <laforge at osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the osmocom-net-gprs mailing list