Project

General

Profile

Bug #2933

change of trans->bearer_cap (e.g. via MNCC) will not trigger BSSMAP ASSIGNMENT

Added by laforge 7 days ago.

Status:
New
Priority:
Low
Assignee:
sysmocom
Category:
-
Target version:
-
Start date:
02/12/2018
Due date:
% Done:

0%

Resolution:

Description

Whenever the trans->bearer_cap change (e.g.due to a CC MODIFY or MNCC MODIFY), the MSC must chck if the new bearer capabilities are different from the old bearer capabilities, and subsequently trigger a BSSMAP ASSIGNMENT towards the BSS.

Currently, the handling of bearer_cap will in only work if the related CC/MNCC message with
besrer_cap IE happens before the pint in time at which the MSC performs the BSSMAP ASSIGNMENT
procedure. Our logic still needs to change in a way that the CC/MNCC
code in gsm_04_08.c detects if trans->bearer_cap != new bearer_cap, and
in that case triggers a new follow-up BSSMAP ASSIGNMENT.


Related issues

Related to OsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCC Resolved 01/22/2018

History

#1 Updated by laforge 7 days ago

  • Related to Bug #2854: OsmoMSC never updates bearer capability from MNCC added

Also available in: Atom PDF