Cellular Network Infrastructure » Core Network (CN) » OsmoMSC

jolly wrote in #note-4:

Patches prepared, but not yet pushed to Gerrit.
I have no phone to test it.

This is sad, adn we should make sure you have some devices that speaks CSD. Will look into that, but that will take some time.

Unrelated to the above, we generally want to have automatic test coverage, so a TTCN3 MSC test for MO and MT csd should verify the LLC is passed through transparently on MO and MT.

laforge wrote in #note-5:

This is sad, adn we should make sure you have some devices that speaks CSD. Will look into that, but that will take some time.

AFAIU, the problem here is that jolly has no phone that would include the Low layer compatibility I IE in MO SETUP.
I do have a few (Calypso based SE K200/K220 definitely does include it), so I could do some testing if I had patches.

Unrelated to the above, we generally want to have automatic test coverage, so a TTCN3 MSC test for MO and MT csd should verify the LLC is passed through transparently on MO and MT.

We do have TTCN-3 test cases verifying MO and MT data calls in ttcn3-msc-test:

• TC_lu_and_mo_csd,
• TC_lu_and_mt_csd.

We can extend those to verify forwarding of the LLC/HLC IEs, but I would go for adding separate testcases for this ticket (re-using the existing code).

Also, some time ago I worked on adding TTCN-3 testcases for osmo-msc, testing MS-to-MS voice and data call with the built-in MNCC.
Currently we only test either the MO or the MT signalling with external MNCC, but not with built-in MNCC.
I will find that WIP code and push it to a branch.

On Tue, Dec 19, 2023 at 04:31:26PM +0000, fixeria wrote:

Currently we only test either the MO or the MT signalling with external MNCC, but not with built-in MNCC.
I will find that WIP code and push it to a branch.

yes, that would make sense to have tests covering built-in mncc.