Actions
Bug #3266
closedCM Service reject with wrong cause-code
Start date:
05/15/2018
Due date:
% Done:
100%
Resolution:
Spec Reference:
Description
When the msc reboots all MS get implicitly detached. On the next CM SERVICE REQUEST the MS will get a CM SERVICE REJECT and by the cause code it knows that it has to perform a LOCATION UPDATE in order to get detached again. Unfortunately the cause code that the MSC returns with the CM SERVICE REJECT (GSM48_REJECT_MS_IDENTITY_NOT_DERVIVABLE = 9) is incorrect because this is a cause code from the GMM domain and is interpreted GSM48_REJECT_SRV_OPT_TMP_OUT_OF_ORDER by the MS, which also will not do any location update then.
Updated by dexter almost 6 years ago
See fix: https://gerrit.osmocom.org/#/c/osmo-msc/+/9169 vlr_access_req_fsm: use correct cause codes
Updated by dexter almost 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 80
Updated by dexter almost 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
Actions