commit 18b5dc1dabc4f7f5ad99a84c46b767388783a748
author Pau Espin Pedrol <pespin@sysmocom.de> Tue Jun 25 16:46:38 2024 +0200
committer Pau Espin Pedrol <pespin@sysmocom.de> Tue Jun 25 18:47:48 2024 +0200
tree af93c7110a5c82c3096dcb52c205fcf0d9ffaa60
parent cc22bee73dcd3ad4334943c88cdc561c5d394b67

asterisk: Introduce test TC_ims_reregistration

So far Asterisk seems to be doing "initial registration" during
re-registration, instead of using the existing security context.
This is "OK" afaiu, but not the best pick (TS 24.229 5.1.1.4.1).

Related: SYS#6983
Change-Id: Icaeec6e2be3469b9e49d4361ca2b039ab44683c0

asterisk/expected-results.xml

diff --git a/asterisk/expected-results.xml b/asterisk/expected-results.xml
index 31a03e5..65a495b 100644
--- a/asterisk/expected-results.xml
+++ b/asterisk/expected-results.xml
@@ -12,6 +12,7 @@
   <testcase classname='Asterisk_Tests' name='TC_ims_registration_timeout_resync_401Unauthorized' time='MASKED'/>
   <testcase classname='Asterisk_Tests' name='TC_ims_registration_timeout_protected_100Trying' time='MASKED'/>
   <testcase classname='Asterisk_Tests' name='TC_ims_registration_timeout_protected_200OK' time='MASKED'/>
+  <testcase classname='Asterisk_Tests' name='TC_ims_reregistration' time='MASKED'/>
   <testcase classname='Asterisk_Tests' name='TC_ims_call_mo' time='MASKED'/>
   <testcase classname='Asterisk_Tests' name='TC_ims_call_mo_noprecondition' time='MASKED'/>
   <testcase classname='Asterisk_Tests' name='TC_ims_call_mt' time='MASKED'/>