MSC: fix SM-RP-OA (SMSC Address) expectations for MT SMS

Since [1] we started to match the SMSC Address in f_mt_sms_expect().
That change caused test case failures because OsmoMSC hard-codes
a different SMSC Address. Let's fix this.

[1] Ib467eeca6439bc6cce72293fbb5bb48f6d233db9

Change-Id: I3bdb6a74c8b02e4bf8dc88634e2380c924242b4b
This commit is contained in:
Vadim Yanitskiy 2020-01-05 14:04:53 +01:00
parent 6f319f9794
commit afb15a8424
1 changed files with 3 additions and 2 deletions

View File

@ -1660,8 +1660,9 @@ template (value) SmsParameters t_SmsPars(hexstring tp_daddr := '12345'H) := {
rp := {
msg_ref := '42'O,
/* We don't really need to have both SM-RP-DA/OA here, because only one IE
* is included in MO/MT SMS, and in the most cases it's the SMSC address. */
smsc_addr := t_RP_Addr('76722337'H)
* is included in MO/MT SMS, and in the most cases it's the SMSC address.
* NOTE: this address is currently hard-coded by OsmoMSC. */
smsc_addr := t_RP_Addr('447785016005'H)
},
tid := 0,
dlci := '03'O,