Project

General

Profile

Bug #3529

osmo-bsc does not send the correct S0-S15 bits for AMR in the Assignment Compl Message.

Added by dexter 17 days ago. Updated 2 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
09/06/2018
Due date:
% Done:

70%

Estimated time:
Spec Reference:

Description

AMR supports a variety of fine rates and settings. Those are set via S0-S15 in the speech codec list that is sent by the MSC to the BSC. the BSC may then choose a configuration and return it back via the ASSIGNMENT COMPLETE message.

In the documented case the S0-S15 were set to 0x0200, but we return 0xFF57. This looks problematic and when checking the source code one can see in assignment_fsm.c:send_assignment_complete() that the speech codec element is computed using gsm0808_speech_codec_from_chan_type(). This function only has perm_spc as input which is an integer and basically only sets the codec type and S0-S15 are populated with standard values. This is presumably not enough, we should take the S0-S15 from the speech codec list in the ASSIGNMENT REQUEST and work with it.

assignment_complete.png View assignment_complete.png 32.5 KB dexter, 09/06/2018 02:56 PM
assignment_request.png View assignment_request.png 57.4 KB dexter, 09/06/2018 02:56 PM
02_ASSIGNMENT_REQUEST.png View 02_ASSIGNMENT_REQUEST.png 36 KB dexter, 09/21/2018 04:01 PM
03_ASSIGNMENT_COMPLETE.png View 03_ASSIGNMENT_COMPLETE.png 32.4 KB dexter, 09/21/2018 04:01 PM
01_COMPLETE_LAYER_3_INFO.png View 01_COMPLETE_LAYER_3_INFO.png 33.8 KB dexter, 09/21/2018 04:01 PM
3327
3328
3366
3367
3368

History

#1 Updated by dexter 2 days ago

3366
3367
3368

The S0-S15 for AMR are no longer hardcodec in osmo-bsc. We now take the configuration bits from the ASSIGNMENT REQUEST and do an intersection between our BSS capabilities. This intersected bits are then returned with the ASSIGNMENT COMPLETE message in speech codec (choosen).

Attached one finds the wireshark screenshots of the speech codec data as they look now. One can see, we first advertise a variety of options, then the MSC limits the options and we agree. However, in this particular example the 0x0200 looks suspicious. I checked the bit ordering against the spec multiple times and I am confident that our endieness is correct, but 0x0200 does not make much sense to me. We probably need to discuss this next week.

See also: https://gerrit.osmocom.org/#/c/osmo-bsc/+/11060 codec_pref: handle S0-S15 in ASSIGNMENT REQUEST

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)