Project

General

Profile

Bug #1663

don't connect channels of incompatible voice codec

Added by laforge almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
03/17/2016
Due date:
% Done:

100%

Spec Reference:

Description

It appears that at least with current osmo-nitb and osmo-bts-octphy it is possible that we end up connecting a TCH/F (FR) call to a TCH/H (HR) call using the internal MNCC handler. We should just drop the call instead.


Related issues

Related to OpenBSC - Bug #20: phone calls between AMR-capable handset and EFR-only handset Closed
Related to OsmoMSC - Feature #1778: avoid mismatching TCH/F vs TCH/H pchan types Stalled 07/21/2016
Related to OsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCC New 01/22/2018

History

#1 Updated by laforge almost 2 years ago

  • Assignee set to msuraev

#2 Updated by msuraev almost 2 years ago

  • Status changed from New to In Progress

Issue also reproduced with LC15 hw.

#3 Updated by laforge almost 2 years ago

  • Priority changed from Normal to High

#4 Updated by msuraev almost 2 years ago

Fix sent to ML for review.

#5 Updated by msuraev almost 2 years ago

Should we also check that channel mode (audio codec) is the same and drop call if not?

#6 Updated by msuraev almost 2 years ago

  • Status changed from In Progress to Feedback

#8 Updated by laforge over 1 year ago

  • Status changed from Feedback to Closed
  • % Done changed from 0 to 100

#9 Updated by laforge over 1 year ago

  • Related to Bug #20: phone calls between AMR-capable handset and EFR-only handset added

#10 Updated by msuraev over 1 year ago

  • Related to Feature #1778: avoid mismatching TCH/F vs TCH/H pchan types added

#11 Updated by laforge 1 day ago

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

Also available in: Atom PDF