MSC/SMPP: introduce TC_smpp_mo_sms_rp_error for OS#4351
This test case reproduces the problem described in OS#4351:
1. MS/UE submits a MO SMS which it getting touted to an ESME;
2. MSC prematurely responds with RP-ACK to the MS/UE;
3. ESME responds with DELIVER-SM error;
4. SMS transaction is already terminated (by RP-ACK).
Expected behaviour:
1. MS/UE submits a MO SMS which it getting touted to an ESME;
2. ESME responds with DELIVER-SM error;
3. MSC terminates the SMS transaction with RP-ERROR.
Change-Id: I33c6ea0ffdf8b8a45f587d690bdceb38fc42c898
Related: OS#4351
diff --git a/msc/expected-results.xml b/msc/expected-results.xml
index e2cca45..68e2958 100644
--- a/msc/expected-results.xml
+++ b/msc/expected-results.xml
@@ -55,6 +55,7 @@
<testcase classname='MSC_Tests' name='TC_lu_and_mt_sms' time='MASKED'/>
<testcase classname='MSC_Tests' name='TC_lu_and_mt_sms_paging_and_nothing' time='MASKED'/>
<testcase classname='MSC_Tests' name='TC_smpp_mo_sms' time='MASKED'/>
+ <testcase classname='MSC_Tests' name='TC_smpp_mo_sms_rp_error' time='MASKED'/>
<testcase classname='MSC_Tests' name='TC_smpp_mt_sms' time='MASKED'/>
<testcase classname='MSC_Tests' name='TC_gsup_mo_sms' time='MASKED'/>
<testcase classname='MSC_Tests' name='TC_gsup_mo_smma' time='MASKED'/>