Feature #2194
closedosmo-gsm-tester: add voice call test
Added by neels about 7 years ago. Updated over 5 years ago.
100%
Description
Add a test case that performs a voice call (probably in a new test suite called 'voice').
Add various scenario configurations picking phys_chan_config timeslot types (TCH/H, TCH/F, TCH/F_TCH/H_PDCH, TCH/F_PDCH) as well as various voice codecs.
See [[cellular infrastructure:Weekly BTS Tests]] for inspiration.
Concentrate on sysmoBTS so far, and osmo-bts-trx if it already works.
Ignore oct and nanoBTS.
Related issues
Updated by neels about 7 years ago
- Related to Feature #1871: test dynamic timeslots added
Updated by neels about 7 years ago
- Priority changed from Normal to High
To clarify, this is only about voice call signalling, not about analysis of the actual voice stream or audio sent/received on either side. The test should merely place a call, somehow query that a voice call was launched (maybe implement new CTRL interface queries?) and then hang up.
Updated by neels about 7 years ago
- Related to deleted (Feature #1871: test dynamic timeslots)
Updated by neels about 7 years ago
- Is duplicate of Feature #1871: test dynamic timeslots added
Updated by neels about 7 years ago
- Status changed from New to Closed
replaced by more concise issue #2194
Updated by neels about 7 years ago
- Is duplicate of deleted (Feature #1871: test dynamic timeslots)
Updated by neels about 7 years ago
- Has duplicate Feature #1871: test dynamic timeslots added
Updated by neels almost 7 years ago
- Blocked by Bug #2240: ofono: voice calls are not implemented for any modem added
Updated by pespin almost 7 years ago
- Related to Feature #2197: osmo-gsm-tester: use MNCC interface added
Updated by pespin over 6 years ago
Basic call is there, still missing to test different time slot and codec configurations.
Updated by pespin over 5 years ago
We do have voice tests, but not all of the ones specified in https://osmocom.org/projects/cellular-infrastructure/wiki/Weekly_BTS_Tests. We do test TCH/F, TCH/H, dynamic timeslots, etc. but we don't test different codecs.
So we can say that the important part is done but still some stuff is missing. But given that we still don't support sending data through the modems, we can close the ticket and care about codecs once we have data to send?
Updated by laforge over 5 years ago
On Mon, Aug 20, 2018 at 10:49:32AM +0000, pespin [REDMINE] wrote:
So we can say that the important part is done but still some stuff is missing. But given that we still don't support sending data through the modems, we can close the ticket and care about codecs once we have data to send?
I think whether or not you're transferring user plane ("data is very
ambiguous here), it's still very useful to check if at least the
signaling plane for the different codecs work. You will exercise
different code paths in BTS/BSC/MSC, as well as all the related
signalling messages.
Updated by pespin over 5 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 90
I submitted several commits which enable testing different timeslot + codec setups during a call:
https://gerrit.osmocom.org/#/c/osmo-gsm-tester/+/10624 suite: Fix generation of config() dictionary
https://gerrit.osmocom.org/#/c/osmo-gsm-tester/+/10621 osmo-bsc: Parametrize codec-list VTY cfg
https://gerrit.osmocom.org/#/c/osmo-gsm-tester/+/10625 default-suites: Add suites testing different codecs
https://gerrit.osmocom.org/#/c/osmo-gsm-tester/+/10626 default-suites: Remove octobts tests
Updated by pespin over 5 years ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100
Merged, closing.
