Patch Set 1:
(1 comment)
https://gerrit.osmocom.org/#/c/6453/1/src/osmobts_sock.cpp
File src/osmobts_sock.cpp:
Line 288: osmo_timer_schedule(&state->timer, 5, 0);
> Do we actually need to wait 5 seconds now that we can reeschedule it in cas
Sure, we can change the timeout period.
Patch Set 1:
(1 comment)
https://gerrit.osmocom.org/#/c/6453/1/src/osmobts_sock.cpp
File src/osmobts_sock.cpp:
Line 288: osmo_timer_schedule(&state->timer, 5, 0);
Do we actually need to wait 5 seconds now that we can reeschedule it in case it
fails? we could this way speedup.
-
Harald Welte has submitted this change and it was merged.
Change subject: Make osmo-pcu wait for BTS to become available at start-up time.
..
Make osmo-pcu wait for BTS to become available at start-up time.
After the PCU socket
Patch Set 1: Code-Review+2
--
To view, visit https://gerrit.osmocom.org/6453
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: Ic42a5601a43b81d260721fef5d9fa52447f9d309
Gerrit-PatchSet: 1
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit
Review at https://gerrit.osmocom.org/6453
Make osmo-pcu wait for BTS to become available at start-up time.
After the PCU socket becomes available, the BTS might send an
INFO_IND message with the 'ACTIVE' flag cleared. If this happens,
do not exit immediately, but keep retrying until an INFO_IND
