This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Harald Welte laforge at gnumonks.orgHi Zecke, On Tue, Jun 22, 2010 at 05:43:05PM +0800, Holger Freyther wrote: > On 06/22/2010 09:27 AM, Holger Hans Peter Freyther wrote: > > On 06/22/2010 12:08 AM, Harald Welte wrote: > > > >> What needs to be done is to actually send the RSL CHAN ACT, save the state, > >> wait for the CHAN ACT ACK, then transmit the IMMEDIATE ASSIGN. > > > > I am going to do this for the assignment and immediate assignment > > commands.. today/now. > > I have implemented that, for the handover case and in the On-Waves > branch for early assignment, we already waited for the signal ack. ok, great news. > My understanding of GSM 08.58 so far is that it is taken for granted > that the BTS will always have a ACK/NACK for requests. With this in mind > I have not added an extra timer waiting for the CHANnel ACTivate > ACK/NACK. makes sense to me. > I am also storing the RACH req information inside the lchan > (as a pointer) and use the pointerz inside the CHAN ACT ACK handling to > decide if an immediate assignment should be send. sounds fine, too. Thanks! -- - Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)