Bug #1865
closed
TCH/F_PDCH is not working as TCH/F channel for CS voice call in USRP B210 board ( osmo-trx)
Added by mrinal over 7 years ago.
Updated over 6 years ago.
Description
In old commit version TCH/F_PDCH was working fine as TCH/F as well as PDCH channel .We further checked the commit version using git bisect to find out the exact version from where this functionality is broken . Below is the commit version of BSC :
c3f72f63afde926dfc46827d6880055597515fb6
dyn TS: fix: ts_subslots() for TCH/F_PDCH in PDCH mode
Below failure logs observed when CS call is initiated using TCH/F_PDCH channel:
0004> bsc_init.c:288 bootstrapping RSL for BTS/TRX (0/2) on ARFCN 563 using MCC=901 MNC=60 LAC=1 CID=0 BSIC=63
<0000> chan_alloc.c:355 Failed to allocate TCH_F channel
<0004> abis_rsl.c:1755 BTS 0 CHAN RQD: no resources for TCH_F 0xee
<0000> chan_alloc.c:355 Failed to allocate TCH_H channel
<0004> abis_rsl.c:1755 BTS 0 CHAN RQD: no resources for TCH_H 0x4d
<0000> chan_alloc.c:355 Failed to allocate TCH_H channel
<0004> abis_rsl.c:1755 BTS 0 CHAN RQD: no resources for TCH_H 0x6a
Files
- Category set to osmo-bts-trx
for the record, here a response from Neels on the mailing list:
please be aware that TCH/F_PDCH is a pchan type that is designed for use with
ip.access nanoBTS exclusively. This BTS model understands a non-standard RSL
message to de-/activate PDCH ("PDCH Act"). Some of our other BTS software also
support this pchan kind: sysmoBTS, lc15 and osmo-bts-trx if I remember
correctly, but preferably use the pchan type TCH/F_TCH/H_PDCH in your osmo-bsc
or osmo-nitb config.
When you refer to a PS call, do you mean that GPRS service is used to place a
VoIP call? This is the same as saying that GPRS is functional.
There should be no significant difference in functionality concerning dynamic
timeslots (either kind) between master and commit 7bc6986f6ba, all commits that
"really matter" concerning dyn TS were already present in that revision.
Please verify your statements and/or accompany with log output,
and also try TCH/F_TCH/H_PDCH instead.
If the problem persists, please a) bisect to pinpoint the failing revision and
b) add full log output, preferably with DRSL and DNM logs set to debug level.
I verified that TCH/F_TCH/H_PDCH is functional on sysmobts with all the newest
commits just yesterday.
So my questions are: does the fully dynamic (osmocom style) TCH/F_TCH/H_PDCH work? The TCH/F_PDCH is intended
primarily for nanoBTS support, not for osmo-bts.
Yes TCH/F_TCH/H_PDCH works fine as TCH/H or as PDCH. But it does not work as TCH/F which means feature is not fully working.
Regarding TCH/F_PDCH even though it is not intended primarily for osmo-bts since the feature was working successfully earlier with osmo-bts and it was broken after the commit version I have mentioned in the issue description, I have raised this issue.
- Related to Bug #1853: validate dynamic TCH/PDCH support in osmo-bts-trx added
- Related to Feature #1778: avoid mismatching TCH/F vs TCH/H pchan types added
- Related to deleted (Bug #1853: validate dynamic TCH/PDCH support in osmo-bts-trx)
- Blocks Bug #1853: validate dynamic TCH/PDCH support in osmo-bts-trx added
I'm unable to reproduce this locally with latest master using attached configs - the voice call goes through just fine. Could you please share you configs, command-line args etc.
- Assignee changed from msuraev to mrinal
- Status changed from Feedback to Rejected
bug was unable to be reproduced and bug reporter did never respond to request for config files
Also available in: Atom
PDF
