tree 853a0dba0095729e835e99613cd281ede4c32415
parent 322c79367b5d38e43c15c3238b18b5f24b9191ee
author Vadim Yanitskiy <axilirator@gmail.com> 1577551534 +0100
committer fixeria <axilirator@gmail.com> 1578138615 +0000

MSC_Tests.ttcn: introduce TC_mm_id_resp_no_identity

While investigating OS#4340, it was discovered that a malformed
MM Identity Request with MI Type '111'B crashes OsmoMSC.

Unfortunately, I could not find a way to encode such an invalid
message in TITAN (because value '111'B is reserved), so I
figured out that '000'B also crashes OsmoMSC.

MM Identity Request is triggered by initiating an Update Location
Request with reserved TMSI value 'FFFFFFFF'O (unknown to the MSC).

Change-Id: I62f23355eb91df2edf9dc837c928cb86b530b743
Related: OS#4340