Bug #2725
closed
OsmoBSC doesn't release lchan if MSC doesn't answer to CR
Added by laforge over 6 years ago.
Updated about 6 years ago.
Description
If the BSC is sending a CR to the MSC to establish a SCCP connection, it seems that even after 30 seconds it is not releasing the related radio channel.
I'm creating a TTCN-3 test case TC_chan_act_ack_est_ind_noreply in BSC_Tests.ttcn for this.
- Related to Bug #2726: OsmoBSC doesn't release lchan if MSC refuses connection (CR -> CREF) added
- Status changed from New to In Progress
- Assignee changed from dexter to laforge
- % Done changed from 0 to 70
I have a patch for this: Change-Id Ie11d7d06353ba1b1e2fab6763dd7b032ce8a5d2c in the laforge/fsm branch. It introduces a new non-3GPP timer 993210 at 20 seconds.
- Priority changed from Normal to High
- Status changed from In Progress to Stalled
waiting for dexter to complete the work on the FSM branch
- Status changed from Stalled to Resolved
- % Done changed from 70 to 100
patch has been merged, testcase passes.
Also available in: Atom
PDF
