Project

General

Profile

Bug #4968

Multiple TTCN3 tests only expect one SGSN

Added by daniel about 1 month ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
01/21/2021
Due date:
% Done:

0%

Spec Reference:
Tags:

Description

There are various tests in TTCN3 that are not yet aware of SGSN-pooling. As such they usually just test that a message is forwarded to the first SGSN where we would expect it to be broadcast.

f_reset_ptp_bvc_from_sgsn() is a bit special and I'm not sure what to do here. Right now we expect the reset from one SGSN to be forwarded to the BSS. In that case we also need to reset the connection on the other SGSNs. Or we block the BVC to the other SGSNs and reset those connection as soon as the RESET-ACK from the BSS arrives at the gbproxy.

Couldn't we also locally answer the BVC-RESET?


Checklist

  • f_reset_ptp_bvc_from_sgsn
  • f_block_ptp_bvc_from_pcu
  • f_unblock_ptp_bvc_from_pcu

Related issues

Related to osmo-gbproxy - Bug #4964: TC_bvc_reset_ptp_from_bss and TC_bvc_reset_sig_from_bss fail sporadicallyResolved01/21/2021

History

#1 Updated by daniel about 1 month ago

  • Related to Bug #4964: TC_bvc_reset_ptp_from_bss and TC_bvc_reset_sig_from_bss fail sporadically added

#2 Updated by daniel about 1 month ago

  • Tags set to ttcn3
  • Subject changed from Multiple TTCN3 tests ony expect one SGSN to Multiple TTCN3 tests only expect one SGSN

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)