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/gerrit-log@lists.osmocom.org/.
pespin gerrit-no-reply at lists.osmocom.orgpespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-tester/+/20825 ) Change subject: sysmocom: emergency_preemptive_call.py: Avoid test failure if 2nd call not fully established ...................................................................... Patch Set 1: Code-Review+2 > Patch Set 1: Code-Review+1 > > I think the proper solution here would be to not do a MO-to-MT emergency call, but to "simply" verify that it arrives on MNCC (e.g. using python-mncc). The ideal solution here would be to test end-to-end with a sip client (we already test with a fake external MNCC in TTCN3), but to do so or simply adding MNCC support to osmo-gsm-tester I have to spend time integrating all those. I'll merge this one to have this test passing and later on we can add another test using external MNCC, this way we test both scenarios (MT inside GSM network and MT outside it). -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-tester/+/20825 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-tester Gerrit-Branch: master Gerrit-Change-Id: I3697227cac56a1327f9ea08c5c2f52568e8d2a8a Gerrit-Change-Number: 20825 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Reviewer: pespin <pespin at sysmocom.de> Gerrit-Comment-Date: Thu, 22 Oct 2020 09:14:51 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20201022/63433320/attachment.htm>