|author||Holger Hans Peter Freyther <firstname.lastname@example.org>||2012-08-06 12:41:45 +0200|
|committer||Holger Hans Peter Freyther <email@example.com>||2012-08-06 12:41:45 +0200|
doc: Document a shortcoming of the current OML code
The BTS has 10s to respond to a command but we do not run any timer. So it is possible that the BTS gets stuck in the process of the bring up.
Diffstat (limited to 'openbsc/doc')
1 files changed, 1 insertions, 0 deletions
diff --git a/openbsc/doc/oml-interface.txt b/openbsc/doc/oml-interface.txt
index 8ddcfea5c..02bead77a 100644
@@ -7,6 +7,7 @@ problems:
* therefore, we can have e.g. both the BSC and the OML interface send a
SET ATTRIBUTE message, where the responses would end up at the wrong
+* The BTS has 10s to ACK/NACK a command. We do not run any timers.
the only possible solutions i can imagine:
* have some kind of exclusive locking, where the OML interface gets blocked