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.
This commit is contained in:
Holger Hans Peter Freyther 2012-08-06 12:41:45 +02:00
parent f42e908cea
commit b7b6cf5695
1 changed files with 1 additions and 0 deletions

View File

@ -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