diff options
| author | Holger Hans Peter Freyther <zecke@selfish.org> | 2012-08-06 12:41:45 +0200 |
|---|---|---|
| committer | Holger Hans Peter Freyther <zecke@selfish.org> | 2012-08-06 12:41:45 +0200 |
| commit | b7b6cf5695e062a9bb4f00903ca1984bb73f2f34 (patch) | |
| tree | 53bce25755ec5ef5386ca7caefa61daeea21fba0 /openbsc/doc | |
| parent | f42e908cea678cf87fcd7b83469d694921021b33 (diff) | |
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')
| -rw-r--r-- | openbsc/doc/oml-interface.txt | 1 |
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 --- 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 |