Actions
Bug #2759
closedOsmoBSC ASSIGNMENT FAIL doesn't contain useful cause
Start date:
12/14/2017
Due date:
% Done:
100%
Spec Reference:
Description
bssmap_handle_assignm_req() will currently only return one cause value no matter what the error: GSM0808_CAUSE_NO_RADIO_RESOURCE_AVAILABLE
This is incorrect, as- in case of missing mandatory information elements we should rather use GSM0808_CAUSE_INFORMATION_ELEMENT_OR_FIELD_MISSING
- in case of decoding errors something like GSM0808_CAUSE_INVALID_MESSAGE_CONTENTS
- in case of unsupported (e.g. mode) something like GSM0808_CAUSE_REQ_CODEC_TYPE_OR_CONFIG_UNAVAIL
We also need to analyze how the functions that are called by bssmap_handle_assignm_req() can fail and make them return according to the exact nature of their failure.
Updated by laforge about 6 years ago
- Status changed from New to In Progress
- Assignee changed from dexter to laforge
- % Done changed from 0 to 70
I have a patch as Change-Id I86adcae2950cbea6dcac4551cfde1054cb0abad1 in the laforge/fsm branch
Updated by laforge about 6 years ago
- Status changed from In Progress to Stalled
waiting for dexter to complete the work on the FSM branch
Updated by laforge almost 6 years ago
- Status changed from Stalled to Resolved
- % Done changed from 70 to 100
Change-Id: I86adcae2950cbea6dcac4551cfde1054cb0abad1 has been merged some time ago
Actions