Project

General

Profile

Bug #2928

OsmoMSC doesn't do BSSMAP ASSIGNMENT if no MNCC_RTP_CREATE is received

Added by laforge 9 days ago. Updated 8 days ago.

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

0%

Resolution:

Description

When operating OsmoMSC with external MNCC handler, it seems that it "forgets" to
  • perform BSSMAP ASSIGNMENT procedure
  • perform CRCX/MDCX on MGW endpoint for RAN side
    if the eternal MNCC handler is not sending the MNCC_RTP_CREATE.

This is wrong and indicates the state machines have some trouble.

The voice call should be established towards MS/RAN/MGW as usual, no matter if and when an external MNCC handler decides to actually connect to the MSC-located MGW. The MNCC_RTP_{CREATE,MODIFY} should only be translated to CRCX/MDCX of the mncc-side connection to OsmoMGW, and not anything on the RAN side.

History

#1 Updated by laforge 9 days ago

TC_lu_and_mt_call from https://gerrit.osmocom.org/6373 can be easily modified to suppress generating the MNCC_RTP_CREATE message for reproducing this

#2 Updated by laforge 8 days ago

  • Subject changed from OsmoMSC doesn't do BSSMAP ASSIGNEMNT if no MNCC_RTP_CREATE is received to OsmoMSC doesn't do BSSMAP ASSIGNMENT if no MNCC_RTP_CREATE is received

Also available in: Atom PDF