Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-11-02T12:47:56ZOpen Source Mobile Communications
Redmine OsmoPCU - Bug #2611 (Closed): PCU does not properly handle TA adjustmenthttps://osmocom.org/issues/26112017-11-02T12:47:56Zmqng2
<p>MS can not establish TBF when it is moving away from BTS more than 2 km. This problem is causing by wrong TA adjustment requested by the PCU.</p>
<p>Below is the PCU traces to indicate that the PCU was wrongly set TA from 6 bits to 0 causing no TBF establishment for given MS.</p>
<p><0001> ../../git/src/pcu_l1_if.cpp:360 RACH request received: sapi=1 qta=24, ra=119, fn=786612<br /><0007> ../../git/src/gprs_rlcmac_meas.cpp:186 DL Bandwitdh of IMSI=901555000002022 / TLLI=0xf6342bc3: 2 KBits/s<br /><0009> ../../git/src/gprs_bssgp_pcu.cpp:183 LLC [SGSN -> PCU] = TLLI: 0xc949121b IMSI: 901555000002021 len: 62<br /><0007> ../../git/src/gprs_rlcmac_meas.cpp:104 UL RSSI of TLLI=0xc949121b: -94 dBm<br /><0007> ../../git/src/gprs_rlcmac_meas.cpp:159 DL packet loss of IMSI=901555000002022 / TLLI=0xf6342bc3: 0%<br /><0002> ../../git/src/bts.cpp:1426 MS supports EGPRS multislot class 10.<br /><strong><0001> ../../git/src/bts.cpp:1664 [PH-DATA] Updating TA 6 -> 0 on TRX = 0, TS = 7, FN = 786695</strong><br /><0009> ../../git/src/tbf_ul.cpp:388 LLC [PCU -> SGSN] <abbr title="TFI=1 TLLI=0xf6342bc3 DIR=UL STATE=FLOW EGPRS">TBF</abbr> len=62<br /><0009> ../../git/src/tbf_ul.cpp:388 LLC [PCU -> SGSN] <abbr title="TFI=2 TLLI=0xc949121b DIR=UL STATE=FLOW EGPRS">TBF</abbr> len=1510<br /><0009> ../../git/src/tbf_ul.cpp:388 LLC [PCU -> SGSN] <abbr title="TFI=3 TLLI=0xd14470ac DIR=UL STATE=FLOW EGPRS">TBF</abbr> len=81</p> OsmoBTS - Bug #2606 (Closed): LC15 BTS variant crashed with the FSM naming rules in latest libosm...https://osmocom.org/issues/26062017-10-31T20:16:16Zmqng2
<p>LC15 BTS variant built against the latest libosmocore (31/10/2017) crashed with DTX enabled for AMR codec configured in osmo-NITB.</p>
<p>Below is BTS log at the moment of the crash:</p>
<p>Tue Oct 31 20:05:45 2017 <0007> l1sap.c:1185 RACH for RR access (toa=0, ra=13)<br />Tue Oct 31 20:05:45 2017 <0000> rsl.c:3439 (bts=0,trx=0,ts=1,ss=0) Rx RSL CHAN_ACTIV<br />Tue Oct 31 20:05:45 2017 <0000> rsl.c:1202 chan_nr=0x41 type=0x00 mode=0x00<br />Tue Oct 31 20:05:45 2017 <0007> l1sap.c:1331 activating channel chan_nr=0x41 trx=0<br />Tue Oct 31 20:05:45 2017 <0007> l1sap.c:581 activate confirm chan_nr=0x41 trx=0<br />Tue Oct 31 20:05:45 2017 <0000> rsl.c:827 (bts=0,trx=0,ts=1,ss=0) Tx CHAN ACT ACK<br />Tue Oct 31 20:05:45 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=1,ss=0) MPH-CONFIG.conf (Configure ciphering params)<br />Tue Oct 31 20:05:45 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=1,ss=0) MPH-CONFIG.conf (Configure ciphering params)<br />Tue Oct 31 20:05:45 2017 <0000> rsl.c:3385 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD<br />Tue Oct 31 20:05:47 2017 <0000> rsl.c:3439 (bts=0,trx=0,ts=1,ss=0) Rx RSL DEACTIVATE_SACCH<br />Tue Oct 31 20:05:47 2017 <0007> l1sap.c:1387 deactivating sacch chan_nr=0x41 trx=0<br />Tue Oct 31 20:05:47 2017 <0000> rsl.c:3439 (bts=0,trx=0,ts=1,ss=0) Rx RSL RF_CHAN_REL<br />Tue Oct 31 20:05:47 2017 <0007> l1sap.c:1371 deactivating channel chan_nr=0x41 trx=0<br />Tue Oct 31 20:05:47 2017 <0007> l1sap.c:606 deactivate confirm chan_nr=0x41 trx=0<br />Tue Oct 31 20:05:47 2017 <0000> rsl.c:798 (bts=0,trx=0,ts=1,ss=0) Tx RF CHAN REL ACK<br />Tue Oct 31 20:05:48 2017 <0007> l1sap.c:1176 RACH for packet access (toa=0, ra=120)<br />Tue Oct 31 20:05:52 2017 <0007> l1sap.c:1185 RACH for RR access (toa=0, ra=69)<br />Tue Oct 31 20:05:52 2017 <0000> rsl.c:3439 (bts=0,trx=0,ts=2,ss=0) Rx RSL CHAN_ACTIV<br />Tue Oct 31 20:05:52 2017 <0000> rsl.c:1202 chan_nr=0x12 type=0x00 mode=0x00<br />Tue Oct 31 20:05:52 2017 <0007> l1sap.c:1331 activating channel chan_nr=0x12 trx=0<br />Tue Oct 31 20:05:52 2017 <0010> fsm.c:216 Attempting to allocate FSM instance of type 'DTX_DL_AMR_FSM' with illegal identifier '(bts=0,trx=0,ts=2,ss=0)'<br />Tue Oct 31 20:05:52 2017 <0007> l1sap.c:581 activate confirm chan_nr=0x12 trx=0<br />Tue Oct 31 20:05:52 2017 <0000> rsl.c:827 (bts=0,trx=0,ts=2,ss=0) Tx CHAN ACT ACK<br />Tue Oct 31 20:05:52 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=2,ss=0) MPH-CONFIG.conf (Configure ciphering params)<br />Tue Oct 31 20:05:52 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=2,ss=0) MPH-CONFIG.conf (Configure ciphering params)<br />Tue Oct 31 20:05:52 2017 <0000> rsl.c:3385 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:3439 (bts=0,trx=0,ts=2,ss=0) Rx RSL MODE_MODIFY_REQ<br />Tue Oct 31 20:05:53 2017 <0007> l1sap.c:1398 modifying channel chan_nr=0x12 trx=0<br />Tue Oct 31 20:05:53 2017 <0006> oml.c:1400 (bts=0,trx=0,ts=2,ss=0) MPH-CONFIG.req (TCH/H) cfgParams Tn=2, subCh=0, dir=0x2 amrCmiPhase=0x01 amrInitCodec=0x00 (3 0 0 0 )<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:1488 (bts=0,trx=0,ts=2,ss=0) Tx MODE MODIF ACK<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:3544 (bts=0,trx=0,ts=2,ss=0) Rx RSL IPAC_CRCX<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:1863 connect_ip 1059066028<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:1870 connect_port 12405<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:1877 speech mode: 21<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:1883 payload type: 98<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:1956 (bts=0,trx=0,ts=2,ss=0) IPAC set RTP socket parameters: 1<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:1693 (bts=0,trx=0,ts=2,ss=0) RSL Tx IPAC_CRCX_ACK (local 172.16.35.220:55696, remote 172.16.32.63:30000)<br />Tue Oct 31 20:05:53 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=2,ss=0) MPH-CONFIG.conf (Set logical channel params) amrCmiPhase=0x01 amrInitCodec=0x00 (3 0 0 0 )<br />Tue Oct 31 20:05:53 2017 <0006> oml.c:1400 (bts=0,trx=0,ts=2,ss=0) MPH-CONFIG.req (TCH/H) cfgParams Tn=2, subCh=0, dir=0x4 amrCmiPhase=0x01 amrInitCodec=0x00 (3 0 0 0 )<br />Tue Oct 31 20:05:53 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=2,ss=0) MPH-CONFIG.conf (Set logical channel params) amrCmiPhase=0x01 amrInitCodec=0x00 (3 0 0 0 )<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:3385 (bts=0,trx=0,ts=0,ss=0) Rx RSL PAGING_CMD<br />Tue Oct 31 20:05:53 2017 <0005> paging.c:213 Add paging to queue (group=18, queue_len=1)<br />Tue Oct 31 20:05:53 2017 <0007> l1sap.c:1185 RACH for RR access (toa=0, ra=44)<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:3439 (bts=0,trx=0,ts=2,ss=1) Rx RSL CHAN_ACTIV<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:1202 chan_nr=0x1a type=0x00 mode=0x00<br />Tue Oct 31 20:05:53 2017 <0007> l1sap.c:1331 activating channel chan_nr=0x1a trx=0<br /><strong>Tue Oct 31 20:05:53 2017 <0010> fsm.c:216 Attempting to allocate FSM instance of type 'DTX_DL_AMR_FSM' with illegal identifier '(bts=0,trx=0,ts=2,ss=1)'</strong><br />Tue Oct 31 20:05:53 2017 <0007> l1sap.c:581 activate confirm chan_nr=0x1a trx=0<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:827 (bts=0,trx=0,ts=2,ss=1) Tx CHAN ACT ACK<br />Tue Oct 31 20:05:53 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=2,ss=1) MPH-CONFIG.conf (Configure ciphering params)<br />Tue Oct 31 20:05:53 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=2,ss=1) MPH-CONFIG.conf (Configure ciphering params)<br />Tue Oct 31 20:05:53 2017 <0000> rsl.c:3385 (bts=0,trx=0,ts=0,ss=0) Rx RSL IMM_ASS_CMD<br />Tue Oct 31 20:05:54 2017 <0005> paging.c:512 Removed paging record, queue_len=0<br />Tue Oct 31 20:05:54 2017 <0000> rsl.c:3439 (bts=0,trx=0,ts=2,ss=1) Rx RSL MODE_MODIFY_REQ<br />Tue Oct 31 20:05:54 2017 <0007> l1sap.c:1398 modifying channel chan_nr=0x1a trx=0<br />Tue Oct 31 20:05:54 2017 <0006> oml.c:1400 (bts=0,trx=0,ts=2,ss=1) MPH-CONFIG.req (TCH/H) cfgParams Tn=2, subCh=1, dir=0x2 amrCmiPhase=0x01 amrInitCodec=0x00 (3 0 0 0 )<br />Tue Oct 31 20:05:54 2017 <0000> rsl.c:1488 (bts=0,trx=0,ts=2,ss=1) Tx MODE MODIF ACK<br />Tue Oct 31 20:05:54 2017 <0000> rsl.c:3544 (bts=0,trx=0,ts=2,ss=1) Rx RSL IPAC_CRCX<br />Tue Oct 31 20:05:54 2017 <0000> rsl.c:1863 connect_ip 1059066028<br />Tue Oct 31 20:05:54 2017 <0000> rsl.c:1870 connect_port 12405<br />Tue Oct 31 20:05:54 2017 <0000> rsl.c:1877 speech mode: 21<br />Tue Oct 31 20:05:54 2017 <0000> rsl.c:1883 payload type: 98<br />Tue Oct 31 20:05:54 2017 <0000> rsl.c:1956 (bts=0,trx=0,ts=2,ss=1) IPAC set RTP socket parameters: 1<br />Tue Oct 31 20:05:54 2017 <0000> rsl.c:1693 (bts=0,trx=0,ts=2,ss=1) RSL Tx IPAC_CRCX_ACK (local 172.16.35.220:36310, remote 172.16.32.63:30000)<br />Tue Oct 31 20:05:54 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=2,ss=1) MPH-CONFIG.conf (Set logical channel params) amrCmiPhase=0x01 amrInitCodec=0x00 (3 0 0 0 )<br />Tue Oct 31 20:05:54 2017 <0006> oml.c:1400 (bts=0,trx=0,ts=2,ss=1) MPH-CONFIG.req (TCH/H) cfgParams Tn=2, subCh=1, dir=0x4 amrCmiPhase=0x01 amrInitCodec=0x00 (3 0 0 0 )<br />Tue Oct 31 20:05:54 2017 <0006> oml.c:1316 (bts=0,trx=0,ts=2,ss=1) MPH-CONFIG.conf (Set logical channel params) amrCmiPhase=0x01 amrInitCodec=0x00 (3 0 0 0 )<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:3544 (bts=0,trx=0,ts=2,ss=1) Rx RSL IPAC_MDCX<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1863 connect_ip 1059066028<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1870 connect_port 13429<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1877 speech mode: 5<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1883 payload type: 98<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1693 (bts=0,trx=0,ts=2,ss=1) RSL Tx IPAC_MDCX_ACK (local 172.16.35.220:36310, remote 172.16.32.63:30004)<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:3544 (bts=0,trx=0,ts=2,ss=0) Rx RSL IPAC_MDCX<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1863 connect_ip 1059066028<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1870 connect_port 12917<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1877 speech mode: 5<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1883 payload type: 98<br />Tue Oct 31 20:05:59 2017 <0000> rsl.c:1693 (bts=0,trx=0,ts=2,ss=0) RSL Tx IPAC_MDCX_ACK (local 172.16.35.220:55696, remote 172.16.32.63:30002)</p>
<p>Program received signal SIGSEGV, Segmentation fault.<br />0x0003b3ac in dtx_dl_amr_fsm_step (lchan=lchan@entry=0xb6bbdc50, rtp_pl=rtp_pl@entry=0xf8040 " \024\351Y\363_\337\345\351f\177\373\300\210\201\200\210",<br /> rtp_pl_len=17, fn=48005, l1_payload=0xf8225 "", marker=marker@entry=true, len=len@entry=0xf82c4 "\024", ft_out=0xbefff7d7 "\002\002",<br /> ft_out@entry=0xbefff7cf "\276\205\273") at msg_utils.c:233<br />233 msg_utils.c: No such file or directory.<br />(gdb)<br />(gdb)</p>
<p>It looks like lchan->name containing illegal characters passed to osmo_fsm_inst_alloc in l1sap_chan_act of l1sap.c cause the issue</p>
<pre><code>/* Init DTX DL FSM if necessary */<br /> if (trx->bts->dtxd && lchan->type != GSM_LCHAN_SDCCH)<br /> lchan->tch.dtx.dl_amr_fsm = osmo_fsm_inst_alloc(&dtx_dl_amr_fsm,<br /> tall_bts_ctx,<br /> lchan,<br /> LOGL_DEBUG,<br /> lchan->name);</code></pre>
<pre><code>This issue does not appear with DTX disabled.</code></pre> OsmoPCU - Bug #2455 (Closed): MS will not be able to use data service if we let the MS idle about...https://osmocom.org/issues/24552017-08-21T13:50:06Zmqng2
<p>I have seen an issue with the Lenovo A916 smartphone when using osmo-pcu from HEAD of master branch (37e4c43a8d9a9b5e64a7dd19c5877d302b7887ac) in LC15 target.</p>
<p>If the phone does not use Internet right after PDP context ACT, the phone will be unable to use the Internet. It is also applied in case the phone waits for an amount of time after a first Web page loaded 100%</p>
<p>The PCU onfiguration is in below text:</p>
<p>Osmo-PCU#<br />Osmo-PCU# show running-config</p>
<p>Current configuration:<br />!<br />!<br />log stderr<br /> logging filter all 1<br /> logging color 1<br /> logging print category 0<br /> logging timestamp 0<br /> logging level all everything<br /> logging level csn1 info<br /> logging level l1if info<br /> logging level rlcmac info<br /> logging level rlcmacdata notice<br /> logging level rlcmacdl info<br /> logging level rlcmacul debug<br /> logging level rlcmacsched info<br /> logging level rlcmacmeas info<br /> logging level ns info<br /> logging level bssgp info<br /> logging level pcu info<br /> logging level lglobal notice<br /> logging level llapd notice<br /> logging level linp notice<br /> logging level lmux notice<br /> logging level lmi notice<br /> logging level lmib notice<br /> logging level lsms notice<br /> logging level lctrl notice<br /> logging level lgtp notice<br /> logging level lstats notice<br /> logging level lgsup notice<br /> logging level loap notice<br /> logging level lss7 notice<br /> logging level lsccp notice<br /> logging level lsua notice<br /> logging level lm3ua notice<br /> logging level lmgcp notice<br />!<br />stats interval 5<br />!<br />line vty<br /> no login<br />!<br />ns<br /> timer tns-block 3<br /> timer tns-block-retries 3<br /> timer tns-reset 3<br /> timer tns-reset-retries 3<br /> timer tns-test 30<br /> timer tns-alive 3<br /> timer tns-alive-retries 10<br /> encapsulation udp local-port 23001<br /> encapsulation framerelay-gre enabled 0<br />pcu<br /> egprs only<br /> flow-control-interval 10<br /> flow-control force-bvc-bucket-size 596000<br /> flow-control force-bvc-leak-rate 59600<br /> flow-control force-ms-bucket-size 596000<br /> flow-control force-ms-leak-rate 59600<br /> cs 4<br /> cs max 4<br /> no cs threshold<br /> no cs downgrade-threshold<br /> cs link-quality-ranges cs1 6 cs2 5 8 cs3 7 13 cs4 12<br /> mcs link-quality-ranges mcs1 6 mcs2 5 8 mcs3 7 13 mcs4 12 15 mcs5 14 17 mcs6 16 18 mcs7 17 20 mcs8 19 24 mcs9 23<br /> mcs 9<br /> mcs max 9<br /> window-size 64 104<br /> queue lifetime infinite<br /> queue idle-ack-delay 10<br /> no queue codel<br /> alloc-algorithm b<br /> two-phase-access<br /> alpha 0<br /> gamma 0<br /> dl-tbf-idle-time 2000<br />end<br />Osmo-PCU#</p>
<p>I have also attached pcap and pcu log with activated debug flags for BSSGP, RLCMAC, RLCMACDL and RLCMACUL for investigation.</p> OsmoBTS - Bug #2014 (Closed): LC15: BTS does not properly handle BS-AG-BLKS-REShttps://osmocom.org/issues/20142017-04-18T19:52:49Zmqng2
<p>I have noticed that after changing BS-AG-BLKS-RES configuration from 1 to 2 or 3 from Osmo-NITB. The DSP starts to complain about unexpected burst as shown below.</p>
<p>[ERROR] : GsmL1_PhDataReq() : Unexpected burst (Invalid sapi) [Sapi = 6, Expected = 7]<br />[ERROR] : GsmL1_PhDataReq() : Unexpected burst (Invalid sapi) [Sapi = 6, Expected = 7]<br />[ERROR] : GsmL1_PhDataReq() : Unexpected burst (Invalid sapi) [Sapi = 6, Expected = 7]<br />[ERROR] : GsmL1_PhDataReq() : Unexpected burst (Invalid sapi) [Sapi = 6, Expected = 7]<br />[ERROR] : GsmL1_PhDataReq() : Unexpected burst (Invalid sapi) [Sapi = 6, Expected = 7]</p>
<p>Looking at ph_date_req function in src/osmo-bts-litecell15/l1_if.c, one can clearly see that the BTS always uses B0 for AGCH SAPI (line 392) leading to the DSP complaints about wrong SAPI for AGCH.</p>
<p>According to GSM 05.02, Section 7 Table 5 of 5, the number of blocks used AGCH must change according to BS-AG-BLKS-RES requested from BSC.</p> OsmoBTS - Bug #1950 (Resolved): LC15: BTS does not send L2 fill framehttps://osmocom.org/issues/19502017-02-13T15:36:21Zmqng2
<p>We have noticed that the LC15 BTS does not send L2 fill frame in case there is nothing to transmit.<br />This leads to bad RXQUAL repored by MS during signaling in TCH channel. Please refer to GSM 05.08, section 8.3</p>
<p>"On any TCH this subset of TDMA frames is always used for transmission during DTX. For speech, when<br />no signalling or speech is to be transmitted these TDMA frames are occupied by the SID (Silence<br />Descriptor) speech frame, see TS GSM 06.12 and TSM GSM 06.31 for detailed specification of the SID<br />frame and its transmission requirements. In other cases when no information is required to be transmitted,<br />e.g. on data channels, the L2 fill frame (see GSM 04.06 section 5.4.2.3) shall be transmitted as a FACCH<br />in the TDMA frame subset always to be transmitted.</p>
<p>On the SDCCH and on the half rate speech traffic channel in signalling only mode DTX is not allowed. In<br />these cases and during signalling on the TCH when DTX is not used, the same L2 fill frame shall be<br />transmitted in case there is nothing else to transmit."</p> OsmoBTS - Bug #1839 (Closed): LC15: BTS failed to send LAPDm UA command to MS after receiving LAP...https://osmocom.org/issues/18392016-11-09T19:08:55Zmqng2
<p>We are facing an issue with MOC with a Motorola Rarz phone. This phone is time to time failed to establish the call if we perform fast successive MOC from this phone.</p>
<p>We have built a special version of DSP to trace all LADPm messages between L1 and L2. When the MO terminates the call, the BTS does not send L2 LAPDm UA message to the L1 after receiving LAPDm DISC from the MS.</p>
<p>Looking at “lapd_core.c” in libosmocore, we have seen that there is an L2 LAPDm UA message supposed to be sent to L1 but it has never sent to the L1 for unknown reason.</p>
<p>We did a small test by commented out “l1sap_chan_rel(lchan->ts->trx, chan_nr);” line in function rsl_rx_rf_chan_rel in osmo-bts/src/common/rsl.c. We observed that the BTS sent out the UA as expected.</p>
<p>It looks like the BTS releases the RF channel too fast preventing the BTS to send the pending LAPDm UA messagge in Tx queue.</p> libosmo-abis - Bug #1785 (Closed): RTP network errorhttps://osmocom.org/issues/17852016-07-28T19:37:55Zmqng2
<p>I got RTP network error in BTS log starting from commit 8c119f7a0510b75e7fa1b96a37f2a6650e13824f. This leads to no voice at both MS. <br />The only way to have voice in both MS is to revert this commit.</p> OsmoPCU - Bug #1775 (Resolved): LC15: No PDCH allocation across two TRXhttps://osmocom.org/issues/17752016-07-12T11:50:27Zmqng2
<p>I am currently testing GPRS with PDCH configuration across two TRX, i.e. TS3 - TS7 are configured as PDCH in TRX0, TS0-TS3 are configured as PDCH in TRX1. <br />Two MS are used for surfing the Web. I have noticed that the both MS always use TS3-TS7 of the TRX0 for DL TBF, they never use TS0-TS3 of the TRX1 for DL TBF.</p>
<p>Is it the limitation of the multi-TRX PCU implementation?</p>
<p>FYI: If I configure TS0-TS7 as PDCH in the TRX1, 8 PDCH will be used for both MS (4 PDCH of DL TBF each MS)</p>