Project

General

Profile

Actions

Feature #1778

closed

avoid mismatching TCH/F vs TCH/H pchan types

Added by neels over 7 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
A interface (general)
Target version:
-
Start date:
07/21/2016
Due date:
% Done:

100%

Resolution:
Spec Reference:

Description

In an osmo-nitb configuration with both TCH/F and TCH/H available,
a voice call may end up with TCH/H to one phone and TCH/F to the other.
The result is:

DCC <0001> gsm_04_08.c:1649 Cannot patch through call with different channel types: local = TCH_F, remote = TCH_H

If I configure the BSC to have both TCH_H and TCH_F slots, my two test phones
try to call each other with mismatching TCH types. The CHANNEL REQUIRED
messages send TCH/H and TCH/F, respectively.

phones: Samsung S4 vs. Sony Ericsson SE K800i.

If the CN is configured with only TCH/H or only TCH/F, the two phones talk to
each other fine.

If one side started off in TCH/H, the other side should be urged towards
TCH/H as well. So we should "clamp" the callee to the caller's pchan type.


Related issues

Related to OsmoBTS - Feature #1776: Implement fully dynamic TCH/F + TCH/H + PDCH switchingClosedneels07/12/2016

Actions
Related to OsmoNITB - Bug #1663: don't connect channels of incompatible voice codecClosedmsuraev03/17/2016

Actions
Related to OsmoBTS - Bug #1865: TCH/F_PDCH is not working as TCH/F channel for CS voice call in USRP B210 board ( osmo-trx)Rejectedmrinal12/02/2016

Actions
Related to OpenBSC - Bug #1971: TCH/F_TCH/H_PDCH: BSC doesn't allocate TCH/FRejectedfixeria03/08/2017

Actions
Related to OsmoBSC - Feature #1606: hand-over for load distribution among BTSsResolvedneels02/23/2016

Actions
Related to OsmoBSC - Feature #1608: various handover improvements, meta-issueRejectedneels02/23/2016

Actions
Blocks OsmoBTS - Bug #1853: validate dynamic TCH/PDCH support in osmo-bts-trxResolvedpespin11/18/2016

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)