Hi
Now I'm trying osmo-pcu on octasic-phy. GPRS worked, but I want to get EGPRS. I set 'gprs mode none' in openbsc.cfg and 'egprs only' in osmo-pcu.cfg. And got next error: "Not accepting non-EGPRS phone in EGPRS-only mode". As I found, it is like bug #3499. What does this error depend on and how can it be fixed? How can I test EGPRS?
Thanks, Andrey Lavrukhin
You've got to use 'gprs mode egprs' because 'none' means disable support for all kinds of packet data.
26.03.19 15:59, Andrey Lavrukhin пишет:
I set 'gprs mode none' in openbsc.cfg and 'egprs only' in osmo-pcu.cfg.
Hi.
I hadn't hit this error yet - which phone are you using?
Would be nice if you could update https://osmocom.org/issues/3499 with more details: config, packet traces, software version, log output etc.
Also, is there any particular reason you use OpenBSC and not OsmoBSC?
If it's only meant for PS setup than migration should be much simpler compared to Voice/SMS case.
Having said that, if the reason is indeed https://osmocom.org/issues/1525 than it might take a while until somebody allocates resources to fix it.
Nevertheless, having as much details as possible documented in the ticket increase the chances that the error gets reproduced and eventually fixed.
Hi Andrey,
in general, as Max stated, you have to use 'gprs mode egprs' if you want EGPRS.
OsmoPCU implements only either GPRS or EGPRS. So as soon as you activate EGPRS, you cannot use GPRS-only phones anymore. All your phones have to support EGPRS or will not be able to use PS services.
Free Software lives by contributions, and OsmoPCU is unfortunately not receiving many. Please feel free to join our project and help us with contributing the features that you need. Thanks :)
Regards, Harald
Hi
I'm using latest versions of osmo-pcu, osmo-bts, openbsc: osmo-pcu Change -Id: Ib39e4424f73c677b34f921917440f211e400e14f osmo-bts Change-Id: Id505594b9f224567566caac84dae2e2ae4477fae openbsc Change-Id: Id5678a74504b4456aba0438ccc34731770801128
Hardware: octasic OCTBTS3500, API version OCTSDR-2G-02.11.00-B1927-ALPHA. I'm using phones HTC Desire 601 and BlackBerry Z10. They both support EDGE.
As I see, in the osmo-bts/src/osmo-bts-octphy field rach_ind_param.burst_type is not modified anywhere. I tried to add next code to osmo-bts/src/osmo-bts-octphy/l1_if.c in function handle_ph_rach_ind:
@@ -1207,6 +1368,22 @@ static int handle_ph_rach_ind(struct octphy_hdl *fl1, else rach_ind_param.acc_delay = ra_ind->MeasurementInfo.sBurstTiming;
+LOGP( DL1C, LOGL_ERROR, "===> ra_ind->burstType=%u\n", ra_ind->ulBurstType ); + switch (ra_ind->ulBurstType) { + case cOCTVC1_GSM_BURST_TYPE_ENUM_ACCESS_TRAINING_0: + l1sap->u.rach_ind.burst_type = GSM_L1_BURST_TYPE_ACCESS_0; + break; + case cOCTVC1_GSM_BURST_TYPE_ENUM_ACCESS_TRAINING_1: + l1sap->u.rach_ind.burst_type = GSM_L1_BURST_TYPE_ACCESS_1; + break; + case cOCTVC1_GSM_BURST_TYPE_ENUM_ACCESS_TRAINING_2: + l1sap->u.rach_ind.burst_type = GSM_L1_BURST_TYPE_ACCESS_2; + break; + default: + l1sap->u.rach_ind.burst_type = GSM_L1_BURST_TYPE_NONE; + break; + } + /* msgb_trim() invalidates ra_ind, make that abundantly clear: */ ra_ind = NULL;
But PCU is logging only "===> ra_ind->burstType=0", i.e cOCTVC1_GSM_BURST_TYPE_ENUM_SYNC
чт, 28 мар. 2019 г. в 14:58, Harald Welte laforge@gnumonks.org:
Hi Andrey,
in general, as Max stated, you have to use 'gprs mode egprs' if you want EGPRS.
OsmoPCU implements only either GPRS or EGPRS. So as soon as you activate EGPRS, you cannot use GPRS-only phones anymore. All your phones have to support EGPRS or will not be able to use PS services.
Free Software lives by contributions, and OsmoPCU is unfortunately not receiving many. Please feel free to join our project and help us with contributing the features that you need. Thanks :)
Regards, Harald --
- Harald Welte laforge@gnumonks.org
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
osmocom-net-gprs@lists.osmocom.org
-
Andrey Lavrukhin -
Harald Welte -
Max