From b7b6cf5695e062a9bb4f00903ca1984bb73f2f34 Mon Sep 17 00:00:00 2001 From: Holger Hans Peter Freyther Date: Mon, 6 Aug 2012 12:41:45 +0200 Subject: 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. --- openbsc/doc/oml-interface.txt | 1 + 1 file changed, 1 insertion(+) (limited to 'openbsc/doc') diff --git a/openbsc/doc/oml-interface.txt b/openbsc/doc/oml-interface.txt index 8ddcfea5c..02bead77a 100644 --- a/openbsc/doc/oml-interface.txt +++ b/openbsc/doc/oml-interface.txt @@ -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 query. +* 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 -- cgit v1.2.3