Hello List,
I've noticed that In-Call Handover doesn't work on my Nokia InSites. OpenBSC attempts the handover but as far as I can tell the device never moves to the new channel. E.g.
<000d> handover_decision.c:203 (bts=2,trx=0,ts=1): Cell on ARFCN XXX is better: <000d> handover_logic.c:97 (old_lchan on BTS 2, new BTS 1) Starting handover <0004> abis_rsl.c:1059 (bts=1,trx=0,ts=1,ss=0) CHANNEL ACTIVATE ACK <000d> handover_logic.c:206 handover activate ack, send HO Command <0004> abis_rsl.c:1032 (bts=1,trx=0,ts=1,ss=0) HANDOVER DETECT access delay = 0 <0000> abis_rsl.c:1481 (bts=1,trx=0,ts=1,ss=0) SAPI=0 ESTABLISH INDICATION <0000> abis_rsl.c:1481 (bts=1,trx=0,ts=1,ss=0) SAPI=0 DATA INDICATION <0003> gsm_04_08.c:1196 HANDOVER COMPLETE cause = Normal event <000d> handover_logic.c:263 Subscriber AAABBBC00000ZZZZ HO from BTS 2->1 on ARFCN YYY->XXX <0000> chan_alloc.c:421 (bts=2,trx=0,ts=1,ss=0) starting release sequence
Here it seems to get measurement results, because the device is still on BTS2 (never moved?)
<0004> abis_rsl.c:967 (bts=2,trx=0,ts=1,ss=0): MEAS RES for inactive channel <0004> abis_rsl.c:967 (bts=2,trx=0,ts=1,ss=0): MEAS RES for inactive channel <0004> abis_rsl.c:967 (bts=2,trx=0,ts=1,ss=0): MEAS RES for inactive channel
After sometime things start to go crazy and the log fills up with messages like:
illegal trau (C1-C5) 00 00 01 01 00
Thanks, Gus
On Thu, Sep 01, 2011 at 11:17:07AM -0700, Gus Bourg wrote:
Hello List,
I've noticed that In-Call Handover doesn't work on my Nokia InSites. OpenBSC attempts the handover but as far as I can tell the device never moves to the new channel. E.g.
yes, there seem to be some problems, at least with nokia BTSs. We've seen them on the camp, too. Guess it needs to be re-tested with nanoBTS + BS-11 to see if it's a nokia specific or a generic problem.