Actions
Bug #4722
closedMSC_Tests.TC_sgsap_unsol_ud fails every 2nd and further execution
Start date:
08/19/2020
Due date:
% Done:
100%
Resolution:
Spec Reference:
Description
It appears that TC_sgsap_unsol_ud passes only once after osmo-msc start, but not any further time of execution. This is rather unfortuantely if working manually debugging tests in osmo-msc.
Files
Updated by laforge over 3 years ago
Ok, so the difference is mainly:
- in the successful case, the SGsAP-RELEASE-REQUEST contains cause "IMSI unknown"
- in the failing case, the SGsAP-RELEASE-REQUEST contains cause "IMSI detached for EPS and non-EPS services"
So what we're missing here is some kind of state clean-up, as after the first attempt, the VLR contains a record:
OsmoMSC> show subscriber cache
Subscriber #00:
MSISDN: 491230011822
LAC / cell ID: 23 / 42
RAN type: GERAN-A
IMSI: 262420000011822
TMSI: 830A872C
Flags:
IMSI detached: false
Conf. by radio contact: true
Subscr. data conf. by HLR: true
Location conf. in HLR: true
Subscriber dormant: false
Received cancel location: false
MS not reachable: false
LA allowed: true
Expires: in 56 min 9 sec
Paging: not paging for 0 requests
SGs-state: SGs-NULL
SGs-MME: (none)
Use count total: 1
Use count: 1 (attached)
Updated by laforge over 3 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 80
Resolved in Change-Id I6c2f1a5d5b5316ffe462335f8461c31564ce4274 (https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/19716)
Updated by laforge over 3 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
patch merged
Actions
