Project

General

Profile

Bug #2782

OsmoBSC sends BSSMAP ASSIGNMENT COMPLETE before RSL MODE MODIFY succeeds

Added by laforge 10 months ago. Updated 8 months ago.

Status:
New
Priority:
Low
Assignee:
Category:
A interface
Target version:
-
Start date:
12/23/2017
Due date:
% Done:

0%

Spec Reference:

Description

OsmoBSC sends the BSSMAP ASSIGNMENT COMPLETE when it receives the RR CHANNEL MODE MODIFY ACK from the MS, but before it has successfully modified the mode on the BTS side.

See attached protocol trace snippet.

ass_compl_too_early.pcapng ass_compl_too_early.pcapng 1.08 KB laforge, 12/23/2017 01:01 AM

History

#1 Updated by laforge 9 months ago

  • Assignee set to dexter

#2 Updated by dexter 8 months ago

In Theory this can still happen with the GSCON FSM. I suspect the reason for this is that we make the FSM depended on the S_ABISIP_MDCX_ACK in osmo_bsc_audio.c and that S_ABISIP_MDCX_ACK arrives earlyer than the MODE MODIFY REQuest.

When S_ABISIP_MDCX_ACK arrives an GSCON_EV_RR_ASS_COMPL is generated in osmo_bsc_audio.c. The FSM is then expected to be in ST_WAIT_ASS_CMPL.

There is also a second location where GSCON_EV_RR_ASS_COMPL can be sent. This is when GSM48_MT_RR_CHAN_MODE_MODIF_ACK arrives in bsc_api.c and the bsc_assign_compl() in osmo_bsc_api.c runs. This looks completely correct. In order to resolve this, the RR assignement and the IPACC RTP negotiation should be untangled and the sending of GSCON_EV_RR_ASS_COMPL should be removed. This should solve the problem cleanly.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)